On a computer that was upgraded to Windows 10 20H2 (19042) from version 2004, when you attempt to repair your 20H2 installation using the in-place upgrade, the “Choose what to keep” options may be grayed out.
The options “Keep personal files and apps” and “Keep personal files only” are dimmed out, and “Nothing” is the only (default) choice.
The dialog has a note at the bottom, which reads:
Your files, apps, and settings can’t be kept because your current version of Windows might be installed in an unsupported directory or you’re trying to install an older version of Windows.
The article is based on the following Windows 20 20H2 ISO (20H2 Build starts with 19042.nnn) that I downloaded from Microsoft:
- Filename: Win10_20H2_English_x64.iso
- SHA-256: e793f3c94d075b1aa710ec8d462cee77fde82caf400d143d68036f72c12d9a7e
This is because there are 19041 versions of files in the 20H2 ISO supplied by Microsoft. If you run the DISM’s get-wiminfo command-line, you can see that the ISO version is 10.0.19041, where 10.0.19042 is expected.
It’s either the wrong version in the ISO header or the 19041 bits in the ISO (including the
setup.exe wizard file) that is causing the problem.
Installing the KB4586853 update (released on
November 22, 2020 November 30, 2020) fixes this problem.
Update (November 30, 2020): Microsoft officially released the optional Cumulative Update KB4586853 via the regular Windows Update channel. You may also directly download the MSU installers via the following links:
Architecture: x64 Applies To: Windows 10 v2004, Windows 10 20H2 Size: 363.4 MB Link: windows10.0-kb4586853-x64_9c181d397b4b5d320af7e6f385ebc4bba693a95c.msu Architecture: x86 Applies To: Windows 10 v2004, Windows 10 20H2 Size: 119.1 MB Link: windows10.0-kb4586853-x86_0468c67fa7cdd1262da75bd97a9f8daac3a4f7c2.msu
After a restart, your OS will be bumped up to version
19042.662 on Windows 10 2004 and v20H2 systems, respectively.
Voilà! This brings back the “Keep personal files and apps” and “Keep personal files only” options in the Setup screen.
You may skip the rest of the article.
The following workaround was posted on Nov 22, 2020. Since Microsoft has released the KB4586853 (November 30, 2020) update, you don’t need the following workaround anyway.
Many users have indicated that uninstalling the KB4562830 update brings back the “Keep personal files and apps” and “Keep personal files only” options in the Windows 10 Setup window during in-place upgrade.
The following workaround applies if you have used “Feature Update to Windows 10 20H2 via Enablement Package (KB4562830)” to switch from v2004 to v20H2 — i.e., without running Setup using the ISO, Media Creation Tool, or the USB setup disk.
- Open the classic Programs and Features Control Panel.
- Click View installed updates
- Right-click Feature Update to Windows 10 20H2 via Enablement Package (KB4562830) and click Uninstall
Alternatively, you can run the following command-line to uninstall the update:
wusa.exe /uninstall /kb:4562830
Click Yes when you see the following prompt:
Windows Update Standalone Installer Do you want to uninstall the following Windows software update? Feature Update to Windows 10 20H2 via Enablement Package (KB4562830) [Yes] [No]
- After a reboot, your system will be rolled back to the build 19041 (2004) from 19042 (20H2).
Windows 10, versions 2004 and 20H2 share a common core operating system with an identical set of system files. Therefore, the new features in Windows 10, version 20H2 are included in the latest monthly quality update for Windows 10, version 2004 (released October 13, 2020), but are in an inactive and dormant state. These new features will remain dormant until they are turned on through the “enablement package,” a small, quick-to-install “master switch” that activates the Windows 10, version 20H2 features.
The version 20H2 enablement package is a great option for installing a scoped feature update like Windows 10, version 20H2 as it enables an update from version 2004 to version 20H2 with a single restart, reducing update downtime. This enables devices to take advantage of new features now. For version 2004 devices that receive updates directly from Windows Update, devices automatically get the enablement package by installing the feature update to Windows 10, version 20H2.
Installed 20H2 from ISO?
If you have upgraded to 20H2 using the Windows 10 ISO instead of the enablement package, you may not be able to uninstall KB4562830. Whether you try to uninstall the update via Programs and Features or using the command-line, the result would be the same.
The wusa.exe command-line would throw the following error:
Windows Update Standalone Installer Feature Update to Windows 10 20H2 via Enablement Package (KB4562830) is required by your computer and cannot be uninstalled.
And, if you use the following DISM command to uninstall the update KB4562830, the error
dism /online /remove-package /PackageName:Package_for_KB4562830~31bf3856ad364e35~amd64~~10.0.1.2
Processing 1 of 1 - An error occurred - Package_for_KB4562830 Error: 0x800f0825 Error: 0x800f0825 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
The DISM.log file would contain the following entries:
---dism.log---- Info DISM DISM Package Manager: PID=11584 TID=8104 Encountered the option "packagename" with value "Package_for_KB4562830~31bf3856ad364e35~amd64~~10.0.1.2" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine Info DISM DISM Package Manager: PID=11584 TID=8104 Package Package_for_KB4562830~31bf3856ad364e35~amd64~~10.0.1.2 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping Info DISM DISM Package Manager: PID=11584 TID=8104 Initiating Changes on Package with values: 5, 0 - CDISMPackage::Internal_ChangePackageState Error DISM DISM Package Manager: PID=11584 TID=8104 Failed initiating changes - CDISMPackage::Internal_ChangePackageState(hr:0x800f0825) Error DISM DISM Package Manager: PID=11584 TID=8104 Failed to Remove the Package. - CDISMPackage::Remove(hr:0x800f0825) Error DISM DISM Package Manager: PID=11584 TID=8104 Permanent package cannot be uninstalled. - GetCbsErrorMsg Error DISM DISM Package Manager: PID=11584 TID=8104 Failed while processing command remove-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0825) Info DISM DISM Package Manager: PID=11584 TID=8104 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0825
Update (Nov 30, 2020): The official Cumulative Update KB4586853 is the ultimate solution.
One small request: If you liked this post, please share this?One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
- Pin it!
- Share it to your favorite blog + Facebook, Reddit
- Tweet it!