Repair Install Windows 10 with an In-place Upgrade  

Any side effects reported?

OldNavyGuy said:

Any side effects reported?

None that I saw when I installed it. But if you want to play it safe and wait, then I would expect it will appear as an optional CU shortly.

I would recommend not installing KB4586853 CU Windows 10 v2004 build 19041.661 and v20H2 19042.661 now as there are no release notes/we don't even know its official purpose and it doesn't install for everyone including me.

Suggest using the proven .bat until M$ gets their shit together on this one. They've already released two versions so far, and the second still has issues.

Bree said:

None that I saw when I installed it. But if you want to play it safe and wait, then I would expect it will appear as an optional CU shortly.

No hurry for us...we're waiting a while before going to 20H2.

Others might be interested.

There are comments here, and in the main thread.

KB4586853 CU Windows 10 v2004 build 19041.661 and v20H2 19042.661

Today is Nov 14, 2020, and MS is no longer offering Win 10 Pro 64-bit version 2004, only now 20H2. How can I use the Inplace Upgrade to upgrade my 1909 to 2004 (and NOT to 20H2).

First, where do I get an .iso of 2004?

Then, when I have that .iso, what exactly do I do to make the Inplace Upgrade use that instead of reaching for 20H2?

Happy to take links if this has already been answered.

Thanks.

glnz said:

Today is Nov 14, 2020, and MS is no longer offering Win 10 Pro 64-bit version 2004, only now 20H2. How can I use the Inplace Upgrade to upgrade my 1909 to 2004 (and NOT to 20H2).

First, where do I get an .iso of 2004?

Then, when I have that .iso, what exactly do I do to make the Inplace Upgrade use that instead of reaching for 20H2?

Happy to take links if this has already been answered.

Thanks.

Uupdump.ml or HeiDoc.net: The Technology Treasure Chest

- - - Updated - - -

Repair Install Windows 10 with an In-place Upgrade

Thank you both for the replies.

- - - Updated - - -

Ztruker said:

The previous reg file did not change the ownership or permissions of the registry key. This batch file does, then applies the reg file so it does it all.

Here is a zip file that includes SETACL.EXE. Unzip to any folder, double click on Allow_20H2_Repair_Install_Keep_Everything.bat and it should work.

Attachment 305638

And the final batch file:

Code:

:: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: Written by Ztruker (TenForums.com/members/ztruker.html) 11/10/2020
:: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
@echo off
::
:: Restart as Admin if not already running as Admin
::
(Net session >nul 2>&1)||(PowerShell start """%~0""" -verb RunAs & Exit /B)
::
:: First backup existing key
::
(REG EXPORT "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\EditionVersion" %temp%\EditionVersion.Backup.reg /y) || Goto Error
::
:: Figure out where we are running from, change directory to there
::
SET ScriptDirectory=%~dp0
Set ScriptName=%~n0
Set ScriptExt=%~x0
CD /D %ScriptDirectory%
SET "REGScript=%ScriptDirectory%%ScriptName%.REG"
::
:: Use SETACL from Helge Klein to change ownership of key to administrators and give them full control
:: https://helgeklein.com/setacl/documentation/command-line-version-setacl-exe/
::
(SetACL.exe -on "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\EditionVersion" -ot reg -actn setowner -ownr "n:Administrators" -rec Yes) || Goto Error
(SetACL.exe -on "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\EditionVersion" -ot reg -actn ace -ace "n:Administrators;p:full" -rec Yes) || Goto Error
Echo.
Echo Key now owned by Administrators with Full permissions.
::
:: Reg file is below. It is written to the %temp% directory as
:: Allow_20H2_Repair_Install_Keep_Everything.reg 
:: then imported into the registry using the REG IMPORT command.
::
(Echo Windows Registry Editor Version 5.00
Echo.
Echo [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\EditionVersion]
Echo "EditionBuildBranch"="vb_release"
Echo "EditionBuildLab"="19041.vb_release.19041.508"
Echo "EditionBuildLabEx"="19041.1.amd64fre.vb_release.19041.508"
Echo "EditionBuildNumber"=dword:00004a61
Echo "EditionBuildQfe"=dword:000001fc) > "%REGScript%"
::
:: Add entries to registry.
::
Echo.
Echo Updating registry
(REG IMPORT %REGScript%) || Goto Error
Echo.
Echo Registry key updated from:
type %temp%\EditionVersion.Backup.reg
Echo.
Echo to
Echo.
type %REGScript%
Echo.
Echo If needed, a backup of the registry key is in %temp%\EditionVersion.Backup.reg
Goto Complete
::
:: Come here on any error
::
:Error
Echo An error occurred. Save the command prompt window text to examine.
Echo If needed, a backup of the registry key is in %temp%\EditionVersion.Backup.reg
Echo.
Echo ACL for key follows:
eCHO.
Powershell Get-Acl -Path 'HKLM:SOFTWARE\Microsoft\Windows NT\CurrentVersion\EditionVersion' ^| Format-List
::
:: Only exit from script. Require user to press Enter.
::
:Complete
pause

I tried this and it did not work for me. So I then downloaded the CAB file mentioned here and not sure what is happening. I tried to install it following instructions I saw. It appeared I had no "Install" in the context menu but there was an "Unzip" So I unzipped it and so far it is still working and has extracted over 4000 file so far and is not even 15% done. Not sure what this is doing. The CAB file was from here,KB4586853 CU Windows 10 v2004 build 19041.661 and v20H2 19042.661 It says it is extracting files and I have no clue what to do if and when this finishes. Any advice would be appreciated.

glnz said:

TO CONFIRM - Is it good to use this inplace upgrade technique (and select to save apps, files, etc.) to upgrade my existing 1909 to version 2004 now that 2004 is no longer offered directly by MS?

But the ISO you got did come directly from MS. Heidoc just generated a link to the MS download servers. Yes, this ISO came direct from Microsoft, it's the same ISO as you would have been offered by MS while 2004 was current. It is perfectly safe to use for an in-place upgrade.