AVD Crashes casuing webviewer2 hard errors, when working with m365 Copilot.

Question

We are using Microsoft AVD and since introducting Microsoft 365 Copilot, there are regular crashes generating issues with Webview2.

AVD VM Performance is running within recommended peramaters.

Specifically looking for guidlines here, how to capture the analysis of these errors as the only way to resolve this seems to be to dump users out and restart the AVD session host.

What is best practice for troubleshooting ?

How to analyse if this is M365 Copilot casuing these issues ? what advanced troubleshooting can be enabled to capture more detailed logs at the point of the crash, without causing additional system overhead to log everything.

Does anyone have similar experiences or resolutions ?

Answer 1

Hi @Steve

It sounds like you’re dealing with a challenging issue. I researched on this and see you have posted it on multiple forums already. Determining whether its M365 copilot is the cause, you need to troubleshoot this a bit, I will try my best to share some guidance here.

Check the event logs on the affected AVD session host to see if there are any error messages or warnings related to the crashes and issues with Webview2. This can help you identify the root cause of the issue.

• Enable more detailed logging for Webview2 to capture additional information about the crashes. You can follow the instructions in the "Enable WebView2 Runtime Logging" document to learn how to enable logging for Webview2.
• Monitor the performance of your AVD environment to ensure that it is running within recommended parameters. You can use Azure Monitor to monitor the performance of your AVD environment and identify any issues that may be causing the crashes.
• Consider disabling Microsoft 365 Copilot temporarily to see if the crashes and issues with Webview2 stop. If they do, then it is likely that Microsoft 365 Copilot is causing the issues. Contact Microsoft support for further assistance if you are unable to resolve the issue using the above steps.

It is important to note that capturing more detailed logs can cause additional system overhead, so you should only enable detailed logging when necessary and disable it when you are done troubleshooting.

If you find my suggestions above helpful, please hit "Yes" to Was this helpful and accept it as answer