clean install 2004 iso and update 20h2 current

steve108 said:

You didn't answer my question ....... why clean install instead of just install enablement to go from 2004 to 20H2?

Sorry. My previous post says I have windows 10 with latest update .804. I forgot to add it is 20H2.804. I do clean install to remove lot of files which are not known and not required periodically. Is it better to wait for 2104?

lvgandhi said:

Sorry. My previous post says I have windows 10 with latest update .804. I forgot to add it is 20H2.804. I do clean install to remove lot of files which are not known and not required periodically. Is it better to wait for 2104?

My crystal ball is broken, so I don't know what 2104 will have and can't answer your question. I don't even like 20H2, so still using 2004 myself.

I don't do clean installs myself, because I have too many apps and files I don't want to install from scratch, so I just uninstall or delete things I don't need. I will eventually update to 20H2 or 21xx.

lvgandhi said:

Sorry. My previous post says I have windows 10 with latest update .804. I forgot to add it is 20H2.804. I do clean install to remove lot of files which are not known and not required periodically. Is it better to wait for 2104?

A clean install with your 2004 ISO would be fine. When you check for updates it would download the .804 cumulative update (KB4601319) which is no more than 415MB. When that has installed Windows Update would offer the update to 20H2, a further 85MB for the enablement package.

As I am in metered connection, I would like to know what will be the size of download for installation and update.

Around 500MB to get you to the latest 20H2, maybe a little more for the .NET updates.


21H1 is expected in April/May. Indications are that it too will be just a small enablement package, bumping up the major build number to 19043 so there seems little point in waiting for it. The current 20H2 can already be 'upgraded' to 21H1 with a few DISM commands that recreate some of the effects of the expected enablement package, as I experimented with here....

steve108 said:

My crystal ball is broken, so I don't know what 2104 will have and can't answer your question. I don't even like 20H2, so still using 2004 myself.

I don't do clean installs myself, because I have too many apps and files I don't want to install from scratch, so I just uninstall or delete things I don't need. I will eventually update to 20H2 or 21xx.

Thanks for the response.

- - - Updated - - -

Ghot said:

OK... the next Feature Update is 21H1. It'll come April 2021.
We are on 19042.804. That is the version number for 20H2.
In the taskbar search box, type winver. If it says 19042.804, you are up-to-date.

If you want to go "back" to 2004 (19041.xxx), you can do that with a clean install.

I already do winver to know the latest update. Hence I wrote I have 20H2 804. However thanks for response to my post.

- - - Updated - - -

Bree said:

A clean install with your 2004 ISO would be fine. When you check for updates it would download the .804 cumulative update (KB4601319) which is no more than 415MB. When that has installed Windows Update would offer the update to 20H2, a further 85MB for the enablement package.
Around 500MB to get you to the latest 20H2, maybe a little more for the .NET updates.
21H1 is expected in April/May. Indications are that it too will be just a small enablement package, bumping up the major build number to 19043 so there seems little point in waiting for it. The current 20H2 can already be 'upgraded' to 21H1 with a few DISM commands that recreate some of the effects of the expected enablement package, as I experimented with here....

I got the answer required from you. Thanks.