In-Place Upgrade 2019 to 2025 failed error "0x80070003 - 0x40008"

Paul Lovegrove 106 Reputation points
2026-10-14T13:15:18.49+00:00

I have been trying to do an in-place upgrade on one of our servers.

At the point it checks the server i get the following error

"Sorry, we're having trouble determining if your PC can run Windows server. Please close setup and try again. Error 0x80070003 - 0x40008

I have tried repairing using Dism & SFC, I have tried repairing the UEFI partition also. Still fails.

Partition 1 System

Partition 2 Reserved

Partition 3 Primary (OS C drive)

Setupact

2026-10-14 14:02:37, Error ConX::Compatibility::CSystemAbstraction::HostIsUEFIDiskLayout: Failed to retrieve system partition NT path.[gle=0x00000001]

2026-10-14 14:02:37, Error CHostIsUEFICompliantChecker failed. [Failed to check whether host has UEFI disk layout.] HRESULT = 0x80070003[gle=0x00000001]

Setuperr

2026-10-14 14:02:26, Error CDeploymentSession::IsRangeRequestSupported(4895): Result = 0x80040154

2026-10-14 14:02:26, Error IsRangeRequestSupported failed with: [80040154 [Error,Facility=FACILITY_ITF,Code=340 (0x0154)]]. Setting RangeRequestSupported to FALSE

2026-10-14 14:02:27, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Suspend(1282): Result = 0xC1800104[gle=0x00000002]

2026-10-14 14:02:27, Error MOUPG CDlpTask::CheckUserInterruptEx(3094): Result = 0x800704D3

2026-10-14 14:02:27, Error MOUPG CDlpTask::CheckUserInterrupt(3147): Result = 0x800704D3

2026-10-14 14:02:27, Error MOUPG CSetupManager::ExecuteInstallMode(1055): Result = 0x800705BB

2026-10-14 14:02:27, Error MOUPG CSetupManager::ExecuteDownlevelMode(609): Result = 0x800705BB

2026-10-14 14:02:27, Error MOUPG CSetupManager::Execute(345): Result = 0x800705BB[gle=0x0000007f]

2026-10-14 14:02:27, Error MOUPG CSetupHost::Execute(517): Result = 0x800705BB[gle=0x0000007f]

2026-10-14 14:02:33, Error CallPidGenX: PidGenX function failed on this product key. (hr = 0x8a010001)

2026-10-14 14:02:33, Error MOUPG CDlpActionProductKeyValidate::ReportDownlevelInstallChannel(3651): Result = 0x8A010001

2026-10-14 14:02:33, Error MOUPG ProductKey: Failed to report Host OS channel to telemetry.

2026-10-14 14:02:37, Error CONX hwreqchk: ERROR,Windows::Compat::HardwareRequirements::HardwareRequirementSettings::IsMeteredConnection,29,Failed to get NetworkCostType assuming metered network [0x80004005].

2026-10-14 14:02:37, Error CONX hwreqchk: ERROR,Windows::Compat::HardwareRequirements::HardwareRequirementSettings::IsMeteredConnection,29,Failed to get NetworkCostType assuming metered network [0x80004005].

2026-10-14 14:02:37, Error ConX::Compatibility::CSystemAbstraction::HostIsUEFIDiskLayout: Failed to retrieve system partition NT path.[gle=0x00000001]

2026-10-14 14:02:37, Error CHostIsUEFICompliantChecker failed. [Failed to check whether host has UEFI disk layout.] HRESULT = 0x80070003[gle=0x00000001]

2026-10-14 14:02:37, Error ConX::Compatibility::CSystemAbstraction::GetSystemVolumeNtPath: Failed to retrieve system partition NT path.[gle=0x00000001]

2026-10-14 14:02:37, Error CFreeSystemPartitionDiskSpaceChecker failed. [Failed to retrieve system volume NT path.] HRESULT = 0x80070003[gle=0x00000001]

2026-10-14 14:02:37, Error ConX::Compatibility::CCompatibilityHost::SetScanResult: Compat scan from provider wsc:setup: failed. HRESULT = 0x80070003

2026-10-14 14:02:41, Error MOUPG CDlpActionCompat::ExecuteSysReqScan(725): Result = 0x80070003

2026-10-14 14:02:41, Error MOUPG CDlpActionCompat::ExecuteRoutine(529): Result = 0x80070003

2026-10-14 14:02:41, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::Execute(503): Result = 0x80070003

2026-10-14 14:02:41, Error MOUPG CDlpTask::ExecuteAction(3334): Result = 0x80070003

2026-10-14 14:02:41, Error MOUPG CDlpTask::ExecuteActions(3487): Result = 0x80070003

2026-10-14 14:02:41, Error MOUPG CDlpTask::Execute(1643): Result = 0x80070003

2026-10-14 14:02:41, Error MOUPG CSetupManager::ExecuteTask(3267): Result = 0x80070003

2026-10-14 14:02:41, Error MOUPG CSetupManager::ExecuteTask(3229): Result = 0x80070003

2026-10-14 14:02:41, Error MOUPG CSetupManager::ExecuteInstallMode(1142): Result = 0x80070003

2026-10-14 14:02:41, Error MOUPG CSetupManager::ExecuteDownlevelMode(684): Result = 0x80070003

2026-10-14 14:02:42, Error MOUPG CSetupManager::Execute(389): Result = 0x80070003[gle=0x0000007f]

2026-10-14 14:02:42, Error MOUPG CSetupHost::Execute(563): Result = 0x80070003[gle=0x0000007f]

Any help here would be very appreciated.

Thanks

Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

1 answer

Sort by: Most helpful
  1. AI answer

    2026-10-14T13:15:43.0366667+00:00

    The failure is occurring during the compatibility scan because Setup cannot retrieve the system partition NT path:

    • HostIsUEFIDiskLayout: Failed to retrieve system partition NT path
    • GetSystemVolumeNtPath: Failed to retrieve system partition NT path
    • CFreeSystemPartitionDiskSpaceChecker failed
    • Compat scan ... failed. HRESULT = 0x80070003

    For 0x80070003, the documented cause is missing or damaged servicing stack content under C:\Windows\WinSxS, which prevents DISM and the upgrade engine from completing upgrade operations.

    Recommended path:

    1. Back up the server before making changes.
    2. Verify the servicing-stack-related failure indicators in these logs:
      • C:$WINDOWS.~BT\Sources\Panther\SetupAct.log
      • C:$WINDOWS.~BT\Sources\Panther\setuperr.log and other MOSetup/MOU. logs
      • C:\Windows\Logs\DISM\DISM.log
      • C:\Windows\Logs\CBS\CBS.log
      Search for:
      • 0x80070003
      • Failed to open new session: (DISM_{GUID})
      • Operation failed: Process Drivers for Migration. Error: 0x80070003
      • MoSetupPlatform: Using action error code: [0x80070003]
      • CDlpActionDriverMigrate::ExecuteRoutine: Result = 0x80070003
      • Failed to bind the online servicing stack - CDISMOSServiceManager::get_ServicingStackDirectory(hr:0x80070003)
      • Failed to create worker session
    3. Check C:\Windows\WinSxS for servicing stack folders whose names include servicingstack. Those folders should not be empty.
    4. Confirm the current servicing stack version:
         reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version"
      
    5. Create a temporary folder such as C:\TemporaryFolder.
    6. Download the latest Servicing Stack Update for the installed Windows version, then extract the .msu package:
         expand -F:* C:\<Path>\update.msu C:\TemporaryFolder
      
    7. Replace the corrupted servicing stack folders in C:\Windows\WinSxS using robocopy /B. Caution:
      • Do not take ownership of WinSxS or change its permissions.
      • robocopy /B is used specifically to preserve file and folder permissions.
      In an elevated PowerShell window:
         $src = "C:\TemporaryFolder"
         $dst = "C:\Windows\WinSxS"
         $log = "C:\Repair\WinSxS_Repair.log"
         
         New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
      
      Preview only:
         Get-ChildItem -Path $src -Directory -Force | ForEach-Object {
           & robocopy $_.FullName $dst /E /COPYALL /B /R:0 /W:0 /L /NFL /NDL /NP /NJH /NJS
         }
      
      Perform the copy:
         Get-ChildItem -Path $src -Directory -Force | ForEach-Object {
           & robocopy $_.FullName $dst /E /COPYALL /B /R:0 /W:0 /LOG+:$log
         }
      
      Alternative from an elevated Command Prompt:
         for /d %i in (C:\TemporaryFolder\*) do robocopy "%i" "C:\Windows\WinSxS" /E /COPYALL /B /R:0 /W:0
      
    8. Retry the in-place upgrade after the SSU files are restored.

    Since DISM, SFC, and UEFI partition repair were already tried, the next supported remediation from the documentation is to validate and repair the servicing stack files in WinSxS. If the upgrade still fails afterward, the documented guidance is to contact Microsoft Support and provide the missing path or file identified in the logs.


    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?