Home / Error Lookup / RESET-PC-NO-CHANGES-MADE

RESET-PC-NO-CHANGES-MADE

General System "There Was a Problem Resetting Your PC — No Changes Were Made" Applies to: Windows 10, Windows 11

What it means

Windows started the Reset this PC process but couldn't complete it, most often due to corrupted system files, a conflicting Windows Store app, low disk space, or a disabled/corrupted Windows Recovery Environment (WinRE) — and rolled back without changing anything, hence "no changes were made."

Also seen as: There was a problem resetting your PC, No changes were made

Quick fix steps

  1. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth if you can reach the desktop — corrupted system files are the single most common cause.
  2. Uninstall any recently added Windows Store apps before retrying, since a conflicting Store app is a well-documented specific cause of this exact failure.
  3. Confirm WinRE is enabled via reagentc /info in an administrator Command Prompt, and run reagentc /enable if it shows disabled.
For the full step-by-step walkthrough, see "There Was a Problem Resetting Your PC" — What to Do.

Frequently Asked Questions

Does this mean the reset process damaged something?
No — this message specifically means the reset didn't even get to make changes yet, so nothing has actually been altered. It's telling you the reset couldn't start, not that it started and failed.
Is my data at risk after seeing this message?
No — since no changes were made, your files, apps, and settings remain exactly as they were before you attempted the reset.

Other error codes

0X80070005 — Access Denied

A permissions problem — the current user account doesn't have rights to the file, folder, or action being attempted.

0XC0000022 — STATUS_ACCESS_DENIED

A related but technically distinct code from the more common 0x80070005 — this is the NTSTATUS-style access-denied error, most often seen when a program can't open a file, DLL, or registry key it needs at startup, or when Windows activation specifically fails because the Software Protection Service can't start.

0X8007000E — Not Enough Storage / Out of Memory

Despite the wording, this is usually about low disk space rather than RAM — an operation ran out of room to complete.

0XC0000005 — Access Violation (STATUS_ACCESS_VIOLATION)

A program tried to read or write memory it wasn't allowed to — usually an app bug, but can indicate corrupted files or faulty RAM if it happens across many different apps.