doing repair-install for 19041.1, the warning for keeping all my data

Bob1212 · 23 Mar 2021

I'm using this site's tutorial:
Repair Install Windows 10 with an In-place Upgrade

which says:

If you have Windows 10 version 20H2 installed, then it is required to have KB4586853 for build 19042.662 or higher installed to be able to do a repair install and keep everything.

I have 19041.1, but I also have the Feature Update to 20H2 (KB4562830) installed. The above warning should not pertain to me, right? So I won't have to uninstall that Feature Update, correct?

Bree · 23 Mar 2021

Bob1212 said:

I have 19041.1, but I also have the Feature Update to 20H2 (KB4562830) installed. The above warning should not pertain to me, right? So I won't have to uninstall that Feature Update, correct?

Welcome to Ten Forums Bob1212.

When you start an in-place upgrade Setup checks what version you currently have on your PC and compares that to the version you are trying to install. As long as the major build number of the installed OS (eg. 19041) is the same as, or lower than that you are trying to install, them you can keep everything.

Unfortunately there was a bug in the earlier builds of 20H2 that, when asked by Setup, misrepresented the currently installed build as being too high to allow apps to be kept. As long as your installed Windows is build 19042.662 or higher then this bug has been fixed and you'll be able to keep everything.

Bob1212 · 23 Mar 2021

Bree said:

Unfortunately there was a bug in the earlier builds of 20H2 that, when asked by Setup, misrepresented the currently installed build as being too high to allow apps to be kept.

Thank you for the welcome! And ty for the extra detail in your answer. I always appreciate knowing the 'why' of things.

erpster4 · 25 Mar 2021

Bree said:

Unfortunately there was a bug in the earlier builds of 20H2 that, when asked by Setup, misrepresented the currently installed build as being too high to allow apps to be kept. As long as your installed Windows is build 19042.662 or higher then this bug has been fixed and you'll be able to keep everything.

that 20H2 in-place upgrade repair install bug was fixed starting with the KB4586853 and KB4592438 updates which allowed keeping existing user files & apps. problem is you need to either have to create updated 20H2 installed media with KB4586853 (build 1904x.662), KB4592438 (build 1904x.685) or higher cumulative update integrated/slipstreamed thru a UUP dump [not for newbies or noobs] or obtain updated MVS based 20H2 ISO install media from generous MVS/MSDN subscriber (google search for an updated 20H2 ISO x64 image like "en_windows_10_consumer_editions_version_20h2_updated_dec_2020_x64_dvd_bde6c5a2.iso" or better which includes the 20H2 in-place bug fix to preserve existing user files & programs; then create that install media onto an 8Gb or bigger usb stick and run setup from the usb drive)

Bree · 25 Mar 2021

erpster4 said:

that 20H2 in-place upgrade repair install bug was fixed starting with the KB4586853 and KB4592438 updates which allowed keeping existing user files & apps..problem is you need to either have to create updated 20H2 installed media with KB4586853 (build 1904x.662), KB4592438 (build 1904x.685) or higher cumulative update integrated/slipstreamed....

No, that is not the case. There was a lot of activity at the time on Ten Forums investigating this bug and possible workarounds. The 'problem' was found to be entirely in the installed OS - it reported incorrect data to Setup when asked for the installed build. Setup was an 'innocent bystander' in this, merely acting on the false information it was provided with.

Once fixed by installing a CU that contains the fix, or fixed manually in the registry, then even the initial release of the ISO can successfully perform a repair install - as I reported here....

Bree said:

...I am happy to confirm that using the same 20H2 ISO as I tested before (and would only keep 'nothing'), I can now keep personal files and apps.

Known and Resolved issues for Windows 10 version 20H2 - post #159

Of course, if you do use an early ISO to do the repair install, you won't be able to do another one until you have installed the latest CU and fixed the bug (again).