question

xadxad-2401 avatar image
0 Votes"
xadxad-2401 asked saldana-msft edited

Updating OS using SCCM Task Sequence

I have successfully deployed my task sequence to the target client PC. When I try to update the OS via the Software Centre, I have successfully downloaded all the required files (install.wim). However, when doing the actual upgrade, I got a 0x80004005 error.

When I ran SetupDiag.exe, I got this error:
Matching Profile found: FindAbruptDownlevelFailure - 55882B1A-DA3E-408A-9076-23B22A0472BD
SetupDiag version: 1.6.2107.27002
System Information:
Machine Name = XADW02-OUTDATED
Manufacturer = VMware, Inc.
Model = VMware Virtual Platform
HostOSArchitecture = 1033
FirmwareType = PCAT
BiosReleaseDate = 20201112000000.000000+000
BiosVendor = PhoenixBIOS 4.0 Release 6.0
BiosVersion = 6.00
HostOSVersion = 10.0.19041
HostOSBuildString = 19041.1.amd64fre.vb_release.191206-1406
TargetOSBuildString = 10.0.19041.1253 (vb_release_svc_prod2.210811-1921)
HostOSLanguageId =
HostOSEdition = EnterpriseEval
RegisteredAV = Windows Defender
FilterDrivers =
UpgradeStartTime = 4/26/2022 12:19:54 AM
UpgradeEndTime = 4/26/2022 12:20:44 AM
UpgradeElapsedTime = 00:00:50
CV = 1Pk/R+9PqE2Du5NS
ReportId =


Error: SetupDiag reports abrupt down-level failure.
Last Operation: Finalize
Error: 0xC1900204 - 0x4000B
LogEntry: 2022-04-26 00:20:18, Error MOUPG CDlpActionCompat::ExecuteMigChoiceScan(1686): Result = 0xC1900204

Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.

mem-cm-generalmem-cm-osd
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

2 Answers

SimonRenMSFT-3639 avatar image
0 Votes"
SimonRenMSFT-3639 answered GaryBlok commented

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

The error code 0xC1900204 means "The migration choice selected is not available (ex: Enterprise to Home, the wrong SKU or architecture)". Is the problematic client OEM computer? Please also make sure the upgrade is not LTSC. In-place upgrade from Windows 8.1, or Windows 10 semi-annual channel to Windows 10 LTSC is not supported.
 
During my research, I found this may be language issue or license issue (mismatch of product key). Please check the registry key 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language\InstallLanguage on the client to see if the language matchs you operating system. And also check if the product key is correct.
 
Similar error described here for your reference:
Windows 10 Inplace Issues 0xC1900204 - Configuration Manager
Windows Setup failed with hexadecimal exit code 0xC1900204
 
Here are some official articles for your reference:
Windows 10 upgrade paths
Windows 10 Pre-Upgrade Validation using SETUP.EXE

Hope it helps. Thanks for your time.

Best regards,
Simon

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 2
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

xadxad-2401 avatar image xadxad-2401 ·

Hi! I would like to say thank you for trying to help me.

I am currently trying to upgrade from "Microsoft Windows 10 Enterprise Evaluation 10.0.19041 Build 19041" to "Microsoft Windows 10 Enterprise Evaluation 10.0.19044 Build 19044". I am not upgrading to or from a LTSC version.

I looked at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Language\InstallLanguage and the install language was 0409 which is english. When I looked at my upgrade package in SCCM, I was also using EN-US.


0 Votes 0 ·
xadxad-2401 avatar image xadxad-2401 xadxad-2401 ·

I was wondering if the problem could be due to the product key not being set.

0 Votes 0 ·
GaryBlok avatar image
0 Votes"
GaryBlok answered

have you tried just using the enablement package? 19041 = 20H1 (2004), and you should be able to run the enablement package for 21H2 (19044). Take just minutes.

https://www.recastsoftware.com/resources/upgrading-to-windows-10-21h2-via-enablement-package-using-configmgr-app-model/

You should be able to use that blog to see where to grab the enablement package, and then test.

5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.