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...
Windows Server
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.

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

        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.

    • WarsawPact's avatar
      WarsawPact
      Copper Contributor
      Oct 19, 2022

      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...

Resources