using sfc

weeder

Senior Member
#1
I have a PC running Windows 8.1 64 bit. I am using sfc.exe and it tells me it tried to fix files but could not fix all of them. I am trying to find which files are corrupt using the command: findstr /c: "[SR]"
%windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt". My command looks like this:
findstr /c: "[SR]" c:windows\Logs\CBS\CBS.log >"DELL2014\marilyn2014\Desktop\sfcdetails.txt"
I get an error: path not found. What am I doing wrong?

I obtained the user profile using the control panel and doing a search.
 


Last edited:

weeder

Senior Member
#2
I updated entry.
 


#3
Hey,

Simply run the following command

findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt
 


weeder

Senior Member
#4
Thank you for the response.
I ran the following command: findstr /c:"[SR]" c:windows\logs\cbs\cbs.log >sfcdetails.txt
and received the reply - cannot open windows\logs\cbs\cbs.log.
I am confused as the file cbs.log is there.
 


#5
Hey,
You don’t need to write DELL2014\marilyn2014, only write %userprofile% in the following command
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
It seems like this C:\Windows\system32>findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
After running this, check your desktop, you can see a file named sfcdetails.txt that contains all information related to sfc process & cbs.log.
Make sure you are running command line as an administrator.
Hope it will help you
 


weeder

Senior Member
#6
Emily,
I finally ran the findstr command successfully. A file sfcdetails.txt was created on my desktop but
it contains no entries. When running the findstr, after letting the PC run for 40 minutes, I did not
get back to the system32 prompt. Does It take a long time to do the scan?
The sfc scan did tell me not all the corrupted files could be fixed so I thought there would
be some entries.

I did scroll down the CBS.log file and near the end of the file there were 2 [SR] entries that could
not be fixed. They are win32k.ptxml and amd64\cnbj2530.dpa. There may be others but the
log is so large it is hard to search by hand.

My goal is to try and replace corrupted files.
Not sure what to do next. I appreciate your continued responses.
 


#7
Hey,

In such situation DISM - Deployment Image Servicing and Management tool can help you. DISM fix windows files corruption errors.

Open an elevated Command prompt then run the following command

dism /online /cleanup-image /checkhealth

then run the below command

dism /online /cleanup-image /restorehealth

Once above commands are executed, run sfc /scannow again.
 


weeder

Senior Member
#8
Emily,

I ran dism .../checkhealth and was successful, no error messages or problems.

Next I ran dism .../restorehealth and had error messages.
First a window appeared that stated roughly ... msiexe.exe application error instruction
at 0x7202ccf9 referenced memory could not be written. click OK to terminate the program
(only option) I did and after a while this appeared: error: 0x800f0906 source files could not
be downloaded use "source" option Configure a Windows Repair Source
dism.log

I seem to be getting deeper and deeper into this issue.

I do have another PC on my home network that is running Win8.1. I have run sfc on
this PC and it is clean. Could I use this PC as the source? If that is the case, I have no
idea how to do this. I am starting to feel this is getting over my head.
 


weeder

Senior Member
#9
update, new actions on PC running Windows 8.1

I deleted file CBS.log.

I ran sfc /scannow.

I ran findstr /C:"[SR]" %windir%\Logs\CBS\CBS.log > "%userprofile%\Desktop\sfcdetails.txt"

interesting part of sfcdetails.txt listed below:
_______________________________________________

2015-10-20 02:20:26, Info CSI 0000050d [SR] Beginning Verify and Repair transaction
2015-10-20 02:20:27, Info CSI 0000050f [SR] Cannot repair member file [l:24{12}]"win32k.ptxml" of Microsoft-Windows-Win32k, Version = 6.3.9600.18045, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-20 02:20:28, Info CSI 00000511 [SR] Repaired file \SystemRoot\WinSxS\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.3.9600.18045_none_a9dde67d6e5cb594\\[l:24{12}]"win32k.ptxml" by copying from backup
2015-10-20 02:20:28, Info CSI 00000513 [SR] Cannot repair member file [l:24{12}]"win32k.ptxml" of Microsoft-Windows-Win32k, Version = 6.3.9600.18045, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-20 02:20:28, Info CSI 00000514 [SR] This component was referenced by [l:154{77}]"Package_3_for_KB3087039~31bf3856ad364e35~amd64~~6.3.1.4.3087039-5_neutral_GDR"
2015-10-20 02:21:05, Info CSI 000005b0 [SR] Verifying 100 (0x0000000000000064) components
2015-10-20 02:21:05, Info CSI 000005b1 [SR] Beginning Verify and Repair transaction
2015-10-20 02:21:05, Info CSI 000005b3 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-20 02:21:06, Info CSI 000005b5 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-20 02:21:06, Info CSI 000005b6 [SR] This component was referenced by [l:166{83}]"Package_2709_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-6825_neutral_GDR"
2015-10-20 02:21:07, Info CSI 000005b7 [SR] Verify complete
2015-10-20 02:23:31, Info CSI 000008fa [SR] Repairing 2 components
2015-10-20 02:23:31, Info CSI 000008fb [SR] Beginning Verify and Repair transaction
2015-10-20 02:23:31, Info CSI 000008fd [SR] Cannot repair member file [l:24{12}]"win32k.ptxml" of Microsoft-Windows-Win32k, Version = 6.3.9600.18045, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-20 02:23:31, Info CSI 000008ff [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-20 02:23:31, Info CSI 00000901 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.17415, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-20 02:23:31, Info CSI 00000902 [SR] This component was referenced by [l:166{83}]"Package_2709_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8.3000850-6825_neutral_GDR"
2015-10-20 02:23:31, Info CSI 00000904 [SR] Repaired file \SystemRoot\WinSxS\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.3.9600.18045_none_a9dde67d6e5cb594\\[l:24{12}]"win32k.ptxml" by copying from backup
2015-10-20 02:23:31, Info CSI 00000906 [SR] Cannot repair member file [l:24{12}]"win32k.ptxml" of Microsoft-Windows-Win32k, Version = 6.3.9600.18045, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-10-20 02:23:31, Info CSI 00000907 [SR] This component was referenced by [l:154{77}]"Package_3_for_KB3087039~31bf3856ad364e35~amd64~~6.3.1.4.3087039-5_neutral_GDR"
2015-10-20 02:23:31, Info CSI 00000908 [SR] Repair complete
2015-10-20 02:23:31, Info CSI 00000909 [SR] Committing transaction
2015-10-20 02:23:32, Info CSI 0000090e [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

Note: Cannot repair member files "win32k.ptxml" and "Amd64\CNBJ2530.DPB" which are the corrupted files.

I then ran SFCFix.exe and used my Windows 8.1 install DVD when prompted by the program.

SFCFix.txt (log) is below:
____________________________________________

SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-10-20 02:33:23.247
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.

AutoAnalysis::
FIXED: Performed DISM repair on file Amd64\CNBJ2530.DPB of version 6.3.9600.17415.

CORRUPT: C:\WINDOWS\winsxs\amd64_microsoft-windows-win32k_31bf3856ad364e35_6.3.9600.18045_none_a9dde67d6e5cb594\win32k.ptxml

SUMMARY: All detected corruptions were successfully repaired.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-10-20 02:41:43.879
----------------------EOF-----------------------

It looks like everything was repaired but if I delete CBS.log and run sfc again, I get listed the same 2 corrupted files listed.
I am at a loss in explaining this. Help.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.