msedge_msedgeview2_image_options

After upgrading to Configuration Manager 2309 on Windows Server 2022, clicking on a console node that utilizes Microsoft Edge WebView2 causes the console node to present a blank view and subsequently crashes the console with a message stating _Microsoft.ConfigurationManagement has stopped working._



There is a known issue with Microsoft Edge and Microsoft Edge WebView2 whereas the executable will crash and reopen, constantly, causing a WerFault.exe storm to occur.



The workaround for Microsoft Edge is described in the **Known issues in this update** for the [January 9, 2024—KB5034129 (OS Build 20348.2227)](https://support.microsoft.com/en-us/topic/january-9-2024-kb5034129-os-build-20348-2227-6958a36f-efaf-4ef5-a576-c5931072a89a) cumulative update.



A similar workaround can be applied for Microsoft Edge WebView2 by replacing msedge.exe with msedgewebview2.exe in the **Workaround** instructions provided in the **Known issues in this update** for the [January 9, 2024—KB5034129 (OS Build 20348.2227)](https://support.microsoft.com/en-us/topic/january-9-2024-kb5034129-os-build-20348-2227-6958a36f-efaf-4ef5-a576-c5931072a89a) cumulative update.



After the workaround was applied for Microsoft Edge WebView2, clicking on a console node that utilizes Microsoft Edge WebView2 presents the expected view.

**Additional Symptoms**

- Application Windows Event Log, Critical Event ID 1, The WebView control is no longer valid because the browser process crashed.
- Application Windows Event Log, .NET Runtime Event ID 1026, The process was terminated due to an unhandled exception.
- Application Windows Event Log, Application Error Event ID 1000, 0xe0434352
- Application Windows Event Log, Application Error Event ID 1000, 0xc000041d