|

Microsoft Rushes Out-of-Band Windows Update to Fix Reset/Recovery Failures — What to Install Now

ByInnoVirtuoso

If you recently tried to “Reset this PC” or kick off a remote wipe and nothing happened, you’re not imagining it. After August’s Patch Tuesday, some Windows devices started failing at key recovery steps—right when you need them most. In response, Microsoft has shipped an out-of-band (OOB) update to fix the issue. And if you haven’t installed August’s security updates yet, Microsoft wants you to install this emergency update instead.

Here’s what changed, why it matters, and the exact steps to take whether you’re a home user or managing thousands of endpoints.

What Happened: August Patch Tuesday Introduced a Recovery Bug

After installing the August 2025 Windows security updates, some Windows clients began failing when users attempted certain recovery tasks. Microsoft confirmed the issue and issued an urgent fix outside the normal release schedule.

The failures were observed in three common scenarios:

  • System > Recovery > Reset this PC
  • System > Recovery > Fix problems using Windows Update
  • RemoteWipe CSP (often used in enterprise via Intune for remote wipe or decommission)

Among the implicated updates were KB5063875, KB5063709, and KB5063877. The result: a recovery or reset attempt might simply fail to complete.

Why that’s a big deal: Reset and recovery are your safety nets. If they’re unreliable, you’re stuck when you need a clean slate, a last-resort repair, or a remote wipe to meet security or compliance requirements. For IT, that becomes a helpdesk and risk-management headache.

The Fix: Microsoft’s Out-of-Band Update (August 19, 2025)

Microsoft released non-security, cumulative out-of-band updates on August 19, 2025. These updates supersede the affected August releases and are intended to restore recovery functionality.

Here are the OOB packages, with their target OS versions and build numbers:

  • KB5066189: Windows 11, versions 23H2 and 22H2 (OS Builds 22621.5771 and 22631.5771)
  • KB5066188: Windows 10, version 22H2 (OS Builds 19044.6218 and 19045.6218)
  • KB5066188: Windows 10 Enterprise LTSC 2021 and Windows 10 IoT Enterprise LTSC 2021 (OS Builds 19044.6218 and 19045.6218)
  • KB5066187: Windows 10 Enterprise LTSC 2019 and Windows 10 IoT Enterprise LTSC 2019 (OS Build 17763.7683)

A few important notes:

  • These are cumulative updates. You don’t need to install earlier updates first.
  • If you haven’t installed the August 2025 security update yet, Microsoft recommends applying the OOB update instead.
  • If your device isn’t affected, installing the OOB isn’t required—but for most, it’s a safe way to avoid recovery headaches.

If you’re curious how OOB updates fit into Microsoft’s release cadence, here’s a good primer on Windows monthly update types, including out-of-band releases: Windows monthly updates explained.

Quick Answer: What You Should Do Right Now

  • Haven’t installed the August 2025 Patch Tuesday update yet?
  • Install the OOB update for your version of Windows instead. It includes previous fixes and resolves the recovery/reset issue.
  • Already installed the August security update?
  • Install the matching OOB update. It supersedes the buggy release and restores recovery functionality.
  • Planning a reset, refresh, or remote wipe soon?
  • Update first. This reduces the risk of a failed reset or a wipe that never starts.
  • Using Windows Update Standalone Installer (WUSA) to deploy manually?
  • Be aware Microsoft also flagged a separate issue where updates released on May 28 might fail with “ERROR_BAD_PATHNAME” when installed using WUSA. If you hit this, consider using standard Windows Update, WSUS, Intune, or DISM as alternatives. See Microsoft’s guidance on WUSA here: Using the Windows Update Standalone Installer.

Who’s Affected: Versions and Scenarios at Risk

Microsoft’s advisory highlights client Windows versions targeted by the OOB fix:

  • Windows 11 23H2 and 22H2
  • Windows 10 22H2
  • Windows 10 Enterprise LTSC 2021 and IoT Enterprise LTSC 2021
  • Windows 10 Enterprise LTSC 2019 and IoT Enterprise LTSC 2019

If you manage Windows devices in an organization, you’re especially at risk if you:

  • Use Intune or another MDM to issue RemoteWipe commands
  • Frequently perform “Reset this PC” to refurbish or reassign devices
  • Depend on “Fix problems using Windows Update” to repair stubborn issues in-place

Enterprises often run scheduled wipe and reset workflows during offboarding, lease returns, or device redeployment. A failure here can halt logistics, delay compliance tasks, and increase data exposure if devices aren’t properly sanitized.

How to Check If You’re Affected

You don’t need to guess. You can verify in a few minutes.

1) Check your Windows version and build: – Press Windows key + R, type “winver”, and press Enter. – Compare your build to the OOB builds: – Windows 11: 22621.5771 or 22631.5771 – Windows 10 22H2 / LTSC 2021: 19044.6218 or 19045.6218 – Windows 10 LTSC 2019: 17763.7683

2) Check installed updates: – Settings > Windows Update > Update history. – If you see the August security update and not the OOB KB listed above, install the OOB update now.

3) If you rely on remote wipe or reset workflows: – Test on a non-production device. Attempt a “Reset this PC” or a remote wipe to confirm success after installing the OOB.

How to Install the OOB Update (Home Users and Small Teams)

Microsoft is pushing these OOB updates via normal channels. That means most people can install them with a standard update check.

Method A: Windows Update (easiest) – Go to Settings > Windows Update. – Click “Check for updates.” – Install the pending cumulative update that matches the KB for your Windows version. – Restart when prompted.

Method B: Manual download from Microsoft Update Catalog – Download the correct OOB KB for your OS: – KB5066189 (Windows 11 23H2/22H2) – KB5066188 (Windows 10 22H2, LTSC 2021, IoT LTSC 2021) – KB5066187 (Windows 10 LTSC 2019, IoT LTSC 2019) – Download the .msu file for your architecture (x64/ARM64). – Double-click to install, then reboot.

Alternative: Use DISM if WUSA fails – If you run into “ERROR_BAD_PATHNAME” with WUSA (reported for certain May updates), consider DISM as a workaround: – Open Command Prompt as Administrator and use DISM to add the package from the .cab inside the .msu, or install via Windows Update/WSUS/Intune instead. Microsoft’s DISM documentation is here: DISM servicing options.

Tip: After reboot, run “winver” again and confirm your build matches the OOB release for peace of mind.

Deployment Guidance for IT and Enterprise Admins

If you manage devices at scale, treat this like any urgent servicing event. The goal is to minimize failed resets and ensure remote wipe works reliably again.

1) Assess and pause where needed – If you staged August Patch Tuesday across rings, pause deployment for any rings that haven’t received it, and fast-track the OOB. – Communicate to helpdesk: resets and remote wipe may fail until the OOB is applied.

2) Expedite the OOB update – WSUS/Configuration Manager: Approve and deploy the relevant KB to affected collections. – Microsoft Intune: – Use Quality updates to expedite if available for the OOB build. – Target dynamic groups for Windows 10/11 versions listed above. – Consider pushing a restart window to complete installation quickly. – For devices not regularly online, coordinate a check-in window or offer a VPN tunnel for update retrieval.

3) Validate key workflows – Test “Reset this PC” on Windows 10 22H2 and Windows 11 23H2 devices. – In Intune, issue a “Wipe” on a non-production device and confirm completion. Microsoft reference: Wipe devices with Microsoft Intune. – Verify “Fix problems using Windows Update” works in Recovery settings.

4) Detection and reporting – Track build numbers across your fleet and confirm devices hit: – 22621.5771 or 22631.5771 (Windows 11) – 19044.6218 or 19045.6218 (Windows 10 22H2/LTSC 2021) – 17763.7683 (Windows 10 LTSC 2019)

5) Communication and change notes – Notify users and device owners that a quick reboot may be required. – Document the incident in your change log and update known-issues pages.

Enterprise tip: If you rely on Autopilot reset during device turnover, validate those flows after the OOB fix. Reference: Windows Autopilot Reset.

Troubleshooting: If You Still Can’t Reset or Wipe

Even with the fix, edge cases happen. Try these steps in order:

  • Confirm the correct OOB build is installed (run “winver”).
  • Check Update history for the specific OOB KB.
  • Run system file checks:
  • Open an elevated Command Prompt and run “sfc /scannow.”
  • Then run “DISM /Online /Cleanup-Image /RestoreHealth.”
  • Attempt Reset this PC again:
  • Settings > System > Recovery > Reset this PC.
  • If you’re trying “Fix problems using Windows Update,” ensure network connectivity and retry.
  • For remote wipe:
  • Confirm the device checks in with Intune/MDM.
  • Retry the wipe and monitor status in the admin console.

If all else fails, you can use recovery media or WinRE to perform an offline reset or a clean install. Microsoft’s guide on recovery options is here: Recovery options in Windows.

Why This Matters (Beyond the Inconvenience)

Reset and recovery options are the seatbelts of Windows administration. You might not need them often, but when you do, you need them to work—right away.

  • For individuals: Reset this PC is often how you recover from stubborn performance issues, malware, or a system you want to hand down or sell.
  • For IT: Remote wipe is essential for security, compliance, and logistics. If it fails, retired or lost devices may retain data longer than policy allows, creating exposure and audit risk.
  • For organizations: Failed resets delay re-provisioning and inflate support costs.

The OOB update restores these safety nets. Even if you haven’t tried a reset lately, installing the cumulative fix prevents a bad surprise when you do.

Pro Tips to Avoid Update Regressions in the Future

No update strategy is perfect, but a few habits reduce risk:

  • Use deployment rings: Pilot with IT and early adopters before broad rollout.
  • Watch Windows Release Health dashboards daily during rollout:
  • Windows 11 status: Windows 11 23H2 release health
  • Windows 10 status: Windows 10 22H2 release health
  • Enable telemetry and Endpoint analytics to spot anomalies early: Endpoint analytics overview
  • Maintain a rollback plan for critical apps and workflows.
  • Keep a bootable recovery USB on hand for emergency repairs.
  • Follow the Microsoft Security Update Guide for Patch Tuesday details and zero-day disclosures: MSRC Security Update Guide

A quick note on Known Issue Rollback (KIR): Microsoft sometimes uses KIR to roll back non-security bugs without requiring full cumulative updates. Not every issue gets a KIR, and in this case Microsoft opted for an OOB cumulative update. For context, see: Known Issue Rollback (KIR).

Timeline at a Glance

  • August 12, 2025: Patch Tuesday lands with over 100 CVE fixes, including a publicly disclosed zero-day.
  • Post-release: Reports emerge of Windows reset/recovery failures on some client systems.
  • August 19, 2025: Microsoft publishes OOB cumulative updates (KB5066189, KB5066188, KB5066187) to resolve the issue and recommends installing these in place of the August security updates for affected versions.

Issues sometimes surface only when millions of machines meet real-world conditions. The quick OOB turnaround is Microsoft’s way of course-correcting as fast as possible.

Step-by-Step Verification After You Patch

To ensure you’re in the clear:

  • Confirm the build number matches the OOB:
  • Windows 11: 22621.5771 or 22631.5771
  • Windows 10 22H2/LTSC 2021: 19044.6218 or 19045.6218
  • Windows 10 LTSC 2019: 17763.7683
  • Test a non-destructive repair step first:
  • Open Settings > System > Recovery > Fix problems using Windows Update.
  • Then test “Reset this PC” on a spare device or VM. Use “Remove everything” only on non-production devices.
  • In enterprise, test a RemoteWipe via Intune on a lab device and confirm the wipe completes.

If these pass, you can proceed with confidence to broader resets, decommissions, or lifecycle events.

FAQs: Microsoft’s Out-of-Band Update for Windows Recovery Failures

Q: What is an out-of-band (OOB) update? A: It’s an update released outside Microsoft’s normal monthly cadence to fix a critical or time-sensitive issue. Learn more here: Windows monthly updates explained.

Q: Should I install the OOB update if I already installed August’s Patch Tuesday? A: Yes, if you rely on “Reset this PC,” “Fix problems using Windows Update,” or remote wipe. The OOB is cumulative and supersedes the buggy release, restoring recovery functionality.

Q: How do I know which KB to install? A: Match the KB to your OS: – Windows 11 23H2/22H2: KB5066189 – Windows 10 22H2, LTSC 2021, IoT LTSC 2021: KB5066188 – Windows 10 LTSC 2019, IoT LTSC 2019: KB5066187

Q: I saw “ERROR_BAD_PATHNAME” when using WUSA. What now? A: Microsoft reported that updates released on May 28 may fail with that error when installed via WUSA. Try Windows Update, WSUS/Intune, or DISM instead. See: Using the Windows Update Standalone Installer.

Q: Will the OOB update include August’s security fixes? A: Yes. The updates are cumulative, so you’ll receive previous fixes plus the recovery fix.

Q: I don’t use reset or remote wipe. Can I skip this? A: If your device isn’t affected and you don’t depend on those features, you can skip. But installing cumulative updates regularly is still best practice.

Q: Does this affect Windows Server? A: Microsoft’s notice focuses on client versions of Windows. If you manage servers, follow their respective release health notes.

Q: How do I verify the fix worked? A: Check your build number against the OOB builds and test a recovery action (e.g., “Fix problems using Windows Update”). Enterprises should test RemoteWipe on a lab device.

Q: Where does Microsoft post official status updates? A: Check the Windows release health dashboards: – Windows 11 release health – Windows 10 release health

The Bottom Line

Microsoft’s August Patch Tuesday introduced a bug that could break Windows reset and recovery workflows, including remote wipe. The company has now shipped out-of-band cumulative updates—KB5066189, KB5066188, and KB5066187—to restore those safety nets. If you haven’t installed August’s updates yet, install the OOB instead. If you already installed them, apply the OOB to fix recovery now.

Actionable next step: Open Windows Update and install the latest cumulative update for your version of Windows, or pull the correct KB from the Microsoft Update Catalog. Then verify your build and test a recovery action on a non-production device.

Want more practical, timely Windows insights like this? Stick around—subscribe for updates, how-tos, and straight-talk guides that help you keep systems secure and resilient without the drama.

Discover more at InnoVirtuoso.com

I would love some feedback on my writing so if you have any, please don’t hesitate to leave a comment around here or in any platforms that is convenient for you.

For more on tech and other topics, explore InnoVirtuoso.com anytime. Subscribe to my newsletter and join our growing community—we’ll create something magical together. I promise, it’ll never be boring! 

Stay updated with the latest news—subscribe to our newsletter today!

Thank you all—wishing you an amazing day ahead!

Read more related Articles at InnoVirtuoso

InnoVirtuoso

Hello there! I'm passionate content writer navigating the digital landscape. With a deep love for words and an insatiable curiosity about technology.

With 10 years of experience in IT field, I write mostly about emerging tech, sharing news, informational articles and covering other topics I find interesting.

Let's craft the future of content together – one word at a time!

Browse InnoVirtuoso for more!