Fix it now
0x80070003 is ERROR_PATH_NOT_FOUND: the system cannot find the path specified. During a reset it means the engine went looking for something its own manifest promised would be there. The reset is not broken; the source it rebuilds Windows from is incomplete. Repair the source and the reset usually completes on the next attempt.
dism /Online /Cleanup-Image /ScanHealth
dism /Online /Cleanup-Image /RestoreHealth
sfc /scannow
reagentc /info
- Run the four commands above and restart. ScanHealth tells you whether the component store is damaged; RestoreHealth repairs it; reagentc tells you whether the recovery environment is present.
- If
reagentc /inforeports Disabled, runreagentc /enablebefore retrying. - Retry the reset from Settings, System, Recovery, Reset PC – and choose Cloud download rather than Local reinstall. Cloud download fetches a fresh copy of Windows and does not care that your local source is damaged.
- If it still fails, mount installation media of the same edition and run
setup.exefrom within Windows, choosing to keep files and apps. That rebuilds every component while leaving software and data alone. - Keep a clean installation as the last option rather than the first.
Reset This PC and a clean installation both destroy things. Keep my files preserves personal files in your profile and removes apps and settings; it is not a backup. Copy what matters elsewhere and confirm you can open the copies first.
If the reset or the repair upgrade completes, you are done. If not, the next section explains where the reset gets its copy of Windows from and why the two options fail for different reasons.
Why it happens
Reset has two sources and Microsoft describes them differently on purpose. Local reinstall uses the files already on the PC, which is faster on a slow connection but may not include the latest updates. Cloud download fetches a fresh copy of Windows from the cloud, which gets you the latest version with all updates at the cost of several gigabytes of transfer. Because they fail for completely different reasons, switching between them is the fastest diagnostic available.
Local reinstall is the fragile one. It depends on the component store being complete, the recovery environment being present and correctly registered, and the folders the manifests refer to existing where they are expected. A deleted recovery folder, a cleaned-up Windows.old, a redirected profile folder, a half-applied update or a partially removed manufacturer customisation each produce a path that does not resolve – and a path that does not resolve is exactly what ERROR_PATH_NOT_FOUND reports.
The companion codes point elsewhere. 0x8007045B is ERROR_SHUTDOWN_IN_PROGRESS, published simply as a system shutdown being in progress; in practice that is usually a previous attempt that left an operation pending, or something else that triggered a restart, but the code itself says only what it says. 0x80070032 is ERROR_NOT_SUPPORTED, the request is not supported – which on consumer machines generally points at a manufacturer’s recovery arrangement or a partition layout that has been modified since the machine was built.
One more thing worth knowing before you start: an in-place repair upgrade is very often a better move than a reset. It replaces every Windows component from media while keeping applications, settings and data, and it fixes precisely the kind of component store damage that made the reset fail. Reset is the right tool when you actually want the machine returned to a clean state, or when you are handing it to someone else.
The component store is damaged
You have this one if dism /Online /Cleanup-Image /ScanHealth reports corruption, or SFC finds files it cannot repair.
- Run
dism /Online /Cleanup-Image /RestoreHealthand let it finish. - If DISM cannot find a repair source, mount an ISO of the same edition and build and repeat with
/Source:WIM:E:\sources\install.wim:<index> /LimitAccess. - Follow with
sfc /scannow, restart, and retry the reset.
The recovery environment is missing or misregistered
You have this one if reagentc /info reports Disabled, no location, or a location that does not exist.
- Try
reagentc /enablefirst. - If that fails, supply a recovery image from installation media and register it:
reagentc /setreimage /path C:\Recovery\WindowsRE /target C:\Windows, then enable it. - Confirm with
reagentc /infobefore retrying the reset.
A servicing operation is still pending
You have this one if Reset aborts within seconds, or 0x8007045B appears, and update history shows an update that installed but never completed.
- Restart and let any pending update finish properly before trying again.
- Tidy the store with
dism /Online /Cleanup-Image /StartComponentCleanup. - If an operation is genuinely stuck, boot the recovery environment, find the Windows volume letter, and run
dism /Image:<vol>\ /Cleanup-Image /RevertPendingActions.
RevertPendingActions is not supported on a running system, or against a Windows PE or Windows RE image. It has to target the offline Windows image with /Image:, which is exactly what the recovery environment lets you do.
A manufacturer arrangement or disk encryption is blocking it
You have this one if 0x80070032, reset options greyed out on a machine that shipped with the maker’s own recovery tool, or failures that only occur on encrypted machines.
- Use the manufacturer’s recovery process instead, if the partition it depends on is still present.
- On an encrypted machine, suspend BitLocker with
manage-bde -protectors -disable C:and have the recovery key available. - Where a user profile folder was redirected to another volume, move it back to C: before running the reset.
Full reference
Matching the failure to its cause
| What happens | Where to look |
|---|---|
| Reset fails immediately, before any progress | A pending servicing operation or a missing recovery environment |
| Reset gets some way through, then reverts | A damaged component store; repair with DISM first |
| Local reinstall fails but Cloud download works | Confirms the local source was the problem |
| Both options fail with 0x80070032 | A manufacturer recovery arrangement or a modified partition layout |
| Fails only on encrypted machines | Disk encryption blocking access to the recovery source |
What each reset choice actually does
| Choice | Microsoft’s description |
|---|---|
| Keep my files | Reinstalls Windows while keeping personal files intact; removes apps and settings |
| Remove everything | Reinstalls Windows and removes all personal files, apps and settings |
| Cloud download | Downloads a fresh copy of Windows from the cloud, with the latest version and updates |
| Local reinstall | Uses the files already on the PC; faster on a slow connection but may not include the latest updates |
Keep my files is the one most often misunderstood. It keeps personal files in the profile and removes installed desktop applications, most settings and anything stored outside the profile folders. It is a rebuild that spares your documents, not a way to avoid backing up.
Where to read what went wrong
Two logs are documented and worth reading first. C:\Windows\Logs\CBS\CBS.log names the specific component the servicing stack could not find or repair, and C:\Windows\Logs\DISM\dism.log records what DISM did. To pull the system file checker’s findings out of the CBS log, run findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > %userprofile%\Desktop\sfcdetails.txt and read the file it produces.
The reset engine also leaves material in a $SysReset folder on the system drive. Microsoft does not document that folder or its contents, so treat anything you find there as supporting evidence rather than as an authoritative account of what happened.
Why the repair upgrade usually wins
Mount an ISO of the same edition and build, run setup.exe from within Windows, and choose to keep files and applications. Setup rebuilds every Windows component from the media while leaving software, settings and data alone. Compared with a reset it is less destructive, it fixes the same class of component store damage, and it does not depend on the local recovery source that has just proved unreliable. Its two requirements are that the machine starts far enough to run setup, and that you have media matching the current edition and build.
Reset This PC and a clean installation both destroy data, and the Keep my files option is not a backup. Copy what matters to another device or to cloud storage, and confirm you can open the copies from a different machine, before starting either.
Before you conclude the machine needs a clean install
- Repair the component store and re-run the reset once. Many failures clear at that point.
- Try Cloud download explicitly. It removes the local source from the equation entirely.
- Try an in-place repair upgrade with matching media.
- Check the disk. A reset that keeps failing on a machine with disk errors is telling you about the disk, not about the reset.
- Only then reset with Remove everything, or install cleanly.
When a licence is the actual fix
Most machines need no licence to come back from this. Microsoft states that with a digital licence you can reinstall the same edition on the same device without entering a product key, and that Windows activates automatically once the installation is complete and online. A key is genuinely needed in the situations Microsoft names: a device that has never had an activated copy of Windows, or an upgrade to a different edition from the one previously installed – moving a machine from Home to Pro while it is open anyway, for instance. Replacing a motherboard is the other practical case, because the hardware the licence was recorded against has changed. Arco supplies Windows 11 Pro retail keys with an invoice and a traceable channel, which matters the next time a hardware change needs a reactivation and someone asks where the licence came from. Send us what slmgr /dli reports before you start and we will tell you whether you need one at all.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x80070003 |
ERROR_PATH_NOT_FOUND (3): the system cannot find the path specified. During a reset, a path the engine expected does not resolve | Microsoft Learn |
0x8007045B |
ERROR_SHUTDOWN_IN_PROGRESS (1115): a system shutdown is in progress, so the request was refused | Microsoft Learn |
0x80070032 |
ERROR_NOT_SUPPORTED (50): the request is not supported. On a consumer machine this typically means a manufacturer recovery arrangement or a modified partition layout | Microsoft Learn |
Confirm the fix worked
- The reset or repair upgrade completed and the machine reaches the desktop and signs in normally.
dism /Online /Cleanup-Image /ScanHealthreports no component store corruption.sfc /scannowreports no integrity violations.slmgr /dlireports Licence Status: Licensed.reagentc /inforeports the recovery environment enabled, so the next attempt at recovery is available to you.
Questions people ask about this
Does Keep my files really keep everything?
It keeps personal files in your profile. Microsoft describes it as reinstalling Windows while keeping personal files intact, and removing apps and settings. Anything stored outside the profile folders goes with them. Treat it as a rebuild that spares your documents, not as a substitute for a backup.
Cloud download or local reinstall?
Cloud download when the local source is suspect, which is exactly what this error describes. Microsoft describes it as downloading a fresh copy of Windows with the latest updates, so it does not care that your component store is damaged. The cost is several gigabytes of download.
Will I have to type a product key afterwards?
Normally not. Microsoft states that with a digital licence you can reinstall the same edition on the same device without entering a key, and that Windows activates automatically once online. Check with slmgr /dli beforehand so you know what you are starting from.
Is an in-place repair upgrade safer than a reset?
For most people, yes. It replaces every Windows component while keeping applications, settings and data. It needs media matching your current edition and build, and it will not rescue a machine whose disk is failing.
Reset fails within seconds with no progress at all.
That pattern points at a pending servicing operation or a missing recovery environment rather than at a damaged source. Restart to let any pending update finish, check reagentc /info, and if something is genuinely stuck, clear it from the recovery environment with RevertPendingActions against the offline image.
