Windows 24H2 Upgrade from 21H2 Windows can't Upgrade but does not provide why

[bswhipp]

Here are errors from the setupact.log
2025-03-05 09:07:54, Error CDeploymentSession::SetEcoQos(11173): Result = 0xD0000003
2025-03-05 09:07:54, Warning GenerateDownloadList: Error requesting EcoQos: HRESULT_FROM_NT(c0000003 [Error,Facility=(system),Code=3])

2025-03-05 09:07:54, Error CDeploymentSession::IsRangeRequestSupported(4497): Result = 0x80040154
2025-03-05 09:07:54, Error IsRangeRequestSupported failed with: [80040154 [Error,Facility=FACILITY_ITF,Code=340 (0x0154)]]. Setting RangeRequestSupported to FALSE

2025-03-05 09:07:56, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Suspend(1282): Result = 0xC1800104[gle=0x00000002]

2025-03-05 09:12:35, Error CDeploymentSession::SetEcoQos(10708): Result = 0xD0000003

2025-03-05 09:12:35, Error CDeploymentSession::IsRangeRequestSupported(4339): Result = 0x80040154
2025-03-05 09:12:35, Error IsRangeRequestSupported failed with: [80040154 [Error,Facility=FACILITY_ITF,Code=340 (0x0154)]]. Setting RangeRequestSupported to FALSE
2025-03-05 09:15:21, Error CDeploymentSession::SetEcoQos(10708): Result = 0xD0000003
2025-03-05 09:19:50, Error DU DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057[gle=0x0000012a]
2025-03-05 09:19:50, Warning SP pDUSearch: DUSearch failed. hr = 0x80070057

2025-03-05 09:21:16, Error CONX aeinv: ERROR,OrphanFileFinder::GetEvidence,98,onecore\internal\base\inc\appcompat\inventory\file.cpp(2086)\aeinv.dll!00007FF9BA4F1951: (caller: 00007FF9BA531FE2) Exception(1) tid(670) 80070001 Incorrect function.##
2025-03-05 09:21:23, Error CONX acmigration: ERROR,PowerShellMatchingPlugin,268,Process timed out
2025-03-05 09:21:28, Error CONX Appraiser: ERROR,SdbpGetMatchingInfoBlocksInternal,2313,TAGREF array insufficient
2025-03-05 09:21:33, Error CONX Appraiser: ERROR,SdbpGetMatchingInfoBlocksInternal,2313,TAGREF array insufficient
2025-03-05 09:21:44, Error CONX Appraiser: ERROR,SdbpGetMatchingInfoBlocksInternal,2313,TAGREF array insufficient
2025-03-05 09:25:01, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::CheckUserInterruptEx(300): Result = 0x800704D3
2025-03-05 09:25:01, Error MOUPG CDlpActionCompat::ExecutePollingScan(2752): Result = 0x800704D3
2025-03-05 09:25:01, Error MOUPG CDlpActionCompat::ExecuteInstallReqScan(2472): Result = 0x800704D3
2025-03-05 09:25:01, Error MOUPG CDlpActionCompat::ExecuteRoutine(662): Result = 0x800704D3
2025-03-05 09:25:01, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::Execute(503): Result = 0x800704D3
2025-03-05 09:25:01, Error MOUPG CDlpTask::CheckUserInterruptEx(3094): Result = 0x800704D3
2025-03-05 09:25:01, Error MOUPG CDlpTask::CheckUserInterrupt(3147): Result = 0x800704D3
2025-03-05 09:25:02, Error MOUPG CSetupManager::ExecuteInstallMode(1115): Result = 0xC1900209
2025-03-05 09:25:02, Error MOUPG CSetupManager::ExecuteDownlevelMode(610): Result = 0xC1900209
2025-03-05 09:25:06, Error MOUPG CSetupManager::Execute(346): Result = 0xC1900209[gle=0x0000007f]
2025-03-05 09:25:06, Error MOUPG CSetupHost::Execute(517): Result = 0xC1900209[gle=0x0000007f]

 

[ChatGPT]

Hi bswhipp,
The log excerpts you provided show several errors across different components during the upgrade process. The final failure, 0xC1900209, is a common—but generic—error that Windows Setup uses when it runs into a fatal problem during the upgrade. Let’s go through some of the notable entries and what they may indicate:

• EcoQos and Range Request Errors:
   – Lines such as
    CDeploymentSession::SetEcoQos returning 0xD0000003 and
    IsRangeRequestSupported failing with 0x80040154
   suggest that the upgrade process was having trouble with its optimized download and update mechanisms. This part of the process usually attempts to leverage range-based downloads (delta updates) for efficiency. When those calls fail, the process typically falls back to a full download. While these errors alone might not be fatal, they can point to an underlying issue with how Windows Update components are interacting with your system.
• DU (Deployment Update) Errors:
   – The error from DU::CDUSession::Search indicates a failure to set an internal configuration property (hr = 0x80070057, which implies an “Invalid Parameter”). This could signal that something in the Windows Update configuration or servicing stack isn’t in the expected state.
• MOUPG Errors:
   – The MOUPG module (likely part of the modern upgrade process) is logging several errors (e.g., CDlpActionCompat::ExecuteRoutine returning 0x800704D3 and later on, CSetupManager::Execute returning 0xC1900209). These errors occur during compatibility processing, installation mode actions, or when handling install requests. The “TAGREF array insufficient” error from SdbpGetMatchingInfoBlocksInternal might be related to reading the compatibility database, which can sometimes fail if there are third-party applications or drivers that don’t quite meet the compatibility checks.
• Final Error – 0xC1900209:
   – This error is the one that causes the upgrade to roll back. It’s a generic failure code that indicates the upgrade encountered a critical issue. Given the context of the other errors, it’s likely that a problem with the Windows Update servicing components or compatibility checks is preventing the upgrade from completing.

While these errors don’t always point to one single culprit, here are some suggestions for further troubleshooting:

• Review Additional Logs: Check setuperr.log (found in the same logs folder as setupact.log) for any error messages that might provide more context or point to a specific driver, application, or component.
• Clean the Update Cache and Repair Windows Update Components: Running utilities like the Windows Update Troubleshooter, DISM, and SFC can help repair potential corruption in Windows Update components. For example:
    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
• **Disable/Uninstall Third-Party Applications:
    Anti-virus, system utilities, or other third-party drivers can sometimes interfere with the upgrade. Consider performing a clean boot or temporarily disabling/removing non-essential software before retrying the upgrade.
• Servicing Stack Update (SSU):** Ensure that your system has the latest servicing stack update installed. This update is essential for handling the upgrade process and might address some issues with the components that are failing.
  [*]Driver Compatibility:
    Double-check if any critical drivers (especially disk, network, or graphics drivers) might be problematic. Manufacturers sometimes release updated drivers specifically for major Windows upgrades.
  
  

It may take a combination of these troubleshooting steps to pinpoint exactly why the upgrade is failing. If you continue to have trouble, consider looking for or posting additional log details on Microsoft support forums—sometimes these errors have been seen with specific software or hardware configurations, especially when upgrading from one major release (21H2) to another (24H2).
Hope this helps shed some light on the issue. Let me know if you have any more questions or need further assistance!
ChatGPT**