Windows pro upgradation from 1123H2 to 24h2

Question

Hi,

We are trying to upgrade system from windows 11 23H2 to 24H2 version using WSUS server, but upgradation process seems to be failed.

Request you to kindly guide us for the same.

Answer 1

Hello again Mohammed Ahmed,

How is your upgrade going? Just following up.

Like I said, your current description is not enough because "failed" could imply the update is not visible, fails to download (Error 0x80d02002), or triggers a rollback after reboot (Error 0xC1900101). Windows 11 24H2 enforces a hard block on CPUs missing the POPCNT instruction set, which manifests as a boot failure distinct from WSUS configuration issues.

To proceed with a reliable solution, you must access a failed client and examine the C:\$WINDOWS.~BT\Sources\Panther\setupact.log file. Search specifically for the string "MOUPG" to isolate the failure code or "Result" to find the rollback cause. Please reply with the exact hexadecimal error code and clarify if the failure occurs during the Windows Update download phase or after the device attempts to restart. Without this telemetry, modifying the IIS MIME types or troubleshooting the DoNotConnectToWindowsUpdateInternetLocations policy is speculative and may not address the actual compatibility block or Servicing Stack Update (SSU) prerequisite. Look forward to you soon.

VP

Answer 2

Hello Mohammed Ahmed,

The missing IIS MIME types for the Unified Update Platform (UUP) is likely a probable cause for download issues, but we can't proceed effectively without a specific error code. Your description that the process "seems to be failed" is insufficient to distinguish between a network distribution failure (WSUS side) and a client-side compatibility rollback. You must access a failed client and check the C:\$WINDOWS.~BT\Sources\Panther\setupact.log file, searching specifically for the string "MOUPG" to locate the hexadecimal error code.

If the error is 0x80d02002 or 0x80244019, check that .wim is mapped to application/x-ms-wim and .msu is mapped to application/octet-stream (or application/vnd.ms-pki.seccat depending on your specific hardening). However, if the error is 0xC1900101 or the device freezes during the SafeOS boot, this indicates a driver conflict or a hard block due to the new Windows 11 24H2 requirement for the POPCNT CPU instruction set, which cannot be bypassed. Additionally, ensure your Windows 11 23H2 clients have the latest Servicing Stack Update (SSU) installed, as outdated SSUs will fail to interpret the UUP upgrade payload regardless of your WSUS configuration. Please provide the exact error code or the last 50 lines of the setupact.log so we can rule out hardware incompatibility.

Do you find this answer useful? Should you have more questions, feel free to leave a comment. Have a nice day!

VP

Answer 3

To troubleshoot the upgrade from Windows 11 version 23H2 to 24H2 using WSUS, you should consider the following points:

1. Check for Known Issues: There have been reports of devices failing to upgrade to Windows 11 version 24H2 via WSUS, particularly if they have installed certain updates prior to the upgrade attempt. Ensure that your system is not affected by these known issues.
2. Error Codes: If you encounter specific error codes during the upgrade, such as 0x80240069, it may indicate that the download of the upgrade did not initiate or complete. Review the Windows updates log for any relevant error messages.
3. Update WSUS: Make sure that your WSUS server is fully updated and configured to support the latest Windows updates. This includes ensuring that the server is set to approve the upgrade for the devices in question.
4. Retry the Upgrade: If the upgrade fails, sometimes simply retrying the process after ensuring that all updates are applied can resolve the issue.
5. Consult Documentation: Refer to Microsoft's official documentation for any specific guidance related to your situation, including any necessary updates or configurations needed for WSUS.

If you continue to experience issues, it may be beneficial to consult with your IT administrator or Microsoft support for further assistance.

---

References:

• 0x800F0818 - 0x20003 error during upgrade from Windows 10 to Windows 11
• Resolved issues in Windows 11, version 23H2