Forum Discussion

ajc196's avatar
ajc196
Iron Contributor
Oct 15, 2021

Server 2022 WSUS shows Windows 11 clients as Windows 10

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?

 

 

 

Windows Server

10 Replies

  • ajc196's avatar
    ajc196
    Iron Contributor
    Aug 22, 2022
    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.
    • AlexandreVsr's avatar
      AlexandreVsr
      Copper Contributor
      Aug 22, 2022

      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) »

      • BrooklynDoge's avatar
        BrooklynDoge
        Copper Contributor
        Nov 16, 2022

        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.

  • ajc196's avatar
    ajc196
    Iron Contributor
    Oct 21, 2021
    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.
    • AlexandreVsr's avatar
      AlexandreVsr
      Copper Contributor
      Nov 09, 2021

      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

       

       

       

      • ajc196's avatar
        ajc196
        Iron Contributor
        Nov 09, 2021
        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.

Resources