OS: Not latest Build of Windows 10 report

[LairdDavid]

I have just installed the most recent Win10 updates.
I am now at v1909 build: 10.0.18363.476
My PC now shows up on the OS: Not latest Build of Windows 10 report.

How do I resolve this?

[Randy_J_Grigg]

Using the modified version of the report I still get one PC reporting that it has 1903 with a build of 10.0.18363.476.


assetname1 Win 10 10.0.18362.476 1903
assetname2 Win 10 10.0.18363.476 1909

[LairdDavid]

RJG wrote:
Using the modified version of the report I still get one PC reporting that it has 1903 with a build of 10.0.18363.476.


assetname1 Win 10 10.0.18362.476 1903
assetname2 Win 10 10.0.18363.476 1909

LanSweeper Support provided me with the following...

• Just to be safe, create a backup of your database first: https://www.lansweeper.com/knowledgebase/backing-up-your-installation/
• Open SQL Server Management Studio and connect to your lansweeperdb
• Copy/past the script below and run it in a New Query window
UPDATE tsysOS
SET OSCodeNumeric = 10018363
WHERE OScode = '10.0.18363'
• Restart the Lansweeper Server and web server (IIS Express or World Wide Web) services.

[grimstar]

The way this report functions (or at least is supposed to function) is that it looks at the highest value detected in your environment for Build, AKA the field that you mention as 10.0.18363.476, and if you are a device beneath that number you show up on the report. In theory, someone has a higher build number than you somehow.

Below is a modified version of this report, with the important piece being that it will show you all devices, including the one that has the highest build number. If you run it, do you end up with anything higher than 10.0.18363.476? You may have to do some creative sorting as Lansweeper gets all weird in trying to interpret the sorting on these types of numbers.

Also, you are a brave person for hopping on 1909 so early in its life cycle!

Select Top (1000000) SQ.icon,
  SQ.AssetID,
  SQ.AssetName,
  SQ.OS,
  SQ.Build,
  SQ.[OS Version]
From (Select tsysOS.Image As icon,
        tblAssets.AssetID,
        tblAssets.AssetName,
        tsysOS.OSname As OS,
        tblAssets.OScode + '.' + tblAssets.BuildNumber As Build,
        tblAssets.Version As [OS Version],
        tblAssets.Domain,
        tblAssets.Username,
        tblAssets.Userdomain,
        tblAssets.IPAddress,
        tblAssets.Description,
        tblAssetCustom.Manufacturer,
        tblAssetCustom.Model,
        tblAssetCustom.Location,
        tsysIPLocations.IPLocation,
        tblAssets.Firstseen,
        tblAssets.Lastseen,
        Cast(Replace(Replace(Replace(tblAssets.OScode, '.', ''), 'S', ''), 'R',
        '') As BIGINT) As OsCodeNumeric,
        Cast(tblAssets.BuildNumber As INT) As BuildNumber
      From tblAssets
        Inner Join tblAssetCustom On tblAssets.AssetID = tblAssetCustom.AssetID
        Inner Join tsysOS On tblAssets.OScode = tsysOS.OScode
        Left Join tsysIPLocations On tblAssets.LocationID =
          tsysIPLocations.LocationID
      Where tsysOS.OSname = 'Win 10' And tblAssetCustom.State = 1 And
        tblAssets.BuildNumber Is Not Null) SQ
Order By SQ.AssetName

[LairdDavid]

Thanks for that, the results from your script show no machines at a higher build level.

As for the early 1909, the machines it is installed onto so far are not mission-critical, our systems are pretty vanilla. (and besides, someone has to)
I have rarely hit any issues with OS version upgrades in our environment.