KB5121767 is an out-of-band (OOB) cumulative update for Windows 11, released July 18, 2026. It moves devices to build 26200.8894 on version 25H2 and build 26100.8894 on version 24H2. Unlike a scheduled Patch Tuesday release, an out-of-band update ships outside the normal monthly cycle to fix a specific, urgent problem — in this case, it addresses a performance and power-behavior issue tied to the Intel Innovation Platform Framework (Intel IPF) driver, and it also unblocks a limited number of Dell devices that had been prevented from installing the earlier July update, KB5101650.

Because it’s cumulative, KB5121767 not installing carries every fix from prior updates plus this new correction, which means it’s a larger and more sensitive package than a small standalone patch — and that’s exactly why it’s more prone to installation trouble on certain configurations. If you’re dealing with a progress bar that won’t move, a failed install with an error code, or an update that installs and then reverts on reboot, you’re not alone, and this is fixable in the vast majority of cases without a full reinstall.

Why KB5121767 Fails to Install

  • It’s cumulative and large. Because it rolls in every prior fix plus the new Intel IPF correction, the staging footprint is bigger than a routine patch, which increases the odds of a disk space or corrupted-cache failure.
  • Servicing stack mismatch. KB5121767 pairs with servicing stack update KB5120102 (version 26100.8872); if the SSU hasn’t applied cleanly, the cumulative update can fail validation.
  • Device-specific blocking. Microsoft applied compatibility holds to certain Dell models before this fix — if your device was on a hold list, the update may show as unavailable rather than failing outright.
  • Intel IPF driver conflicts. Since this update specifically targets Intel IPF driver behavior, machines with an outdated or already-patched IPF driver can hit installation conflicts.
  • Corrupted Windows Update components in the SoftwareDistribution or Catroot2 folders.
  • Interrupted or throttled download, especially on metered or unstable connections.
  • Pending reboot left over from the prior update, KB5121767 not installing (build 26100.8875/26200.8875), blocking this one from stacking on top.
  • Third-party antivirus quarantining files inside the update staging directory.
  • Low disk space during the staging phase.
  • Damaged system files in the WinSxS component store.
  • Group Policy or WSUS restrictions on managed or enterprise devices.

Expert Tip: If you’re on an affected Dell system, check Settings > Windows Update > Update history first. If KB5121767 isn’t listed as offered at all, it may simply not have reached your device yet rather than having failed — Microsoft rolled this out gradually rather than to everyone simultaneously.

Step-by-Step Fixes

Fix 1: Run the Windows Update Troubleshooter

Problem explanation: A stalled download, a stuck update job, or a permissions issue on the update cache is often the reason a cumulative update refuses to progress.

Why this fix works: The built-in troubleshooter automatically detects and clears the most common blockers without requiring manual diagnosis.

Step-by-step instructions:

  1. Go to Settings > System > Troubleshoot > Other troubleshooters.
  2. Locate Windows Update and select Run.
  3. Apply any fixes it suggests.
  4. Restart and check for updates again.

Expected result: The update either installs cleanly or surfaces a specific error code you can act on.

Possible side effects: None.

When to skip this fix: If you’ve run it twice already with no change.

Fix 2: Verify the Servicing Stack Update Installed First

Problem explanation: KB5121767 depends on servicing stack update KB5120102 (version 26100.8872). If that SSU is missing or only partially applied, the cumulative update can fail during validation.

Why this fix works: The servicing stack is what actually installs Windows updates — if it’s outdated or broken, every update built on top of it can fail regardless of what else you fix.

Step-by-step instructions:

  1. Open Settings > Windows Update > Update history.
  2. Scroll to confirm KB5120102 (or a servicing stack update at version 26100.8872 or later) is listed as successfully installed.
  3. If it’s missing, search “KB5120102” on the Microsoft Update Catalog and install it manually first.
  4. Reboot, then retry KB5121767.

Expected result: KB5121767 installs cleanly once the servicing stack is current.

Possible side effects: None — SSUs only affect the update-installation mechanism itself.

When to skip this fix: If update history already confirms the SSU installed successfully.

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

Problem explanation: These folders cache update metadata and catalog signatures. A corrupted entry in either one can silently block installation.

Why this fix works: Renaming the folders forces Windows to rebuild a clean cache on the next update scan.

Step-by-step instructions:

  1. Open Command Prompt as Administrator.
  2. Stop the relevant services:
   net stop wuauserv
   net stop cryptSvc
   net stop bits
   net stop msiserver
  1. Rename the 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.

Expected result: A fresh update cache rebuilds and KB5121767 re-downloads cleanly.

Possible side effects: Update history in Settings briefly appears empty — cosmetic only.

When to skip this fix: On a metered connection, since this triggers a full re-download.

Fix 4: Run SFC and DISM

Problem explanation: Damaged files in the WinSxS component store can block a cumulative update from applying the changes it needs to make.

Why this fix works: DISM repairs the component store itself, and SFC then validates individual protected system files against it.

Step-by-step instructions:

  1. Open Command Prompt as Administrator.
  2. Run:
   DISM /Online /Cleanup-Image /RestoreHealth
  1. Then run:
   sfc /scannow
  1. Reboot and retry the update.

What each command does:

  • DISM repairs the underlying Windows component store that updates rely on.
  • SFC checks and replaces protected system files against a known-good reference.

Expected result: Both report no remaining integrity issues.

Possible side effects: None.

When to skip this fix: If DISM reports a source error — that needs a mounted ISO as the repair source instead, a separate advanced step.

Fix 5: Free Up Disk Space

Problem explanation: As a cumulative package, KB5121767 needs more staging space than its final installed size suggests.

Why this fix works: Windows Update can stall or fail silently when it can’t reserve enough space during staging.

Step-by-step instructions:

  1. Go to Settings > System > Storage.
  2. Run Storage Sense, and manually clear Temporary files and Windows Update Cleanup.
  3. Aim for at least 20 GB free before retrying.

Expected result: The update proceeds past staging instead of stalling.

Possible side effects: None.

When to skip this fix: If you already have well over 20 GB free.

Fix 6: Update the Intel IPF Driver Before Installing

Problem explanation: Since KB5121767 specifically targets Intel Innovation Platform Framework driver behavior, an outdated IPF driver can conflict with the update’s changes during install.

Why this fix works: Updating the driver first removes the exact component this update is designed to patch, reducing the chance of a conflict during installation.

Step-by-step instructions:

  1. Open Device Manager.
  2. Check under System devices or Software devices for an Intel IPF-related entry (naming varies by device manufacturer).
  3. Right-click and choose Update driver > Search automatically, or check your device manufacturer’s support page (Dell, Lenovo, HP, etc.) for the latest Intel IPF driver package.
  4. Reboot and retry the Windows update.

Expected result: The update installs without conflicting with an outdated driver version.

Possible side effects: None.

When to skip this fix: If Device Manager shows no Intel IPF-related device — this only applies to systems using that framework.

Fix 7: Temporarily Disable Third-Party Antivirus

Problem explanation: Some security suites scan or quarantine files inside the update staging folder mid-download.

Why this fix works: Removing that interference lets the update package download and stage without being flagged.

Step-by-step instructions:

  1. Open your antivirus software and disable real-time protection temporarily.
  2. Retry the KB5121767 install.
  3. Re-enable protection immediately after.

Expected result: The update completes without being blocked mid-process.

Possible side effects: Reduced protection during the window — avoid browsing unfamiliar sites.

When to skip this fix: If you’re only using Windows Defender.

Fix 8: Update via PowerShell / PSWindowsUpdate

Problem explanation: The Settings app’s update engine can get stuck in a state that a fresh command-line session bypasses.

Why this fix works: PSWindowsUpdate communicates with the update service directly, sidestepping any UI-level hang.

Step-by-step instructions:

  1. Open PowerShell as Administrator.
  2. Install the module:
   Install-Module PSWindowsUpdate -Force
  1. Scan and install:
   Get-WindowsUpdate
   Install-WindowsUpdate -AcceptAll -AutoReboot

Expected result: KB5121767 installs through the command line even if Settings was stuck.

Possible side effects: None.

When to skip this fix: On managed devices where module installation is restricted by policy.

Fix 9: Reset Network Stack

Problem explanation: A corrupted Winsock catalog or stale DNS cache can interrupt the download of a large cumulative package.

Why this fix works: Resetting these components clears corrupted network state without touching saved network credentials.

Step-by-step instructions:

  1. Open Command Prompt as Administrator.
  2. Run:
   netsh winsock reset
   ipconfig /flushdns
   ipconfig /release
   ipconfig /renew
  1. Restart and retry.

What each command does:

  • netsh winsock reset rebuilds the network communication catalog used by Windows Update and other apps.
  • ipconfig /flushdns clears cached DNS entries that could be stale.
  • ipconfig /release and /renew request a fresh IP address from your router.

Expected result: Downloads complete without stalling.

Possible side effects: VPN software occasionally needs reinstalling afterward.

When to skip this fix: If other downloads on the network work fine.

Registry Fix (Use With Caution)

Purpose: Clear a stuck reboot-pending flag that can prevent a new cumulative update from applying even after restarting.

⚠️ Backup warning: Export this registry key first (File > Export in Registry Editor) or set a System Restore point before editing.

Registry path:

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

Value: If the RebootRequired key still exists after a completed restart, delete that key only — not the parent folder.

Restart requirement: Yes, restart immediately after this change before retrying the update.

Windows Settings Fix

  • Settings > Windows Update > Update history — confirm whether KB5121767 shows as “Failed” (with an error code) or simply hasn’t been offered yet.
  • Settings > Windows Update > Advanced options > Additional settings — confirm “Pause updates” is off.
  • Settings > System > Recovery — check for any pending recovery action.
  • Settings > Apps > Startup — temporarily disable non-essential startup apps that could lock files during install.
  • Settings > Windows Update > Windows Insider Program — if you’re on Release Preview, confirm your enrollment is still active, since some builds are offered differently depending on channel.

Device Manager Fix

  1. Open Device Manager.
  2. Expand System devices, Storage controllers, and Display adapters.
  3. Right-click any device with a warning icon and choose Update driver > Search automatically.
  4. For a persistent conflict, right-click the device, select Uninstall device, then reboot to let Windows reinstall it cleanly.
  5. Retry the update.

BIOS / UEFI Fix (Only If Needed)

Only necessary if Event Viewer shows a TPM, Secure Boot, or firmware-related validation error during the install attempt.

  1. Reboot into BIOS/UEFI (commonly Del, F2, or F10 at startup).
  2. Confirm TPM 2.0 is enabled (PTT on Intel, fTPM on AMD).
  3. Confirm Secure Boot is enabled.
  4. Check for a pending motherboard/firmware update from your manufacturer, since some out-of-band Windows updates interact with firmware-level components.
  5. Save, exit, and retry.

Advanced Fixes

  • Manual install via Microsoft Update Catalog. Search “KB5121767” on the Microsoft Update Catalog and download the matching .msu package for your exact architecture (x64 or ARM64).
  • Clean boot troubleshooting. Use msconfig > Services > Hide all Microsoft services > Disable all to rule out a third-party service conflict.
  • Check for a compatibility hold. If you’re on an affected Dell model, confirm with Dell’s support site whether a driver update is required before the hold clears.
  • In-place repair install. As a last resort, run a repair install through the Media Creation Tool, which keeps your files and apps intact while replacing system files.

Prevent This Problem in Future

  • Keep at least 20–30 GB free at all times, since out-of-band cumulative updates often need more staging room than expected.
  • Confirm the servicing stack update is current before applying any cumulative update, especially out-of-band ones.
  • Keep device-specific drivers (like Intel IPF) current through your manufacturer’s support site rather than relying solely on Windows Update.
  • Avoid installing a new update while a prior one is still pending a restart.

Final Summary

KB5121767 failing to install on Windows 11 24H2 or 25H2 usually comes down to one of a few things: a missing or incomplete servicing stack update, a corrupted update cache, insufficient disk space for this larger cumulative package, an outdated Intel IPF driver, or a pending reboot from the prior update. Working through the fixes here in order — starting with the troubleshooter, confirming the servicing stack, then clearing the update cache and running SFC/DISM — resolves the majority of installation failures. If you’re on an affected Dell system and it still won’t show up, a manual install from the Microsoft Update Catalog remains the most reliable path forward.