I am currently working on our first Windows 10 build for XenDesktop with AppSense EM. I have a new image built with Windows 10 1709 and everything is working as expected up to the point of installing EM. I have the deployment agent installed and connected to our management server, and it successfully deploys the software, but once rebooted, Microsoft Edge hangs and crashes with multiple DCOM errors in the event logs. Upon uninstalling EM and rebooting again, Edge returns to normal functionality. Trying to determine if this is a known issue or what might be causing this behavior as Edge is heavily used in our environment. Any insight or advice is appreciated.
1 of 1 people found this helpful
This issue was discovered to be an issue relating to the Control Flow Guard within the Windows 10 Creator's Update, as mentioned in the following post:
In our case, the solution was to add additional exceptions for MicrosoftEdge.exe and MicrosoftEdgeCP.exe to the AsModLdr driver hook for AppSense. Once the exceptions were in place, Microsoft Edge began working normally for all users and workflows, and persisted after rebooting. As a side note, it appears that this issue was causing the Environment Manager policy to not fully apply, as certain actions which were thought to not be working, began working as expected following the fix for Edge.
Here's hoping this helps in some of your deployments!
I have the same issues with Win 10 build 1709 and we did not have the problem with 1607. I have tried adding the .exe's to the exceptions and that is now working. Just cant personalize edge now so that stinks. Did you do anything else?
I have not had to take any further actions, however, we utilize XenDesktop, AppSense, and Edge in a primarily non-persistent clinical environment with very little need to personalize Edge.
Now seeing similar isssues to IE11 on 1709.