ErrorVaultHQ

Solved Error

How to Fix: KB5101650 Failed to Install (Windows 11)

Quick Fix

Most KB5101650 install failures are fixed by resetting the Windows Update components and installing the file manually: 1. Restart your PC, then go to Settings > Windows Update and click Check for updates again — many failures resolve on a second try. 2. If it still fails, run the built-in Windows Update Troubleshooter (Settings > System > Troubleshoot > Other troubleshooters). 3. If that doesn't work, download the matching KB5101650 package from the Microsoft Update Catalog and install it manually as administrator.

What this error means

KB5101650 is the July 2026 Patch Tuesday cumulative update for Windows 11, moving systems to build 26100.8875 (24H2) or 26200.8875 (25H2). It is the mandatory July 2026 security update for Windows 11 24H2 and Windows 11 25H2, upgrading PCs to Build 26100.8875 or Build 26200.8875, depending on the installed version of Windows. An 'install failed' message generally means Windows Update could not download, unpack, or apply the update package. Common causes include corrupted update files, insufficient storage, damaged system components, incompatible drivers, VPN software, or an incomplete previous update. Some users also see specific error codes; for example, the update is failing with error 0x800f0841 on Windows 11 version 25H2 for one reported case, while error 0x80073712 is also common. 0x80073712 usually indicates missing or corrupted system files needed by the update. Separately, Microsoft has also put a compatibility block on some Dell PCs — this is different from a normal install failure. Microsoft has blocked the Windows 11 KB5101650 update on a limited number of Dell PCs after confirming a compatibility issue that can cause unexpected shutdowns, poor performance, increased heat, and battery drain. If you're on an affected Dell device, the update simply won't appear at all — that's expected, not an error to fix.

Step-by-Step Guide

Fix 1: Basic checks (restart, space, connection)

  1. 1Restart your PC first — this clears stuck update processes.
  2. 2Check free disk space. Windows 11 needs enough free space to download, unpack, and install KB5101650. If your system drive (C:) is almost full, the update may remain stuck at 0%, fail to download, or display installation errors. Aim for at least 15-20GB free. Press Windows + E, select This PC, and check space on Local Disk (C:).
  3. 3Free up disk space. If low, run Disk Cleanup, remove Delivery Optimization files, uninstall unused apps, or move large files off the drive.

Fix 2: Run the Windows Update Troubleshooter

  1. 1Access the troubleshooters menu. Go to Settings > System > Troubleshoot > Other troubleshooters.
  2. 2Run Windows Update troubleshooter. Find Windows Update and click Run, then follow the prompts.
  3. 3Restart and check for updates. Restart the PC and check for updates again.

Fix 3: Reset the Windows Update components manually

  1. 1Open Command Prompt as Administrator.
  2. 2Stop the update services by running: net stop bits, net stop wuauserv, net stop cryptsvc.
  3. 3Rename the update cache folders so Windows rebuilds them: ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak and ren %systemroot%\System32\catroot2 catroot2.bak.
  4. 4Restart the Windows Update services. Restart the services: net start bits, net start wuauserv, net start cryptsvc.
  5. 5Restart the PC and check for updates again. This recreates Windows Update's working folders and often resolves update installation loops.

Fix 4: Install KB5101650 manually from the Microsoft Update Catalog

  1. 1Check your system architecture. Check your system type first: Settings > System > About, note whether you're on x64 or ARM64.
  2. 2Search for KB5101650 online. Go to the Microsoft Update Catalog website and search KB5101650.
  3. 3Download the matching .msu package. Download the .msu package matching your build and architecture.
  4. 4Install the downloaded update file. Right-click the downloaded file and choose Open, then confirm the install prompt.
  5. 5Wait for it to finish (5-15 minutes) and restart when prompted. Installing the standalone package often succeeds even when the normal Windows Update process keeps failing, since it bypasses a corrupted download/cache.

Fix 5: Check Reliability Monitor and run a clean boot

  1. 1Open Reliability Monitor. Press Win + R, type perfmon /rel, and press Enter to open Reliability Monitor.
  2. 2Look for failure entries in logs. Look for red X entries around the time KB5101650 failed to identify the exact conflicting component.
  3. 3Perform a clean boot and retry. If a third-party app or security software seems to interfere, perform a clean boot (via msconfig, disable all non-Microsoft services and startup items) and retry the update. This helps determine whether a third-party service or security software is interfering with installation.
  4. 4Disable third-party antivirus temporarily. Temporarily disable third-party antivirus during the update if you suspect it is blocking installation, then re-enable it afterward.

Fix 6: Cause: Dell / Intel IPF driver compatibility block (not a normal failure)

  1. 1Check for Intel IPF driver warning. Check Device Manager for a yellow exclamation mark on the Intel Innovation Platform Framework Processor Participant driver. Affected PCs will show this warning and can experience unexpected shutdowns, poor performance, increased heat, and battery drain.
  2. 2Understand the Dell compatibility block. If you have a Dell PC and KB5101650 simply doesn't appear in Windows Update, this is intentional — Microsoft has blocked KB5101650 from being pushed to affected Dell systems through Windows Update, and committed to releasing a fix in the coming days.
  3. 3Do not manually install on affected Dell PCs. Do not force-install it manually from the Update Catalog in this case — Microsoft's guidance is not to manually install KB5101650 on affected Dell devices and to wait for the official fix instead.
  4. 4Microsoft later shipped an out-of-band fix, KB5121767, for this specific issue. Check Settings > Windows Update > Update history for it, and install it if offered — affected PCs can install KB5121767 when Windows Update offers it, while unaffected devices need no action.
  5. 5Roll back if experiencing shutdowns. If you already installed the June preview (KB5095093) and are seeing shutdowns/overheating on a Dell PC, the recommended path is to roll back to the previous update until the fix is applied.

In-place repair upgrade (last resort before contacting support)

Download the latest Windows 11 installation media (ISO) tool from Microsoft's official site. Run setup.exe from the mounted ISO and choose Keep personal files and apps. This reinstalls Windows while keeping your files, apps, and most settings, and often resolves persistent Windows Update problems without requiring a clean install.

When to seek more specific help

If Reliability Monitor or Update history shows a specific error code (e.g. 0x800f0841, 0x80073712) that isn't resolved by the steps above, search or report that exact code — different codes point to different root causes (corrupted files, driver conflicts, disk issues). If a new problem appeared only after KB5101650 (e.g. keyboard/Windows key stops responding, BSOD, or the PC won't boot), uninstalling the update via Settings > System > Recovery and pausing updates is a reasonable temporary fix while waiting for Microsoft's follow-up patch — but remember uninstalling a security update also removes its fixes. For business/enterprise deployment scenarios (WSUS, deployment media), a separate error, 0xc0430001, can occur if KB5101650 is applied as a dynamic update without the required boot.stl file — this needs an IT admin to correct the deployment media rather than an end-user fix. If none of these steps work, or your device becomes unusable, contact Microsoft Support (or Dell Support with your Service Tag, if hardware-specific) for personalized troubleshooting.

Sources:

Heads up: this guide was drafted with AI assistance from the real sources listed below, and structured by our team for clarity. It may not cover every possible cause — if it doesn't fix your issue, let us know and we'll take a closer look. See how we create our fixes.

Was this fix helpful?

Related Error Fixes