K
Klaasklever
Installing the May 17 Cumulative Update for Server 2016 (OS Build 2273)
leads to the "SFC /scannow" command attempting to repair the file "NlsData0000.dll"
in the Windows - SysWOW64 directory. The repair is reported as "successful",
but when running the command again, another repair is attemped.
In other words: SFC /scannow never succeeds without integrity violations.
Uninstalling the May 17 CU helps (reverting to April 10, 2018 Build 2189).
No more integrity violations are shown after that.
Reinstall the May 17 CU and voila, the error returns.
Should be straightforward to reproduce (did so with two servers and a VM).
Maybe the MS guys should have bothered running the SFC command before
publishing the update, but I guess that would count as "testing"
Please fix this issue with the next update and make SFC work without errors again!
Thanks and best regards
Klaas Klever
EDIT: Still happens with the June 2018 Cumulative Update (KB4284880)
Continue reading...
leads to the "SFC /scannow" command attempting to repair the file "NlsData0000.dll"
in the Windows - SysWOW64 directory. The repair is reported as "successful",
but when running the command again, another repair is attemped.
In other words: SFC /scannow never succeeds without integrity violations.
Uninstalling the May 17 CU helps (reverting to April 10, 2018 Build 2189).
No more integrity violations are shown after that.
Reinstall the May 17 CU and voila, the error returns.
Should be straightforward to reproduce (did so with two servers and a VM).
Maybe the MS guys should have bothered running the SFC command before
publishing the update, but I guess that would count as "testing"
Please fix this issue with the next update and make SFC work without errors again!
Thanks and best regards
Klaas Klever
EDIT: Still happens with the June 2018 Cumulative Update (KB4284880)
Continue reading...