J
jtrimme
I have two 2016 servers. Recently I ran a Nessus scan against them and it told me I needed to install Kb4465659 (Servicing stack update for Windows Server 2016) because the C:\Windows\system32\Cmifw.dll file version was 10.0.14393.351 and it should be 10.0.14393.693. I checked WSUS and found the update was said Not Applicable for these two servers but the update had been superseded by KB4485447. I checked and both servers did have this update installed.
I checked the file list for both KB's and found the version of Cmifw.dll to be 10.0.14393.693. So far so good. I then went to both server and did a search for Cmifw.dll and did find two files with the correct version, but both files were in the WinSxS folder. My question is, if the update put the newer files in the WinSxS folder why did it not update the file in C:\Windows\sytem32. Could there be a reason this file was not updated or does Nessus have it all wrong. Trying to figure this out without calling Microsoft and having to pay for the answer.
Continue reading...
I checked the file list for both KB's and found the version of Cmifw.dll to be 10.0.14393.693. So far so good. I then went to both server and did a search for Cmifw.dll and did find two files with the correct version, but both files were in the WinSxS folder. My question is, if the update put the newer files in the WinSxS folder why did it not update the file in C:\Windows\sytem32. Could there be a reason this file was not updated or does Nessus have it all wrong. Trying to figure this out without calling Microsoft and having to pay for the answer.
Continue reading...