Copilot Not Working

How to Troubleshoot Microsoft 365 Copilot and WebView2 Crashes in AVD

Muhammad Talha Oct 1, 2026 868 views

Question details

Users are experiencing application instability where Microsoft Edge WebView2 crashes repeatedly within Azure Virtual Desktop environments following the deployment of Microsoft 365 Copilot.

Troubleshooting Microsoft 365 Copilot and WebView2 Crashes in AVD

Product: Microsoft 365 Copilot / Azure Virtual Desktop
Device & OS: not provided
Scenario: Operating Microsoft 365 Copilot features within an Azure Virtual Desktop (AVD) virtualized environment.
Observed behavior: Microsoft Edge WebView2 crashes, disrupting workflow and requiring investigation through crash and event logs to identify the root cause.

Before you start

Ensure you have administrative access to your Azure Virtual Desktop host environment so you can retrieve application event logs and WebView2 crash dumps before seeking support.

Solution 1Recommended

Gather Diagnostic Logs and Report to the Microsoft Support Community

Since this is a complex integration issue between AVD, WebView2, and Copilot, collecting system logs and escalating the problem to specialized Microsoft communities is the most effective resolution path.

WebView2 crashes in virtualized environments like AVD are often tied to specific host configurations, rendering conflicts, or version mismatches. Microsoft actively monitors their dedicated Q&A forums for these emerging deployment issues.

Collect Event and Crash Logs

Open the Event Viewer on your AVD host by pressing Win + R, typing 'eventvwr.msc', and pressing Enter. Navigate to Windows Logs > Application to export errors related to WebView2 or Copilot. Locate your WebView2 crash logs typically found in the local AppData folder.

Document Host Specifications

Note down your current Azure Virtual Desktop host details, virtual machine sizing, and the exact version of the Microsoft Edge WebView2 runtime installed via the Apps & Features settings menu.

Post in the Microsoft Community

Navigate to the Microsoft Q&A platform or the Copilot for Microsoft 365 community forum online. Click on 'Ask a Question' and apply the 'Copilot' tag to ensure it reaches the right engineers.

Provide Reproduction Steps

In your forum post, write a clear, step-by-step account of the actions that trigger the crash. Attach the exported event logs and your host specifications to help Microsoft support diagnose the underlying bug.

Gather Diagnostic Logs and Report to the Microsoft Support Community

Protect Sensitive Information: Always review and redact sensitive or personally identifiable information (PII) from your event and crash logs before uploading them to public Microsoft forums.

Free Microsoft Office alternative

Experience Stable Document Editing with WPS Office

If you are dealing with continuous WebView2 or Copilot crashes in Microsoft 365 within your virtual environments, consider switching to WPS Office. It provides a lightweight, highly stable workspace for your daily document needs without heavy background resource dependencies.

1. Download the Installer: Visit the official WPS Office website and click the Free Download button to get the latest version.
2. Install the Software: Run the downloaded executable file and follow the simple on-screen instructions to install WPS Office on your system.
3. Open Your Files: Launch WPS Office and directly open your existing Microsoft Office documents to continue working without interruptions.

Lightweight architecture that minimizes system resource usage and prevents environment crashes.Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Built-in advanced AI features to boost your productivity without complex AVD integrations.Free to use with an intuitive, familiar tabbed interface for seamless user migration.

microsoft office alternative - wps office

Frequently Asked Questions

Why does WebView2 crash when using Microsoft 365 Copilot in AVD?

WebView2 relies on modern edge rendering engines which can sometimes conflict with graphics acceleration protocols or specific virtual machine configurations in AVD when processing resource-intensive Copilot AI requests.

Where can I find WebView2 crash logs to diagnose the issue?

Crash logs for WebView2 are generally located in the local AppData folder of the active user profile (e.g., C:\Users\[Username]\AppData\Local\Microsoft\EdgeWebView\Crashpad), or they can be identified in the Windows Event Viewer under the Application logs.

Is Microsoft 365 Copilot fully supported in Azure Virtual Desktop?

Yes, it is supported, but it requires specific host pool configurations, fully updated Microsoft Edge WebView2 runtimes, and appropriate Microsoft 365 licensing. Running outdated runtimes is a common trigger for these crashes.

Microsoft Copilot Issues