The dread Windows version update

The dread Pirate Roberts Windows version update

Trying to keep W10 update 2004 off my machines (having removed it once) I got really fed up with it trying to re-install and now there is the October update on the horizon. So I managed to find out just exactly how to stop these version updates installing themselves thanks to a computerworld article. So:

If you have W10 PRO (not home) and you want to stay on a particular version ( in my case 1909) then have a look at the bottom of this article which takes you through the (simple) steps to do so using Group Policy:


It seems to have worked OK for me but of course, as usual, make your own choice.
 
Thank you for that helpful reference.

I had a bit of trouble with the installation of the 2004 update on my desktop computer, (the update from 1903 on Win 10 Home). Ok, that's an understatement; the problem was serious. There's a real problem associated with the hardware monitoring driver known as CPUZ140_x64.sys.
It's important to note that this doesn't have anything to do with the CPU-Z program (certainly in my case). I have never installed that program on my PC. That's not to say it won't cause the same problem if it uses this driver.

This can be quite mysterious to resolve due to the broad range of little programs that may use this driver. Make no mistake though, if it gets in the way, you will experience blue screens (page fault errors, to be exact). The OS will not proceed from the error; it is indeed a STOP code. The error is un-helpful in resolving the problem beyond reporting that it has to do with cpuz140_x64.sys.

I'm always nervous* when a "feature update" is released because (to me) it means:
bloatware! yeah - really!
re-installation of carp I've removed from the OS (Grr!)
changes in the color scheme; double - GRR! Hey! this is a PERSONAL computer, remember? What the heck are you doing changing my PERSONAL settings?! (sorry, pet peeve of mine.)
another instance of arm-twisting users by making it more and more difficult for non-savvy users to avoid signing up for an unwanted online account to use the OS. I can't count how many folks I've had to reassure that this is NOT necessary. People can't figure it out and simply capitulate. Terrible tactics, imo.

Another recent "feature" added was native support for print-to-PDF in the OS. Nominally you'd think that would be cool but, not if it doesn't work. I wondered why all of a sudden the option in my PDF-reader software was gone. The now-native PDF printer driver often doesn't work properly until you jump through some hoops to make it work. Great job, big boys!

Security updates/patches make me a little less nervous although I tend not to install them until I see what happens "out there."

* "annoyed" is likely a better term.
 
The dread Pirate Roberts Windows version update

Trying to keep W10 update 2004 off my machines (having removed it once) I got really fed up with it trying to re-install and now there is the October update on the horizon. So I managed to find out just exactly how to stop these version updates installing themselves thanks to a computerworld article. So:

If you have W10 PRO (not home) and you want to stay on a particular version ( in my case 1909) then have a look at the bottom of this article which takes you through the (simple) steps to do so using Group Policy:


It seems to have worked OK for me but of course, as usual, make your own choice.
Ahhhh....much better than the "deferral" method...thanks @Para Handy
 
For Windows 10 Home version, the only way to prevent windows updates is to install a software firewall (I like Tinywall personally, but any of them will work) to block/allow outgoing internet connections on a per app basis. You can't do that with Windows Firewall on its own -- it only blocks incoming internet connections.

It's easier for Windows 7 -- just disable the windows update service. If you try that for Windows 10, it will turn that service back on all on its own eventually.
 
Last edited:
For Windows 10 Home version, the only way to prevent windows updates is to install a software firewall (I like Tinywall personally, but any of them will work) to block/allow outgoing internet connections on a per app basis. You can't do that with Windows Firewall on its own -- it only blocks incoming internet connections.
The word "only" should be used with care...

And you can use Windows Firewall to block outbound connections (I do it all the time), but I have found that Windows will rewrite some of the rules for things like Update, thus why I do it on the router.
 
I have Windows 10 2004 and prefer to keep all my programs up to date with latest drivers etc. Never had a problem between Windows 7 or 10 and Elite in the 6yrs I have owned ED. There are any amount of posts online on what to switch off in Windows 10 to avoid their spyware etc. I would rather do that every now and again than leave my PC vulnerable to an attack by a real nasty rather than keep it up to date and safe.
 
I have Windows 10 2004 and prefer to keep all my programs up to date with latest drivers etc. Never had a problem between Windows 7 or 10 and Elite in the 6yrs I have owned ED. There are any amount of posts online on what to switch off in Windows 10 to avoid their spyware etc. I would rather do that every now and again than leave my PC vulnerable to an attack by a real nasty rather than keep it up to date and safe.

You perhaps misunderstand what my OP in this thread is about.

It is not stopping all updates - it just freezes the "build version" of windows. Hence the thread title "The dread Windows version update" (maybe I should have capitalised "version" to highlight that was the subject). The build is still supported by M$ with bug fixes, security updates, etc. When the build version is scheduled for end of support, one just changes to another build to freeze your installed version, should you so wish.

I do appreciate that other posters in the thread have said they don't do updates, I am just clarifying what the actual thread was intended* for.


* Actually my desire to avoid 2004 build was down to the nannying way it changed certain aspects and the final straw was it giving issues with MSFS 2020.
 
Last edited:
This happened on my computer,my computer has repeatedly prompted me to update to the latest Windows version,i don't know how many times it reminds me every month,but it reminds me at least twice,for my work or needs, I don't need to do anything with Windows Update,in fact,if it is not operated correctly,it may cause unexpected losses to the computer,after all,my colleagues experienced the nightmare of Windows updates.
The last thing I did something about how to disable Windows update.
 
Last edited:
I was in awe when a new win 10 machine I had built started up by itself and installed an update then shut back down.
I still play all my games but two on my win 7 machine. Those two I could barely play on a 7 year old win 7 machine.
I must ask why would you buy win 10 pro for a game machine?
 
Last edited:
I don't understand the issues some of you are having with updating Windows. I let mine update when it needs to, don't have any issues, stable as the rock of Gibraltar, no bsd's, no crashes of Elite. Honestly don't know what you guys are so paranoid about.
 
I've found that blocking any major update to W10 for a few weeks or a couple of months at first is good, as the initial problems that may or may not arise are sorted by MS in the meantime. Did that with 2004 and recently with 20H2, no problems. I just don't let the Windows Update to mess with my drivers, at least not with GFX drivers.
 
I'm sure hackers love exploiting your out of date PCs

You obviously don't appreciate that it is just the build version that I talk about freezing. The OS is still supported and updated and of course security updates are still applied. The point of freezing the build state is all about not incorporating the "new features" of newer builds (and in this case avoiding certain compatibility issues).

Of course once the chosen build is no longer supported (for updates, security etc) then one moves to a newer (proven) convenient build.

Maybe read the posts in the thread before making inflammatory / alarmist statements?
 
Last edited:
9/10 times I hear of people having problems with windows feature updates is because they started messing with things to not get them.

The last time is when something actually breaks during the patching process but this was always an issue.

Particularly bad on windows xp.

Run a repair, not a revert.
I'm not saying you should update on day one.
But when they are starting to push it you'll find yourself tilting at windmills real quick.
 
Back
Top Bottom