Edge crashes when SRP are enabled with DLL enforcement since Windows 1703

Fixed, not yet flighted Issue #13758012


Manuel M.
Sep 14, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 8 people

Sign in to watch or report this issue.

Steps to reproduce

Steps to reproduce the issue:

  1. Install Windows 10 Creators Update, Version 1703.
  2. Open Local Security Settings. (secpol.msc)
  3. In the console tree, click Software Restriction Policies.
  4. On the Action menu, click New Software Restriction Policies.
  5. In the details pane, double-click Enforcement.
  6. Under Apply software restriction policies to the following, click All software files.
  7. Click OK.
  8. Now launch Edge. It will open, display a blank page for a couple of seconds (you can’t navigate anywhere) and then crash.


  • This issue does not occur in any previous version of Windows before 1703.
  • As described above, the issue also occurs if no restricting policies are defined. Simply enabled DLL enforcement causes the error to happen.
  • Without DLL enforcement, Edge works. (Obviously not a viable workaround for the more security-minded.)

Error logged:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <TimeCreated SystemTime="2017-09-14T17:51:05.226440400Z" />
    <Security />


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

      Changed Assigned To to “wprpprtri@microsoft.com”

    • Quick follow-up: The issue also occurs in Windows 1709.
      Is there any news on this, as I’m holding off deploying/updating Creators Update to/on the clients for the time being but won’t be able to do so indefinitely (and therefore might be forced to look for another browser). :/

    • Having a Windows computer running w/o Application Whitelisting such as SRP is not an option for me. Disabling DLL enforcement is not an option as well. Microsoft, please pay attention to this issue. And yes, your OneDrive that launches from user AppData folder is soo bad! You better listen to Aaron Margosis, and remove executables from AppData.

    • Microsoft Edge Team

      Changed Assigned To from “wprpprtri@microsoft.com” to “Zach M.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Zach M.” to “Sermet I.”

      Changed Assigned To from “Sermet I.” to “Dylan D.”

      Changed Status from “Confirmed” to “Fixed”

    • This is marked as Fixed. Can someone please explain how is this fixed? Its Not Fixed yet!

    • Microsoft Edge Team

      Changed Status from “Fixed” to “Fixed, not yet flighted”

    • Where when can I download this fix?
      Will this fix also availabe for Windows 10 1703?

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge and available in the upcoming Insider Preview build 17054.

      Best Wishes,
      The MS Edge Team

    • Thanks for this Information.
      Will this fix ported back to 1709, 1703?
      We don’t upgrade all our Windows 10 Clients until this fix is officialy released.

    • Dear Support
      I Download an install Windows 10 Build 17063 in a VM.
      With my Tests the Problems with SPR are still there.
      So the fix does not work!!!

      Please fix this asap.

    • When I run Edge with SRP I get the following Event:
      Protokollname: Application
      Quelle: Application Error
      Datum: 04.01.2018 13:58:44
      Ereignis-ID: 1000
      Ebene: Fehler
      Benutzer: Nicht zutreffend
      Computer: DESKTOP-1643MBI
      Name der fehlerhaften Anwendung: MicrosoftEdge.exe, Version: 11.0.17063.1000, Zeitstempel: 0x5a31eb8f
      Name des fehlerhaften Moduls: EMODEL.dll, Version: 11.0.17063.1000, Zeitstempel: 0x5a31ec16
      Ausnahmecode: 0xc0000409
      Fehleroffset: 0x0022e6f8
      ID des fehlerhaften Prozesses: 0x16b0
      Startzeit der fehlerhaften Anwendung: 0x01d3855bb8e07768
      Pfad der fehlerhaften Anwendung: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdge.exe
      Pfad des fehlerhaften Moduls: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\EMODEL.dll
      Berichtskennung: 556c5e05-9f4d-4c92-9006-cb412874ed61
      Vollständiger Name des fehlerhaften Pakets: Microsoft.MicrosoftEdge_42.17063.1000.0_neutral__8wekyb3d8bbwe
      Anwendungs-ID, die relativ zum fehlerhaften Paket ist: MicrosoftEdge

    • This issue has just become critical, since Windows 1607 now ignores the group policy setting to delay the upgrade to Creators Update any longer, and there is still no backport of this fix (if there really is one, as Reto pointed out).
      Dear Microsoft, I truly cannot understand why this issue - of which I’m quite sure is affecting many corporate users - is treated so unimportantly. Do you want admins that still see value in Edge and the effort that was put into it to switch to a different browser? Well, at least I know a couple of hundred users that won’t surf with Edge anymore, not because they don’t like the browser, but because they can’t thank’s to your actions, or rather the lack thereof.

    • Hoping for a fix soon, thank you.

    • This should help:
      reg add “HKCU\Software\Microsoft\Internet Explorer\Spartan” /v RAC_LaunchFlags /t REG_DWORD /d 1 /f

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

    Sign in