Windows may uninstall updates that cause startup problems
Microsoft implemented a new troubleshooting step recently in Windows 10 that improves the operating system's handling of startup problems.
Windows 10 may uninstall recently installed operating system updates automatically to address startup issues as a last resort if all other steps to fix the issue fail.
Startup problems are one of the most frustrating issues that Windows users may experience. One of the big issues for users is that they have only a few options at their disposal to fix the issue: using built-in troubleshooting options, recovery disks or tools, or restoring backups of the system if they do exist.
Updates can be the source of startup problems. Updates may cause bluescreens or other startup related issues that prevent the system from booting.
To name just a few recent incidents:
- Microsoft releases AMD-specific Windows 7 and 8.1 updates to fix unbootable state issue
- New Windows 10 version 1809 woes: no audio, bluescreens
- How to fix Boot BCD startup errors on Windows PCs
- Fix Windows 7 BSOD 0x000000c4 after installing KB4056894
We removed some recently installed updates
Windows 10 may remove recently installed updates as part of a troubleshooting process to restore proper startup behavior.
The operating system informs the user about the removal of updates on the next successful start:
We removed some recently installed updates to recover your device from a startup failure.
Microsoft notes on a support page that this is done only if all other attempts to recover the boot process and system start fail.
Updates removed in the process will be blocked for 30 days automatically to avoid the issue from happening again. Blocked updates will be downloaded and installed again after the 30-day period, and that may mean that the issue is experienced again if Microsoft did not resolve it in the time.
Administrators who want to block the update continuously may use Microsoft's update blocking tool to do so.
Closing Words
Automatic recovery is great if it works and the new update removal option is certainly a welcome addition to the automatic recovery process. The option speeds up the recovery if it works.
The new option may resolve some issues automatically but it certainly is not a catch-all option that recovery any issue that is update related.
Administrators still need to use advanced troubleshooting tools or recovery images to restore a system to a working state if automatic recovery fails.
Now You: Did you run into update related issues recently? (via Bleeping Computer / Windows Latest)
This really proves that M$/Nadella are in control of all Win 10 computers via Windows Update, ie the computer-owners are not in control..
Like I said before, M$/Nadella may terminate or immobilize any Win 10 computer that is in non-compliance with the EULA, eg those who purposely do not keep Win 10 updated or current, or are running an old Version of Win 10 that has reached EOL. eg Version 1703 or 1607.
Seems, M$/Nadella have not been sending forced auto-upgrades to some Win 10 computers that are 5 year or older = such old Win 10 computers that could not be upgraded would soon be EOL’ed by M$ = affected users may need to buy new OEM Win 10 computers = Planned Obsolescence = more profit$ for M$ and more bonu$ for Nadella.
@AnorKnee
But you’ve said this sort of thing before. I don’t think you’ve fully thought it through….for example, I am frozen on 1607, and its now two years since any updates to my main Win10 box.
Just how do you think MS$ are in control of my 1607? How do you think they can terminate or immobilise it? After all….nothing has got through from MS$ to my PC for two years now.
So do you think suddenly, a two year old box can get force-shut down?
It’s just not going to happen, and in my view, you are focusing far too much on the EULA. Who really cares about that? Why are you even worrying about that? Do you think MS$ are going to come knocking on my door…..seriously? You are over-thinking things.
https://answers.microsoft.com/en-us/windows/forum/all/windows-10-64-bit-version-1703-on-my-hp-computer/9db68925-6de1-4247-a99e-553ccaeab2dd …
…. = likely “official” proof that some 5 year or older Win 10 computers cannot be upgraded = soon to be EOL’ed by M$.
You are over-thinking.
>Did you run into update related issues recently?
No, because I usually wait 2/3 weeks before actually installing them.
My Lenovo G580 Ivy Bridge was upgraded with no problems…
@ Jon Arbuckle
See whether your Lenovo G580 can still be upgraded to Version 1903 or 1909, and after Jan 2020, to Version 2003 or 2009. Please keep us updated.
This is because M$/Nadella will likely only expand and/or accelerate their Planned Obsolescence program or “pogrom” against 5 year or older Win 10 computers after Win 7 EOL in Jan 2020. Now may just be the “birth-pangs of the coming Apocalypse”.
My 2013 ThinkPad Lenovo E520 Sandy Bridge with Windows 7 wasn’t compatible with Windows 10.
Logical next step:
Windows 10 uninstalling itself because it causes so much problems overall. Will auto-revert to 7 SP1.
(sorry for this very obvious comment, but I really couldn’t help it).
@ Henk ……. lol . !
Better still, M$ uninstalls Win 10 and auto-reverts to Linux Mint 19.0 LTS Cinnamon = supported until April 2023.
Then in April 2023, MS will force auto-upgrade it to LM 21.0 LTS.
“Microsoft truly loves Linux”.
No. WRONG!
M$ installs M$ Linux.
Seems logical. Microsoft send updates, and they are installed automatically, so why shouldn’t they be able to uninstall them automatically? Especially if Microsoft knows there will (could) be issues. I’d rather a smoother running machine by this happening instead of them posting there are issues with certain updates, and leaves it up to the user to find, and uninstall it/them. Of course in a perfect world Microsoft shouldn’t have so many issues to begin with, and I personally think they push more than they should with “feature” updates, instead of focusing on perfecting what is already out first.
Intel has the unfixable SPOILER bug in all her existing processors because she traded in security for performance with her Speculative Execution and Branch Prediction features. AMD and ARM processors are not affected by this built-in bug.
Won’t be a surprise if M$ also ends up with 1 or 2 unfixable bugs in Win 10 because she traded in simplicity in OS coding for greed.
……. Eg why should M$’s apps be integrated into the OS.?
Also, imagine someone being able to hack into M$’s Update servers and download the collected Telemetry & Data of all Win 10 computers. Of course, hackers are mostly interested in the Telemetry & Data of high-value targets, eg politicians, government officers, CEOs, IT Admins, celebrities, etc.
So you not only risk having a update install badly, but then you risk it uninstalling badly as well. Real smart Microsoft what could possibly go wrong? So when it does get uninstall then how long before Windows update tries to ram in onto the system again? I would hope their is some sort of pause for that update? Personally I would rather the updates be vetted better in the first place? But I suppose this is all we can expect from Microsoft. A whoops we bad, let’s get that update off your device.
“Did you run into update related issues recently?”
No. I am on the semi-annual channel … until M$ gets rid of that option. When they do I’ll abandon Windows for Linux.
@ pHFROZEN
Win 10 Version 1903 and later will be getting rid of the SAC option = Win 10 Pro 1903 computers with the default setting of 0 day deferral for feature updates will be forced auto-updated to Version 1909 as soon as it is released by M$, just like for Win 10 Home 1903 computers or unpaid beta-testers.
……. With this new policy, M$/Nadella can recruit more clueless Win 10 Pro users as unpaid beta-testers, so that M$/Nadella can provide better VIP service to the Enterprises or their ca$h-cows.
In previous Win 10 Versions, M$ wait about 3 to 4 months after the release of the new Version to designate it as SAC or CCB or Ready-for-Business, eg to have enough time to fix teething bugs in the new Version. It was only then that Win 10 Pro computers with the default setting of 0 day deferral for feature updates would be forced auto-updated to the new Version.
https://imgflip.com/i/2vvvph
W10 will uninstall itself some day. It’s not a joke. Please, Microsoft, stop this madness and let us to enjoy one stable version of W10 without the torture of two major upgrade ISO builds per year.
Looks like the feature may ship with 1903…
https://support.microsoft.com/en-au/help/4492307/windows-10-why-recently-installed-updates-removed
I wonder how it will deal with this situation just one of my machines has with an occasional monthly updates – at the first reboot after it has downloaded and installed the updates it just sits there with the whirling dots and never goes further.
After 2 or 3 forced resets it finally attempts a PC Repair, but that never fixes it. My only course it to try some manual actions, but annoyingly the one that should get me back to as it was won’t i.e. system restore complains it cannot restore because there are updates pending – catch 22.
To fix it I discovered that I first need to go into Safe Mode, and that allows the updates to complete, but I still cannot revert to a previous restore point, and the system still won’t boot. So I go into Safe Mode once again and but this time I can use System Restore to revert back and all is well again. Afterwards I can immediately re-check for updates, apply them successfully and if it’s as if nothing was wrong.
OMG..!!!
Windows 10 – 1903 build make me love my Windows 7 even more