We encountered a strange issue on the Windows Server 2016 Remote Desktop Session Host (RDSH) used for VMware Horizon Application Publishing. The Internet Explorer would launch and get into “Not Responding” state, and eventually, the process would close out without any errors.
IE Opening and Crashing
Process of elimination
We thought either Windows cumulative updates introduced the issue as it was working fine earlier.
There were no errors in the Windows Event Viewer (Application, System or Internet Explorer)
We used the Deployment Image Servicing and Management (DISM) command line tool to disable/enabled Internet Explorer without any luck.
Procmon is showing IE tries to launch the process multiple times, but the sub-process keep failing, and IE finally gives up at the end
IE Process launching multiple times
We were running out of troubleshooting ideas
Resolution
My team ended up opening a Microsoft Support case, and they could see that “Name Not Found for the ieproxy.dll” which is due to ieproxy.dll registration issues. Support confirmed they had seen similar instances in the past.
Please open command prompt with Admin rights and re-register the dll from System32 and Syswow64 folders.
%SystemRoot%\System32\regsvr32 ieproxy.dll
%SystemRoot%\Syswow64\regsvr32 ieproxy.dll
I hope you will find this information useful if you encounter the issue. If you manage to tweak or improvise further on this solution, please don’t forget to keep me posted.
The AppX package for (Calc, Photos and Edge) did exist in the base operating system
We can launch all the three applications within the optimized golden image template.
We were running the VMWare OSOT tool with the default VMware Windows 10 template. No additional customization or options selected.
One thing was evident the base template was working fine. The suspicion was around AppStack – App Volumes (We disabled the AppStacks/Writable Delivery – Same issue observed) or Dynamic Environment Manager causing the application from launching
We selected to put the Powershell script within the UEM Share as the end-users have the read- access.
DEM-LogonTasks
Quick Update based on 4th Aug 2021 (Thanks to Curtis for bring this up in the comments section)
The above DEM 9.10 logon task no longer works in situation where end-users dont have local administrative priviledges users not being able to run the script at logon.
In the latest version of Dynamic Enivornment Manager 20XX onwards, you can now hook logon tasks into Elevated Tasks by using Privilege Elevation rules.
In DEM:
1. User Environment > Privilege Elevation > Create new privilege elevation rule
2. In the “Type” drop down menu, select “Elevated Task”
3. Click “Add”
4. In the Executable field: “C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe”
5. In the Arguments field type the path to your script logon script
6. In User Environment > Logon Tasks, select the logon task that runs and registers the UWP apps.
7. Check “Elevated Task” and in the drop down select the Elevated Task you just created in the list.
After this, the script should be able to run at logon regardless of whether or not the user has local administrator rights!
I hope you will find this information useful if you encounter the issue. If you manage to tweak or improvise further on this solution, please don’t forget to keep me posted.
Recent Comments