156
Microsoft admits a Windows 11 bug is eating up to 500GB of storage, verify if you are affected
(www.windowslatest.com)
this post was submitted on 06 Jul 2026
156 points (98.1% liked)
PC Master Race
21680 readers
747 users here now
A community for PC Master Race.
Rules:
- No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
- Be respectful. Everyone should feel welcome here.
- No NSFW content.
- No Ads / Spamming.
- Be thoughtful and helpful: especially when new beginners have questions.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A huge chunk of my work used to be fixing things after a client’s Windows OS went tits-up after an update for seemingly no reason.
These days, those cases are incredibly rare and when they happen there’s usually an underlying hardware condition.
Windows has been able to roll back botched updates for about 10 years now. I’d say that qualifies as an improvement.
In my experience, updates that break boot are up 250% since 7, and their "roll back" for "Feature" and "quality" upgrades fails 85% of the time, "Sorry we weren't able to uninstall.."
Not to mention that they've disabled the default registry backup since 10. Go ahead- check the "regback" folder. There's nothing in it. Don't even get me started on auto-bitlockering.
Odd how we have such different experiences the last 10 years.