Published August 31, 2026

My PC Said "No Changes Were Made" and I Almost Gave Up

My laptop had been misbehaving for weeks — small things, nothing I could ever pin down to one specific cause, just a general sense that something underneath had gotten quietly wrong. I'd finally decided to stop chasing individual symptoms and do the thing I'd been putting off: a full reset, back to a clean starting point. I backed everything up properly first, took a breath, and clicked through to Reset this PC.

The Problem

The progress bar climbed steadily for a while, long enough that I'd started to relax, and then stopped. A few seconds later, the screen changed to a message I hadn't been expecting at all: "There was a problem resetting your PC. No changes were made." No detail, no error code, nothing to actually act on — just a flat statement that the one thing I'd finally committed to doing hadn't worked.

I tried again, half-assuming it had been some kind of fluke. It failed at almost exactly the same point, with the exact same message, the second time.

What I Initially Thought

My first reaction was a specific kind of discouragement, worse in some ways than the original problem had been. I'd built up to this — decided a full reset was the right move, actually done it — and having it fail twice, with no explanation at all, made it feel like even the "start over completely" option was closed off to me. I genuinely wondered, for a few minutes, whether the whole machine was simply beyond fixing.

What I Tried

Before accepting that, I searched the exact message, and found a scattering of forum threads and a couple of short articles, most suggesting some version of "try again" or a single generic step without much explanation of why it might actually help. One mentioned running the System File Checker, which I'd never used before, so I looked into what it actually did rather than just running it blindly on faith.

Once I understood that sfc /scannow checks and repairs corrupted system files, and that corrupted files are specifically one of the most common reasons a reset fails partway through, running it actually felt like a real diagnostic step rather than a guess. It found and fixed several things. I followed it with DISM, since I'd read that sfc sometimes can't fully repair something DISM needs to fix first, and let that run to completion as well.

What I Discovered

The reset still failed a third time, in almost the same spot, which was honestly the most discouraging moment of the whole thing — I'd done real repair work and it hadn't been enough. But reading further, rather than just repeating the same step again, I found something more specific: a documented pattern connecting this exact failure to certain Windows Store apps, whose files can conflict with the reset process in a way that has nothing to do with general file corruption at all.

I went through my installed Store apps and uninstalled a couple I'd added recently and barely used, more as an experiment than with real confidence it would help. The reset finished successfully on the next attempt, all the way through, for the first time since I'd started this whole process.

I never got a definitive answer on which single thing had actually been at fault — the file corruption sfc and DISM fixed, the specific app I removed, or some combination of both. What mattered more was that the vague, unhelpful "no changes were made" message had turned out to have several well-documented, specific causes behind it, none of which the message itself had given me any hint of.

What I Changed

I run sfc and DISM as a first step now before attempting anything as drastic as a full reset, rather than treating them as a last resort I only reach for once something's already gone wrong in a more dramatic way. I also know now that a Store app can be a legitimate, specific suspect if a reset fails with no other explanation — not just generic file corruption, which is where every search result I initially found had stopped.

The Lesson

A generic, unhelpful error message made a real, fixable problem feel much bigger than it actually was. Once I had the actual, specific causes in front of me — corrupted files, a conflicting Store app — the problem stopped feeling like a dead end and started feeling like a checklist. The message itself never changed. My understanding of what was actually behind it did.

Practical Takeaway

• If "Reset this PC" fails with "There was a problem resetting your PC — No changes were made," run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth before trying again.
• Uninstall recently added Windows Store apps before retrying — a conflicting Store app is a specific, documented cause of this exact failure, separate from general file corruption.
• If one reset option fails (like "Keep my files"), try the other ("Remove everything," with a real backup first) — sometimes only one path is actually broken.
• Check that Windows Recovery Environment is enabled (reagentc /info in an administrator Command Prompt) if repeated attempts keep failing with no further detail.
• Don't take a vague failure message as the final word — search for the exact wording specifically, since messages this generic often have several well-documented, specific causes behind them.

A Personal Ending

I think about how close I came to just accepting that the machine was unfixable, purely because the message itself gave me nothing to work with and my first two attempts at a real fix hadn't been enough either. Since then, "no changes were made" reads very differently to me — not a dead end, just a message that needed more digging than it was willing to offer on its own.

Had a vague failure message turn out to have a real, specific cause once you dug past the first few search results? I'd like to hear about it.

Frequently Asked Questions

Is "no changes were made" always a dead end?

No — it usually means the specific fix that was tried didn't address the real underlying cause, not that the problem is unfixable. Trying a different, more targeted approach for the actual cause resolves it.