Edge fails to navigate or display any tabs and then crashes after 30+ seconds

Confirmed Issue #11975881

Details

Author
Matthew H.
Created
May 11, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
15.15063
Reports
Reported by 10 people

Sign in to watch or report this issue.

Steps to reproduce

This bug has been proposed as engineering blocking

      by          REL Bug Service
     on  flight (Windows.Desktop) 10.0.16232.*.rs_prerelease. Fixing the bug helps Windows build achieve the goal of this reliability measure - The % of Machines with Good MTTF. The reliability measure on the flight is 64.91 % and goal is 70 %. Fixing this bug could improve the measure by 0.02 %.         


        -- start: Promo Info --            Why this bug is important?

We have identified that this bug was promoted based on telemetry data and affects following products failure 07eecc43-b515-eb9a-5eb0-89e266d3a773 impacts Product

                          Predictive metrics        
                              ([#126 on curve](https://insights/Report?id=cee3bfdf-c677-4dff-9b69-6967c234d34d&isPublished=true#UniqueID=D79F2008-E0F4-CEB3-6A74-14BF441310BD))                 [10.0.16232.*](http://watson/Failure?FailureSearchText=07eecc43-b515-eb9a-5eb0-89e266d3a773&MaxRows=100&OSVersion=10.0.16232.%2a&DeviceFamily=Windows.Desktop)                    
    
                    * indicates that we have shown only top 5 reasons
  
  
  
          
      
          
        -- end: Promo Info --                                    Ever since the Creator update Edge always crashes.  I am unable to launch or view any site.

I’ve attached a Windows Error Report generated mini-dump.

Details from the Windows Application Event log:

Faulting application name: MicrosoftEdge.exe, version: 11.0.15063.250, time stamp: 0x58f6ff5f
Faulting module name: EMODEL.dll, version: 11.0.15063.250, time stamp: 0x5bc6bca2
Exception code: 0xc0000409
Fault offset: 0x00000000000ea8fc
Faulting process id: 0x346c
Faulting application start time: 0x01d2c9ee82b10517
Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe
Faulting module path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\EMODEL.dll
Report Id: 5e5d32af-b429-41d7-9c19-4fc5bc7d2fb7
Faulting package full name: Microsoft.MicrosoftEdge_40.15063.0.0_neutral__8wekyb3d8bbwe
Faulting package-relative application ID: MicrosoftEdge

Attachments

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

  • Hello,

    Thank you for providing extensive information about the issue. After thorough testing, we are unable to reproduce this problem in Edge 15063. Your issue appears to stem from a bad installation of Edge; please reinstall Windows to see if this resolves the problem. 

    Best Wishes,
    The MS Edge Team

  • I depend on this surface book for presentations and travel, reinstalling Windows is an interruption I won’t be able to tolerate for at least a few weeks. FYI - I am one of 3 people in my office with this same issue. They just gave up and are using Chrome full time.

    I’ll ask them to submit the same information and dumps when I am back in the office. I don’t think this is an isolated issue.

  • I downloaded the Creators update again, created USB media and preformed an upgrade re-install. The crash issue with Edge persists even after re-installing.

    I’ve also preformed:
    Dism /Online /Cleanup-Image /CheckHealth
    <-- no issues found. -->
    DISM /Online /Cleanup-Image /RestoreHealth /Source:\Sources\install.esd
    <-- No change in behavior -->

    sfc /scannow
    <-- No issues found -->

  • I am also able to replicate this issue on my SurfaceBook

    Source
    Microsoft Edge

    Summary
    Stopped working

    Date
    ‎5/‎25/‎2017 1:11 PM

    Status
    Report sent

    Description
    Faulting Application Path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe

    Problem signature
    Problem Event Name: MoBEX
    Package Full Name: Microsoft.MicrosoftEdge_40.15063.0.0_neutral__8wekyb3d8bbwe
    Application Name: praid:ContentProcess
    Application Version: 11.0.15063.0
    Application Timestamp: 58ccbae4
    Fault Module Name: ntdll.dll
    Fault Module Version: 10.0.15063.0
    Fault Module Timestamp: b79b6ddb
    Exception Offset: 00000000000aa030
    Exception Code: c0000409
    Exception Data: 000000000000000a
    OS Version: 10.0.15063.2.0.0.256.48
    Locale ID: 1033
    Additional Information 1: e4b6
    Additional Information 2: e4b62901ff6b9ac7d6e7c7b8004037ab
    Additional Information 3: e4b6
    Additional Information 4: e4b62901ff6b9ac7d6e7c7b8004037ab

    Extra information about the problem
    Bucket ID: 9466c36fe568469927f3d48f089f609b (133476432870)

  • Microsoft Edge Team

    Changed Assigned To to “Lee H.”

    Changed Assigned To to “Dave B.”

    Changed Assigned To from “Dave B.” to “Feng M.”

    Changed Status to “Confirmed”

  • Has a fix been found for this problem yet? I have the same problem, and have tried all of the suggested fixes that I have managed to find online, with no joy.

    Exception code = 0xc0000409
    Exception offset = 0x000eae6c
    Fault Module Name = EMODEL.dll
    Fault Module Version = 11.0.15063.332

    Crash dump report:

    Version=1
    EventType=MoBEX
    EventTime=131412566419252140
    ReportType=2
    Consent=1
    UploadTime=131412566592188703
    ReportStatus=268435456
    ReportIdentifier=78f1c736-05c2-428a-a894-f6e13db34cee
    IntegratorReportIdentifier=aa8537c9-4ea2-4a83-b9f4-50b4424a8a9c
    Wow64Host=34404
    NsAppName=praid:MicrosoftEdge
    AppSessionGuid=00002b38-0001-0008-b023-2b5f08dfd201
    TargetAppId=U:Microsoft.MicrosoftEdge_40.15063.0.0_neutral__8wekyb3d8bbwe!MicrosoftEdge
    TargetAppVer=40.15063.0.0_neutral_!2017//05//20:05:58:08!b11765!MicrosoftEdge.exe
    BootId=4294967295
    TargetAsId=264
    Response.BucketId=922670eaef40b4d8d11328b1689caa6e
    Response.BucketTable=5
    Response.LegacyBucketId=133504082949
    Response.type=4
    Sig[0].Name=Package Full Name
    Sig[0].Value=Microsoft.MicrosoftEdge_40.15063.0.0_neutral__8wekyb3d8bbwe
    Sig[1].Name=Application Name
    Sig[1].Value=praid:MicrosoftEdge
    Sig[2].Name=Application Version
    Sig[2].Value=11.0.15063.332
    Sig[3].Name=Application Timestamp
    Sig[3].Value=591fdaf0
    Sig[4].Name=Fault Module Name
    Sig[4].Value=EMODEL.dll
    Sig[5].Name=Fault Module Version
    Sig[5].Value=11.0.15063.332
    Sig[6].Name=Fault Module Timestamp
    Sig[6].Value=7f5a6051
    Sig[7].Name=Exception Offset
    Sig[7].Value=00000000000eae6c
    Sig[8].Name=Exception Code
    Sig[8].Value=c0000409
    Sig[9].Name=Exception Data
    Sig[9].Value=0000000000000007
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.15063.2.0.0.768.101
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=5eab
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=5eaba6f95422f2cad1441eda706f1ac6
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=c835
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=c835a3f35c70bba5df935a2824b711aa
    UI[2]=C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe
    LoadedModule[0]=C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe
    LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
    LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
    LoadedModule[4]=C:\WINDOWS\SYSTEM32\apphelp.dll
    LoadedModule[5]=c:\program files (x86)\trusteer\rapport\bin\x64\rooksbas_x64.dll
    LoadedModule[6]=C:\WINDOWS\System32\SHLWAPI.dll
    LoadedModule[7]=C:\WINDOWS\System32\msvcrt.dll
    LoadedModule[8]=C:\WINDOWS\System32\combase.dll
    LoadedModule[9]=C:\WINDOWS\System32\ucrtbase.dll
    LoadedModule[10]=C:\WINDOWS\System32\RPCRT4.dll
    LoadedModule[11]=C:\WINDOWS\SYSTEM32\VERSION.dll
    LoadedModule[12]=C:\WINDOWS\System32\bcryptPrimitives.dll
    LoadedModule[13]=C:\WINDOWS\System32\GDI32.dll
    LoadedModule[14]=C:\WINDOWS\System32\gdi32full.dll
    LoadedModule[15]=C:\WINDOWS\System32\msvcp_win.dll
    LoadedModule[16]=C:\WINDOWS\System32\USER32.dll
    LoadedModule[17]=C:\WINDOWS\System32\win32u.dll
    LoadedModule[18]=C:\WINDOWS\System32\PSAPI.DLL
    LoadedModule[19]=C:\WINDOWS\System32\ADVAPI32.dll
    LoadedModule[20]=C:\WINDOWS\System32\sechost.dll
    LoadedModule[21]=C:\WINDOWS\System32\SHELL32.dll
    LoadedModule[22]=C:\WINDOWS\System32\cfgmgr32.dll
    LoadedModule[23]=C:\WINDOWS\System32\shcore.dll
    LoadedModule[24]=C:\WINDOWS\System32\windows.storage.dll
    LoadedModule[25]=C:\WINDOWS\System32\kernel.appcore.dll
    LoadedModule[26]=C:\WINDOWS\System32\powrprof.dll
    LoadedModule[27]=C:\WINDOWS\System32\profapi.dll
    LoadedModule[28]=C:\WINDOWS\System32\WINTRUST.dll
    LoadedModule[29]=C:\WINDOWS\System32\MSASN1.dll
    LoadedModule[30]=C:\WINDOWS\System32\CRYPT32.dll
    LoadedModule[31]=C:\WINDOWS\System32\ole32.dll
    LoadedModule[32]=C:\WINDOWS\SYSTEM32\wincorlib.DLL
    LoadedModule[33]=C:\WINDOWS\System32\OLEAUT32.dll
    LoadedModule[34]=C:\WINDOWS\System32\IMM32.DLL
    LoadedModule[35]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
    LoadedModule[36]=C:\WINDOWS\system32\rsaenh.dll
    LoadedModule[37]=C:\WINDOWS\SYSTEM32\bcrypt.dll
    LoadedModule[38]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
    LoadedModule[39]=c:\program files (x86)\trusteer\rapport\bin\x64\rookscom_x64.dll
    LoadedModule[40]=c:\program files (x86)\trusteer\rapport\bin\x64\rooksdol_x64.dll
    LoadedModule[41]=C:\WINDOWS\SYSTEM32\ntmarta.dll
    LoadedModule[42]=C:\Program Files (x86)\Trusteer\Rapport\bin\x64\RapportGP_x64.DLL
    LoadedModule[43]=C:\WINDOWS\System32\WS2_32.dll
    LoadedModule[44]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
    LoadedModule[45]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
    LoadedModule[46]=C:\WINDOWS\System32\NSI.dll
    LoadedModule[47]=C:\Program Files (x86)\Trusteer\Rapport\bin\x64\MSVCP120.dll
    LoadedModule[48]=C:\Program Files (x86)\Trusteer\Rapport\bin\x64\MSVCR120.dll
    LoadedModule[49]=c:\program files (x86)\trusteer\rapport\bin\x64\RapportUtil_x64.dll
    LoadedModule[50]=c:\program files (x86)\trusteer\rapport\bin\x64\trf_x64.dll
    LoadedModule[51]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.15063.0_none_9055be80f37df5c1\gdiplus.dll
    LoadedModule[52]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll
    LoadedModule[53]=C:\WINDOWS\SYSTEM32\WINMM.dll
    LoadedModule[54]=C:\WINDOWS\SYSTEM32\USERENV.dll
    LoadedModule[55]=C:\WINDOWS\SYSTEM32\Secur32.dll
    LoadedModule[56]=C:\WINDOWS\SYSTEM32\winmmbase.dll
    LoadedModule[57]=C:\WINDOWS\SYSTEM32\SSPICLI.DLL
    LoadedModule[58]=C:\ProgramData\Trusteer\Rapport\store\exts\RapportCerberus\baseline\x64\RapportGH_x64.DLL
    LoadedModule[59]=C:\Program Files (x86)\Trusteer\Rapport\bin\x64\RapportEjo_x64.DLL
    LoadedModule[60]=C:\WINDOWS\SYSTEM32\OLEACC.dll
    LoadedModule[61]=C:\WINDOWS\SYSTEM32\WININET.dll
    LoadedModule[62]=C:\WINDOWS\SYSTEM32\urlmon.dll
    LoadedModule[63]=C:\WINDOWS\SYSTEM32\iertutil.dll
    LoadedModule[64]=C:\WINDOWS\system32\jscript.dll
    LoadedModule[65]=C:\WINDOWS\SYSTEM32\dbghelp.dll
    LoadedModule[66]=C:\Windows\System32\twinapi.appcore.dll
    LoadedModule[67]=C:\Windows\System32\WinTypes.dll
    LoadedModule[68]=C:\WINDOWS\SYSTEM32\msIso.dll
    LoadedModule[69]=C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\EMODEL.dll
    LoadedModule[70]=C:\WINDOWS\SYSTEM32\clipc.dll
    LoadedModule[71]=C:\WINDOWS\SYSTEM32\EShims.dll
    LoadedModule[72]=C:\WINDOWS\SYSTEM32\MPR.dll
    LoadedModule[73]=C:\WINDOWS\system32\uxtheme.dll
    LoadedModule[74]=C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
    LoadedModule[75]=C:\WINDOWS\SYSTEM32\CoreMessaging.dll
    LoadedModule[76]=C:\WINDOWS\SYSTEM32\dwmapi.dll
    LoadedModule[77]=C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\eData.dll
    LoadedModule[78]=C:\WINDOWS\SYSTEM32\ESENT.dll
    LoadedModule[79]=C:\Windows\System32\Windows.UI.Xaml.dll
    LoadedModule[80]=C:\WINDOWS\SYSTEM32\Bcp47Langs.dll
    LoadedModule[81]=C:\Windows\System32\Windows.Storage.ApplicationData.dll
    LoadedModule[82]=C:\Windows\System32\threadpoolwinrt.dll
    LoadedModule[83]=C:\Windows\System32\Windows.UI.dll
    LoadedModule[84]=C:\WINDOWS\SYSTEM32\TextInputFramework.dll
    LoadedModule[85]=C:\WINDOWS\SYSTEM32\CoreUIComponents.dll
    LoadedModule[86]=C:\WINDOWS\SYSTEM32\usermgrcli.dll
    LoadedModule[87]=C:\Windows\System32\OneCoreUAPCommonProxyStub.dll
    LoadedModule[88]=C:\WINDOWS\SYSTEM32\dxgi.dll
    LoadedModule[89]=C:\Windows\System32\Windows.ApplicationModel.dll
    LoadedModule[90]=C:\WINDOWS\SYSTEM32\d3d11.dll
    LoadedModule[91]=C:\WINDOWS\SYSTEM32\igd10umd64.dll
    LoadedModule[92]=C:\WINDOWS\SYSTEM32\d2d1.dll
    LoadedModule[93]=C:\Windows\System32\MrmCoreR.dll
    LoadedModule[94]=C:\WINDOWS\System32\msctf.dll
    LoadedModule[95]=C:\Windows\System32\UiaManager.dll
    LoadedModule[96]=C:\WINDOWS\SYSTEM32\windows.ui.core.textinput.dll
    LoadedModule[97]=C:\Windows\System32\Windows.UI.Immersive.dll
    LoadedModule[98]=C:\WINDOWS\system32\DataExchange.dll
    LoadedModule[99]=C:\WINDOWS\SYSTEM32\dcomp.dll
    LoadedModule[100]=C:\Windows\System32\Windows.System.Profile.RetailInfo.dll
    LoadedModule[101]=C:\WINDOWS\SYSTEM32\policymanager.dll
    LoadedModule[102]=C:\WINDOWS\SYSTEM32\msvcp110_win.dll
    LoadedModule[103]=C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\eView.dll
    LoadedModule[104]=C:\Windows\System32\ieproxy.dll
    LoadedModule[105]=C:\WINDOWS\SYSTEM32\profext.dll
    LoadedModule[106]=C:\WINDOWS\SYSTEM32\firewallapi.dll
    LoadedModule[107]=C:\WINDOWS\SYSTEM32\fwbase.dll
    LoadedModule[108]=C:\WINDOWS\SYSTEM32\tokenbinding.dll
    LoadedModule[109]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll
    LoadedModule[110]=C:\WINDOWS\SYSTEM32\winhttp.dll
    LoadedModule[111]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
    LoadedModule[112]=C:\WINDOWS\system32\mswsock.dll
    LoadedModule[113]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
    LoadedModule[114]=C:\Windows\System32\Windows.StateRepository.dll
    LoadedModule[115]=C:\WINDOWS\SYSTEM32\StateRepository.Core.dll
    LoadedModule[116]=C:\Windows\System32\twinapi.dll
    LoadedModule[117]=C:\WINDOWS\SYSTEM32\dwrite.dll
    LoadedModule[118]=C:\Windows\System32\Windows.Globalization.dll
    LoadedModule[119]=C:\WINDOWS\SYSTEM32\msftedit.dll
    LoadedModule[120]=C:\WINDOWS\SYSTEM32\globinputhost.dll
    LoadedModule[121]=C:\WINDOWS\SYSTEM32\NInput.dll
    LoadedModule[122]=C:\WINDOWS\SYSTEM32\ieapfltr.dll
    LoadedModule[123]=C:\Windows\System32\Windows.Graphics.dll
    LoadedModule[124]=C:\WINDOWS\SYSTEM32\XmlLite.dll
    LoadedModule[125]=C:\WINDOWS\system32\directmanipulation.dll
    LoadedModule[126]=C:\Windows\System32\Windows.Globalization.Fontgroups.dll
    LoadedModule[127]=C:\WINDOWS\SYSTEM32\wkscli.dll
    LoadedModule[128]=C:\WINDOWS\System32\coml2.dll
    LoadedModule[129]=C:\WINDOWS\SYSTEM32\netjoin.dll
    LoadedModule[130]=C:\WINDOWS\SYSTEM32\JoinUtil.dll
    LoadedModule[131]=C:\WINDOWS\SYSTEM32\netutils.dll
    LoadedModule[132]=C:\WINDOWS\SYSTEM32\MDMRegistration.DLL
    LoadedModule[133]=C:\WINDOWS\SYSTEM32\DMCmnUtils.dll
    LoadedModule[134]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
    LoadedModule[135]=C:\WINDOWS\SYSTEM32\ncrypt.dll
    LoadedModule[136]=C:\WINDOWS\SYSTEM32\NTASN1.dll
    LoadedModule[137]=C:\Windows\System32\Windows.Web.dll
    LoadedModule[138]=C:\Windows\System32\rmclient.dll
    LoadedModule[139]=C:\Windows\System32\execmodelclient.dll
    LoadedModule[140]=C:\WINDOWS\SYSTEM32\fontgroupsoverride.dll
    LoadedModule[141]=C:\Windows\System32\Windows.Shell.ServiceHostBuilder.dll
    LoadedModule[142]=C:\WINDOWS\system32\execmodelproxy.dll
    LoadedModule[143]=C:\Windows\System32\uiautomationcore.dll
    LoadedModule[144]=C:\Windows\System32\Windows.ApplicationModel.Core.dll
    LoadedModule[145]=C:\Windows\System32\Windows.Security.Authentication.Web.Core.dll
    LoadedModule[146]=C:\Windows\System32\OneCoreCommonProxyStub.dll
    LoadedModule[147]=C:\Windows\System32\Windows.Perception.Stub.dll
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    FriendlyEventName=Stopped working
    ConsentKey=MoBEX
    AppName=Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge
    AppPath=C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=7770C0A292B788E229C873B03B711038
    MetadataHash=-1907785266

  • Microsoft Edge Team

    Changed Status from “Confirmed” to “Confirmed”

  • Hello,

    Thank you for providing this information about the issue. We have confirmed the problem, and we are working on a solution for a future build of Edge. We are presently tracking this issue as a duplicate of an existing internal bug report. We look forward to additional feedback you may have on how we can improve Microsoft Edge.

    Best Wishes,
    The MS Edge Team

  • I have just a pc with the same error, i uninstalled Trusteer Rapport, rebooted and it all started to work again.

  • Based on Paul C.’s comment, I “Stopped” Trusteer Rapport (rather than uninstalling), and Edge then worked. It thus appears to be some sort of conflict with Trusteer Rapport, when it is running. HOWEVER, I would prefer to have this software running and protecting me!

  • Paul\Alan … thank-you both for spotting this. so many MS blogs etc. and MS saying there are no issues.

    I stopped Rapport instead of uninstalling it, fired up Edge (which i’d lost all my settings in due to troubleshooting steps taken), re-imported IE favourites, re-started Rapport.

    working fine since … about 14 hours so far.

    will reboot later and see if issue comes back.

  • Thank you for this tip. I stopped Trusteer, and Edge started working again, but failed as soon as it restarted.
    What caused Edge to fail initially for myself, was using Sophos Home Advance Beta security software.

  • The following is a workaround to the problem as suggested by IBM Trusteer Support

    Dear Nigel,

    Thank you for updating us on the matter.

    The issue you have reported is currently being investigated by our company experts
    and we expect it to be resolved in a future release of Rapport.

    Please use other browsers in the meantime. Kindly note that once the issue will be
    resolved you will be notified via E-mail.

    Should you wish to use Microsoft Edge still, please try to disable Rapport’s Early
    Browser Protection.

    To disable Rapport’s Early Browser Protection:

    1. Open Rapport’s Console by choosing - Start Menu > Programs > Trusteer Endpoint
      Protection > Trusteer Endpoint Protection Console
    2. Advance to the next page by clicking on the green arrow at the bottom-right.
    3. Under ‘Security Policy’ at the top left corner, click on 'Edit Policy’.
    4. Enter the letters as they are shown in the image and click OK.
    5. Locate ‘Early Browser Protection’ and select ‘Never’ in the drop-down menu.
    6. Click ‘Save’ and reboot your computer.
    7. Check if the issue is resolved.

    Please be advised that disabling Rapport’s Early Browser Protection will limit some
    of Rapport’s protections.

    Please let us know if this has resolved the issue. Thank you for your cooperation.

    Thank you for your patience.

    Should you need additional assistance, feel free to contact us by submitting the
    following form: http://www.trusteer.com/support/submit-ticket
    We also have helpful information available in our FAQ:
    http://www.trusteer.com/support/faq

    Sincerely,

    Lior K.
    Tier 1 Support Representative
    Trusteer, IBM Security Systems

  • tried the IBM suggested workaround but the “Early Browser Protection” is set to “Always” and greyed out, so I can’t change it.
    I will have to stick to stopping Rapport, start edge, start rapport.

  • Microsoft Edge Team

    Changed Steps to Reproduce

    Changed Steps to Reproduce

  • Paul C. is a star. Thanks.
    Stopping Trusteer Rapport worked for me. Trusteer’s suggestion of setting ‘Early Browser Protection’ to never did not work.

    The people at the Help app in Windows 10 were of no help. They wasted hours of my time.

  • Microsoft Edge Team

    Changed Steps to Reproduce

    Changed Steps to Reproduce

    Changed Steps to Reproduce

    Changed Steps to Reproduce

    Changed Steps to Reproduce

    Changed Steps to Reproduce

    Changed Steps to Reproduce

  • I have the same problem every five or six days. Checked for “Trusteer Rapport” on this PC and could not find.
    Suggestions?

  • After spending many days on this issue and trying the many suggestions without success, I went back to an earlier Image copy made just after the Creator’s Update. Edge then worked but as soon as Windows Update had installed further updates and rebooted, Edge failed to work.
    Finally found the above suggestion and Switching off Trusteer Rapport Early Browser Protection now seems to work.
    This problem must have affected lots of users as Rapport is the recommended protection software by most banks for on-line banking.

  • We have this issue on all devices imaged with a non-OEM iso; obtained from Microsoft. This issue occurs directly after the image is applied; and persists when using domain users and local users; all local administrator
    We do not use trusteer; I tried DISM.exe /Online /Cleanup-image /Scanhealth
    DISM.exe /Online /Cleanup-image /restoreheath and sfc /scannow
    also tried to remove edge and reinstall using the powershell commands.
    The final thing I tried is copying a working folder to the affected PC; but all to no avail.

    I am unable to find any issues related to edge; in earlier versions of Windows, the trouble with edge was related to permissions etc; checked those but they seem to be OK. Also, Edge issues also affected other store apps, but I tested them all and Edge is the only crashing application

    Description
    Faulting Application Path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe

    Problem signature
    Problem Event Name: MoBEX
    Package Full Name: Microsoft.MicrosoftEdge_40.15063.0.0_neutral__8wekyb3d8bbwe
    Application Name: praid:MicrosoftEdge
    Application Version: 11.0.15063.447
    Application Timestamp: 5948acf2
    Fault Module Name: EMODEL.dll
    Fault Module Version: 11.0.15063.483
    Fault Module Timestamp: 5b988a75
    Exception Offset: 00000000000eaf4c
    Exception Code: c0000409
    Exception Data: 0000000000000007
    OS Version: 10.0.15063.2.0.0.256.48
    Locale ID: 1043
    Additional Information 1: 5eab
    Additional Information 2: 5eaba6f95422f2cad1441eda706f1ac6
    Additional Information 3: a3df
    Additional Information 4: a3dfcc44cbb0b67c69f29b02d7580fbc

    Extra information about the problem
    Bucket ID: ca0eb6e23fe4aa7365db231c1b15fb1c (133524411117)

  • i just switched to chrome because all the fixes i have seen dont work for me and i dont have much time to waste on it. i believe if everyone stops using it and gives another browser their marketshare, microsoft will either fix the problems they have or cancel their browser department to focus on other areas.

  • Try the following to see if this resolves the problem: -

    1. Load Microsoft Edge.
    2. Open another New Window on Microsoft Edge.
    3. Check to see if the Tabs appear.
      This worked after the first Edge window did not have the Tabs.
  • Nigel,

    It is impossible to open multiple pages of Edge; either via the Start menu or via run microsoft-edge://microsoft.com; Only one instance appears, with no tabs and no content.

  • “It is impossible to open multiple pages of Edge; either via the Start menu or via run microsoft-edge://microsoft.com; Only one instance appears, with no tabs and no content.”

    No its not. Just open your edge and continuously hit CTRL+T to open a new tab (like in this video https://www.youtube.com/edit?o=U&video_id=KWNs_jjxeZQ) and if done correctly, edge should open and stay up with multiple tabs

  • My PC is getting worse everyday with this problem. It is acting just like EI 11.1 before I switched to Edge. Same song second verse. I’m just an everyday home user of Windows 10, I would hate to think of this happening if I was back in the IT world.

  • @Carlington R.: Neither the video nor the CTRL+T works. I’ve been spamming CTRL+T for the entire duration that Edge was on screen; but nothing happens.

  • Ok, it’s almost a month since we detected that Edge wasn’t able to run on 1703.
    For us, it happens on both Domain users, Local Users, Existing en new Profiles.
    We do not have trusteer installed; in fact: It happens out of the box on a clean install (Microsoft Image, non-OEM bloatware etc).

    Funny thing is, Edge launches and as long as I don’t touch it, it stays open. It’ll eventually display the Default Browser question, (which I am honestly never gonna set… but that’s another topic). It’s been open for 10 minutes now… and once I click on any buttons; it crashes in +/- 10-20 seconds.
    I’ve tried multiple things now, cleanup; dism checkhealth and repairhealth, sfc scannow, remove the folder and reinstall Edge; Windows updates are up2date, I checked the registry settings to see if the ‘old permissions issue’ was in play here; all are configured as it should.
    Get-Process edge only shows one entry. Opening an PDF with edge: the same issue. microsoft-edge:// and microsoft-edge://microsoft.com all open edge, but with a blank page and no responsive UI.
    Setting all defaults to edge doesn’t fix anything. Hence, resetting all default apps: nope nothing nada.
    I checked the process monitor, but it displays quite a lot of access denieds on the internet temp/cookies folders; I set the ALL APPPACKAGES rights to Read on my complete User Profile and also got a few Access Denieds, apparently on Symbolic Links to ‘Temporary Internet Files’
    [Content]
    ‘C:\Users\Username\AppData\Local\Temporary Internet Files’ is not accessible.
    Access is denied.
    This is also the case for the ‘Application Data’ symbolic link. (they are hidden) I don’t know if others can confirm this?

    ===== edit ===

    Ok, opening Edge via the Shortcut makes is crash in 10 seconds most; opening edge with the microsoft-edge:// method gives me the result I described above… running until I touch it.

  • Is there any followup on this issue? The latest cumulative update (KB4032188) did not fix Edge.

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

Sign in