This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 89%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJP%3C/text%3E%3C/svg%3E)
Hi,
I am currently testing 2 OS versions to Upgrade to Win11 24H2 using WSUS.
Windows 11 22H2 Enterprise - Updates with no issues.
Windows 10 22H2 Enterprise - Showing as Not Applicable.
I can not see anything obvious in the get-windowsupdatelog output.
Both machines are built using an SCCM OSD with an almost identical task sequence on Hyper-V machines in the same environment.
Win10 22H2 build Upgrades to Win11 23H2 with no issues but even when it has upgraded to Win11 23H2, 24H2 still shows as Not Applicable.
Any advice appreciated.
Are the Windows 10 systems hardware compliant for Windows 11? If they are not, that's the reason why they are showing as Not Appllicable. Even with the AllowUpgradesWithUnsupportedTPMOrCPU registry key in play, WSUS does not detect the upgrade as needed. I noticed this with 23H2 as well last year - had to update those 'non-compliant' systems manually (or via deployment tool).
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 8%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKB%3C/text%3E%3C/svg%3E)
This was not my experience yesterday. I was able to get a test VM showing as applicable in WSUS and to the downloading stage on the client. Before it would go past 0% downloading it would pop up a message on the client saying it didn't meet the requirements for TPM, processor, or memory. I then gave the VM a virtual TPM, more memory, and 2 CPUs. After another check for updates, the popup message then changed to say only CPU was not compatible.
I spent quite a bit of time then trying to find out why it was complaining about CPU on the guest VM. The host is only a couple years old and 2 CPUs looks to be the minimum. I gave up and entered the AllowUpgradesWithUnsupportedTPMOrCPU registry key and was able to continue. After downloading the bits, the I was presented with yet another warning on the client saying if I continue I will be unsupported.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 9%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWL%3C/text%3E%3C/svg%3E)
Hello
Here are some insights and potential solutions based on the information available:
Enable Windows 11 24H2 Updates in WSUS: Ensure that you have enabled the updates for Windows 11 version 24H2 in the WSUS admin console. This involves selecting the appropriate products and classifications, such as "Windows 11 Client, version 24H2 and later, Servicing Drivers" and "Windows 11 Client, version 24H2 and later, Upgrade & Servicing Drivers".
Synchronization: After enabling the updates, synchronize the WSUS server to check for the latest updates. Verify if the Windows 11 24H2 updates appear in the WSUS console.
Configuration Manager: If you are using Configuration Manager (SCCM), ensure that the Windows 11 product is enabled under the Software Update Point role properties. Avoid making product selections directly in WSUS to prevent sync issues between ConfigMgr and WSUS.
If these steps do not resolve the issue, you might want to consider checking for any specific error messages in the get-windowsupdatelog output that could provide more clues. Additionally, reviewing the task sequence in SCCM for any discrepancies between the two OS versions might help identify the root cause.
RESOLVED
This issue was raised with Microsoft who had received other instances of this issue.
This has been resolved with this months updates including the updated "Windows 11, Version 24H2 x64 2024-11B" Upgrade.
I can confirm the 11B release for 22H2 is now showing applicable. Same clients that were applicable for 23H2.
@James Partridge how did you learn of this? I'm not seeing any mention of it on the release health page. Are you just assuming it was a bug they fixed? I was sort of assuming it could be how they intended to do the release phases. I assumed they had not yet given most hardware the green light until the initial rollout was complete in an effort to minimize risk.
