A Copilot white screen is frustrating mostly because there’s no error message. Here’s how we tracked down one case, including the dead ends, since the troubleshooting path is the useful part.

The Copilot White Screen Symptom
A Windows PC launched the Copilot app, and the window opened but stayed completely white. This Copilot white screen came with no error, no crash, and no sign-in prompt.
The Usual Suspects Behind a Copilot White Screen (All Ruled Out)
White-screen problems in Chromium and WebView2-based apps usually come from a few places, so we worked through them in order of likelihood.
GPU rendering. We tested with GPU acceleration disabled, using the --disable-gpu flag and the WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS environment variable. Nothing changed, and the app’s GPU process reported zero crashes.
The WebView2 runtime. It didn’t appear in the Installed Apps list, which looked suspicious. A registry check showed it was installed (machine-wide, version 157), and the files were present.
Corrupted app data. We renamed the app’s User Data profile folder so it would rebuild from scratch. The Copilot white screen remained.
Network and TLS interference. We tested connectivity to the endpoints the app uses, checked for proxies and a modified hosts file, and inspected the certificate issuer for the sign-in site. Everything connected normally, and the certificate came from Microsoft itself.
Crash logs. Event Viewer showed no faulting module. The app wasn’t crashing. It was running and rendering nothing.
The Detour
Our Appx package queries (Get-AppxPackage) found no Copilot at all, which suggested the app wasn’t installed. A running-process check then showed copilotapp.exe in C:\Program Files (x86)\Microsoft\Copilot\Application\. This was a standalone desktop install, not a Store package, so the Appx commands could never have found it. If a package query says an app doesn’t exist but the process is clearly running, trust the process.
The Clue in the Log
Launching the app with logging enabled gave us a log file. Most of it was harmless noise, but two details mattered:
- The app loaded its interface from
cr.m365copilotapp.svc.cloud.microsoft. - It then redirected to
login.microsoftonline.com, the Entra ID work and school sign-in service.
That isn’t the consumer Copilot. It’s the Microsoft 365 Copilot app, which is designed for work or school accounts.
The Actual Cause
The only account on the PC was a personal Hotmail address. A personal Microsoft account has nothing to sign into on the Microsoft 365 Copilot sign-in path, so the app sat on a blank window instead of showing an error. The dsregcmd /status output matched this: the PC wasn’t joined to any organization, and no work account was listed under Settings > Accounts > Access work or school.
Fixing the Copilot White Screen
- Remove the Microsoft 365 Copilot app. Its folder was locked, so we booted into Safe Mode and deleted
C:\Program Files (x86)\Microsoft\Copilotand the profile data under%LOCALAPPDATA%\Microsoft\Copilot. Use the normal uninstaller first if you can. - Exit Safe Mode (
msconfig> Boot tab > uncheck Safe boot). The Microsoft Store doesn’t work properly in Safe Mode. - Install the consumer Microsoft Copilot from the Store. Here the Store claimed Copilot was already installed, which was stale state from the manual deletion. A forced install fixed it:
powershell
winget install --id 9NHT9RB2F4HD --source msstore --force --accept-package-agreements --accept-source-agreements
- Sign in with the personal account. Copilot worked.
Cleanup
We removed the GPU test variable, since it was no longer needed:
powershell
[Environment]::SetEnvironmentVariable("WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS", $null, "User")
We also deleted the leftover User Data.old folder from the profile rename test.
Takeaways
- Check which Copilot you have. The consumer Copilot works with personal Microsoft accounts. The Microsoft 365 Copilot app expects a work or school account, and signing into the wrong one can cause a Copilot white screen instead of an error.
- Read the log for hostnames, not just errors. The domain the app was loading told us more than any error string.
- Test the whole chain. Our early network tests only hit
copilot.microsoft.com, not the domains the app actually used. - Don’t treat one empty command result as proof. A missing Installed Apps entry, silent
--versionoutput, and an empty package query each looked like a finding, and none were. - Check the simple explanation first. A mismatched account type is cheaper to test than a GPU driver.
If you’re stuck on a Copilot white screen on a client machine, start with what the app is, which account it expects, and where it’s loading content from. The fix may be a different app, not a repair.

Leave a Reply