KB5083769: 6 Proven Fixes and What It Changes

Written by: Kymakers Support Team · Reviewed by: Kymakers Technical Team Last updated: July 2026 · Applies to: Windows 11 versions 24H2 and 25H2 (OS Builds 26100.8246 / 26200.8246) Difficulty: Intermediate · Estimated time: 30–90 minutes

KB5083769 is the April 14, 2026 cumulative security update for Windows 11 24H2 and 25H2, taking the OS to build 26100.8246 or 26200.8246. It’s a mandatory Patch Tuesday release that patched 167 vulnerabilities across Microsoft’s ecosystem, and it also serves as the Q2 2026 hotpatch baseline — which means a restart is required this month even on hotpatch-eligible devices.

It fixes several genuinely annoying problems from earlier updates, including the “Reset this PC” error. But some users reported boot loops and BSODs after installing, and Microsoft documented a BitLocker known issue worth reviewing before wide deployment. This guide covers what KB5083769 changes and six proven fixes if it causes trouble.

⚠️ Before deploying widely

KB5083769 is a security update — install it. But if you manage multiple machines, validate on a test device first. Microsoft documented a BitLocker known issue that matters in environments using custom BitLocker policy settings, and community reports described boot loops on some hardware. For a single home PC that installed cleanly and is running fine, do nothing.

Table of Contents

1. What KB5083769 fixes and changes
2. Fix 1: Check the BitLocker known issue first
3. Fix 2: If the PC is stuck in a boot loop
4. Fix 3: If it fails to install
5. Fix 4: Roll back safely
6. Fix 5: Repair with SFC and DISM
7. Fix 6: In-place repair as a last resort
8. Should you install it?
9. FAQ

What KB5083769 Fixes and Changes

KB5083769 rolls in the fixes from March’s releases (KB5079473, KB5085516, and the out-of-band KB5086672 that replaced the pulled KB5079391), plus its own additions:

• “Reset this PC” fixed — the error introduced by an earlier March hotpatch update is resolved, which matters if you were unable to reset a PC.
• Secure Boot status visibility — certificate update status now appears in the Windows Security app (Settings → Privacy & security → Windows Security), and the update addresses a case where a device could enter BitLocker Recovery after Secure Boot updates.
• SMB over QUIC — compression requests complete more consistently, reducing timeouts.
• Remote Desktop phishing protection — opening an .rdp file now shows all requested connection settings up front, each disabled by default.
• Smart App Control — can be turned on or off without reinstalling Windows.
• Narrator — image descriptions now use Copilot, available on all devices.

Confirm KB5083769 installed by running winver — build 26100.8246 (24H2) or 26200.8246 (25H2).

Fix 1: Check the BitLocker Known Issue First

Before deploying KB5083769 across managed machines, review Microsoft’s documented BitLocker known issue. It’s most relevant in enterprise environments using custom BitLocker policy settings.

The practical precaution: have your BitLocker recovery keys accessible before you update. If a device does enter BitLocker Recovery, you’ll need the 48-digit key to get back in — and without it, the data isn’t recoverable by anyone. Our guide on finding your BitLocker recovery key covers all six places to look, including aka.ms/myrecoverykey.

For a managed fleet, confirm keys are escrowed to Azure AD before rollout. For a home PC, check they’re backed up to your Microsoft account. This takes five minutes and prevents the worst outcome.

Fix 2: If the PC Is Stuck in a Boot Loop

Community reports described systems restarting into boot loops or BSODs after installing KB5083769, with recovery screens returning them to the same failure. If that’s your situation:

1. Force the recovery environment — power on and interrupt the boot twice; the third start enters WinRE automatically.
2. Go to Troubleshoot → Advanced options → Uninstall Updates → Uninstall latest quality update.
3. Reboot and let Windows start normally.

If WinRE itself won’t load, boot from Windows installation media and use the repair options there. Check Microsoft’s Windows release health dashboard for the current status before assuming it’s your hardware — if an out-of-band fix has shipped since, installing it is better than staying rolled back.

Fix 3: If It Fails to Install

Install failures on a cumulative update usually mean component-store corruption. Work through these in order:

1. SFC and DISM — from an admin Command Prompt: sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth. Reboot and retry.
2. Manual install — download KB5083769 from the Microsoft Update Catalog and install the .msu directly, bypassing Windows Update.
3. Clear the update cache — stop the Windows Update and BITS services, clear the SoftwareDistribution folder, restart the services, and check again.
4. Free up disk space — a combined SSU + LCU package needs several gigabytes free to stage.

Note that error 0x80073712 was widespread on the March updates; the same repair sequence applies here.

Fix 4: Roll Back Safely

If KB5083769 destabilised your PC and you can still boot, roll it back from within Windows:

Settings → Windows Update → Update history → Uninstall updates → select KB5083769 → Uninstall.

Treat this as temporary. It’s a security update covering 167 vulnerabilities, so staying without it leaves you exposed. Pause updates for a week or two while you wait for a corrected build, then reinstall. Don’t permanently block a security update as a fix.

Fix 5: Repair With SFC and DISM

If KB5083769 installed but the system became unstable — crashes, corrupted apps, odd behaviour — system file corruption is a common cause and these tools repair it:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Run SFC first, then DISM, then SFC again, rebooting between. Also update your display and storage drivers, since driver conflicts are a frequent cause of post-update instability that gets blamed on the update itself.

Fix 6: In-Place Repair as a Last Resort

When rolling back doesn’t restore stability and SFC/DISM come back clean, an in-place repair replaces system components wholesale while keeping your files and apps.

Mount an ISO of your exact Windows 11 version, run setup, and choose to keep files and apps. Back up first. This resolves deep servicing damage that normal repairs can’t reach, and it’s far less disruptive than a clean install. Afterwards, let Windows Update install KB5083769 normally.

Should You Install It?

Yes. KB5083769 patched 167 vulnerabilities and fixed real problems from earlier updates — skipping it isn’t sensible.

The nuance is how you deploy it. On a single home PC: install it, and make sure your BitLocker recovery key is backed up first. On managed machines: validate on a test device, confirm BitLocker keys are escrowed, review Microsoft’s known-issue documentation, then roll out. And remember the restart requirement this month, even on hotpatch-eligible devices.

If you already installed it and everything works, you’re done — leave it alone.

FAQ About KB5083769

What build does KB5083769 install? OS Build 26100.8246 on Windows 11 24H2, or 26200.8246 on 25H2. Check with winver.

What does KB5083769 fix? It patched 167 vulnerabilities and fixed the “Reset this PC” error from an earlier March update, improved SMB compression over QUIC reliability, strengthened Remote Desktop .rdp phishing protection, and added Secure Boot certificate status visibility.

Is KB5083769 causing boot loops? Some users reported boot loops and BSODs after installing. If affected, boot into WinRE (interrupt startup twice; the third boot enters recovery) and uninstall the latest quality update. Check Microsoft’s release health dashboard for current status.

Does KB5083769 have a BitLocker issue? Microsoft documented a BitLocker known issue relevant to environments with custom BitLocker policy settings. Back up your recovery keys before updating, and review the documentation before wide deployment.

Do I need to restart for KB5083769? Yes. It’s the Q2 2026 hotpatch baseline, so a restart is required this month even on hotpatch-eligible devices that normally avoid one.

Can I skip KB5083769? Not advisable — it covers 167 vulnerabilities. If it causes problems, roll back temporarily and reinstall once a corrected build is available, rather than blocking it permanently.

If a KB5083769 problem forces a clean reinstall and you need to reactivate Windows, Kymakers supplies genuine Windows 11 Pro and Windows 11 Home keys with instant delivery and activation support. Our guide to downloading, installing, and activating your Microsoft license covers the process, and no operating system installed helps if the PC won’t boot at all.

Back up your BitLocker key first. Install it. If it breaks something, roll back temporarily — then patch forward rather than staying exposed.

Official reference: April 14, 2026—KB5083769 — Microsoft Support