Windows 11 KB5094126: Fix BSODs, BitLocker Lockouts, and OneDrive Errors

Windows 11 · 6 min read · Target: windows 11 kb5094126 fix · Updated September 2026

If your PC has blue-screened, rebooted into a BitLocker recovery prompt, or suddenly can't open OneDrive or Office after a recent update, the cause is very likely KB5094126, the update Microsoft pushed out as part of June 2026 Patch Tuesday. It's been one of the messier updates this year, and Microsoft has only partially patched the fallout so far. Here's what's actually going on and what you can do about it today, without waiting for an official fix.

What this update actually breaks

Reports since the June rollout point to a consistent pattern: File Explorer and OneDrive suddenly failing to open, Office applications refusing to launch, and — on a smaller but more alarming number of systems, especially HP machines — a blue screen with error code 0xc0430001 followed by a BitLocker recovery key prompt on the next boot. None of these mean your PC is broken; they're update-specific and reversible.

Fix it: what to try, in order

1. Step 1: Have your BitLocker recovery key ready before doing anything else

   If you haven't hit the recovery prompt yet, find your key now while you still can. Go to Settings → Privacy & Security → Device encryption, or check your Microsoft account at account.microsoft.com/devices/recoverykey. Write it down or save it somewhere outside this PC. This one step alone prevents the scariest part of this bug from turning into a real problem.

2. Step 2: Uninstall the update if you're already affected

   Go to Settings → Windows Update → Update history → Uninstall updates, find KB5094126, and remove it. This resolves the OneDrive, File Explorer, and Office launch failures for most affected systems within one restart.

3. Step 3: Pause updates until a proper fix ships

   In Windows Update, use "Pause updates for 7 days" (repeatable) to avoid the same update reinstalling itself automatically. Check Microsoft's release health dashboard before unpausing so you're not caught by the same issue twice.

4. Step 4: If you're on an affected Dell or HP system

   Some Dell configurations had a related driver conflict during this update cycle and had it withheld automatically — if you're on Dell hardware and haven't seen the update yet, that's likely intentional, not a problem to fix. HP systems seeing the BSOD should prioritize Step 2 above rather than waiting on an HP-side driver update.

Where things stand right now

Microsoft has acknowledged the OneDrive and Office issues and shipped a partial fix, but as of this writing the BitLocker/BSOD path on certain HP systems still doesn't have an official patch. Uninstalling and pausing is the safest move until that changes. If you're still stuck after these steps, check Microsoft's official release health page for your specific build number — the fix timeline is moving week to week, and it's worth confirming you're not chasing an issue that's already been resolved for your configuration.