KB5101684 is the July 2026 preview update for Windows 11, delivered as build 26200.8968 on version 25H2 and build 26100.8968 on version 24H2. It’s a Release Preview Channel update, meaning it ships to Windows Insiders and to anyone who’s opted into “get the latest updates as soon as they’re available” before rolling out more broadly as an optional non-security update. Because it travels through the Release Preview pipeline rather than the mainstream Patch Tuesday channel, it tends to hit more download and installation snags than a standard cumulative update.

If you’re here, you’ve probably already seen one of these symptoms: the update sits at 0% or 35% and never moves, Windows Update throws a generic error code after a failed install attempt, the PC reboots but never actually applies the update, or it installs and then silently rolls back on the next restart. Any Windows 11 24H2 or 25H2 device enrolled in the Release Preview ring can hit this, and it shows up on both consumer and managed machines.

In this article, I’ll walk through why this specific update fails to install, then go fix by fix —KB5101684 Not Installing starting with the quick wins and working up to registry, Device Manager, and BIOS-level troubleshooting for the stubborn cases.

Why KB5101684 Not Installing

A handful of root causes account for almost every failed install of this specific update.

  • Corrupted Windows Update components. The SoftwareDistribution and Catroot2 folders cache update metadata, and a single damaged entry can block the whole install.
  • Interrupted download. Release Preview builds are large cumulative packages; an unstable connection or a background app throttling bandwidth can leave a partial download that Windows can’t apply.
  • Pending reboot from a prior update. If build 26100.8942/26200.8942 (the initial, later-corrected build number for this same rollout) never fully finished applying, KB5101684 can’t stack on top of it.
  • Third-party antivirus interference. Some security suites quarantine or block files inside the update staging folder.
  • Low disk space. Cumulative Windows 11 updates routinely need 15–20 GB of free space during staging, even though the final footprint is smaller.
  • Driver conflicts, especially with GPU or storage drivers that hook low-level system calls.
  • Corrupted system files in the WinSxS component store, detectable with DISM and SFC.
  • Group Policy or WSUS restrictions on managed devices blocking Insider/Release Preview content.
  • TPM or Secure Boot state changes that were made after enrollment, which can cause install validation to fail.
  • Windows Update service not running or set to a startup type that prevents background installation.

Expert Tip: Before touching anything else, check whether you’re still enrolled in the Release Preview channel under Settings > Windows Update > Windows Insider Program. If your enrollment lapsed or got reset by a prior feature update, KB5101684 Not Installing may appear to “not install” simply because it’s no longer being offered to your device.

Step-by-Step Fixes

Fix 1: Run Windows Update Troubleshooter

Problem explanation: Windows Update sometimes gets stuck due to a corrupted download token, a stalled service, or a leftover job from a previous update attempt.

Why this fix works: The built-in troubleshooter automatically resets the most common blockers — stuck downloads, orphaned update jobs, and permission issues on the update cache — without you having to diagnose which one applies.

Step-by-step instructions:

  1. Open Settings > System > Troubleshoot > Other troubleshooters.
  2. Find Windows Update and click Run.
  3. Let it scan and apply any fixes it finds.
  4. Restart the PC and retry the update from Settings > Windows Update > Check for updates.

Expected result: The update either downloads cleanly or gives a more specific error code you can search for.

Possible side effects: None — this tool only resets update state, it doesn’t touch personal files.

When to skip this fix: If you’ve already run it twice with no change, move on rather than repeating it a third time.

Windows Update Troubleshooter

Fix 2: Reset Windows Update Components (SoftwareDistribution & Catroot2)

Problem explanation: These two folders store cached update metadata and cryptographic catalog files. If either becomes corrupted, updates fail silently or with vague error codes.

Why this fix works: Renaming (not deleting) these folders forces Windows Update to rebuild them from scratch on the next scan, clearing out any corrupted cache entries.

Step-by-step instructions:

  1. Open Command Prompt as Administrator.
  2. Stop the update-related services:
   net stop wuauserv
   net stop cryptSvc
   net stop bits
   net stop msiserver
  1. Rename the cache folders:
   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
   ren C:\Windows\System32\catroot2 catroot2.old
  1. Restart the services:
   net start wuauserv
   net start cryptSvc
   net start bits
   net start msiserver
  1. Reboot and check for updates again.

Expected result: Windows rebuilds a fresh update cache and re-downloads KB5101684 from scratch.

Possible side effects: Update history in Settings may briefly show as empty until the new cache repopulates — this is cosmetic only.

When to skip this fix: If you’re on a metered or capped connection, since this forces a full re-download of the update package.

CMD
CMD

Fix 3: Run SFC and DISM to Repair System Files

Problem explanation: Damaged system files in the WinSxS component store can block cumulative updates from applying, since the update needs to modify files that are already corrupted or missing.

Why this fix works: DISM repairs the underlying component store using a known-good source (Windows Update or a mounted image), and SFC then verifies individual protected system files against that repaired store.

Step-by-step instructions:

  1. Open Command Prompt as Administrator.
  2. Run DISM first:
   DISM /Online /Cleanup-Image /RestoreHealth
  1. Once it completes, run SFC:
   sfc /scannow
  1. Reboot regardless of the result, then retry the update.

What each command does:

  • DISM (Deployment Image Servicing and Management) repairs the Windows component store itself — the underlying files that Windows and its updates rely on.
  • SFC (System File Checker) compares your active system files against a protected reference copy and replaces any that don’t match.

Expected result: Both tools report “no integrity violations” or confirm they repaired the corruption they found.

Possible side effects: None; this is a repair-only operation.

When to skip this fix: If DISM fails with a source error, you may need to run it against a mounted ISO instead of Windows Update — that’s a separate, more advanced step.

Fix 4: Free Up Disk Space

Problem explanation: Cumulative updates for 24H2/25H2 stage a full copy of changed system files before applying them, which temporarily needs significantly more space than the final installed size.

Why this fix works: Windows Update silently fails or stalls when it can’t allocate enough space to complete staging, and it doesn’t always surface a clear “low disk space” error.

Step-by-step instructions:

  1. Open Settings > System > Storage.
  2. Run Storage Sense or manually clear Temporary files and Windows Update Cleanup.
  3. Aim for at least 20 GB free on the system drive before retrying.
  4. Retry the update.

Expected result: The update proceeds past the staging phase instead of stalling partway through.

Possible side effects: None, provided you only clear temporary/cache categories.

When to skip this fix: If you already have well over 20 GB free — the bottleneck is elsewhere.

Fix 5: Temporarily Disable Third-Party Antivirus

Problem explanation: Some third-party security suites scan or quarantine files inside the Windows Update staging directory, which can corrupt the install package mid-download.

Why this fix works: Disabling real-time protection removes the interference during the download-and-stage phase; Windows Defender doesn’t cause this issue since it’s designed to work alongside Windows Update.

Step-by-step instructions:

  1. Open your antivirus software and disable real-time/on-access scanning temporarily.
  2. Retry the KB5101684 install.
  3. Re-enable protection immediately afterward.

Expected result: The update downloads and applies without being flagged or blocked mid-process.

Possible side effects: Your PC is briefly less protected — stay off untrusted sites during this window.

When to skip this fix: If you’re only using Windows Defender, since this isn’t typically the cause.

Fix 6: Reset Network Stack

Problem explanation: A corrupted Winsock catalog or DNS cache can interrupt the download portion of the update, leaving a partial package that fails validation.

Why this fix works: Resetting these components clears out misconfigured or corrupted network state without affecting your saved Wi-Fi passwords or IP settings.

Step-by-step instructions:

  1. Open Command Prompt as Administrator.
  2. Run:
   netsh winsock reset
   ipconfig /flushdns
   ipconfig /release
   ipconfig /renew
  1. Restart the PC.
  2. Retry the update.

What each command does:

  • netsh winsock reset rebuilds the Winsock catalog, which handles network communication for apps and services including Windows Update.
  • ipconfig /flushdns clears cached DNS entries that might be pointing to a stale or unreachable update server.
  • ipconfig /release and /renew force your PC to request a fresh IP address from your router.

Expected result: Downloads complete without stalling or timing out.

Possible side effects: VPN software occasionally needs reinstalling after a Winsock reset — a known, minor side effect.

When to skip this fix: If other downloads on the same network are working fine — the issue likely isn’t network-related.

Fix 7: Update via PowerShell / PSWindowsUpdate

Problem explanation: The Settings app update engine occasionally gets stuck in a state that a fresh command-line session can bypass entirely.

Why this fix works: PSWindowsUpdate talks to the update service directly, sidestepping any UI-level state that’s causing the Settings app to hang.

Step-by-step instructions:

  1. Open PowerShell as Administrator.
  2. Install the module if you don’t have it:
   Install-Module PSWindowsUpdate -Force
  1. Scan and install:
   Get-WindowsUpdate
   Install-WindowsUpdate -AcceptAll -AutoReboot

Expected result: KB5101684 downloads and installs through the command line even if the Settings app was stuck.

Possible side effects: None; this uses the same underlying update engine as Settings.

When to skip this fix: On a managed/corporate device where PowerShell module installation is restricted by policy.

Fix 8: Use winget to Check for Pending System Updates

Problem explanation: Occasionally a pending app or runtime update (like a Microsoft Store dependency) blocks a Windows Update install from finalizing.

Why this fix works: winget can surface and resolve pending package updates that the Windows Update engine is waiting on before it will proceed.

Step-by-step instructions:

  1. Open PowerShell or Terminal.
  2. Run:
   winget upgrade --all
  1. Let all pending app updates finish, then reboot and retry KB5101684.

Expected result: Removes an unrelated pending-update conflict that was silently blocking the OS update queue.

Possible side effects: None beyond apps updating to their latest versions.

When to skip this fix: If winget upgrade --all returns no pending updates — this isn’t your bottleneck.

Registry Fix (Use With Caution)

Purpose: Clear a stuck “PendingXmlIdentifier” or reboot-required flag that can block a new cumulative update from applying even after a restart.

⚠️ Backup warning: Export the registry key before editing it (File > Export in Registry Editor) or create a System Restore point first. An incorrect registry edit can cause boot issues.

Registry path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired

Value: If this key exists and a reboot has already been completed, delete the RebootRequired key entirely (not the parent folder).

Restart requirement: Yes — restart immediately after making this change, before attempting the update again.

Windows Settings Fix

Navigate to each of these in order and confirm the settings match:

  • Settings > Windows Update > Windows Insider Program — confirm you’re still enrolled in the Release Preview Channel.
  • Settings > Windows Update > Advanced options > Additional settings — make sure “Pause updates” is off.
  • Settings > System > Recovery — confirm no pending recovery action is queued.
  • Settings > Apps > Startup — temporarily disable non-essential startup apps that might interfere with the install (some cloud sync or overlay tools lock files mid-update).
Windows update
Windows update

Device Manager Fix

Driver conflicts, especially around storage controllers and GPUs, can block a cumulative update from completing.

  1. Open Device Manager.
  2. Expand Display adapters and Storage controllers.
  3. Right-click each device and choose Update driver > Search automatically.
  4. If a driver shows a yellow warning icon, right-click it and select Uninstall device, then reboot to let Windows reinstall a clean version.
  5. Retry the update.
device manger
device manger

BIOS / UEFI Fix (Only If Needed)

This step is only necessary if TPM or Secure Boot validation errors appear during the install attempt (visible in Event Viewer under the WindowsUpdateClient log).

  1. Reboot into BIOS/UEFI (usually Del, F2, or F10 at startup — check your motherboard manual).
  2. Confirm TPM 2.0 is enabled (sometimes listed as “PTT” on Intel or “fTPM” on AMD).
  3. Confirm Secure Boot is enabled.
  4. Save and exit, then retry the update from Windows.
BIOS UEFI

Advanced Fixes

If nothing above resolves it:

  • Manual install via Microsoft Update Catalog. Search “KB5101684” on the Microsoft Update Catalog site and download the matching .msu package directly for your architecture (x64 or ARM64), then install it manually.
  • Clean boot troubleshooting. Boot with only Microsoft services running (msconfig > Services > Hide all Microsoft services > Disable all) to rule out a third-party service conflict.
  • In-place repair install. As a last resort, use Media Creation Tool to run a repair install that keeps your files and apps but replaces system files entirely.

Prevent This Problem in Future

  • Keep at least 20–30 GB of free disk space at all times if you’re on the Release Preview or Beta channel.
  • Run sfc /scannow monthly as routine maintenance rather than only when something breaks.
  • Avoid installing a new preview build while another update is still pending a restart.
  • If you’re not actively testing preview features, consider switching from Release Preview back to the standard update channel for a more stable install experience.

Final Summary

KB5101684 failing to install on Windows 11 24H2 or 25H2 almost always traces back to a handful of causes: a corrupted update cache, insufficient disk space, a pending reboot from an earlier build, third-party antivirus interference, or a driver conflict. Working through the fixes in order — starting with the troubleshooter and update component reset, then SFC/DISM, then network and driver checks — resolves the vast majority of cases without needing to touch the registry or BIOS. If you’ve gone through every fix here and it’s still stuck, a manual install from the Microsoft Update Catalog is the most reliable fallback.