Windows update KB5063709 caused a confirmed recovery problem on some Windows 10 computers. After installing the August 12, 2025 security update, Reset this PC and certain other recovery operations could fail instead of completing.
Microsoft fixed the regression one week later. Most computers should no longer need the original emergency patch because subsequent cumulative updates include the correction. That changes the correct troubleshooting approach today: update Windows first, then investigate other causes only when reset still fails.
The short answer
Install the newest cumulative update offered for your Windows 10 edition, restart the computer, and try the recovery operation again. KB5066188 was Microsoft’s immediate out-of-band fix for the problem, but it is mainly relevant to an older or isolated system that remains on the affected August 2025 build.
Removing KB5063709 is usually the wrong first move. It was a security update, and installing a later corrected update preserves its security fixes while resolving the recovery bug.
Confirm that KB5063709 is relevant
The symptoms alone are not enough to identify this update as the cause. “There was a problem resetting your PC” is a general Windows message that can also appear when Windows Recovery Environment is disabled, system files are damaged, the drive has errors, or local recovery files are unusable.
KB5063709 is a likely cause only when these details line up:
- The computer runs an affected Windows 10 release.
- Reset or recovery worked before the August 2025 update.
- KB5063709 appears in update history.
- The operating-system build is still close to the affected servicing level.
- A later cumulative update containing the correction has not been installed.
Open Settings > Update & Security > Windows Update > View update history and look for KB5063709. You can also press Windows key + R, enter winver, and check the build number.
The affected August 2025 Windows 10 22H2 build was 19045.6216. The immediate out-of-band correction moved it to 19045.6218. A substantially newer cumulative build should already contain the fix, so seeing KB5063709 in historical update records does not mean it is still breaking recovery.
Microsoft records the original problem on the KB5063709 support page.
Install the current Windows update first
Open Settings > Update & Security > Windows Update, select Check for updates, and install every applicable cumulative or servicing update. Restart Windows when requested, return to Windows Update, and check again for anything still pending.
Do not test Reset this PC before completing the restart. Windows may download and stage an update without fully applying it until the computer reboots.
This is the preferred repair for an internet-connected PC because Windows cumulative updates supersede older quality fixes. Manually searching for the August 2025 emergency package can put the machine on an unnecessarily old servicing path.
When Windows Update repeatedly fails, repair that process before retrying reset. The Windows Update cache troubleshooting guide covers stalled downloads, damaged update data, and recurring installation errors. Do not clear update folders while Windows says an installation is underway.
When KB5066188 is still appropriate
KB5066188 was released on August 19, 2025 specifically to correct the reset and recovery regression. A manual installation may still make sense when an administrator is repairing:
- an offline computer frozen on the affected build;
- an older system image from August 2025;
- a controlled business environment that cannot immediately move to a later cumulative update; or
- an eligible Windows 10 servicing branch with deliberately restricted updates.
Download historical packages only from Microsoft Update Catalog or an approved organizational update system. Avoid third-party update-download websites.
Microsoft describes the emergency correction and its scope on the KB5066188 support page.
Retry Reset this PC safely
Back up important files to a separate drive or trusted cloud location before using recovery. Keep my files preserves normal personal files, but it removes installed programs and resets many settings. It should not be treated as a backup.
After installing the corrected update and restarting:
- Open Settings > Update & Security > Recovery.
- Under Reset this PC, select Get started.
- Choose Keep my files or Remove everything based on the intended result.
- Select Cloud download or Local reinstall when Windows offers the choice.
Cloud download is useful when local Windows recovery files may also be damaged and the internet connection is reliable. Local reinstall avoids a large download but depends on files already stored on the computer.
The update bug must be corrected before either reinstall source can be judged properly.
Reset still fails after Windows is updated
A reset failure on a build newer than the affected August 2025 version should not automatically be blamed on KB5063709. Use the result of each check to narrow the next step.
Check Windows Recovery Environment
Open Command Prompt as administrator and run:
reagentc /infoLook for Windows RE status: Enabled. When it shows Disabled, run:
reagentc /enableThen check the status again. Do not delete, resize, or recreate a recovery partition merely because Windows RE will not enable. A missing recovery image or incorrect partition configuration requires separate diagnosis.
Repair Windows system files
Run these commands from an elevated Command Prompt, one at a time:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannowRestart after both tools finish. DISM repairs the component store used to service Windows, while SFC verifies protected system files. When SFC itself cannot complete, use the Windows Resource Protection error guide instead of repeatedly running the same command.
Check storage and free space
Recovery needs working space on the system drive. Remove unneeded temporary files and move large personal files elsewhere when the C: drive is nearly full.
Repeated reset failures accompanied by freezing, corrupted files, SMART warnings, or unusually slow disk access can indicate a failing SSD or hard drive. Back up the data before performing further write-intensive repairs. A Windows reset cannot make unreliable storage healthy.
What to do when Windows will not start
Use Windows Recovery Environment when the desktop is unavailable. From Troubleshoot > Advanced options, try Startup Repair, System Restore, or Uninstall Updates according to the failure that occurred.
Uninstall latest quality update is reasonable when Windows stopped booting immediately after an update and the corrected update cannot be installed. It is less suitable for a computer that starts normally and only has a reset problem.
Official Windows installation media can provide the same repair environment when built-in recovery is unavailable. Choose Repair your computer on the setup screen before considering a clean installation. A clean install is a last resort because it can remove applications, settings, and files.
Should you uninstall KB5063709?
Install a later corrected update whenever possible. Uninstalling KB5063709 is a temporary fallback only when the PC is confirmed to be on the affected build, recovery is urgently required, and the correction cannot be installed.
Avoid forcing removal with undocumented servicing commands. Forced package removal can damage the component store and create a harder recovery problem than the original bug.
Windows 10 Home and Pro reached the end of normal support on October 14, 2025. A Windows 10 computer used in 2026 should be covered by an applicable Extended Security Updates program, a supported LTSC release, or a planned migration. Updating an unsupported installation once does not provide ongoing protection.
The practical distinction is simple: KB5063709 caused a real reset problem, but Microsoft resolved it in August 2025. A computer that has installed later cumulative updates and still cannot reset needs ordinary recovery diagnosis rather than more treatment for an obsolete update regression.
