Share via

Windows Server DLL Not Updated

Anonymous
2023-09-12T18:37:26+00:00

So I have a Windows 2022 VM in Azure that vulnerability scanning is flagging because of an outdated Windows system DLL that has a vunlerability that was patched.

The dll in question is winmm.dll and the version in c:\windows\system32\ is 10.0.20348.1 which should be the original version of this DLL from the launch of Server 2022.

If I check the file manifest from KB5029250 (which is installed) it lists that this file was included and should be version 10.0.20348.1906.

I ran a dism /online /cleanup-image /restorehealth and then a sfc /scannow. DISM does report image version 10.0.20348.1906 but SFC finds no problems with the DLL.

Out of desperation I even renamed the DLL and re-ran SFC only to have the DLL replaced with the 10.0.20348.1 version again.

Anyone seen this before or have any recommendations?

Windows Server | Devices and deployment | Set up upgrades and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-09-13T05:49:23+00:00

    Hi Kepabar3

    To further troubleshoot this issue, I recommend trying the following steps:

    1. Check the permissions on the winmm.dll file to ensure that the correct permissions are set for the file. You can do this by right-clicking on the file, selecting Properties, and then navigating to the Security tab.
    2. Try manually replacing the winmm.dll file with the correct version from the KB5029250 update package.

    Best Regards,

    Hania Lian

    0 comments
  2. Anonymous
    2023-09-13T14:33:12+00:00
    1. Yes, the permissions are correct.
    2. Do you have instructions on how to sucessfully do this? I actually have been trying to do so from before I posted this.

    I was able to extract the CAB files from the MSU and I see the winmm.dll file inside the CAB file, but trying to extract the individual DLL file leaves me with a 1kb empty file.

    0 comments