Updating from 2004 to 21H1

Topic

New Reply

I am trying to stay a little more current…..last time I upgraded to 2004 I used an ISO to update.

 

Given my jump is much smaller this time is the recommendation to just let windows update do its thing or generate an ISO like last time and run that?

And as I type this I realize that 21H1 has not been out that long so perhaps I am better off just waiting some more!

Thanks,

WSBJB

 

Reply | Quote

Replies

The ISO update should be slower.  With an SSD the enablement package mini update could be 5 minutes and the ISO could be 30 minutes.  If you have a non-SSD the ISO could be over an hour.

Reply | Quote

Use the TRV method. Download the required file and double click it, then wait for Windows Update to do its thing.

cheers, Paul

1 user thanked author for this post.

WSBJB

Reply | Quote

My OS drive is an SSD.  If I used an ISO it would be on a mechanical internal drive on the same PC.

Sounds like you are saying it is better to use windows update or run the Windows Update Assistant on the PC?

 

WSBJB

 

Reply | Quote

If you have the Pro Edition, use Group Policy as described in AKB2000016 Guide for Windows Update Settings for Win10. Use Section 5 and the screenshots at the end under the instructions. Set Target Release Version to 20H2.

If you have The Home Edition, download Susan’s .reg file 20H2.reg, put it on your Desktop, and double click on it. It will set the Target Release Version (TRV) to 20H2 in the Registry so you don’t get 21H1. The explanation of whet the .reg file does is in AKB2000016 Section 2.

Use Windows Update for the upgrade.

1 user thanked author for this post.

WSBJB

Reply | Quote

Thanks to you both for your input. One solution involves editing the registry, the other uses group policy. I am comfortable with either one and then I guess I just use windows update and it will “find it” after making the changes.

Is the reason I have to do either of these things because otherwise windows update will not yet download this new version?

If that is the only reason and it will eventually be offered to me in a month or two, I am in no hurry to force it just to get it right now.  I just want to install it in the manner that is most reliable.

WSBJB

 

Reply | Quote

The settings I suggested will guarantee you get v20H2 instead of 21H1 through Windows Update if there are no problems and everything works right., nothing more.
They don’t make something work that does not work, ie, fix problems..

1 user thanked author for this post.

WSBJB

Reply | Quote

Got it.. Thanks, that’s what I thought.

And there is never a guarantee of no issues with Windows Updates 🙂

 

 

Reply | Quote

I guess one could read between the lines and think it’s ok – but has anyone had issues going from 2004 directly to 21h1, skipping 20h2? Should it be ok?

Reply | Quote

2004, 20H2, and 21H1 all have the same core, they all get the same Cumulative Updates and Servicing Stacks. The only difference is which Feature Enhancement Pack is turned on. If you are going to have problems with an update, it will effect all three versions.

If you update 2004 to its latest CU first, then the upgrade to 21H1 is just turning on the switches to give you the Enhancements. You should have no problems going from 2004 to 21H1.

1 user thanked author for this post.

jaman57

Reply | Quote

Upgraded both my PCs from 2004 to 21h1 back in March and haven’t had any problems with either one.

1 user thanked author for this post.

jaman57

Reply | Quote

I never did get the above done. I am on 2004 and now Adobe is requiring me to update to upgrade to their most recent versions.

What is the best method these days to upgrade?  Just use the media creation tool and create an ISO?   Or do I need to use that 3rd party tool to download the right version?

Any issues going all the way from 2004 to the most recent Windows 10 version? I dread doing these but now I have to…

O yes, this PC is not Windows 11 upgrade compatible as it is not TPM 2.0 compliant…

Thanks as always,

WSBJB

 

Reply | Quote

The very first thing you should do, before you upgrade is make a full disk image of your computer and a separate file backup of your personal data (under your User ID C:\Users\<yourID>\)

The easiest way to upgrade is to use the Registry setting for the version you want. It works for both Home and Pro (you didn’t say which you have). You can download the script file here:

https://www.askwoody.com/forums/topic/6000003-registry-keys-and-group-policy-settings-to-select-specific-feature-rele/

I would suggest you upgrade to version 21H2, since 22H2 just came out and we haven’t seen if it causes any problems yet. You should use an ID that is an Admin, not a Standard ID to do this.
Download the script. Put it on your desktop and double click it. Give the permissions. It will create the Registry entries that cause Windows Update to look for version 21H2. And just wait for Windows Update to do the rest. The next time Windows Update searches for updates, it will offer you the 21H2 upgrade. You can treat this as a usual update and install it.

If you are using a third-party AntiVirus, you may want to turn it off before you start the upgrade.

EDIT: When you get ready to update/upgrade again, you will need to use a different script to move to the next version.

Reply | Quote

Thanks!  Sorry, I am on Windows 10 Pro.

And for sure, I have weekly backups of the drives both to my NAS and to the cloud. Great advice!

I checked out those links and even though they talk about using those registry entries to stay on a certain version of Windows 10, those same entries force an upgrade if you are not on that version?  Do I have that right?

I am fine using windows update to do this. However I have changed every setting I can over the years to delay having Windows update do things on its own as it just loves to install it’s own drivers for things that I already have newer/better drivers for.  I assume if I use  this registry Windows update method it will probably try to do all that and I will just have to re-update those drivers?

Thinking back several years I think I tried windows update for a major version rev and ended up using the ISO due to an issue. But I will do whatever works best as of now!

Thanks again,

WSBJB

 

Reply | Quote

Since you are on Pro, there is an easier way to set the TargetReleaseVersion (TRV) using Group Policy (That’s what the script does using Registry settings).

I suggest you read through AKB2000016 for how to do this. Sections 4 and 5 are specifically for Pro. The most important setting is the “2” (notify download/install). What this dows is trap the updates in the Windows Update queue until you click a “Doenload” button (not “Check for updates). The other settings that are important are the ProduceVersion and the TargetReleaseVersion. You can choose to stay on Win10 and choose the version you want to install (or stay on). Don’t worry about the deferal settings mentioned, just leave them “Not Configured.” There are screenshots below to show you where the settings are in GP.

Once the updates are controled in this way, you can use wushowhide.diagcab to hide updates you don’t want (there is a download link in Section 1 or 2). And DO NOT use “Pause” with the GP settings. wushowhide uses the Windows Update Service to search for updates, and “Pause” stops that Service

If you have any questions, come back and ask.

 

Reply | Quote

Outstanding! Thanks.

WSBJB

Reply | Quote