Newbie here, need help updating Windows 10 Pro 22H2 to Windows 11 Pro 25H2

bblue99 said:

<?xml version="1.0" encoding="utf-16"?>
<SetupDiag xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="SetupDiag">
<Version>1.6.0.0</Version>
<ProfileName>FindAbruptDownlevelFailure</ProfileName>
<ProfileGuid>55882B1A-DA3E-408A-9076-23B22A0472BD</ProfileGuid>
<LogErrorLine>2026-08-12 16:40:47, Error MOUPG CSetupResponseTemplate&lt;class IDlpResponse&gt;::OnCancel(238): Result = 0x800704C7</LogErrorLine>
<FailureData>Error: SetupDiag reports abrupt down-level failure.Last Operation: FinalizeError: 0x800704C7 - 0x40004</FailureData>
<FailureData>LogEntry: 2026-08-12 16:40:47, Error MOUPG CSetupResponseTemplate&lt;class IDlpResponse&gt;::OnCancel(238): Result = 0x800704C7</FailureData>
<FailureData>Refer to "Tutorial - Debug system error codes - Win32 apps" for error information.</FailureData>
<FailureDetails>ErrorCode = 0x800704C7, ExCode = 0x40004, Oper = Finalize</FailureDetails>
</SetupDiag>

Click to expand...

The SetupDiagResults.xml you posted appears to be from an earlier upgrade attempt. It is dated August 12, 2026, and reports 0x800704C7 - 0x40004 (which means Setup processed a cancellation), not the more recent 0xC1900101 - 0x40017 failure. Microsoft says SetupDiag normally runs automatically after an upgrade problem, but this file does not appear to contain the results from your latest attempt.

After the upgrade fails again with 0xC1900101 - 0x40017, you can use the SetupDiag tool to analyze the logs and try to determine what went wrong (as @pseymour mentioned earlier).

https://learn.microsoft.com/en-us/windows/deployment/upgrade/setupdiag

1. Reproduce the 0xC1900101 - 0x40017 failure.
2. Return to Windows 10 after rollback.
3. Do not start another upgrade.
4. Download and manually run the latest SetupDiag.
5. Paste the newly generated XML result into the forum.

ChatGPT:

Download the latest SetupDiag from Microsoft's page and run it from an elevated Command Prompt. In its normal online mode, SetupDiag automatically searches the current computer for the relevant Windows Setup logs; there is no need to specify the Panther or Rollback folders manually.

For example:

SetupDiag.exe /Output:C:\SetupDiagResults.xml /Format:xml /ZipLogs:False

Microsoft documents /Format:xml and confirms that, without /LogsPath, SetupDiag checks the current system for Windows Setup logs.

One qualification is important: manually running the latest SetupDiag does not guarantee that it will identify the actual driver or component. SetupDiag works by applying diagnostic rules to the underlying Setup logs. Microsoft says that if a rule matches, the result can explain why the upgrade failed and potentially how to fix it. If it produces only something generic such as:

RollbackErrorCode = 0xC1900101
ExtendedCode = 0x40017

without naming a driver or component, then you would still need the underlying setupact.log, setuperr.log, Rollback logs, and possibly setupmem.dmp.

Click to expand...

If you copy the downloaded SetupDiag.exe file to the root of the C: drive, then run the following command:

C:\SetupDiag.exe /Output:C:\SetupDiagResults.xml /Format:xml /ZipLogs:False