[SOLVED] SFC hash mismatch--SFCFIX crashes

T

TripodBob

New member
Joined
Apr 15, 2020
Posts
4
Computer is Dell laptop with Windows 10.0.18363 (1909)
SFC is unable to repair file with hash mismatch. SFCFIX gives crash report immediately after start and then continues running. CBS.zip and sfcfix.txt attached. I deleted file with hash mismatch and replaced it with identical file from another computer with same OS but still get hash mismatch with SFC. What next?
 

Attachments

Code: 
2020-04-15 12:29:15, Info                  CSI    000000ad Hashes for file member [l:12]'tahomabd.ttf' do not match.
 Expected: {l:32 ml:33 b:68f92341975acc275c7d4a2ec52a1569b70e992b521c42b30f29149806421674}.
 Actual: {l:32 b:544c1d9374f18973d981b9417f19d39a17a4df811b4cea56e57c6d120770898a}.
2020-04-15 12:29:15, Info                  CSI    000000ae [SR] Cannot repair member file [l:12]'tahomabd.ttf' of Microsoft-Windows-Font-TrueType-Tahoma, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2020-04-15 12:29:15, Info                  CSI    000000af [SR] This component was referenced by [l:157]'Microsoft-Windows-Client-Desktop-Required-Package0411~31bf3856ad364e35~amd64~~10.0.18362.752.81D7CBA8C1580E955331EC320F011C6AC13DFC8195DEEDDFE06C55256C14810D'
2020-04-15 12:29:15, Info                  CSI    000000b0 Hashes for file member [l:12]'tahomabd.ttf' do not match.
 Expected: {l:32 ml:33 b:68f92341975acc275c7d4a2ec52a1569b70e992b521c42b30f29149806421674}.
 Actual: {l:32 b:544c1d9374f18973d981b9417f19d39a17a4df811b4cea56e57c6d120770898a}.
2020-04-15 12:29:15, Info                  CSI    000000b1 Hashes for file member [l:12]'tahomabd.ttf' do not match.
 Expected: {l:32 ml:33 b:68f92341975acc275c7d4a2ec52a1569b70e992b521c42b30f29149806421674}.
 Actual: {l:32 b:544c1d9374f18973d981b9417f19d39a17a4df811b4cea56e57c6d120770898a}.
2020-04-15 12:29:15, Info                  CSI    000000b2 [SR] Could not reproject corrupted file \??\C:\WINDOWS\Fonts\\tahomabd.ttf; source file in store is also corrupted

Let's try using DISM. If it doesn't fix it, it will at least give a little more information.

DISM /RestoreHealth Scan

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Right-click on the Start
    w8start.png
    button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter

    Dism /Online /Cleanup-Image /RestoreHealth

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  3. This will create a file, cbs.txt on your Desktop. Please zip and attach this to your next post.

If the zip file is larger than 8MB, please use a file sharing service such as OneDrive, DropBox, SendSpace, etc. and include the link with your reply.
 
Code: 
2020-04-17 08:35:39, Info                  CSI    00000011 StoreCorruptionRepair transaction completed.
2020-04-17 08:35:39, Warning               CBS    Current tick count: 1100 lower than last tick count: 1321. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2020-04-17 08:35:39, Info                  CBS    Repr: Finished repairing CSI store.
2020-04-17 08:35:39, Info                  CBS   
2020-04-17 08:35:39, Info                  CBS    =================================
2020-04-17 08:35:39, Info                  CBS    Checking System Update Readiness.
2020-04-17 08:35:39, Info                  CBS   
2020-04-17 08:35:39, Info                  CBS    (p)    CSI Payload Corrupt    (w)    (Fixed)    amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_10.0.18362.1_none_0229daa7f1dbe659\tahomabd.ttf
2020-04-17 08:35:39, Info                  CBS   
2020-04-17 08:35:39, Info                  CBS    Summary:
2020-04-17 08:35:39, Info                  CBS    Operation: Detect and Repair
2020-04-17 08:35:39, Info                  CBS    Operation result: 0x0
2020-04-17 08:35:39, Info                  CBS    Last Successful Step: Entire operation completes.
2020-04-17 08:35:39, Info                  CBS    Total Detected Corruption:    1
2020-04-17 08:35:39, Info                  CBS        CBS Manifest Corruption:    0
2020-04-17 08:35:39, Info                  CBS        CBS Metadata Corruption:    0
2020-04-17 08:35:39, Info                  CBS        CSI Manifest Corruption:    0
2020-04-17 08:35:39, Info                  CBS        CSI Metadata Corruption:    0
2020-04-17 08:35:39, Info                  CBS        CSI Payload Corruption:    1
2020-04-17 08:35:39, Info                  CBS    Total Repaired Corruption:    1
2020-04-17 08:35:39, Info                  CBS        CBS Manifest Repaired:    0
2020-04-17 08:35:39, Info                  CBS        CSI Manifest Repaired:    0
2020-04-17 08:35:39, Info                  CBS        CSI Payload Repaired:    1
2020-04-17 08:35:39, Info                  CBS        CSI Store Metadata refreshed:    True
2020-04-17 08:35:39, Info                  CBS   
2020-04-17 08:35:39, Info                  CBS    Total Operation Time: 1800 seconds.
2020-04-17 08:35:39, Info                  CBS    Ensure CBS corruption flag is clear
2020-04-17 08:35:39, Info                  CBS    All WCP store corruptions were fixed
2020-04-17 08:35:39, Info                  CBS    Ensure WCP corruption flag is clear
2020-04-17 08:35:39, Info                  CBS    All CSI corruption was fixed, ensure CorruptionDetectedDuringAcr is clear
2020-04-17 08:35:39, Info                  CBS    CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
2020-04-17 08:35:39, Info                  CBS    Count of times corruption detected: 1
2020-04-17 08:35:39, Info                  CBS    Seconds between initial corruption detections: -1
2020-04-17 08:35:39, Info                  CBS    Seconds between corruption and repair: 1085698

Looks good. Go ahead and try SFC again, then zip and attach the CBS log.
 
I ran SFC and this time it said it fixed corrupt file . I ran it once more and it reported no errors. I think you solved it!
 

Attachments

Code: 
2020-04-17 11:42:03, Info                  CSI    000002a6 [SR] Verify complete
2020-04-17 11:42:03, Info                  CSI    000002a7 [SR] Repairing 1 components
2020-04-17 11:42:03, Info                  CSI    000002a8 [SR] Beginning Verify and Repair transaction
2020-04-17 11:42:03, Info                  CSI    000002a9 Hashes for file member [l:12]'tahomabd.ttf' do not match.
 Expected: {l:32 ml:33 b:68f92341975acc275c7d4a2ec52a1569b70e992b521c42b30f29149806421674}.
 Actual: {l:32 b:544c1d9374f18973d981b9417f19d39a17a4df811b4cea56e57c6d120770898a}.
2020-04-17 11:42:03, Info                  CSI    000002aa [SR] Repairing corrupted file \??\C:\WINDOWS\Fonts\\tahomabd.ttf from store
2020-04-17 11:42:03, Info                  CSI    000002ab [SR] Repair complete
2020-04-17 11:42:03, Info                  CSI    000002ac [SR] Committing transaction
2020-04-17 11:42:03, Info                  CSI    000002ad Creating NT transaction (seq 1)
2020-04-17 11:42:03, Info                  CSI    000002ae Created NT transaction (seq 1) result 0x00000000, handle @0xb3c
2020-04-17 11:42:03, Info                  CSI    000002af@2020/4/17:15:42:03.792 Beginning NT transaction commit...
2020-04-17 11:42:03, Info                  CSI    000002b0@2020/4/17:15:42:03.870 CSI perf trace:
CSIPERF:TXCOMMIT;80120
2020-04-17 11:42:03, Info                  CSI    000002b1 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
2020-04-17 11:44:14, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

Looks good! Anything else I can assist you with?
 
No, that's all I needed. All is well. Thanks very much for your help. Donation forthcoming
 
Great! I'll mark the thread solved. If you encounter any problems post back and I will continue to assist you.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top