Forum Discussion

Chuchmenkin's avatar
Chuchmenkin
Copper Contributor
Jul 20, 2026

Edge beta crashes after 5 seconds on some old versions of Windows 10

We have problems with Edge Beta versions 151.0.4129.15, 151.0.4129.21 and 151.0.4129.35.

On launch Microsoft Edge briefly opens and then closes (like in 5 seconds) on Windows 10 RS1/RS2/RS3. I can't reproduce problem on other versions of Windows 10, such as TH1 or RS4

5 Replies

  • Günter Born's avatar
    Günter Born
    Brass Contributor

    Got same reports for the final build from German blog reader. The problem appears to be caused by a new TPM-based feature. TPM key attestation via ncrypt.dll/tbs.dl seems to fail and crashed the UI. There is a workaround: Use a newer dll on affected machines. I've described the findings so far at this blog post:

    https://borncity.com/win/2026/08/05/microsoft-edge-version-151-x-or-later-crashes-in-windows-10/

  • ErinDay's avatar
    ErinDay
    Brass Contributor

    Experiencing the same thing on latest July 31 151 version. 300+ Win 10 LTSB 1607 devices affected. MSFT ticket raised and crashdumps submitted

  • IntTrins's avatar
    IntTrins
    Copper Contributor

    My *stable" v151 just installed is crashing like this on win10 22H2 ESU. I'm attempting a system restore to get back to 150 while writing this on my phone

  • The version pattern suggests an OS-support or servicing issue before a profile problem. RS1 (1607) and RS2 (1703) are below Edge’s supported Windows 10 SAC baseline; Microsoft lists SAC 1709 and later, plus specific Enterprise LTSC/LTSB releases. RS3 is 1709, so its edition and update level matter. TH1 working does not prove every TH1 edition is supported.

     

    On each failing PC, run winver and record the edition, OS build, and latest cumulative update. Fully patch eligible LTSB/LTSC images; move ordinary SAC devices to a supported Windows release rather than treating a Beta rollback as a fix. On RS3, launch the Beta executable with --user-data-dir="%TEMP%\edge-test-profile". If it still closes, collect the Application Error event for msedge.exe, faulting module, Edge version, and crash ID from edge://crashes if Beta remains open long enough. Submit those diagnostics with Alt+Shift+I from Stable. This will distinguish an Edge 151 regression from an unsupported or unserviced OS.

    • Chuchmenkin's avatar
      Chuchmenkin
      Copper Contributor

      I wasn't able to get anything about crash from the Edge, because it doesn't remain long enough to open edge://crashes. But there is no error in Event viewer, only information event:

      "svchost (3092,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000."