[SOLVED] 2016 SFC Re-repair and 'Event Viewer.lnk'

[Asanam]

Hello,

Having exhaustively tested this on various systems I have come across a problem with Datacenter 2016 installed from the MS Eval site.

1. A new HV guest vm on W10 and 2016. After all updates are done there is a continual repeating error reported wihis is reported as fixed by SFC:

Repairing corrupted file \??\C:\Windows\SysWOW64\NlsData0000.dll from store

2. Once that VHD (copy) is attached to a new HV vm SFC reports:

2018-11-17 17:56:44, Info CSI 00000fba [SR] Cannot repair member file [l:16]'Event Viewer.lnk' of EventViewerSettings, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-11-17 17:56:44, Info CSI 00000fcd [SR] Cannot repair member file [l:16]'Event Viewer.lnk' of EventViewerSettings, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-11-17 17:56:44, Info CSI 00000fce [SR] This component was referenced by [l:165]'Microsoft-Windows-Server-Features-Package-AutoMerged-admin~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Server-Features-Package-AutoMerged-admin-Deployment'
2018-11-17 17:56:44, Info CSI 00000fcf [SR] This component was referenced by [l:132]'Microsoft-Windows-Server-Gui-Mgmt-Package-admin~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Server-Gui-Mgmt-Package-admin'
2018-11-17 17:56:44, Info CSI 00000fd2 [SR] Could not reproject corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\Event Viewer.lnk; source file in store is also corrupted

So, running 2 identical vms using the (effectively) same underlying hvd report 2 different SFC results.

Any thought what might be causing tis?

Many thanks.

Asanam

 

[Sysnative Windows Update]

Hello and welcome! Do you still require assistance?

 

[Asanam]

Hi,


Thanks for responding. Having done a bit of digging around I seem not to be the only person who has come across this. I am inclined to conclude that this is 'defect' of Server 2016 unless you know better. Apparently there was a fix slated for the end of the year possibly KB4467691. Actually, no. Still hasn't been fixed.


Would be most interested to hear if there's a fix.

 

[Sysnative Windows Update]

Please open Command Prompt as Administrator and enter the following commands pressing Enter after each:

reg delete  "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_none_3e3344a37f21d3c5"  /ve /f

reg delete  "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-naturallanguage6-base_31bf3856ad364e35_none_3e3344a37f21d3c5\10.0"  /ve /f

Let me know if you get the message: "The operation completed successfully."

 

[Asanam]

Yes, yes and yes��.

Scans are completing as fesired. Thank you for your advice and resolution.

 

[Sysnative Windows Update]

Excellent news! No corruptions detected?

 

[Asanam]

Runs clean now on both native and differencing disks in my lab. Onward to production deployment����.