Windows 10 version 2004 being forced upon my DeskTop

I'm running version 1909 and have decided to skip the upgrade to version 2004 due to potential issues I want to avoid. Now, the 2004 upgrade has been downloaded without my conscent and is forced upon my DeskTop. I have been informed that a restart is needed and I'm urged to either let it restart now or to choose a time. Why isn't there an option to tell them to f-u-c-k off ... ... ? For Gods sake, version 20H2 is there!

 

If I hadn't noticed this hijacking of my computer, it would have been restarted automatically at 22.00 tonight, in less than two hours. I've asked in a different thread and I repeat my question: What are the inbred idiots up to ... ... ?

 

RL, thanks for the link. I took a glance but will have a better read later. What they suggest is my strategy. I create the installation media on a USB-drive, using "the tool". I use two drives and always keep one "generation" back. I never let Microsoft download and install the version upgrades but I do it the "installation media" way. (I didn't let Microsoft do it this time either but the bastards did it anyway.)

I'm also a true believer in creating images when things are working as the should and a fresh version 1909 is only an "image restore" away ... ... !

I still don't understand why version 2004 was forced upon my system when the version currently installed still is supported ... ... ?

 

Now, I've had the time to give it a more thorough read and they actually share most of my thoughts and objections. A few quotes (and my reflections) from the article:

Exactly but that's what I wasn't allowed.

Maybe MS change the behaviour when users have found ways around their "enforcing methods"?

I think that it would be a bigger problem for MS if everyone tried to get the upgrade done on the first day. So, why is it a problem that some users want to delay the installation?

How many of us have a spare machine and what would the point be to install it on a spare machine that doesn't see much use?

Yeah, right!

I don't need to click "check for updates", these optional .NET updates pop up no matter what!

That's what happened on my DeskTop!

I can confirm that but I don't remember if it was still there on 1909 Pro? On 2004 Pro it is gone!

On 1909 Home it is gone but maybe it was never there?

This is the bottom line and the point of your post. I believe that I'm skilled enough to find the group policy editor and make the changes. Maybe that's why the limitations in the Home edition are there, to prevent less skilled users from creating a disaster? Better keep them in their shakels!

Thanks for leading me to that article ... ... and sorry for the rant ... ... !

 

Well, I made the mistake of installing it when offered..

Was running fine for a few days (although some annoying differences with 1909), but then I noticed that Hyper-V was no longer working (change in virtual switch or smthing), so my backup DC was down

Then I got a BSOD, the first one in I don't know how many years, and my MotionPro VPN stopped working too (need to connect to web server), that was it!

Back to 1909, till the end of support for 1909!

 

How would you avoid it? It (2004, not 20H2) was forced upon my DeskTop and later, today actually, upon my LapTop. The timer was ticking and I wasn't able to search for other updates to the still current system!

The only thing I've noticed on the DeskTop is that it's having a go at my old FDD. I still have it for use with Norton Ghost, booted from a floppy. All previous versions left it well alone but not version 2004. It wanks the FDD at boot time (as did previous versions) but also at randomly seeming times during normal usage, me not touching the FDD. As soon as I mark a file to open it or to copy it from the SSD to a USB-stick, it wanks the FDD for no reason. Very annoying and sooner or later, the FDD will wear out !

I'm considering testing 20H2 to find out if it is worse or better!

 

I have Windows 10 PRO. It has a policy setting that will keep it on your chosen build until EOL

 

Okey, I have Windows 10 PRO on the DeskTop and will check that out, should I have to revert to 1909.

 

Hi Christer. I am running Windows 10 Pro 20H2 and haven't had any issues so far with it.

If you don't want this issue happening again enable this group policy setting, Force Windows 10 to Stay on Existing / Installed Feature Update Version.

Additionally you can use Windows Update Manager to manage Windows Updates so you can be in full control for when you want to install Windows Updates.

 

Hi Evan,

Thanks for your hints.

The first one would work on PRO but not on HOME. Also, I believe it's too late to change the GP setting when Microsoft has "set the date", telling the user that the system will get upgraded on the next restart (or whatever it said). Or maybe not, I have to look into it if it happens again.

The second one, is it available on HOME as well as on PRO?

 

Yes the Windows Update Manager works on both Home and Pro versions of Windows 10.

You also should be able to set the group policy using the registry editor instead but I am not sure if the option will stick using the Home version as I would never use the Home version of Windows 10 myself.

 

At full price, neither would I but the discount on that LapTop couldn't be resisted ... ... !