[SOLVED] [W10ProV1703b16299 x64] sfc /scannow found corrupted files but was unable to fix them

T

Talb

Active member
Joined
Apr 21, 2017
Posts
30
The files are:
2017-11-30 18:47:41, Info CSI 0000196f [SR] Cannot repair member file [l:11]'dxgkrnl.sys' of Microsoft-Windows-LDDMCore, version 10.0.16299.64, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-11-30 18:47:42, Info CSI 0000198a [SR] Cannot repair member file [l:11]'dxgkrnl.sys' of Microsoft-Windows-LDDMCore, version 10.0.16299.64, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file is missing
2017-11-30 19:45:23, Info CSI 00000d23 [SR] Cannot repair member file [l:12]'SearchUI.exe' of Microsoft-Windows-Cortana.Desktop.AppxMain.Root, version 10.0.16299.19, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-11-30 19:45:25, Info CSI 00000d83 [SR] Cannot repair member file [l:12]'SearchUI.exe' of Microsoft-Windows-Cortana.Desktop.AppxMain.Root, version 10.0.16299.19, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-11-30 19:46:05, Info CSI 00001472 [SR] Cannot repair member file [l:10]'SitkaZ.ttc' of Microsoft-Windows-Font-TrueType-Sitka, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-11-30 19:46:09, Info CSI 00001516 [SR] Cannot repair member file [l:10]'SitkaZ.ttc' of Microsoft-Windows-Font-TrueType-Sitka, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-11-30 19:49:49, Info CSI 0000402f [SR] Cannot repair member file [l:17]'ExplorerFrame.dll' of Microsoft-Windows-ExplorerFrame, version 10.0.16299.15, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-11-30 19:49:51, Info CSI 0000407a [SR] Cannot repair member file [l:17]'ExplorerFrame.dll' of Microsoft-Windows-ExplorerFrame, version 10.0.16299.15, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-11-30 19:51:37, Info CSI 000053eb [SR] Cannot repair member file [l:12]'SearchUI.exe' of Microsoft-Windows-Cortana.Desktop.AppxMain.Root, version 10.0.16299.19, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-11-30 19:51:37, Info CSI 000053ed [SR] Cannot repair member file [l:10]'SitkaZ.ttc' of Microsoft-Windows-Font-TrueType-Sitka, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-11-30 19:51:37, Info CSI 000053ef [SR] Cannot repair member file [l:17]'ExplorerFrame.dll' of Microsoft-Windows-ExplorerFrame, version 10.0.16299.15, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-11-30 19:51:37, Info CSI 000053f2 [SR] Cannot repair member file [l:10]'SitkaZ.ttc' of Microsoft-Windows-Font-TrueType-Sitka, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-11-30 19:51:37, Info CSI 000053fa [SR] Cannot repair member file [l:17]'ExplorerFrame.dll' of Microsoft-Windows-ExplorerFrame, version 10.0.16299.15, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2017-11-30 19:51:38, Info CSI 00005402 [SR] Cannot repair member file [l:12]'SearchUI.exe' of Microsoft-Windows-Cortana.Desktop.AppxMain.Root, version 10.0.16299.19, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

(from sfcdetails.txt)

How do I repair these files?
 
SFCFix Script

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. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

softwaremaniac said:
SFCFix Script

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. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
Click to expand...
Yeah, so I've done a few things, first I ran the Script and it said something like could not find anything (I don't remember), so I didn't wanna mess with all that stuff and just reinstalled Windows all together (clean install from USB).
But unfortunately.. I'm still having Issues, I was still getting BSOD, so I did two things:
  1. Removed my new 8GB ram.
  2. Used the delete option in the driver verifier.
I don't know if my new ram had anything to do with it, but ever since I got it, the problem occurred (one day after I installed it), it's from a different company as my other ram and looks sorta cheap (I think?), my first ram stick is Kingston HyperX Fury 8GB 2133 DDR4, second is from a company called Team Group, but is still 8GB DDR4 2133 (TED48G2133C15bk, 1.2V), looks like a russian brand, there shouldn't be any issues right? From what I understood from CPU-Z it looked fine (dual channel memory and all)....
So, now I am not experiencing BSOD scenarios, but SFC still cannot fix some files, here's the CBS.log from the new installation:
View attachment CBS.rar
SFCFix still crashing, but it's only ReAgent.dll and xmllite.dll that SFC could not repair.
I think I'm going to return the ram stick back to see if I get BSOD with it?
Also I forgot to mention, my PC was unable to boot (got BSOD every time I booted), and apparently my SSD was corrupt, and they say the fixed the issue, idk if that's what causing the problems.
What also could have caused the issue:
  • Driver updater? I downloaded Driver Booster
  • Malware from torrents? I scanned my PC several times with Malwarebytes, Hitman Pro and Avast and found a few PUPs and apparently a Virus called GPUBoost but that's all been cleaned.
Other than that I got no clue, I could try SFCFix with the Script again?
If it helps, I could post the BSOD messages (the message sorta changed after I removed the ram)
But I don't think it's a BSOD issue anymore, because the BSOD crashes stopped once I ran delete existing setting in the verifier.
 
Actually installed the ram stick back, no issues so far.
Just need help repairing the files SFC couldn't...
Also, I don't really understand why this post was moved to windows update, this is NOT an update issue, my windows is on the latest update.
Please move back so I'll know whether to post my issue again in the Windows 10 subforum, this is no longer a BSOD issue so I don't think it belongs in the BSOD subforum, and certainly not in this subforum..
 
Hello, you've provided the SFC log and had corrupt files, and therefore I moved it in there for the experts to see it. Regarding your other issues, it seems to me like you've got a compatibility problem with your RAM. Try another one, please.
You could also test it if you want.
As far the file is concerned, I'll try to source it for you.
Let me know if you have any further questions.
 
softwaremaniac said:
Hello, you've provided the SFC log and had corrupt files, and therefore I moved it in there for the experts to see it. Regarding your other issues, it seems to me like you've got a compatibility problem with your RAM. Try another one, please.
You could also test it if you want.
As far the file is concerned, I'll try to source it for you.
Let me know if you have any further questions.
Click to expand...
Hey, sorry for the confusion, the subforum's name really confused me.
So I installed the ram stick back and seeing no BSOD, so seems like everything's good on that front, just wanted to give the full story with all the info.
only issue is that sfc can repair the files, I posted my new CBS.rar in one of the previous post, how can I fix it? Do I just download the system files again and replace them?
Thank you for your help !
 
softwaremaniac said:
Are there any available updates to isntall? If so, install them.
Click to expand...

Hi, update:
Turns out it was my ram, thought it was not but after a bit my PC started crashing again... could it be that it corrupted ReAgent.dll and xmllite.dll? well anyways, I'm getting a new ram stick tommrow (this time HyperX fury), also, turns out there was an update, but it had still not fixed these files.
 
Retrieve Components Hive
 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload toa file sharing service and just provide the link here.
 
softwaremaniac said:
Retrieve Components Hive
 1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload toa file sharing service and just provide the link here.
Click to expand...
Here you go
View attachment COMPONENTS.rar

I can also try SFCfix script again if you think it might help

View attachment CBS.rar
 
SFCFix Script

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. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.




SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

softwaremaniac said:
SFCFix Script

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. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.




SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
Click to expand...
Yes ! SFCfix worked !
Code: 
[/COLOR]SFCFix version 3.0.0.0 by niemiro.Start time: 2017-12-03 00:51:47.539
Microsoft Windows 10 Build 16299 - amd64
Using .zip script file at D:\Users\Tal B\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-xmllite_31bf3856ad364e35_10.0.16299.15_none_ac27aa8514730161
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-winre-recoveryagent_31bf3856ad364e35_10.0.16299.15_none_ddb8c9d6e107ed32\ReAgent.dll


Successfully copied file C:\Users\Tal B\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-xmllite_31bf3856ad364e35_10.0.16299.15_none_ac27aa8514730161\xmllite.dll to C:\Windows\winsxs\amd64_microsoft-windows-xmllite_31bf3856ad364e35_10.0.16299.15_none_ac27aa8514730161\xmllite.dll.
Successfully copied file C:\Users\Tal B\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-winre-recoveryagent_31bf3856ad364e35_10.0.16299.15_none_ddb8c9d6e107ed32\ReAgent.dll to C:\Windows\winsxs\amd64_microsoft-windows-winre-recoveryagent_31bf3856ad364e35_10.0.16299.15_none_ddb8c9d6e107ed32\ReAgent.dll.


Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-xmllite_31bf3856ad364e35_10.0.16299.15_none_ac27aa8514730161
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-xmllite_31bf3856ad364e35_10.0.16299.15_none_ac27aa8514730161
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-winre-recoveryagent_31bf3856ad364e35_10.0.16299.15_none_ddb8c9d6e107ed32\ReAgent.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-winre-recoveryagent_31bf3856ad364e35_10.0.16299.15_none_ddb8c9d6e107ed32\ReAgent.dll
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2017-12-03 00:51:48.579
Script hash: 0NHo9HxNYEx/IXdO9jFplzouOONMgjQTg+ddAqyBslo=

----------------------EOF-----------------------[COLOR=#333333]
sfc /scannow can't find anything either,
Thanks for everything !

Guess the lesson here is don't let your dad buy your ram for you :P
 
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