The Issues raised in this Blog post are now available as individual articles within the Ivanti Community.
Be aware that this Blog will not be updated and that customers are advised to search for the Creators Update tag to view all related articles.
On 11th April, Microsoft released their latest Windows 10 feature update “Creators Update” 1703 build. As with all Windows 10 updates this is initially a Current Branch release, aimed at the consumer market.
Under the Windows as a Service program it is expected that this build will become Current Branch for Business within the next 4 months.
We have discovered the following issues when using DesktopNow with the latest 15063 build of Creators Update:
Environment Manager (10.1)
fontdrvhost.exe crash with EM Agent installed on Windows 10 Creators Update* Updated
MicrosoftEdge.exe and MicrosoftEdgeCP.exe crashes on Win 10 Creators Update when EM Agent is installed* Updated
Application Control (10.1)
The Start Menu is not selectable when blocking all Windows Store Apps using AC on the Win 10 Creators Update
fontdrvhost.exe crash with AC Agent installed on Windows 10 Creators Update* Updated
MicrosoftEdge.exe and MicrosoftEdgeCP.exe crashes on Win 10 Creators Update when AC Agent is installed* Updated
Updated *The listed application issues can be resolved by updating the AsModLdr Exclusions list on the Endpoint with either the EM or AM Agent installed to the AsModLdr Driver Exclusions list.
- MicrosoftEdgeCP.exe (for the Edge crash, just this executable is required)
The graphic above displays the EM registry setting, the path for the AM entry is :
After investigation it was found that both the listed processes contain additional security enhancements for Control Flow Guard within the Windows 10 Creators Update. Customers are advised to add the recommended exclusion update for both applications.
This could be implemented either via EM Policy, updated Gold Build or script. A reboot is recommended after applying.
Both of these processes will be added to the default exclusion list in a future release.
We will update this document as more information becomes available, be advised that we are actively working on fixes and workarounds for these issues.
New As updated above, the issues stated were found within the 10.1 agent versions, however previous Windows 10 compatible versions would experience similar symptoms.