Microsoft Patch Tuesday - April 2025

[#1]

April Patch Tuesday brings 121 fixes including 11 critical and 1 exploited vulnerability in the Windows CLFS driver. Unusually, patches for Windows 10 Version 1507 are delayed which means affected devices remain unpatched for now ⚠️

Full breakdown and an audit to spot outdated devices in your network in the April blog.

[PatchingThings]

Hello,

I am seeing an discrepancy with the April report.

Server 2016 with installed updates are still showing out of date.

WHEN (tsysOS.OScode LIKE '10.0.14393%' OR tsysOS.OSname = 'Win 2016') AND SubQuery2.Buildnumber >= 7970 THEN 'Up to date'

WHEN (tsysOS.OScode LIKE '10.0.14393%' OR tsysOS.OSname = 'Win 2016') AND SubQuery2.Buildnumber < 7970 THEN 'KB5055521'

After installing April Updates, the Build Number on all my 2016 servers show 7969. Not 7970.
(March Build Number was 7876)

[PatchingThings]

I am also unable to get the Server 2022 to show up to date on the report.

If I go to a Server 2022 Asset and check the Quickfix section, it does reflect the KB5055526 is installed. The Build Number on the server matches the report unlike the Server 2016 Build Number I mentioned in my other comment. 

So I am not sure why Server 2022 shows Out of date and tells me to still install KB5055526 still on the April report.

[Ode2Joy]

Yep, I'm seeing the same thing here with my 2016 servers.

[PatchingThings]

For Server 2022, I swapped the following the OSname for OScode and now I am showing up to date for the 2022 server that are and I am still showing Out of date on the servers that are not updated.

WHEN tsysOS.OSname = 'Win 2022' AND SubQuery2.Buildnumber >= 3453 THEN 'Up to date'
WHEN tsysOS.OScode LIKE '10.0.20348%' AND SubQuery2.Buildnumber >= 3453 THEN 'Up to date'

WHEN tsysOS.OSname = 'Win 2022' AND SubQuery2.Buildnumber < 3453 THEN 'KB5055526'
WHEN tsysOS.OScode LIKE '10.0.20348%' AND SubQuery2.Buildnumber < 3453 THEN 'KB5055526'

[Sinan]

Every 23H2 build is up to date (5189) and yet they are still wants to be updated to build number 5191 in the report. Is it related to this:
https://answers.microsoft.com/en-us/windows/forum/all/inconsistency-in-kb5055528-release-note-os-bui...

What part should I correct in the report?

[Esben_D]

@Sinan It is indeed related to that. Microsoft has been screwing up big time this month with the build numbers it has been publishing. This will be #3 and #4 I will be correcting. I have corrected the ones I identified were wrong.

@PatchingThings The OS name should be listed in the report along with the build number. If for Server 2022 those both match, it should be green. Swapping to the version numbering would only cause a change if the devices you were looking at were identified as another OS version or weren't exactly listed as Win 2022.
Since it doesn't really matter whether OS name or Version number is used, I swapped them for the future.

@Ode2Joy I updated the 2016 build info. This was related to what @Sinan posted.

[JoaoClSantos]

See: https://community.lansweeper.com/t5/reports-analytics/sharing-sql-query-to-summarize-microsoft-tuesd...