Upgrade Windows Server 2022 Standard to Windows Server 2025 Standard failed

The IT Guys 65 Reputation points
2026-10-22T18:43:00.3733333+00:00

I'm trying to upgrade but it is failing over and over again from WINSER 2022 to WINSER 2025

Windows for business | Windows Server | User experience | FSLogix
0 comments
Answer accepted by question author
Ronald Sabiiti 1,585 Reputation points Independent Advisor
2026-10-22T19:35:08.97+00:00

Hello @The IT Guys ,

I'm sorry the upgrade from Windows Server 2022 Standard to Windows Server 2025 Standard hasn't completed successfully. Please try the following steps to identify and resolve the issue.

  1. Back up the server: Ensure you have a verified backup of the operating system, applications, and data before proceeding.
  2. Check compatibility: Confirm the server meets the requirements, the installation media is correct, and the upgrade path supports retaining your applications and settings.
  3. Prepare the server: Install pending updates, restart the server, ensure sufficient free disk space, and temporarily remove or disable incompatible third-party security software only if your organization's policy permits.
  4. Check the setup logs: Review C:\Windows\Panther\setuperr.log and C:\Windows\Panther\setupact.log. If the upgrade was started from installation media, also check C:\$WINDOWS.~BT\Sources\Panther\.
  5. Run SetupDiag: Use Microsoft SetupDiag to identify potential upgrade blockers.
  6. Retry the upgrade: After addressing the identified issue, launch setup.exe from the Windows Server 2025 media and select Keep files, settings, and apps, if offered. Do not proceed if this option is unavailable.

If the server runs Hyper-V: Gracefully shut down or migrate running virtual machines before the maintenance window.

Microsoft documentation:

Windows Server in-place upgrade guide

SetupDiag troubleshooting tool

If the upgrade still fails, please share the error code and the relevant setup logs so we can identify the specific cause and recommend the next steps.

And if this information was helpful, please click Accept Answer.

Thank you for choosing Microsoft Q&A.

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-10-22T18:45:24.2966667+00:00

    The Windows Server 2022 Standard Desktop Experience → Windows Server 2025 Standard Desktop Experience path is supported, so identify the application, driver, or server compliance block behind Need attention before attempting Setup again.^1^

    Run a compatibility-only scan

    From an elevated Command Prompt, replace D: with the mounted ISO drive:

    D:
setup.exe /auto upgrade /noreboot /eula accept /compat scanonly /compat ignorewarning

    This runs the compatibility checks without performing another full upgrade.^2^

    After it finishes:

    1. Enable File Explorer → View → Show → Hidden items.
    2. Open the newest file matching:
      • C:\$WINDOWS.~BT\Sources\Panther\CompatData*.xml
    3. Search it for:
      • BlockingType="Hard" — identifies a blocking application.
      • BlockMigration="True" — identifies a driver that cannot migrate.
    4. Search the system drive for the newest *_APPRAISER_HumanReadable.xml.
    5. In that file, search for:
      • DT_ANY_FMC_BlockingApplication=True
      • Then locate the nearby LowerCaseLongPathUnexpanded value, which gives the path of the blocking file.

    Upgrade or uninstall the named application or driver. If the software was already removed but the appraiser identifies a leftover executable or DLL, remove that specific artifact after confirming which product installed it. Then rerun the compatibility scan. A result of 0xC1900210 means Setup found no compatibility issue; 0xC1900208 means another compatibility block remains.^2^

    Check SetupDiag results

    Windows Setup normally runs SetupDiag automatically after a failed upgrade. Open:

    C:\Windows\Logs\SetupDiag\SetupDiagResults.xml

    Look at the last reported failure, which is typically the fatal one when multiple failures are present. In particular, PlugInComplianceBlock identifies a server-specific compliance block and its required remediation.^3^

    If that file is missing or inconclusive, run the latest SetupDiag.exe from an elevated Command Prompt:

    mkdir C:\SetupDiag
SetupDiag.exe /Output:C:\SetupDiag\Results.log
notepad C:\SetupDiag\Results.log

    SetupDiag parses the existing upgrade logs and maps them to known blocking rules.^3^

    Verify prerequisites and restrictions

    Before the next attempt:

    • Take and test a full backup.
    • Confirm the ISO language matches the installed OS language.
    • Use licensed Windows Server 2025 media, not evaluation media.
    • Keep the installation type unchanged: Desktop Experience → Desktop Experience.
    • Keep the edition as Standard unless performing a supported edition upgrade.
    • If NIC Teaming is configured, disable it temporarily.
    • Confirm the server is not booting from a VHD and is not a failover-cluster node.

    These are documented in-place-upgrade restrictions and prerequisites.^1^^4^

    Also apply these workload-specific branches only if relevant:

    • Azure VM: Do not use the normal ISO-media procedure; use the Azure VM upgrade process and its assessment tool.^5^
    • Domain controller: Microsoft recommends deploying a clean Windows Server 2025 installation, promoting it, and demoting the older DC rather than using an in-place upgrade.^4^
    • Exchange Server installed: A major-version in-place OS upgrade is unsupported; migrate Exchange to a supported Windows Server installation instead.^6^

    Once the compatibility scan passes, rerun setup.exe, select Windows Server 2025 Standard (Desktop Experience) and Keep files, settings, and apps, and allow Setup to download updates so it receives current compatibility information.^4^

    References

    1. Plan your Windows Server upgrade
    2. Use Windows Setup compatibility scan logs to identify blocking issues
    3. SetupDiag
    4. Perform an in-place upgrade of Windows Server
    5. In-place upgrade for VMs running Windows Server in Azure
    6. Exchange Server supportability matrix
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.