Microsoft updates its Win10 auto-uninstall feature announcement

Topic

New Reply

Remember the gnarly Win10 auto-uninstall announcement that suddenly appeared yesterday? I was — and still am — scratching my head over that one. Acc
[See the full post at: Microsoft updates its Win10 auto-uninstall feature announcement]

4 users thanked author for this post.

PhotM, abbodi86, Elly, GreatAndPowerfulTech

Reply | Quote

Replies

“Hey look! We’re still doing it wrong but now we have even *more* marketing for it!”

This reminds me of the history of coffee in the US, some decades ago. Coffee quality was awful, so, instead of improving it’s quality, they’ve done more marketing!

Reply | Quote

I’m just speculating here based on the wording of the error notices, but the difference between this and the current “srylol, the update didn’t install, reverting” error is probably this:

– The current behavior triggers only when the update itself fails to install. Windows then undoes everything it did in that update session and reboots again on the old code. Then the computer reboots, Windows installs the update again, which fails, and it undoes it and reboots, and installs it again, and fails, and on and on.

– This new thing Microsoft is showing off sounds like it will remove the most recent update(s?) if the computer fails to boot a couple times, even if those updates installed properly. It will then blacklist that update for 30 days, effectively letting you skip that update because the next one will just supercede it anyway. The hope is that Microsoft fixes that bit of bad code during that 30 day window. I must admit that I have my doubts.

This is probably a nice little failsafe sort of thing, but in my experience, it’s considerably more rare for a bad update to prevent booting than for one to cause problems on a fully booted system. So, I’d say it’s not that useful if it’s what it sounds like.

2 users thanked author for this post.

woody, Steve S.

Reply | Quote

I think you’re right.

There’s a difference, but it ain’t much.

Reply | Quote

One small correction. You/they wrote “Win 10 will detect when you’ve tried to install a patch…”. FYI I -for that matter- have not tried to install anything. They did. On the contrary, I, if I could, would have avoided anything being installed on my computer running Windows 10. That’s why I, am currently testing Windows 10 LTSC, in order to avoid what THEY install. More specifically, those [flawed] updates that will prevent my computer from starting up.

Reply | Quote

Is 2019H1 officially 1903 now?

Fractal Design Pop Air * Thermaltake Toughpower GF3 750W * ASUS TUF GAMING B560M-PLUS * Intel Core i9-11900K * 4 x 8 GB G.Skill Aegis DDR4 3600 MHz CL16 * ASRock RX 6800 XT Phantom Gaming 16GB OC * XPG GAMMIX S70 BLADE 1TB * SanDisk Ultra 3D 1TB * Samsung EVO 840 250GB * DVD RW Lite-ON iHAS 124 * Windows 10 Pro 22H2 64-bit Insider * Windows 11 Pro Beta Insider

Reply | Quote

Yep – in the sense that “1903” appears internally, in the product. There’s been no official announcement that I’m aware of.

Reply | Quote