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(73.60000000000001, 78%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENI%3C/text%3E%3C/svg%3E)
WSUS Win 2019 not showing client OS install with Windows 11 correctly. it shows Windows 10 Pro version 10.0.22000.194
![](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(51.2, 83%, 14%)' 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)
If you search Registry Editor on Windows 11, you would see that the term "Windows 11" is no where to be found, all references still named "Windows 10"
so it's not WSUS fault
![](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(89.60000000000001, 81%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
What version of Windows Server are you using?
Have you download and installed all updates?
Windows Server 2019 Standard with all the latest updates installed.
You can change this in the registry of the client under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion.
It's simple as changing a character and you're all good
![](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(57.599999999999994, 75%, 15%)' 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,
im seeing this across all pc's and laptops and is now becoming a pian to update each one manually from the Cloud.
Microsoft what are you doing to resolve this?
i will not be updating these computers or laptops manually! what is the point of having WSUS when Microsoft cannot even sort this little thing out.
if you change the registry setting, on reboot it reverts back to windows 10
has anyone managed to resolve this?
if not what is Microsoft doing about this?
now saying the above, im thinking of moving over to linux, at least we dont have any issues with updating linux, but Microsoft, i will hand it to you! all money no work and screwed up software coming out of Microsoft! test your software first thoroughly!!!!
This is 'by design' from Microsoft.
Confirmed.
WAM will support Windows 11 Renaming on the next version of being released in January.
![](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(32, 9%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJI%3C/text%3E%3C/svg%3E)
Do you already know when this update is going live and the KB number?
Thank you in advance
![](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(249.60000000000002, 51%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJC%3C/text%3E%3C/svg%3E)
Adam, we did not see an update come out for this issue in January, did you? If so, what is the KB number? Thanks!
Adam, we did not see an update come out for this in January, did you? If so, what is the KB number? Thanks!
If you are subscribed to WSUS Automated Maintenance (WAM), then you would be having your Windows 11 Machines be renamed properly as of 2022.01.
Full disclosure - WAM is our software.
I Subscribed to WAM. After the -FirstRun completed, all my Windows 11 clients showed up in WSUS correctly, and detected their respective updates. Thank you.
Thank you for becoming a client, and Welcome to WSUS Freedom!
![](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(28.799999999999997, 67%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJT%3C/text%3E%3C/svg%3E)
Adam, after running 2022.1.2.0 WAM (subscriber) FirstRun, over half of our Win11 machines still show Windows 10 Pro. Anything else I can do to get them showing correctly?
Please contact us through our support site. We'll work with you to resolve the issue.
I believe this is a bug, in case you have Windows 11 or Windows 10, open start and search for feedback and open Feedback Hub app and report this issue.
![](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(124.80000000000001, 28.999999999999996%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EST%3C/text%3E%3C/svg%3E)
The problem here with this, is that the clients are not updating if they are Windows 11 I believe because of how it's reporting to WSUS. The clients have to go out to get updates, as there are already a few that have been released. The updates collect them, but the client won't get them from WSUS.
![](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(73.60000000000001, 35%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
I'm also having the same problem, has anyone managed to solve this problem?
Below change in the client registry , able to solve this issue.
Looks like it's Windows 11 at fault and not WSUS, which is simply relaying the "ProductName" value under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion. This is currently "Windows 10 [edition]" on Windows 11, even the latest Insider builds. Change the string & check into WSUS, and that's what will show up.
