Most writing about system tuning is written by people on their good days. This is one from a bad day, because the failure mode I hit is the one nobody warns you about: nothing crashed, nothing errored, and the machine was simply wrong in ways that took a week to surface.
The mistake
It was my fourth laptop of the afternoon and I stopped reading labels. I ran through Software & Apps with a selection that made sense on my own bench machine — the aggressive profile — on a unit destined for someone who needed exactly none of that.
Specifically, I removed a Store framework package, several capabilities, and Edge, on a machine whose owner had a work portal that turned out to need WebView2. The interface had told me, clearly, that some of those could not be reinstalled. I clicked past it because I had clicked past it three times already that day and nothing had gone wrong.
Repetition is what turns a warning label into wallpaper.
How it showed up
Not immediately, and not as an error. In order:
- Day 1: everything fine. Machine handed over.
- Day 3: "the sign-in page just goes white". No error text, no code.
- Day 4: a PDF from an email opened in a window with no controls.
- Day 6: the Store said it needed an update and could not install one.
Each of those looked like a separate problem. That is the signature of a missing framework: symptoms scattered across unrelated applications, none of which mention the thing that is actually absent.
What the restore point recovered
Winhance had made its initial restore point, as it does, and I used it. It brought back registry state cleanly — policies, content delivery values, the lot. What a restore point does not reliably do is bring back removed provisioned packages and capabilities, because those are not what System Restore snapshots.
So the machine went back to "configured the way it was before I touched settings", while still missing the packages I had removed. Half a recovery is a confusing place to be, because the machine now looks untouched and behaves broken.
Getting it back
What eventually worked, in escalating order of effort: re-enabling optional features from the Windows Features dialog, then reinstalling the Store framework packages via Add-AppxPackage from a matching build's provisioning folder, then installing the WebView2 runtime directly from Microsoft.
That got the portal working. The Store took a repair-install of Windows — an in-place upgrade from a mounted ISO, which keeps files and apps and rebuilds the component store. Three hours I did not bill for.
# In-place repair keeps files and apps, rebuilds system components
# Mount the matching-build ISO, then run from the mounted drive:
setup.exe /auto upgradeThe rule since
One rule, written on the wall above the bench:
Tier 3 removals happen at the start of a session, on a machine I own, never at the end of a session, on a machine I do not.
Alongside it, three habits: I make a fresh restore point manually before each session rather than relying on the first-launch one; I export the machine's current config as a rollback file before importing mine; and on client machines I stop at tier 2, always.
The whole point of a tool that shows you what it is about to do is that you read it. The tool did its job that afternoon. I did not do mine.
Written by Joseph Savastano. Measurements come from my own machines and are not a promise about yours. Corrections are welcome and get published — send one.