Corrupt files found but not fixed in SFC /Scannow

[daniellouwrens]

Hi

Yes, it boots into Windows fine, but a sfc /scannow still cannot repair some files

Cheers

Daniel

 

[topgundcp]

If you look at this post: http://www.eightforums.com/performa...ng-repairing-c-drive-chkdsk-2.html#post294524 , it took 26-28 hours to do the disk repair.

Even though Seatools passed the test, however, there's no such thing as a perfect disk, all disks including brand new will tend to have some bad spots. For Windows not to use these spots, chkdsk /r will register these bad spots in the MFT (Master File Table). My suggestion is to try again with chkdsk but this time, use chkdsk /r c: and be patient to wait until it is done checking.

Cheers !!!

 

[daniellouwrens]

Hi all

I should have posted that the chkdsk scan did complete after many hours, I then tried the offline scan sfc /scannow /offbootdir=c:\ /offwindir=e:\windows
but again I got the result "Windows Resource Protection could not start the repair services"
so I tried sfc from the elevated cmd prompt in the OS and it ran but once again could not fix errors,
I think I will do a repair install.

Is there a log file kept of the results of a CHKDSK C: /F /R scan? If yes, where is it saved to?

Thanks

Daniel

 

[topgundcp]

Log file: Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums

Now that chkdsk is completed. Let us try to run the dism command again then sfc from Windows.

 

[daniellouwrens]

Hi

thanks for the link, it says that the event viewer log is only there of the chkdsk was run in windows,
the chkdsk I ran was started from the cmd prompt in windows but the scan was on re-booting, does that mean no
record was kept?

I ask because there is no event shown for the scan, all of the events shown are for external drives which run after the drives are "dismounted" (if that's the correct terminology) so are run in windows.

I will run the DISM etc, probably tonight as I do not have access the that PC at the moment.

Thanks again for the help.

Regards

Daniel

 

[daniellouwrens]

Hi

I ran the DISM the sfc but still have the same issues, I suspect there is a problem with the hardware
but I need to define it because then I can get the rig replaced.

I am going to do a repair install as that will achieve what I need, no corrupted files.

Regards

Daniel

 

[rnmishra]

minor error on previous post

I had some issues with my windows8.1. Thanks David Baily...."sfc /scannow" now shows no issue on my laptop!
I have another issue..when I right click on my network(wifi) my home connection, it does not show anything. Usually in win7 , it allows us to see the network setting and find the wifi password....It does not work the way it is shown in the youtube video How to Find your WiFi Password!!!! - Windows 8 WiFi - It's easy - YouTube . I am not allowed to right click my network!
Is there a way to work around it?
Thanks,
Raghu Mishra.
I am a first time vistor/user on this site...if my post happen to land on a wrong spot , please correct me.

 

[David Bailey]

You're welcome.

 

[Zobadd123]

Hi Guys, thanks a lot, this thread really helped me.
I was having problems with sfc /scannow not being able to fix apparent errors but the Dism /Online /Cleanup-Image /RestoreHealth did it's job properly and now scf /scannow comes up with an "All Clear" result.

A*

 

[David Bailey]

Glad to hear it.

 

[gb2K]

I guess I’m dusting off an old topic here. If there’s a more current posting on this topic, please redirect me. I have a few questions, and a suggestion.

1. This thread started out dealing with corrupt files found by SFC/SCANNOW. I read this thread fairly thoroughly, but never found any advice for looking at the CBS.log file to determine which files were corrupt. I saw this topic discussed in a thread on the Windows7 forum (How do you fix corrupted files found by SFC /SCANNOW? - Windows 7 Help Forums), with a user named “Tom982” supposedly having some mythical powers to decode the lousy output from SFC and identify corrupted files. That thread went nowhere, and never gave any suggestions about how to ID which files were corrupted.

Maybe it’s not necessary to actually ID these files, since the current thread suggests a brute-force fix with CHKDSK and DISM (in that order). Still, I’m left curious: is there information somewhere about decoding the cryptic CBS.log files and identifying which files SFC found to be “corrupt and not repairable” (or however they put it)?

1. The issues with gathering log data from CHKDSK seem overly complicated (I’m not crazy about Event Viewer!) Being an old DOS guy, I decided to try “CHKDSK [switches]>check.txt”. I haven’t been able to test this extensively (because most actions in CHKDSK take so long), but quick testing shows that it works. Can anybody confirm/deny this?

1. The usage of DISM seems deceptively simple:
   1. Is there ever a need to tell it where to find your “good” image? I’m guessing that it looks for a “RESTORE” partition on your hard disk – is that right?
   2. There was some discussion in this thread about specifying /offbootdir and /offwindir for SFC. I figured a similar thing might exist for DISM in some situations
   3. Accordingly, if/when I update to 8.1 (I’m still at 8.0, as provided by the manufacturer, HP), would I not have to point DISM to a different image somewhere? Do I have to worry about creating that image when I upgrade to 8.1 (and then to Windows 10…) <eyeroll>

1. As noted in this thread, running CHKDSK can take a LOOOOOOOONNNNG time. There are some interesting switches to be found if you type “chkdsk/?” in a Command prompt. Following up on that a bit, I found this great tutorial on YouTube: https://www.youtube.com/watch?v=TbAfn4heGhE . The author discusses using the /scan and /spotfix switches to speed up the process enormously! I would also suggest throwing in the /perf switch in the right place in the command line; this will give the CHKDSK process top priority access to system resources. It will slow down everything else; but most people are not going to try to do any work on their PC while CHKDSK is running, anyway!

Cheers,
gb

 

[David Bailey]

Run---

Dism /Online /Cleanup-Image /RestoreHealth

then sfc.

 

[gb2K]

Results of my testing:
(1) Run CHKDSK /scan /perf. I would suggest doing this before DISM, because if DISM is trying to work on a disk with bad sectors, it might not be very successful. With these switches, CHKDSK runs very quickly; it checked my 1TB HD in less than five minutes. It found no problems on my disk.

(2) Run DISM, as suggested.

(3) Run SFC/SCANNOW again. This time, it executed perfectly, finding no corrupted files.

I'm still interested in more detailed answers to my questions...

 

[nrabus]

scannow, Dism failures

My browser has been lagging/g much the last two days. I hadn't received anything from Avira so I ran sfc /scannow. I am using Norton now (free trial with safe search installed in my Chrome browser. I haven't had a notification from Norton yet.

Now, file explorer freezes for 5 seconds whenever I select a folder.

I have Win 8.1

I have attached screenshots of the cmd prompt windows and the CBS log file.

Most recently, I did a start of trusted installer before scannow but still failure.

One screenshot has the error codes. I wasn't able to upload the entire CBS log, I pasted some of it here:

2017-06-24 10:36:42, Info CBS Loaded Servicing Stack v6.3.9600.18384 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.18384_none_fa1d93c39b41b41a\cbscore.dll
2017-06-24 10:36:42, Info CSI 00000001@2017/6/24:15:36:42.799 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffc782e7fa9 @0x7ffc794f4924 @0x7ffc794f415b @0x7ff63d85d69a @0x7ff63d85df4f @0x7ffc8ba020f3)
2017-06-24 10:36:42, Info CBS SQM: Initializing online with Windows opt-in: False
2017-06-24 10:36:42, Info CBS SQM: Cleaning up report files older than 10 days.
2017-06-24 10:36:42, Info CBS SQM: Requesting upload of all unsent reports.
2017-06-24 10:36:42, Info CBS SQM: Failed to start upload with file pattern: C:\WINDOWS\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2017-06-24 10:36:42, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2017-06-24 10:36:42, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\WINDOWS\servicing\sqm\*_all.sqm, flags: 0x6
2017-06-24 10:36:42, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
2017-06-24 10:36:42, Info CBS NonStart: Set pending store consistency check.
2017-06-24 10:36:42, Info CBS Session: 30600447_2920482624 initialized by client WindowsUpdateAgent.
2017-06-24 10:36:45, Info CBS Session: 30600447_2945013919 initialized by client WindowsUpdateAgent.
2017-06-24 10:36:46, Info CBS Session: 30600447_2956732689 initialized by client WindowsUpdateAgent.
2017-06-24 10:36:46, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2017-06-24 10:36:46, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2017-06-24 10:36:46, Info CBS Session: 30600447_2956888945 initialized by client WindowsUpdateAgent.
2017-06-24 10:36:46, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2017-06-24 10:36:46, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2017-06-24 10:36:46, Info CBS Session: 30600447_2956888946 initialized by client WindowsUpdateAgent.
2017-06-24 10:36:46, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2017-06-24 10:36:46, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2017-06-24 10:36:46, Info CBS Session: 30600447_2956888947 initialized by client WindowsUpdateAgent.
2017-06-24 10:36:46, Info CBS Session: 30600447_2957911167 initialized by client WindowsUpdateAgent.
2017-06-24 10:36:46, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2017-06-24 10:36:46, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2017-06-24 10:36:46, Info CBS Session: 30600447_2958067424 initialized by client WindowsUpdateAgent.
2017-06-24 10:36:46, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2017-06-24 10:36:46, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]Most of the log file had entries that included "Read out cached applicability from TiLight for package:" and slao had "ApplicableState: 0, CurrentState:0"

I have researched a little but don't have time to fully check the logs myself

Thank you.