Edge IE Mode Crash on Windows Server 2022

No current Microsoft release-health entry identifies a general Edge IE mode crash on Windows Server 2022, so update Windows and Edge first, then capture the faulting module and IE-mode diagnostics needed to distinguish an application compatibility failure from a version-specific regression.^1^^2^

Recommended remediation and investigation

1. Record the exact builds before changing anything
   • Edge: open edge://version and record the full version, channel, executable path, and command line.
   • Windows: run winver, or record the OS build from Settings → System → About.
   • Confirm whether the failure closes Edge, crashes only the IE-mode tab, or leaves the tab unresponsive.
2. Install current Windows Server 2022 and Edge updates
   • Install the latest cumulative Windows Server update.
   • In Edge, open Settings and more (…) → Help and feedback → About Microsoft Edge, allow the update to complete, and restart Edge.
   Microsoft lists current Windows and Edge updates as prerequisites for reliable IE-mode operation.^3^
3. Export the IE-mode diagnostic report
   • Open edge://compat/iediagnostic.
   • Export the diagnostic data as XML.
   • Note any failed Registry key check, Windows Update prompt, IE-mode API problem, or unexpected policy value.
   • If Fix it appears for the registry check, use it and retest.
   • Open edge://compat/enterprise and verify that the expected site-list location, version, and compatibility mode are loaded.
   • Open edge://policy and confirm that the intended IE integration and site-list policies have status OK.
   The diagnostic page reports the IE-mode API version, registry state, command line, configuration, and applied Group Policies.^4^
4. Collect the crash signature
   • In Event Viewer → Windows Logs → Application, export the events at the crash time, especially Event IDs 1000 and 1001.
   • Include:
     • Faulting application
     • Faulting module and its version
     • Exception code
     • Fault offset
     • Event timestamp
   • Open edge://crashes and record the matching crash entries. Crash reports can contain the browser/device state, URL, CPU usage, and network information relevant to diagnosis.^5^

Reproduce once with only the affected tab open and record the exact action that triggers the failure—for example, opening a modal dialog, authentication redirect, ActiveX operation, printing, or file selection.

Check the historical Server 2022 defect only if the symptom matches

Windows Server 2022 had a documented 2022 issue where an IE-mode tab stopped responding when a site displayed a modal dialog and called window.focus.^6^

That defect was fixed in KB5016693, OS build 20348.946, and the fix is included in later cumulative updates.^7^ It is relevant only when:

• the server is still on an affected 2022 build, and
• the failure occurs around a modal dialog or window.focus.

For a currently patched server, that historical defect does not explain the crash without additional matching evidence.

Application compatibility checks

If Edge remains running but the legacy application fails or becomes unstable:

• Use IEChooser: press Win+R, run %systemroot%\system32\f12\IEChooser.exe, and select the affected IE-mode tab.
• Check whether the Enterprise Mode Site List applies the correct document mode. Microsoft recommends starting with Default, then testing IE8 Enterprise and IE7 Enterprise only when the application requires those modes.
• If the failure occurs during SSO or redirects and the IE-mode icon disappears, capture edge://net-export and identify redirect hosts missing from the site list as neutral sites.^4^

Update strategy and temporary rollback

Remain on the latest Stable release unless the crash can be reproduced only on one Edge version. For organizations needing more validation time, Extended Stable uses an eight-week feature-release cadence while continuing to receive applicable security and critical fixes.^8^

If controlled A/B testing proves that the current Edge build introduced the crash, domain-joined Windows devices can temporarily use Target version override with Roll back to Target version under:

Computer Configuration → Administrative Templates → Microsoft Edge Update → Applications → Microsoft Edge

Rollback can expose the server to known security issues and risks browser-data loss, so it should be temporary and tested on a nonproduction server first.^9^

If the updated server still crashes, provide the Edge version, Server 2022 build, exported iediagnostic XML, Enterprise Site List entry, Event 1000/1001 details, and edge://crashes identifier to Microsoft Support or App Assure. Those artifacts are required to determine whether the fault is in Edge, mshtml.dll/IE mode, an ActiveX component, or the application itself.

References

1. Windows Server 2022 known issues and notifications
2. Microsoft Edge known issues | Microsoft Learn
3. What is Internet Explorer (IE) mode?
4. Internet Explorer (IE) mode troubleshooting and FAQ
5. User data and privacy in Microsoft Edge
6. July 12, 2022—KB5015827 (OS Build 20348.825) | Microsoft Support
7. August 16, 2022—KB5016693 (OS Build 20348.946) Preview
8. Overview of the Microsoft Edge channels
9. Microsoft Edge - Update policies