Windows Server 2016 upgrade 2025 compatibility scan fails 0x80070003 but Server 2022 succeeds

Sullyc3po 0 Reputation points
2026-11-10T22:58:32.3633333+00:00

Windows Server 2016 → 2025 compatibility scan fails with 0x80070003 - 0x40008 in CSystemAbstraction::GetSystemVolumeNtPath / CFreeSystemPartitionDiskSpaceChecker. On the same server with no disk or partition changes, a Server 2022 compatibility scan successfully resolves \Device\HarddiskVolume1 and returns 0xC1900210. Has anyone encountered a Server 2025-specific regression in system-volume discovery on Legacy BIOS/MBR systems?

2025 Setup:

GetSystemVolumeNtPath

→ Cannot resolve \Device\HarddiskVolume1

→ 0x80070003

2022 Setup:

GetSystemVolumeNtPath

→ Detects \Device\HarddiskVolume1

→ Constructs \?\GLOBALROOT\Device\HarddiskVolume1\

→ 153 MB free / NoIssue

→ 0xC1900210

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

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-11-10T22:59:38.33+00:00

    Install Setup Dynamic Update KB5135883 before rerunning the Server 2025 scan if the installation media contains the October 2026 update; Microsoft documents this exact Server 2016 → Server 2025 failure with 0x80070003 - 0x40008 and fixes it in KB5135883.^1^

    Apply the fix

    1. Identify the media/update level.
      This documented regression applies when Server 2025 installation media includes the October 2026 update, KB5126646. Microsoft does not characterize it specifically as a Legacy BIOS/MBR defect, so the firmware type should not be changed to address this case.
    2. Obtain KB5135883 through one of its supported channels:
      • Permit Windows Setup to download Dynamic Update during Setup.
      • Download KB5135883 from the Microsoft Update Catalog and apply it to the Server 2025 installation media.
      • In WSUS, synchronize:
        • Product: Microsoft Server operating system-24H2
        • Classification: Update
      KB5135883 has no prerequisites and does not require a restart after application.^1^
    3. Alternatively, use Server 2025 media containing the November 10, 2026 fixes or later.
      The November cumulative update also lists the identical Server 2016 → Server 2025 compatibility-check failure as fixed.^2^
    4. Rerun the scan from an elevated Command Prompt:
    D:
setup.exe /auto upgrade /noreboot /eula accept ^
  /compat scanonly /compat ignorewarning
echo Exit code: %errorlevel%

    Replace D: with the mounted, updated Server 2025 media drive.

    The expected result when no compatibility block exists is 0xC1900210; 0xC1900208 indicates an actionable compatibility issue.^3^

    What this establishes

    • There is a documented Server 2025 Setup regression matching the source OS, target OS, phase, message, and exact 0x80070003 - 0x40008 code.
    • The documented applicability condition is October 2026-updated Server 2025 media.
    • The documentation does not establish Legacy BIOS/MBR as the cause.
    • A direct, media-based upgrade from Windows Server 2016 to Windows Server 2025 is supported for nonclustered systems; an intermediate Server 2022 upgrade is not required.^4^

    Because the unchanged partition layout is successfully resolved by Server 2022 Setup, avoid modifying active flags, partition types, or boot files before testing corrected Server 2025 Setup binaries. Those changes are unnecessary for the documented regression and can make the server unbootable.

    If the media predates October 2026 or the corrected scan still fails

    That would fall outside the documented KB5135883 condition. Collect the new Panther logs and verify whether the failure remains in GetSystemVolumeNtPath:

    • C:\$WINDOWS.~BT\Sources\Panther\setupact.log
    • C:\$WINDOWS.~BT\Sources\Panther\setuperr.log
    • Latest CompatData*.xml
    • Latest *_APPRAISER_HumanReadable.xml

    Dynamic Update should remain enabled so Setup receives current setup and compatibility components. After remediation, repeat the scan and verify that it returns 0xC1900210.^5^

    References

    1. KB5135883: Setup Dynamic Update for Windows Server 2025: November 10, 2026 | Microsoft Support
    2. November 10, 2026—KB5131080 (OS Build 26100.33822) | Microsoft Support
    3. Windows Setup Command-Line Options
    4. Plan your Windows Server upgrade
    5. Use Windows Setup compatibility scan logs to identify blocking issues
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Jason Nguyen Tran 30,105 Reputation points Independent Advisor
    2026-11-11T00:25:44.1033333+00:00

    Hi Sullyc3po,

    Windows Server 2022 compatibility scan successfully resolves \Device\HarddiskVolume1 and returns 0xC1900210, while the Windows Server 2025 setup fails in CSystemAbstraction::GetSystemVolumeNtPath with 0x80070003, suggests that the issue is occurring very early in the compatibility assessment phase and is related to how Setup identifies the system partition rather than a lack of disk space or a licensing problem.

    Your observation that the upgrade works when the virtual network adapter is removed is particularly interesting. This points toward a setup compatibility interaction involving installed network components, filter drivers, management agents, backup software, or virtual NIC bindings rather than an actual storage configuration issue. In cases like this, I would review Setupact.log and CompatData XML files generated during the failed scan and compare them to a successful test VM to identify what component is loaded just before the system-volume discovery failure occurs.

    Because the servers are running on Nutanix, I would also verify whether there are differences in NIC drivers, VirtIO components, endpoint security software, or monitoring agents between the development and production environments. The fact that you did not modify the disk layout and that Server 2022 can successfully enumerate the same system volume makes a true partition corruption issue less likely.

    As a practical next step, I would perform a controlled test by temporarily removing or disabling non-essential network-related software components one at a time and re-running only the compatibility scan. This can help determine whether the network adapter itself is the trigger or merely exposes another driver or filter that Setup does not handle correctly during the Server 2025 assessment process.

    Overall, I agree with your assessment that changing the partition structure does not appear to be the primary issue here. The behavior looks more like a Server 2025 Setup compatibility detection problem that is surfaced by a specific network or filtering component loaded on the production servers.

    I hope the response provided some helpful insight. If you find this answer useful, please hit “accept answer” so I know it addressed your concern.

    Jason

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.