September 2025 Patch audit report

[Daremo18]

Hey guys, when I run the latest Sept patch audit report devices are showing red and out of date, when the device DOES have the KB installed.  Has anyone else seen this behavior?  Note: they do say reboot may be required or reboot required but I've rebooted to no avail.

[Daremo18 · Accepted solution]

To get through patching last Friday I changed this line in the Sept query:

WHEN tsysOS.OSname = 'Win 2019' AND SubQuery2.Buildnumber >= 7786 THEN 'Up to date'

It orig read 7792, i change to 7786 which is what all my 2019 were reporting as.  Machines showed Out of Date until the KB was applied, then they went green.  THanks!

[Katgroup]

Thank you for posting this. I'm going to mark it as a solution.

We're still working to correct the issue internally.

[Jockeman1]

I also get this issue with september report, when I try to create it, never seen before.

'Try_Convert' is not a recognized built-in function name. 'Try_Convert' is not a recognized built-in function name. Incorrect syntax near the keyword 'As'. Incorrect syntax near the keyword 'As'. Incorrect syntax near the keyword 'As'. Incorrect syntax near the keyword 'As'. Incorrect syntax near the keyword 'As'. Incorrect syntax near the keyword 'As'.

[Katgroup]

You need to update your database compatibility level to >= SQL Server 2019.

View or Change the Compatibility Level of a Database - SQL Server | Microsoft Learn

[Jockeman1]

Thanks, works fine now! 👍🏼

[Daremo18]

paste that query into Notepad and replace all TRY_CONVERT with simply CONVERT.  your SQL server doesn't support that command.  

[grandfinalemike]

looking particularly at the 2019 servers, it looks for the build number of >=7792 to mark as 'up to date'

i have verified on individual servers, that in fact, the servers are at 7792

When tsysOS.OScode Like '10.0.19045%' And SubQuery2.Buildnumber >= 6332
Then 'Up to date'
When tsysOS.OSname = 'Win 2019' And SubQuery2.Buildnumber >= 7792 Then
'Up to date'
When tsysOS.OScode Like '10.0.20348%' And SubQuery2.Buildnumber >= 4166
Then 'Up to date'

but, in the scan of the report, i am seeing this as my result
Workstation/Server OS SP Version Buildnumber Highest KB Patch installed Installed On Install one of these updates
Server Win 2019 0 1809 7786 5065765 9/11/2025 0:00 KB5065428
Server Win 2019 0 1809 7786 5065765 9/11/2025 0:00 KB5065428

notice the build number is incorrect (which if retrieved correctly, would mark as up to date)

and also notice that the latest installed patch is greater than the one suggested to install.

AND, i am using the report posted here as the workaround.

[grandfinalemike]

Select Distinct Top 1000000 tsysOS.Image As icon,
tblAssets.AssetID,
tblAssets.Username,
tblAssets.AssetName,
tblAssets.Lastseen,
tblAssets.Domain,
tblAssets.IPAddress,
tsysOS.OSname,
tblAssets.SP,
SubQuery.Value As build_info
From tblAssets
Inner Join tsysOS On tsysOS.OScode = tblAssets.OScode
Left Join (Select tblRegistry.AssetID,
tblRegistry.Regkey,
tblRegistry.Valuename,
tblRegistry.Value,
tblRegistry.Lastchanged
From tblRegistry
Where
tblRegistry.Regkey Like
'%HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion%' And
tblRegistry.Valuename = 'UBR') SubQuery On SubQuery.AssetID =
tblAssets.AssetID
Inner Join tblComputersystem On tblAssets.AssetID = tblComputersystem.AssetID
Inner Join tsysIPLocations On tsysIPLocations.LocationID =
tblAssets.LocationID
Where tblComputersystem.Domainrole > 1
Order By tblAssets.Domain,
tblAssets.AssetName

this is my simple report to pull the actual build number for my servers.  im not sure how i would use this query in the patch report

[Katgroup]

That's correct. We are troubleshooting to see if there is a scan issue with 7792 not being detected.