Edge Broken After 1703 Creators Update Upgrade

Issue #14004473 • Assigned to Steven K.

Details

Author
John M.
Created
Sep 29, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Using a ConfigMgr (1706) Task Sequence to deploy a W10 1703 Creators Update Upgrade Package (Build 15063.632) to my test clients.

Edge works fine prior to the upgrade but immediately after it is broken. Specifically, i get 4 x pop up error boxes with “Microsoft.MicrosoftEdge_8wekyb3d8bb… has stopped working” when Edge is launched after the Task Sequence has completed.

Event viewer entries include…

“Activation of application Microsoft.MicrosoftEdge_8wekyb3d8bbwe!ContentProcess failed with error: The app didn’t start. See the Microsoft-Windows-TWinUI/Operational log for additional information.”

and…

“The server Microsoft.MicrosoftEdge40.15063.0.0_neutral_8wekyb3d8bbwe!ContentProcess did not register with DCOM within the required timeout.”

and…

“Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.15063.608, time stamp: 0x59ae240c Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x8274fd8b Exception code: 0xc0000409 Fault offset: 0x00000000000aa020 Faulting process ID: 0x2188 Faulting application start time: 0x01d33909d1bf0a56 Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge8wekyb3d8bbwe\MicrosoftEdgeCP.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report ID: 501b408f-ff3e-4d8c-8392-99614b8e7af5 Faulting package full name: Microsoft.MicrosoftEdge_40.15063.0.0_neutral_8wekyb3d8bbwe Faulting package-relative application ID: ContentProcess”

and…

“Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.15063.608, time stamp: 0x59ae240c Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x8274fd8b Exception code: 0xc0000409 Fault offset: 0x00000000000aa020 Faulting process ID: 0x2fdc Faulting application start time: 0x01d33909db4b40f6 Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge8wekyb3d8bbwe\MicrosoftEdgeCP.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report ID: 5734478e-5a89-44e4-8046-a3cff3859209 Faulting package full name: Microsoft.MicrosoftEdge_40.15063.0.0_neutral_8wekyb3d8bbwe Faulting package-relative application ID: ContentProcess”

I’m interested in a manual fix short term so i can at least roll this out to our pilot users but more interested in the root cause & permanent resolution. Trying to deploy this upgrade across the estate but cannot due to this.

Looks like a lot of people having similar issues as i’ve trawled through every forum & hacked my way though every resolution to no avail.

Are you able to assist?

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

    • Hi John,

      Yes, we can help you with this issue.  I would like to see if you are experiencing a known issue that user’s have been reporting.  Will you look at the following issue and let me know if you are having that issue?

      https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/13779603/

      I recommend you run the following in an admin powershell to verify this is the issue you are experiencing, I.e. run this before reviewing the above link.

      Get-Acl HKLM:\System\CurrentControlSet\Services\Tcpip\Parameters | Format-List

      You are having the issue that the script in the bug report linked above will correct if you DO NOT have the following entries in the output of the Get-Act command.

      APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES Allow  ReadKey
      APPLICATION PACKAGE AUTHORITY\Your Internet connection Allow  ReadKey
      APPLICATION PACKAGE AUTHORITY\Your Internet connection, including incoming connections from the Internet

      Let me know and if the above is not your issue, we can debug further.

      Steve

    • Hi Steven K,

      Powershell output from machine with broken Edge as follows…

      PS C:\WINDOWS\system32> Get-Acl HKLM:\System\CurrentControlSet\Services\Tcpip\Parameters | Format-List

      Path : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
      Owner : NT AUTHORITY\SYSTEM
      Group : NT AUTHORITY\SYSTEM
      Access : OWNER RIGHTS Allow ReadPermissions
      NT AUTHORITY\SYSTEM Allow FullControl
      NT AUTHORITY\LOCAL SERVICE Allow ReadKey
      NT AUTHORITY\NETWORK SERVICE Allow SetValue, CreateSubKey, CreateLink, Delete, ReadKey
      BUILTIN\Administrators Allow FullControl
      BUILTIN\Users Allow ReadKey
      BUILTIN\Network Configuration Operators Allow SetValue, CreateSubKey, Delete, ReadKey
      NT SERVICE\Dhcp Allow SetValue, CreateSubKey, Delete, ReadKey
      NT SERVICE\WwanSvc Allow SetValue, CreateSubKey, ReadKey
      APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES Allow ReadKey
      APPLICATION PACKAGE AUTHORITY\Your Internet connection Allow ReadKey
      APPLICATION PACKAGE AUTHORITY\Your Internet connection, including incoming connections from the Internet
      Allow ReadKey
      APPLICATION PACKAGE AUTHORITY\Your home or work networks Allow ReadKey
      S-1-15-3-4214768333-1334025770-122408079-3919188833 Allow ReadKey
      Audit :
      Sddl : O:SYG:SYD:PAI(A;CIIO;RC;;;OW)(A;CI;KA;;;SY)(A;CI;KR;;;LS)(A;CI;CCDCLCSWRPWPSDRC;;;NS)(A;CI;KA;;;BA)(A;CI;KR;;;
      BU)(A;CI;CCDCLCSWRPSDRC;;;NO)(A;CI;CCDCLCSWRPSDRC;;;S-1-5-80-2940520708-3855866260-481812779-327648279-1710889
      582)(A;CI;CCDCLCSWRPRC;;;S-1-5-80-3981856537-581775623-1136376035-2066872258-409572886)(A;CI;KR;;;AC)(A;CI;KR;
      ;;S-1-15-3-1)(A;CI;KR;;;S-1-15-3-2)(A;CI;KR;;;S-1-15-3-3)(A;CI;KR;;;S-1-15-3-4214768333-1334025770-122408079-3
      919188833)

      Please advise.

      thanks
      john

    • Hi Steven K,

      Any updates on this?

      thanks
      john

    • Looking for some feedback on this if possible?

    • anyone?

    • Anyone have a status update?

    • Hi John,

      I was also suffering from 0xc0000409 in ntdll.dll per my posts over at the other thread, as soon as 1703 was applied (whether new build or in place upgrade TS).

      I can only recommend you start stripping out 3rd party software to try and narrow down where the problem is, as for us it was our user virtualization software which needed an exception adding to it’s driver so it didn’t attempt to hook into Edge (and also another process), after 1703 introduced Control Flow Guard security changes.

    • Hi Chris M.

      Your post set me off on a path that lead me to the resolution. AppSense’s parent company is Ivanti. We deploy an Ivanti Endpoint Device Control client to our workstations.

      Once i upgraded the HEAT agent/device control client from v8.3 to the latest (v8.5) Edge works again!

      I had previously brushed this aside as the root cause as their (out-of-date) documentation states that W10 is supported, upon contacting their support, turn out that v8.5 is required for W10 1703 Creators Upgrade

      Thanks!

    You need to sign in to your Microsoft account to add a comment.

    Sign in