none
Microsoft Edge does not work after upgrading to Creator Update 1703

    Question

  • Microsoft Edge does not open after upgrading to Creator Update 1703. I get these two event id errors:

    Event ID 5990 -

    Activation via contract helper of the app Microsoft.MicrosoftEdge_8wekyb3d8bbwe!ContentProcess for the Windows.ComponentUI contract failed with The remote procedure call failed..

    Event ID 5961 -

    Activation of the app Microsoft.MicrosoftEdge_8wekyb3d8bbwe!ContentProcess for the Windows.ComponentUI contract failed with error: The remote procedure call failed..

    Its a Surface 4 running in a Domain environment.  Had no issues prior to upgrading to Creator Update 1703.

    Sunday, April 16, 2017 5:27 PM

Answers

  • the issue is having PaloAlto Traps 3.4.3 running on my surface.  once I removed it, it worked fine.
    • Marked as answer by Noe.O Monday, April 17, 2017 6:00 PM
    Monday, April 17, 2017 6:00 PM

All replies

  • Try reregistering Edge with PowerShell. Copy and paste into a PowerShell prompt;

    Get-AppXPackage -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" -Verbose}

    See if that helps.

    Sunday, April 16, 2017 7:11 PM
  • Hello,

    Try creating new user account and see it Edge works on that.

    Regards.

    Microsoft MVP (Windows and Devices for IT)

    Windows Insider MVP

    Windows Help & Support [www.kapilarya.com]

    Monday, April 17, 2017 10:23 AM
  • Tried both the Powershell script and creating a new local account (admin rights).  Microsoft Edge still does not open. 

    Anything else I should try, please let me know.

    thanks

    Monday, April 17, 2017 3:14 PM
  • Hmm ok. Edge is part of the system, so try from an Admin Command Prompt;

    sfc /scannow

    Will take 30mins or so to run. See if that helps.

    Monday, April 17, 2017 3:19 PM
  • ran that a couple of times in admin mode and every time it came out clean
    Monday, April 17, 2017 4:51 PM
  • when Edge tries to open, I get this in the URL section:

    ms-appx-web:///assets/errorpages/acr_error.htm#https://go.microsoft.com/fwlink/?LinkId=746405

    It then closes.

    not sure if this helps.

    Monday, April 17, 2017 5:03 PM
  • Well the fwlink goes to the Edge tips page the standard page it opens after the update. Not quite sure what has gone wrong here.

    From a command line;

    start microsoft-edge:http://www.microsoft.com

    Does that open Edge to MS's homepage?

    Did you \ do you other browsers installed? Thinking it might be the default application settings. What Settings > Apps then Default Apps show for Web browser show? Does the Reset option there help? 

    Monday, April 17, 2017 5:20 PM
  • here is another entry in Eventviewer

    event ID:  1000

    Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.15063.0, time stamp: 0x58ccbae4

    Faulting module name: ntdll.dll, version: 10.0.15063.0, time stamp: 0xb79b6ddb

    Exception code: 0xc000041d

    Fault offset: 0x0000000000004b90

    Faulting process id: 0x31f4

    Faulting application start time: 0x01d2b79c396940d1

    Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe

    Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

    Report Id: e22b7183-f1ea-4f62-b3dd-2f80c6aed76b

    Faulting package full name: Microsoft.MicrosoftEdge_40.15063.0.0_neutral__8wekyb3d8bbwe

    Faulting package-relative application ID: ContentProcess

    Monday, April 17, 2017 5:22 PM
  • the issue is having PaloAlto Traps 3.4.3 running on my surface.  once I removed it, it worked fine.
    • Marked as answer by Noe.O Monday, April 17, 2017 6:00 PM
    Monday, April 17, 2017 6:00 PM
  • Cool glad you solved it thanks for lettings us know.
    Monday, April 17, 2017 6:41 PM
  • This was also the issue with Traps 4.0. Uninstalling fixed the problem.

    I would imagine that if others have an issue with the same symptoms (but they don't have Traps), then I would try a clean boot and disable any security software they might have, eg., Bitdefender, Esset, etc., 

    ....


    • Edited by SirVoltron Wednesday, May 31, 2017 7:16 PM
    • Proposed as answer by SirVoltron Wednesday, May 31, 2017 9:15 PM
    • Unproposed as answer by SirVoltron Wednesday, May 31, 2017 10:05 PM
    Wednesday, May 31, 2017 7:15 PM
  • So if Traps was your issue, they (Palo Alto) have a content update that you can download and apply. One was released not too long ago that will fix the problem with Traps on versions 3.4 and above. We were only a few months behind and downloading the current content update fixed the problem.
    • Proposed as answer by OwenITGuy Thursday, July 6, 2017 3:22 PM
    Wednesday, May 31, 2017 9:24 PM
  • The User profile of the 1703 Creator Update is like the 1607 anniversary update still a Version 6 profile (username.V6). I had to recreate alot of user domain profiles after the automatic update from 1607 to 1703. The domain user profiles got corrupted during the 1703 update.

    Tuesday, June 6, 2017 9:09 AM
  • I found same issue on build 15063.0 with Traps 3.4.1. 

    As soon as uninstalled traps agent Edge would function fine.

    Thursday, June 22, 2017 7:11 AM
  • the issue is having PaloAlto Traps 3.4.3 running on my surface.  once I removed it, it worked fine.
    Been working for over an hour on this issue. Malwarebytes Anti-Malware was the problem for me in case anyone else is running this product. Opening a ticket with them to see if they can fix the issue.
    Thursday, July 6, 2017 2:37 PM
  • Thanks, this post helped me solve the same problem in about five minutes!
    Thursday, July 6, 2017 3:21 PM
  • Thanks, this post helped me solve the same problem in about five minutes!

    Hi OwenITGuy,

    Which Post solved your issue?

    Wednesday, July 12, 2017 4:38 PM
  • when Edge tries to open, I get this in the URL section:

    ms-appx-web:///assets/errorpages/acr_error.htm#https://go.microsoft.com/fwlink/?LinkId=746405

    It then closes.

    not sure if this helps.

    I get the same thing... this has happened on many PCs whether an upgrade to 1703 or clean installs to 1703, Edge works for a while then stops, opens, you see that URL and it closes, same errors in the Event Log... It's not profile related as I have created different profiles to prove this. It's system wide.
    Wednesday, July 12, 2017 4:41 PM
  • It works for me.
    Friday, July 14, 2017 9:10 PM