Windows 10 Will Uninstall Incompatible Updates

cageymaru

Fully [H]
Joined
Apr 10, 2003
Messages
22,060
Microsoft has rolled out a new feature for Windows 10 that allows the operating system (OS) to automatically uninstall broken or incompatible updates. Windows 10 will attempt to fix startup failures with automatic recovery attempts before uninstalling the updates. Users will see this message "We removed some recently installed updates to recover your device from a startup failure." The OS will prevent problematic updates from installing automatically for the next 30 days. Users can manually install the updates, but Windows 10 will still remove the problematic updates if it detects issues with startup. Thanks Monkey34 !

To ensure that your device can start up and continue running as expected, Windows will also prevent problematic updates from installing automatically for the next 30 days. This will give Microsoft and our partners the opportunity to investigate the failure and fix any issues. After 30 days, Windows will again try to install the updates. If your device is unable to start up properly after automatic or manual installation of these updates, Windows will uninstall them again.
 
Does 10 already remove old updates when the monthly bundles are released? I've noticed recently that 10 only shows ~ 15 installed updates on several PCs and there is no way to view \ uninstall older updates. This lead to having to reload one customer PC just because we couldn't locate and remove an update we knew was conflicting with hardware. It seems this started with 1809
 
What about fixing a feature that actually used to work in Windows 7, called Windows Restore?

Isn't that the windows story. Constantly adding features that get killed or replaced a few years later, often with something less good. I realize all companies do this somewhat, (google is pretty bad for it), but in Microsoft's case I'm often puzzled as to why. I doubt it's all that much work to keep many of these utlities and features working or make them optional components. The whole reason windows is so popular is that you can run 20 year old crap without recompiling it.
 
Uninstalling some of those by hand can completely bork your system, so I'd imagine their automatic version will do the same thing.
For me the best solution is to make image back-ups weekly and go back to one of those if things screw up colossally.
 
If it works well enough, this is a good thing but it's just a bandaid for issue that shouldn't happen to begin with. That being, proper QA before releasing updates.
As much as I do like that idea there are too many variables and too many softwares that cut corners that sometimes get patched and when that happens you are going to have a bad time.
 
I'm waiting for the update that patches a security hole that is being exploited that causes the system to then not boot so they remove the security update to allow the exploit to remain in place.
 
It’s still there under the name Windows 7 Backup.

It doesn't work if you try to recover a PC with it. Hasn't since 1607ish. Microsoft knows and won't fix it because it's EOL. They should really remove it at the very least so customers are aware their backups aren't working correctly.
 
Am I reading this right? Microsoft's solution to installing updates without your permission is to now uninstall updates without your permission?


you-gonna-get-updated-without-your-permission.jpg
 
my policy is to defer feature updates all the way out and put off 'quality??? updates' for 2-4 weeks, create a buffer while others complete the beta testing. In 1903 it appears m$ has gotten rid of the 'defer feature updates' in settings and lowered the 'pause updates' time from 30 days to only 7. m$ seems to double down on stupidity at each turn.
 
Can't wait for some random OEM system to be hit by a bug that automatically uninstalls a working driver. Preferably networking, lol.
 
did this just suddenly start? I dont see any notice anywhere, or more info
 
my policy is to defer feature updates all the way out and put off 'quality??? updates' for 2-4 weeks, create a buffer while others complete the beta testing. In 1903 it appears m$ has gotten rid of the 'defer feature updates' in settings and lowered the 'pause updates' time from 30 days to only 7. m$ seems to double down on stupidity at each turn.

Are you kidding gonna have to replace MS update server entirely
 
What about fixing a feature that actually used to work in Windows 7, called Windows Restore?
I have to disagree. I believe it works quite well. I've used Windows Restore on Windows 10 twice now, both times to uninstall a broken update.

What they need to fix is their ability to test shit before they push it out. Windows update was great under Win7.
 
It doesn't work if you try to recover a PC with it. Hasn't since 1607ish. Microsoft knows and won't fix it because it's EOL. They should really remove it at the very least so customers are aware their backups aren't working correctly.
I haven't tried to use it as a full restore medium only for recovering files and such. Though I am phasing it out for Onedrive and the automatic folder backup functions, pair that with Sharepoint for pictures and video's and things are great. Honestly outside a select few machines here now the only thing on most windows PC's here is Adobe reader, Java, Flash, and Chrome, just about everything else is a Citrix session or a web app. And if Citrix and nVidia can actually tell me what combination of GPU's I need to cram into my server those few remaining stand alone installs will be in Citrix too.
 
Does 10 already remove old updates when the monthly bundles are released? I've noticed recently that 10 only shows ~ 15 installed updates on several PCs and there is no way to view \ uninstall older updates. This lead to having to reload one customer PC just because we couldn't locate and remove an update we knew was conflicting with hardware. It seems this started with 1809

Windows 10 updates mostly supersede the previous month's update, so it will only show the latest version installed.
 
I have to disagree. I believe it works quite well. I've used Windows Restore on Windows 10 twice now, both times to uninstall a broken update.

What they need to fix is their ability to test shit before they push it out. Windows update was great under Win7.
Based on the stuff I am seeing its ability to work depends entirely on the usage of UEFI and secure boot, when they are off and the system boots under Legacy then it seems to work fine, if you are using a combination of UEFI and Secure boot, then it becomes a crap shoot.
 
This sounds like a great feature... For all of you who were updated to Win10 from Win7... You will now have all of the broken parts of win10 removed... I think that means you will be rolled back to a working windows 7 machine. Congratulations.
 
Worked for me, 1803 was refusing to install on my xeon x5670 system and now it does. I've got an old FM1 system that also refused to install 1803 that I've yet to try it on.
 
Based on the stuff I am seeing its ability to work depends entirely on the usage of UEFI and secure boot, when they are off and the system boots under Legacy then it seems to work fine, if you are using a combination of UEFI and Secure boot, then it becomes a crap shoot.

File recovery does still work at least.

Even non Secure Boot or UEFI the last time we absolutely had to recover the image we had to jump through hoops doing things like changing sata controllers to ide mode because of a bug that makes restore extremely slow in ahci, manually rebuilding mbr, and a ton of misc windows repairs. When researching the issue we found that this was normal functionality now.

Even if the issue is limited to UEFI or Secure boot that means any OEM computer built since Windows 8 has the problem and any custom build that didn't specifically disable UEFI. Which effectively means 99+% of any decent size company's PCs cant be correctly restored from a Windows backup. It's possible they went back and fixed the issues even tho the feature is EOL, but I wouldn't know since we moved all of our clients off it after learning it was borked.

The real annoying part is Windows server backup still works great and works pretty much the same so Microsoft can obviously fix the issue if they wanted to. Instead they want to push everyone into MS accounts \ one drive.
 
Windows 10's awful updates regime is a thing of the past for me because I got Windows 10 LTSC.

Also, I disabled Windows Update before anyway. Who's got time for its BS? Not me.
 
File recovery does still work at least.

Even non Secure Boot or UEFI the last time we absolutely had to recover the image we had to jump through hoops doing things like changing sata controllers to ide mode because of a bug that makes restore extremely slow in ahci, manually rebuilding mbr, and a ton of misc windows repairs. When researching the issue we found that this was normal functionality now.

Even if the issue is limited to UEFI or Secure boot that means any OEM computer built since Windows 8 has the problem and any custom build that didn't specifically disable UEFI. Which effectively means 99+% of any decent size company's PCs cant be correctly restored from a Windows backup. It's possible they went back and fixed the issues even tho the feature is EOL, but I wouldn't know since we moved all of our clients off it after learning it was borked.

The real annoying part is Windows server backup still works great and works pretty much the same so Microsoft can obviously fix the issue if they wanted to. Instead they want to push everyone into MS accounts \ one drive.
Yeah I use the server backup tool but I have most of my servers in Hyper-V now so I just have them doing a live migration over to sister server every 15 min, shadow copy covers for accidental file deletion and such, paired with the Office 365 Onedrive for business and Sharepoint online and it basically covers the rest of the bad case scenarios. I don't think they want to do a backup utility for Win10 and instead want people to be using their online services for file backup and the built in rebuild tools for win 10 in the event of a critical failure.
 
Windows 10's awful updates regime is a thing of the past for me because I got Windows 10 LTSC.

Also, I disabled Windows Update before anyway. Who's got time for its BS? Not me.
People who don't want their pc to be part of a botnet.
 
That's like the mechanics are constantly fiddling around under the hood of your car!

What the hell are you doing, Microsoft?
 
Windows "updates" that are so bad that they prevent Windows from starting (the kind of problem fixed by this new feature) are rare, in my experience.
The bigger problem is when third party software suddenly doesn't work as a result of a (quietly installed) Windows update.
 
Being that it's a Win 7 update/upgrade, will it uninstall itself?

My old 4820K box hated certain updates about every six months. So much so that Win 10 had to be reinstalled each time. No recovery.
The 3770k box was a win7 to win 10 upgrade. Has worked and taken the updates flawlessly, so has the Nuc.

We will see how the TR 2920 box goes with Win 10 as well as the AMD 2600 box. Otherwise Linux will be spreading in this household.
No patience for messed up updates.
 
Worked for me, 1803 was refusing to install on my xeon x5670 system and now it does. I've got an old FM1 system that also refused to install 1803 that I've yet to try it on.

I'll have to really try this - that update has been failing on my x5670 as well. Just haven't taken much time to figure it out :p
 
Couldn't get it to run on my old fm1 system but I didn't try very hard. I mainly wanted on the x5670 for the less buggy HDR.
 
Back
Top