{"id":40192,"date":"2026-08-05T11:13:34","date_gmt":"2026-08-05T09:13:34","guid":{"rendered":"https:\/\/borncity.com\/win\/?p=40192"},"modified":"2026-08-05T14:25:30","modified_gmt":"2026-08-05T12:25:30","slug":"microsoft-edge-version-151-x-or-later-crashes-in-windows-10","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2026\/08\/05\/microsoft-edge-version-151-x-or-later-crashes-in-windows-10\/","title":{"rendered":"Microsoft Edge version 151.x or later crashes in Windows 10"},"content":{"rendered":"

\"Edge\"[German<\/a>]I got reports from German blog readers about an issue with the Microsoft Edge browser starting with version 151.x. The browser crashes 5 seconds after start on Windows 10 systems, while it continues to run on other systems.<\/p>\n

<\/p>\n

Microsoft Edge Version 151.x<\/h2>\n

\"\"According to this Microsoft release notes<\/a>, Microsoft Edge version 151.x was released on July 30, 2026, with numerous new features. Our colleagues at deskmodder.de discussed the rollout of version 151.0.4129.59 in this German post<\/a> on August 1, 2026.<\/p>\n

In this reddit.com post<\/a>, someone notes that Microsoft Edge 151 appears to disable hardware acceleration for Intel HD Graphics. This could be an early indication of the issues described below.<\/p><\/blockquote>\n

Windows 10 2016 LTSB: 1st Report about crashes<\/h2>\n

German blog reader Ronni reported on August 4, 2026, crash issues with Microsoft Edge within my German blog. The reader stated: \"On our Windows 10 2016 LTSB systems, the Edge browser has been crashing about 5 seconds after startup since version 151.x. This does not occur on 2019 LTSC or Windows 11.\" (I don't link the comment here, because I delete the comment section frequently) The reader referred to discussion on Microsoft's forum mentioned below and asked: \"Does anyone else have this problem, and if so, is there a workaround (without rolling back to 150.x)?\"<\/p>\n

Same problem with Windows 10 Pro with ESU<\/h2>\n

Blog reader ChristophH commented on the reader report about the crash issue: \"Same problem here with Edge on Windows 10 Pro with ESU.\" The reader writes that Edge Stable 64-bit version 151.0.4129.59 briefly launches a few Edge processes. These are terminated after a few seconds, and the browser UI does not appear.<\/p>\n

Temporary profile doesn't help<\/h3>\n

The reader tried using a temporary profile to see if it would help, but that didn't work either. Only downgrading to version 150.0.4078.110 helped. The problem can be reproduced on this computer: after updating to Edge 151.0.4129.59, the problem returned.<\/p>\n

Microsoft has published this article<\/a> with general guidance on diagnosing Edge crashes. It also suggests using a temporary profile and other measures, but these do not seem to help.<\/p><\/blockquote>\n

Admin Rights Help<\/h3>\n

According to a reader, the problem occurs for a standard user without administrator rights. Christoph's observation is interesting: If the user logs in to the computer interactively with an admin account, Edge 151.0.4129.59 works.<\/p>\n

Does Not Occur on All Computers<\/h3>\n

Blog reader ChristophH writes that the affected Edge version 151.0.4129.59 was installed on the affected computer running Windows 10 22H2 on July 31, 2026. The problem did not become apparent until August 4, 2026, when the user logged in at the start of the week.<\/p>\n

According to the blog reader, however, there are Windows 10 Pro machines (22H2) in his environment with a similar setup, and Edge version 151.0.4129.59 works flawlessly on those. The reader concludes that another, as yet unknown factor must be at play for this error to occur.<\/p>\n

Discussion in the tech community about the beta<\/h2>\n

Blog reader Ronni mentioned in his comment the discussion titled \"Edge beta crashes after 5 seconds on some old versions of Windows 10<\/a>\" from July 20, 2026. In that thread, the original poster wrote:<\/p>\n

We have problems with Edge Beta versions 151.0.4129.15, 151.0.4129.21 and 151.0.4129.35.<\/p>\n

On launch Microsoft Edge\u00a0briefly 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<\/p><\/blockquote>\n

Within the thread, additional users confirm the issue. An administrator wrote that the same problem also occurs in the latest version of Edge (151.x) released on July 31, 2026. There, 300 devices running Windows 10 LTSB 1607 are affected. The original poster created an MSFT ticket, and crash dumps were submitted to Microsoft.<\/p>\n

Report from an Affected User on deskmodder.de<\/h2>\n

A user also contacted our colleagues at German site deskmodder.de on August 4, 2026, with this comment<\/a>, confirming the crash reports mentioned above. The poster writes that, among other things, a German VW\/Audi car dealer is still using a few workshop test computers running Windows 10 Enterprise 2016 LTSB. On those systems, Edge crashes and closes after 5 seconds.<\/p>\n

According to the poster, other dealership colleagues have since confirmed this issue. Similarly, the VW Group's vehicle diagnostics software, ODIS, cannot be launched on these systems if the latest Edge WebView (version 151) is installed. The only solution at the moment is to roll back to the previous Edge 150 version.<\/p>\n

A possible workaround<\/h2>\n

A German blog reader postet this comment<\/a>, confirming the same issue (Edge closing after about 5 seconds\u2014but only on Windows Server 2016 (1607)). Newer operating systems are not affected. The reader wrote, they were able to resolve the issue with the help of an analysis by Claude Code.\u00a0The reader wrote, that the problem appears to be caused by a new TPM-based feature. Quote from Claude:<\/p>\n

\"Regarding the mechanism: The crash path is the TPM key attestation via ncrypt.dll\/tbs.dll. Both DLLs exist on Server 2016 and are loaded\u2014the crash occurs because Edge resolves all delay-load imports for these DLLs at once using LoadAllImportsForDll. If even a single export is missing from the 14393 version of ncrypt.dll (the attestation APIs were extended after 1607), the entire delay-load fails \u2192 failure hook \u2192 CHECK termination.\"<\/p><\/blockquote>\n

They used the followong workaround, until Microsoft addresses the issue: They copy a \"newer\" tbs.dll<\/em> to:<\/p>\n

C:\\Program Files (x86)\\Microsoft\\Edge\\Application<\/pre>\n
They used one from C:\\Windows\\system32<\/em> on a Windows Server 2019 system. Since programs typically search for DLLs in their own directory first, the correct one will be loaded. This resolves the problem for now at the reader's affected systems.<\/p>\n
If you're using Edge WebView2, you'll need to do the same and copy the tbs.dll<\/em> to the directory:<\/p>\n
C:\\Program Files (x86)\\Microsoft\\EdgeWebView\\Application\\151.0.4129.59<\/pre>\n
Hope that helps to solve the issue.<\/p>\n","protected":false},"excerpt":{"rendered":"
[German]I got reports from German blog readers about an issue with the Microsoft Edge browser starting with version 151.x. The browser crashes 5 seconds after start on Windows 10 systems, while it continues to run on other systems.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[872,463,2],"tags":[3004,166,76],"class_list":["post-40192","post","type-post","status-publish","format-standard","hentry","category-browser","category-issue","category-windows","tag-edge-151-x","tag-issues","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/40192","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=40192"}],"version-history":[{"count":5,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/40192\/revisions"}],"predecessor-version":[{"id":40197,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/40192\/revisions\/40197"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=40192"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=40192"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=40192"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}