SFC/DISM cannot repair corrupted .lnk files

Question

Hello there. I'm at my wits end and can use some help.

I have a brand new domain controller running Windows Server 2016 Standard with all the latest updates applied. Everything appears to be working fine on the server, however, I noticed some irregularities with the "search" function from the start menu.

So, I ran an "sfc /scannow" and it found corrupted files. From the looks of the log, it appears as though some of the ".lnk" files (e.g. DHCP.lnk) are corrupted.

SFC could not repair the files.

I tried the DISM RestoreHealth command and it states Error 14 - not enough storage space, which is completely ridiculous because I have literally more than 500GB free space for the OS volume.

Can someone tell me how I can get my windows image cleaned up? Listed below are the errors in the CBS log..if the entire thing is needed, please let me know.

This is a domain controller and it would be an immense pain in the rear-end to have to rebuild it.

2020-08-07 10:44:58, Info CSI 000063ed Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-d..ermanagementconsole_31bf3856ad364e35_10.0.14393.2879_none_f23c330fdc1974a5\dhcp.lnk do not match actual file [l:8]'dhcp.lnk' :
Found: {l:32 gEoZTIRXQLzL3Z8PloX0vJe0MxPBNBWfnUIKdzkWkNg=} Expected: {l:32 yMu02MNRuXhswYPGhmaM1LqrUWcPMkQpnZFuvTFpCxw=}
2020-08-07 10:44:58, Info CSI 000063ee [SR] Cannot repair member file [l:8]'dhcp.lnk' of Microsoft-Windows-DHCPServerManagementConsole, version 10.0.14393.2879, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-08-07 10:44:58, Info CSI 000063ef Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-dns-server-snapin_31bf3856ad364e35_10.0.14393.2608_none_0bf98471660cc65a\DNS.LNK do not match actual file [l:7]'DNS.LNK' :
Found: {l:32 AcO2nR9si/JcxDLEJO5T1nTIOeO8kEkaDqfGUUQNlog=} Expected: {l:32 IWJgnbMiiIZEm8yqGKjVj/aQ5szV819SsL+AA5NnbOo=}
2020-08-07 10:44:58, Info CSI 000063f0 [SR] Cannot repair member file [l:7]'DNS.LNK' of Microsoft-Windows-DNS-Server-Snapin, version 10.0.14393.2608, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-08-07 10:44:58, Info CSI 000063f1 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-g..rveradmintools-gpmc_31bf3856ad364e35_10.0.14393.3750_none_2bb3ecae0b7f5545\Group Policy Management.lnk do not match actual file [l:27]'Group Policy Management.lnk' :
Found: {l:32 ioMMt5vN1j2C1DPggwvTgJqhY31vbPoLFX76Xxk8u0g=} Expected: {l:32 nhJVlETvvC1lD9oh6AttKbT1fVNPhM6AGBb+hemLdXg=}
2020-08-07 10:44:58, Info CSI 000063f2 [SR] Cannot repair member file [l:27]'Group Policy Management.lnk' of Microsoft-Windows-GroupPolicy-ServerAdminTools-GPMC, version 10.0.14393.3750, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-08-07 10:44:58, Info CSI 000063f3@Paul Reiken /8/7:14:44:58.655 Primitive installers committed for repair
2020-08-07 10:44:58, Info CSI 000063f4 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-dns-server-snapin_31bf3856ad364e35_10.0.14393.2608_none_0bf98471660cc65a\DNS.LNK do not match actual file [l:7]'DNS.LNK' :
Found: {l:32 AcO2nR9si/JcxDLEJO5T1nTIOeO8kEkaDqfGUUQNlog=} Expected: {l:32 IWJgnbMiiIZEm8yqGKjVj/aQ5szV819SsL+AA5NnbOo=}
2020-08-07 10:44:58, Info CSI 000063f5 [SR] Cannot repair member file [l:7]'DNS.LNK' of Microsoft-Windows-DNS-Server-Snapin, version 10.0.14393.2608, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-08-07 10:44:58, Info CSI 000063f6 [SR] This component was referenced by [l:80]'Package_5472_for_KB4565511~31bf3856ad364e35~amd64~~10.0.1.8.4565511-9426_neutral'
2020-08-07 10:44:58, Info CSI 000063f7 Hashes for file member \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\DNS.LNK do not match actual file [l:7]'DNS.LNK' :
Found: {l:32 AcO2nR9si/JcxDLEJO5T1nTIOeO8kEkaDqfGUUQNlog=} Expected: {l:32 IWJgnbMiiIZEm8yqGKjVj/aQ5szV819SsL+AA5NnbOo=}
2020-08-07 10:44:58, Info CSI 000063f8 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-dns-server-snapin_31bf3856ad364e35_10.0.14393.2608_none_0bf98471660cc65a\DNS.LNK do not match actual file [l:7]'DNS.LNK' :
Found: {l:32 AcO2nR9si/JcxDLEJO5T1nTIOeO8kEkaDqfGUUQNlog=} Expected: {l:32 IWJgnbMiiIZEm8yqGKjVj/aQ5szV819SsL+AA5NnbOo=}
2020-08-07 10:44:58, Info CSI 000063f9 [SR] Could not reproject corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\DNS.LNK; source file in store is also corrupted
2020-08-07 10:44:58, Info CSI 000063fa@Paul Reiken /8/7:14:44:58.690 Primitive installers committed for repair
2020-08-07 10:44:58, Info CSI 000063fb@Paul Reiken /8/7:14:44:58.722 Primitive installers committed for repair
2020-08-07 10:44:58, Info CSI 000063fc Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-g..rveradmintools-gpmc_31bf3856ad364e35_10.0.14393.3750_none_2bb3ecae0b7f5545\Group Policy Management.lnk do not match actual file [l:27]'Group Policy Management.lnk' :
Found: {l:32 ioMMt5vN1j2C1DPggwvTgJqhY31vbPoLFX76Xxk8u0g=} Expected: {l:32 nhJVlETvvC1lD9oh6AttKbT1fVNPhM6AGBb+hemLdXg=}
2020-08-07 10:44:58, Info CSI 000063fd [SR] Cannot repair member file [l:27]'Group Policy Management.lnk' of Microsoft-Windows-GroupPolicy-ServerAdminTools-GPMC, version 10.0.14393.3750, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-08-07 10:44:58, Info CSI 000063fe [SR] This component was referenced by [l:81]'Package_5980_for_KB4565511~31bf3856ad364e35~amd64~~10.0.1.8.4565511-10191_neutral'
2020-08-07 10:44:58, Info CSI 000063ff Hashes for file member \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\Group Policy Management.lnk do not match actual file [l:27]'Group Policy Management.lnk' :
Found: {l:32 ioMMt5vN1j2C1DPggwvTgJqhY31vbPoLFX76Xxk8u0g=} Expected: {l:32 nhJVlETvvC1lD9oh6AttKbT1fVNPhM6AGBb+hemLdXg=}
2020-08-07 10:44:58, Info CSI 00006400 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-g..rveradmintools-gpmc_31bf3856ad364e35_10.0.14393.3750_none_2bb3ecae0b7f5545\Group Policy Management.lnk do not match actual file [l:27]'Group Policy Management.lnk' :
Found: {l:32 ioMMt5vN1j2C1DPggwvTgJqhY31vbPoLFX76Xxk8u0g=} Expected: {l:32 nhJVlETvvC1lD9oh6AttKbT1fVNPhM6AGBb+hemLdXg=}
2020-08-07 10:44:58, Info CSI 00006401 [SR] Could not reproject corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\Group Policy Management.lnk; source file in store is also corrupted
2020-08-07 10:44:58, Info CSI 00006402@Paul Reiken /8/7:14:44:58.789 Primitive installers committed for repair
2020-08-07 10:44:58, Info CSI 00006403@Paul Reiken /8/7:14:44:58.795 Primitive installers committed for repair
2020-08-07 10:44:58, Info CSI 00006404 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-d..ermanagementconsole_31bf3856ad364e35_10.0.14393.2879_none_f23c330fdc1974a5\dhcp.lnk do not match actual file [l:8]'dhcp.lnk' :
Found: {l:32 gEoZTIRXQLzL3Z8PloX0vJe0MxPBNBWfnUIKdzkWkNg=} Expected: {l:32 yMu02MNRuXhswYPGhmaM1LqrUWcPMkQpnZFuvTFpCxw=}
2020-08-07 10:44:58, Info CSI 00006405 [SR] Cannot repair member file [l:8]'dhcp.lnk' of Microsoft-Windows-DHCPServerManagementConsole, version 10.0.14393.2879, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-08-07 10:44:58, Info CSI 00006406 [SR] This component was referenced by [l:80]'Package_5397_for_KB4565511~31bf3856ad364e35~amd64~~10.0.1.8.4565511-9330_neutral'
2020-08-07 10:44:58, Info CSI 00006407 Hashes for file member \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\dhcp.lnk do not match actual file [l:8]'dhcp.lnk' :
Found: {l:32 gEoZTIRXQLzL3Z8PloX0vJe0MxPBNBWfnUIKdzkWkNg=} Expected: {l:32 yMu02MNRuXhswYPGhmaM1LqrUWcPMkQpnZFuvTFpCxw=}
2020-08-07 10:44:58, Info CSI 00006408 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-d..ermanagementconsole_31bf3856ad364e35_10.0.14393.2879_none_f23c330fdc1974a5\dhcp.lnk do not match actual file [l:8]'dhcp.lnk' :
Found: {l:32 gEoZTIRXQLzL3Z8PloX0vJe0MxPBNBWfnUIKdzkWkNg=} Expected: {l:32 yMu02MNRuXhswYPGhmaM1LqrUWcPMkQpnZFuvTFpCxw=}
2020-08-07 10:44:58, Info CSI 00006409 [SR] Could not reproject corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\dhcp.lnk; source file in store is also corrupted
2020-08-07 10:44:58, Info CSI 0000640a@Paul Reiken /8/7:14:44:58.859 Primitive installers committed for repair
2020-08-07 10:44:58, Info CSI 0000640b [SR] Repair complete
2020-08-07 10:44:58, Info CSI 0000640c [SR] Committing transaction
2020-08-07 10:44:58, Info CSI 0000640d Creating NT transaction (seq 1), objectname '(null)'
2020-08-07 10:44:58, Info CSI 0000640e Created NT transaction (seq 1) result 0x00000000, handle @0xa98
2020-08-07 10:44:58, Info CSI 0000640f@Paul Reiken /8/7:14:44:58.871 Beginning NT transaction commit...
2020-08-07 10:44:58, Info CSI 00006410@Paul Reiken /8/7:14:44:58.878 CSI perf trace:
CSIPERF:TXCOMMIT;6857
2020-08-07 10:44:58, Info CSI 00006411 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

Answer 1

To be honest this isn't worth all the trouble going down the \cbs.log, \dism.log, \windowsupdate.log debug rabbit hole. The much simpler / cleaner option is to demote this one (if possible), and build a new one which can be done in about 30 minutes.

The much safer / cleaner option is to seize roles to a healthy one (if needed)
https://support.microsoft.com/en-us/help/255504/using-ntdsutil-exe-to-transfer-or-seize-fsmo-roles-to-a-domain-control

then perform cleanup.
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup

then rebuild the failed one from scratch by first using dcdiag / repadmin tools to verify health correcting all errors found before starting. Then stand up the new replacement 2016, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health.

--please don't forget to Accept as answer if the reply is helpful--

Answer 2

Had the same problem and it was driving me nuts! Copied the DNS.LNK file from another 2016 server, the version there was 7/16/2016, older than on DC with DISM error.
No DISM error anymore. Blunt, but easier than rebuilding DC with ADFS setup.
Use it at your own risk.

Answer 3

Thank you for the reply. This server also has file shares on it and various users/computers pointing to it. Without going into too much detail, it would be a bit more painful than doing your suggestion. I would only consider doing that as a last resort. I don't know why Windows isn't able to repair some ".lnk" shortcut files...it's driving me insane.

It seems like these ".lnk" files should be easily repairable.

Thank you for the reply and please let me know if there's anything else I can do.

Answer 4

Not recommended to add other roles to a domain controller because of the complexity issues you now experience. Another option is to install the hyper-v role only on host, then stand up two Server 2016 standard virtual machine guests. One for active directory domain services and another for the file print server role.

--please don't forget to Accept as answer if the reply is helpful--

Answer 5

If repairing is the only option you can start a case here with product support.
https://support.microsoft.com/en-us/hub/4343728/support-for-business

--please don't forget to Accept as answer if the reply is helpful--