Windows Version different between reports

[ProspeS]

Hi
Why sometimes the Windows version is 21H2 and sometimes 2009 .... strange no ?
When I check the Windows version directly to the asset : I have 2009
when I run a Windows Tuesday Audit report the version is 21H2
and the version is really 21H2
Thanks
Stef

[MartiAtWaldi]

Hi all,

we use the 'Patch Tuesday' report to identify Windows clients that are not up-to-date. This worked so far until the last report for October. Somehow the build number is not correctly assigned to the version number and there is no such SQL case in the query like show above.

Either way the built-in report 'OS: Not latest Build of Windows 10' shows some strange build version assignments...


OS Build OS Version
Win 10 10.0.19043.985 21H1
Win 10 10.0.19043.1266 2009
Win 10 10.0.19043.1266 2009
Win 10 10.0.19043.1266 21H1
Win 10 10.0.19043.1266 21H1
Win 10 10.0.19043.1237 21H1
Win 10 10.0.19043.1237 2009
Win 10 10.0.19043.1237 2009
Win 10 10.0.19043.1237 2009
Win 10 10.0.19043.1237 21H1
Win 10 10.0.19043.1237 21H1

How is this possible?

[RCorbeil]

Odds are the Version value displayed on the asset page -- tblAssets.Version -- is something Windows is reporting. LANSweeper asks Windows to report all kinds of things about itself, and different requests for information often return slightly different values.

In this case, wherever Windows is pulling the Version information from, it clearly isn't quite consistent with the public names they're using for the release versions. As a consequence of this, when the LANSweeper folks release reports that include the Win10 version, they're ignoring the Version value and instead using the Build value to determine and display Microsoft's public version names/numbers.

How can we update the Version shows on the asset page? We can't. That's what Windows is reporting its version as. Think of it as asking someone named Michael to tell you his name and him responding "call me Mike". You want him to tell you his true name, but he keeps telling you to call him by his nickname. We'll just have to read the version and interpret it ourselves: 2009 = September 2020 = second half of 2020 = 20H2, just as recognizing that Mike = Michael.

It's not like the reported Version values are technically accurate anyway.

• 1803 was released in April, so should have been 1804.
  
• 1809 was released in October, so should have been 1810.
  
• 1903 was released in May, so should have been 1905.
  
• 1909 was released in November, so should have been 1911.
  
• 2004 was released in May, so should have been 2005.

[ProspeS]

OK thanks but how can we update the Display for the Asset line ?
the Build is displayed as '10.0.19043.1110' so normally this is 21H2
S

[RCorbeil]

The question should be "what is the source of tblAssets.Version"?

As far as the Patch Tuesday report, why it appears as "21H2" is spelled out right there in the report code:

  Case
    When tsysOS.OScode Like '10.0.10240%' Then '1507'
    When tsysOS.OScode Like '10.0.10586%' Then '1511'
    When tsysOS.OScode Like '10.0.14393%' Then '1607'
    When tsysOS.OScode Like '10.0.15063%' Then '1703'
    When tsysOS.OScode Like '10.0.16299%' Then '1709'
    When tsysOS.OScode Like '10.0.17134%' Then '1803'
    When tsysOS.OScode Like '10.0.17763%' Then '1809'
    When tsysOS.OScode Like '10.0.18362%' Then '1903'
    When tsysOS.OScode Like '10.0.18363%' Then '1909'
    When tsysOS.OScode Like '10.0.19041%' Then '2004'
    When tsysOS.OScode Like '10.0.19042%' Then '20H2'
    When tsysOS.OScode Like '10.0.19043%' Then '21H2'
  End As Version,

It displays "21H2" because tsysOS.OSCode starts with "10.0.19043". If that line in the CASE statement read

When tsysOS.OScode Like '10.0.19043%' Then 'Banana'

then is would display "Banana".