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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am testing to update Windows 11 from WSUS server. Currently we have 3 units of test client, however, there is 2 issues related to the testing.
I already ticked all the Windows 11 updates options but still the issues still persist. All of the test PC was freshly installed with Win 11 and haven't updated yet. Appreciate the helps from the community. Thank you.
![](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(204.8, 79%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPV%3C/text%3E%3C/svg%3E)
Hi, I have the same WSUS error
We have a setup, where there is Windows Server 2019, 2022, WIndows 10, Windows 11 computers... But since jannary all windows 11 computer have not got updates. All the other type works fine.
Like the 2024-07 Cumulative Update, it install on all type except. the Windows 11 computers... And here there come "Not Applicable". Do anybody know why it stopped working.
We have the good program from AJ tek, there is renaming the computer to WIndows 11 Enterprise 23H2...
But why is WSUS suddenly not pushing drivers out to the Windows 11 computers.
Help.
![](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(92.8, 23%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Internally, Windows 11 shares a lot of its core with Windows 10. WSUS might be picking up on this and reporting them as the same OS.
You can differentiate them by looking at the build number. Windows 11 will have a different build number compared to Windows 10.
This is Microsoft "BY DESIGN". The "Version" column is also not the operating system version - it's the Windows Update Agent version on the client machine. This can be different across Windows 11, Windows 10, and EACH month's CUs as you can tell from an older screenshot of mine below. The WUA does not have an 'update cadence' that follows each CU - meaning they are independent as you can see from the switch of versions of 10.x to 922.x in the screenshots below and from 922.x to 923.x in the newer screenshot at the bottom.
WAM renames the OSes properly. Full Disclosure, WAM is our product.
This being said, Windows 11 knows what it needs and internally distinguishes what updates it requires from WSUS. If your upgrade isn't working, you likely are missing an SSU, Prerequisite, haven't selected the correct products/classifications (https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-3-windows-as-a-service-waas-and-group-policy-administrative-templates/), or you have not completed the required updates for UUP (https://www.ajtek.ca/guides/how-to-prepare-for-on-prem-wsus-uup-updates/). It is also possible (but unlikely) that your client machines are simply not reporting properly - https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/