Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

sfc & dism cannot repair corrupted system files


  • Please log in to reply
4 replies to this topic

#1 walkerjohn

walkerjohn

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:02 AM

Posted 28 March 2016 - 03:16 PM

sfc reports the following as corrupted:

 2016-03-28 15:32:02, Info                  CSI    00005d51 [SR] Cannot repair member file [l:24{12}]"kernel32.dll" of Microsoft-Windows-Kernel32, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, file is missing2016-03-28 15:32:02, Info                  CSI    00005d53 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-28 15:32:02, Info                  CSI    00005d55 [SR] Cannot repair member file [l:14{7}]"VGX.dll" of Microsoft-Windows-IE-VGX, Version = 11.0.10240.16425, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-28 15:32:02, Info                  CSI    00005d57 [SR] Cannot repair member file [l:30{15}]"NlsData0000.dll" of Microsoft-Windows-NaturalLanguage6-base, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-28 15:32:02, Info                  CSI    00005d59 [SR] Unable to repair \SystemRoot\WinSxS\amd64_microsoft-windows-kernel32_31bf3856ad364e35_10.0.10240.16384_none_9bbe56eff0f8d352\\[l:24{12}]"kernel32.dll"
2016-03-28 15:32:02, Info                  CSI    00005d5a [SR] Repaired file \SystemRoot\WinSxS\amd64_microsoft-windows-kernel32_31bf3856ad364e35_10.0.10240.16384_none_9bbe56eff0f8d352\\[l:24{12}]"kernel32.dll" by copying from backup
2016-03-28 15:32:02, Info                  CSI    00005d5c [SR] Cannot repair member file [l:24{12}]"kernel32.dll" of Microsoft-Windows-Kernel32, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, file is missing
2016-03-28 15:32:02, Info                  CSI    00005d5d [SR] This component was referenced by [l:334{167}]"Microsoft-Windows-Client-Features-Package-AutoMerged-base~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-Package-AutoMerged-base-Deployment"
2016-03-28 15:32:02, Info                  CSI    00005d5f [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\System32"\[l:24{12}]"kernel32.dll"; source file in store is also corrupted
2016-03-28 15:32:02, Info                  CSI    00005d63 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-28 15:32:02, Info                  CSI    00005d64 [SR] This component was referenced by [l:258{129}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.RemoteFX clientVM and UMTS files and regkeys"
2016-03-28 15:32:02, Info                  CSI    00005d67 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted
2016-03-28 15:32:02, Info                  CSI    00005d6b [SR] Cannot repair member file [l:30{15}]"NlsData0000.dll" of Microsoft-Windows-NaturalLanguage6-base, Version = 10.0.10240.16384, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-28 15:32:02, Info                  CSI    00005d6c [SR] This component was referenced by [l:370{185}]"Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-enduser~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-enduser-Deployment"
2016-03-28 15:32:02, Info                  CSI    00005d6f [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:30{15}]"NlsData0000.dll"; source file in store is also corrupted
2016-03-28 15:32:02, Info                  CSI    00005d73 [SR] Cannot repair member file [l:14{7}]"VGX.dll" of Microsoft-Windows-IE-VGX, Version = 11.0.10240.16425, pA = x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2016-03-28 15:32:02, Info                  CSI    00005d74 [SR] This component was referenced by [l:156{78}]"Package_591_for_KB3081448~31bf3856ad364e35~amd64~~10.0.1.0.3081448-954_neutral"
2016-03-28 15:32:02, Info                  CSI    00005d75 [SR] This component was referenced by [l:158{79}]"Package_597_for_KB3081455~31bf3856ad364e35~amd64~~10.0.1.3.3081455-1117_neutral"
2016-03-28 15:32:02, Info                  CSI    00005d76 [SR] This component was referenced by [l:156{78}]"Package_523_for_KB3081436~31bf3856ad364e35~amd64~~10.0.1.1.3081436-855_neutral"
2016-03-28 15:32:02, Info                  CSI    00005d77 [SR] This component was referenced by [l:156{78}]"Package_538_for_KB3081444~31bf3856ad364e35~amd64~~10.0.1.0.3081444-884_neutral"
2016-03-28 15:32:02, Info                  CSI    00005d78 [SR] This component was referenced by [l:156{78}]"Package_523_for_KB3081438~31bf3856ad364e35~amd64~~10.0.1.0.3081438-855_neutral"
2016-03-28 15:32:02, Info                  CSI    00005d7b [SR] Could not reproject corrupted file [ml:122{61},l:120{60}]"\??\C:\Program Files (x86)\Common Files\Microsoft Shared\VGX"\[l:14{7}]"VGX.dll"; source file in store is also corrupted
2016-03-28 15:32:02, Info                  CSI    00005d7d [SR] Repair complete
2016-03-28 15:32:02, Info                  CSI    00005d7e [SR] Committing transaction
2016-03-28 15:32:02, Info                  CSI    00005d83 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

 
When I run DISM it fails:

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
 
Deployment Image Servicing and Management tool
Version: 10.0.10240.16384
 
Image Version: 10.0.10240.16384
 
[===========                20.0%                          ]
Error: 1726
 
The remote procedure call failed.
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth /source:E:\sources\install.wim:1 /limitaccess


Deployment Image Servicing and Management tool
Version: 10.0.10240.16384


Image Version: 10.0.10240.16384


[===========                20.0%                          ]
Error: 1726


The remote procedure call failed.


The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Both the RPC(Automatic) & RPC Locator(Manual) services are running.

I've tried rebooting into safemode to run the commands but I'm unable to enter safe mode as receive BSOD error: CRITICAL_PROCESS_DIED

Attached Files


Edited by walkerjohn, 28 March 2016 - 03:31 PM.


BC AdBot (Login to Remove)

 


#2 Willy22

Willy22

  • Members
  • 945 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Planet Earth
  • Local time:04:02 PM

Posted 28 March 2016 - 03:42 PM

The program called "SFC" still has a number of bugs in it. And Microsoft knows it.

http://news.softpedia.com/news/microsoft-acknowledges-system-file-checker-issue-in-windows-10-version-1511-502258.shtml



#3 walkerjohn

walkerjohn
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:02 AM

Posted 28 March 2016 - 03:52 PM

The program called "SFC" still has a number of bugs in it. And Microsoft knows it.

http://news.softpedia.com/news/microsoft-acknowledges-system-file-checker-issue-in-windows-10-version-1511-502258.shtml

The article mentions opencl.dll which is one of the listed corrupted files in my logs so I'll ignore that one for now. How would I go about repairing the other corrupted files?



#4 1PW

1PW

  • Members
  • 316 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North of the 38th parallel.
  • Local time:08:02 AM

Posted 28 March 2016 - 04:50 PM

Hello walkerjohn:

 

It might have been useful to see the then S.M.A..R.T. attribute values for the system drive's HDD/SSD. ...and it's still not too late...

 

Then perhaps, run the Windows' full ChkDsk with recovery of bad sectors and fix errors. You might then Copy/Paste the summary into your next reply.

 

More than a few BC forum helpers appreciate it when you publish the URL to your latest Speccy run.

 

HTH


Edited by 1PW, 28 March 2016 - 05:13 PM.

All viruses are malware but not all malware are viruses and if the malware doesn't self replicate it just isn't a virus.


#5 walkerjohn

walkerjohn
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:11:02 AM

Posted 28 March 2016 - 10:46 PM

Hello walkerjohn:

 

It might have been useful to see the then S.M.A..R.T. attribute values for the system drive's HDD/SSD. ...and it's still not too late...

 

Then perhaps, run the Windows' full ChkDsk with recovery of bad sectors and fix errors. You might then Copy/Paste the summary into your next reply.

 

More than a few BC forum helpers appreciate it when you publish the URL to your latest Speccy run.

 

HTH

Forgot to mention I scheduled chkdsk on my boot drive drive a couple days ago and it repaired a few orphaned links. I also did a full scan "chkdsk /f /r" afterwards no errors were present. crystaldiskinfo SMART status is good.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users