Microsoft Patch Tuesday - November 2024

[Esben_D]

Patch Tuesday is here with 88 new fixes, with 4 rated as critical and 2 exploited. The highlight are the already exploited Windows Task Scheduler Elevation of Privilege Vulnerability and NTLM Hash Disclosure Spoofing Vulnerability. Grab the details and the audit from the November blog post.

[donohue17]

@Esben_D i seem to be having issues with Server 2019 showing patched again this month. So far Server 2022 is looking good. I hope to have a few Server 2016's patched soon to test as well. 

[RVBC]

Hi @donohue17   we are seing the same issue.  LanSweeper is reporting the version build as 10.0.17763.6530 which is causing the issue within the report as the report is set to look for  build 10.0.17763.6532 once the patches have been installed.   Our Win 2019 Srvs show the build as 10.0.17763.6532 after applying this months updates when checked through settings/ system/about.  I have found a get around by modifying the report. There are 4 instances that check for  build 6532, I simply changed this to 6530 and then the servers are shown as up to date.  Hope this helps.

[Esben_D]

This might be a similar issue as this one: https://community.lansweeper.com/t5/patch-tuesday-updates/microsoft-patch-tuesday-september-2024/bc-...

I'll have a look.

[Esben_D]

I updated the report to look for build >= 6530. I was able to confirm that Microsoft made the same mistake again

[mhaymore]

I'm having a similar issue, except Lansweeper isn't reporting the correct build number is correct on the server.

I've manually forced a rescan of the device, but Lansweeper still shows the wrong build number. How is Lansweeper pulling the build number?

Anything else to try?