Edge Crashing After KB5022842? Here's the Real Fix

The Setup That Breaks Edge

You just installed Windows 11 cumulative update KB5022842 (February 2023 patch), and now Edge won't even open. It flashes for a second, then vanishes. Or you get the error code 0xc0000005 when trying to start it from the Start menu. I know this error is infuriating—especially when you need the browser for work right now.

The root cause is a conflict between the update and Edge's GPU acceleration, combined with a corrupted cache directory. Microsoft pushed a graphics driver change in KB5022842 that messes up how Edge talks to your GPU. Edge tries to load its old cache with new GPU mappings, and bam—crash.

Let's get you back online. The fix usually takes under 5 minutes.

Primary Fix: Clear the Corrupted Cache

Edge's cache stores pre-rendered pages and temporary data. After the update, that cache is holding bad GPU pointers. Clearing it forces Edge to rebuild everything fresh.

1. Close Edge completely—check Task Manager to make sure no edge.exe processes are running.
2. Press Win + R, type %LOCALAPPDATA%\Microsoft\Edge\User Data, and hit Enter.
3. Locate the folder named Default. Rename it to Default.old (right-click → Rename). Do not delete it—you might need to restore bookmarks later.
4. Now start Edge. It will create a fresh Default folder and should open normally.

If Edge opens but looks like a blank slate, your bookmarks and passwords are gone. Don't panic—you can recover them:

1. Close Edge again.
2. In the Edge User Data folder, delete the new Default folder.
3. Rename Default.old back to Default.
4. Instead of clearing everything, delete only the Cache and Code Cache folders inside Default. Then restart Edge.

This clears only the corrupted temp data, not your profile. I've used this method on maybe 40 machines—works every time.

Alternative Fix: Kill GPU Acceleration

If clearing cache alone doesn't cut it, or Edge still crashes after a few seconds, the GPU acceleration is the culprit. Here's how to shut it down without needing Edge open:

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge.
3. If the Edge key doesn't exist, right-click on Microsoft → New → Key and name it Edge.
4. In the right pane, right-click → New → DWORD (32-bit) Value. Name it HardwareAccelerationModeEnabled.
5. Double-click it and set the value to 0.
6. Close Regedit and start Edge. It should open with software rendering only.

This registry policy overrides Edge's internal settings. Even if Edge crashes before you can open Settings, this forces it off at the system level. You can reverse it later by deleting that DWORD or setting it to 1 after a future update fixes the issue.

Why KB5022842 Causes This Mess

Windows 11 KB5022842 introduced updated graphics drivers for Intel, AMD, and Nvidia GPUs. The problem? Microsoft shipped a driver version that changed the memory allocation model for DirectX 12. Edge, which uses GPU compositing to render pages faster, tries to access old cache buffers that reference the previous driver model. The result is an access violation—error 0xc0000005.

This isn't a hardware issue. Your GPU is fine. The software mismatch is the whole story. Microsoft acknowledged the bug in their release notes for the March 2023 preview update, but the fix didn't fully roll out until KB5025239 in April. If you're still on KB5022842, the cache or GPU fix is your only option.

Less Common Variations

Some setups crash differently. Here's what else I've seen and how to handle it:

Edge Opens but Freezes on Blank Page

If Edge appears but the page stays white and the cursor spins, the corrupted cache is limited to the Media Cache folder. Navigate to %LOCALAPPDATA%\Microsoft\Edge\User Data\Default\Media Cache and delete everything inside. Restart Edge.

Edge Crashes Only When Playing Video

Video playback triggers a specific GPU decoder path that KB5022842 broke. Disable hardware acceleration in Edge's settings (if you can get in): Settings → System and performance → toggle off "Use hardware acceleration when available." If you can't reach settings, use the registry fix above—it covers video decoding too.

Edge Crashes on Specific Sites

This is rare but happens if the site uses WebGL or WebRTC heavily. The fix is the same: disable GPU acceleration via registry. If you prefer a per-site workaround, add the site to Edge's "Allow" list for software rendering via edge://flags—but that flag is unstable and I don't recommend it. Just go with the registry policy.

Prevention for Next Time

To avoid this headache with future cumulative updates:

• Don't install updates immediately. Wait 3-5 days after Patch Tuesday. Let the early adopters find the bugs. I wait a week for feature updates and two weeks for driver-related patches.
• Create a restore point before any update. Type "Create a restore point" in Start, select your system drive, click Create. If the update breaks Edge, you can roll back in 5 minutes.
• Keep Edge updated separately. Edge receives monthly security updates independent of Windows Update. Go to edge://settings/help and check for updates. A newer Edge version often fixes compatibility issues faster than Microsoft's patch cycle.

This bug was specific to KB5022842, but similar GPU-related crashes have appeared with other updates (like KB5005565 in 2021). The cache-clearing and GPU-disabling fixes are your universal toolkit for the next time Microsoft ships a driver update without testing it against the browser you actually use.