Server 2022 WSUS shows Windows 11 clients as Windows 10

[ajc196]

Title; See attached image I did as a test since our production WSUS is still on Server 2019.

Windows 11 sticks out by build number so it's not an Earth-shattering ordeal, but still. Any chance of this being accounted for via future updates to Server 2022? (or downlevel for those not on the bleeding edge)  Microsoft had to know this was coming, right?

 

[#2]

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.

A search on the registry shows Windows 11 littered with "Windows 10" references. Great attention to detail there guys.

[#3]

@ajc196 

I don't suggest you to do this modification in registry, because we don't know the side effects of it.

According to tests I done (installed 2 brand-new Windows Server 2019 and Windows Server 2022 ; installed a fresh Windows 11 VM), the wrong product shown in WSUS don't have an impact on proposed updates for the computer.

Proposed updates for the W11 VM (reported as Windows 10 Pro) are linked to Windows 11 product.

So it's "just" an aesthetic issue

[#4]

@AlexandreVsr

Oh for sure, I never planned on touching that registry key. As you said, it is just aesthetic. We can go by build number for now (22000) in checking things out at a glance in the WSUS console. But with the build number being tied to the Windows Update agent, that could get wonky in the future too. (see: Win10 2004/20H2/21H1/21H2 all being reported as 19041) I'd hope that with once-a-year feature updates now, that Win11 22H2 would not be an enablement package and therefore the WU agent's build would increment when it releases next year.

[#5]

@ajc196 

Hi, after 7 months the situation is the same .... this is not just an aesthetic thing; i'm migrating over 200 pc from windows 10 to windows 11 and i don't understand which pc's have migrated and which not! it is a frustrating situation. is it possible that Microsofty will not be able to correct such a silly situation?

[#6]

Same issues here. WSUS installed on Server 2019 is showing clients with Windows 11 as Windows 10.

[#7]

The bits for Win11 22H2 have been out for a while and it was never fixed there. So this will continue to be a problem for a while, unless Microsoft fixes it at random between feature updates.

My suggestion would be to give up on Microsoft and just self-fix with AJTek WAM's custom OS description functionality.

[#8]

@ajc196 maybe after the release of 22h2 this will be fixed ?

maybe they will fix the Windows Server 2022 Core product too, which is detected as « Windows (Version 10.0) »

[#9]

All Windows releases since 2015 are in the 10.0.x.x build range.  The 'retail names' like 'Windows 10', 'Windows 11', or 'Windows Server 2022' are nearly always meaningless fluff designed to cause you 'upgrade fever' so you purchase the same thing all over again.

Occasionally they'll add something useful (e.g. Windows 11's Subsystem for Android) but most of the time it's a UI 'refresh' and something they add that could have been backported just as well.  The addition of virtualization capabilities was really the last 'huge' and meaningful addition many years ago.

Releases for most companies are:  Major.Minor.Patch.Build and sometimes an additional .Package

'Windows 7', for example, was not.  It was Windows 6.1, just as Vista was Windows 6.0.  Even these days Windows '11' still appears as Windows 6.3 (a.k.a. Windows '8.1') unless an application does a manifest.  It's backward-compatibility-related.

Want to know your build?  Open cmd.exe and look at the displayed version...

[#10]

@AlexandreVsr spoiler: upgrade 22H2 has not fixed this issue. Now I am running Server 2019, WSUS ver. 2931, but I doubt Server 2022 has fixed this either.

[#11]

@BrooklynDoge 

I'm guessing Microsoft has blown off any updates to WSUS.  FYI the behavior is the same with Server 2019 or 2022. It's time to move on from WSUS.