If it helps, I just checked a few random Windows 2012 R2 boxes and that DLL is at version 6.3.9600.18454 after the servers were fully patched. Two of the servers were patched by our automated solution, BMC BladeLogic, the other one was done manually by WU.
*From:* [email protected] [mailto: [email protected]] *On Behalf Of *James Anderson *Sent:* Thursday, December 8, 2016 12:05 PM *To:* [email protected] *Subject:* [NTSysADM] Nessus reports outdated version dlls after new WUP Rollups Is anyone else having issues with new server builds and the new rollup patches? I recently built two new 2012 R2 boxes - took them manually through a Windows Update patch cycle. The new rollups amazed me and I only ended up only needing a few cycles to get it fully patched. SCCM shows the server as compliant but when Nessus looks at specific DLLs patched by even patches even earlier this year. MS16-080 for example -- the versions on the files are do not match the KB designation. It's almost like the rollups are hitting some of the major points but not actually updating all the DLLs that the specific KB should. For example -- MS16-080 wants Glcndfilter.dll to be 6.3.9600.18336 but my fully patched from disc to rollup 2012 R2 server has it as 6.3.9600.16408.
