SFC /scannow unable to complete!

Hello everyone, this is my first time to the forums here and I have to say, I am very impressed with what you guys have going on here. I'm hoping I can get my problem solved!

OS: Windows Vista Ultimate

Story: I connected a 160GB External Hard drive to my Vista Laptop and went into the Backup and Restore Center to back my files up. I received an error message however that I can not back my computer up because my hard drive files are corrupt. Here is the error message:

"The disk C: has errors.
Windows has detected file system corruption on C:. You must check the disk for errors before it can be restored."

I try to check the disk for errors while it's in a full boot, and I get the 'you must be in safe mode' message and it asks me if I want to schedule a safe boot the next time my computer starts. Yes! So I restart and it doesn't work... I do a little research as to why I cannot boot into safe mode and I find a tutorial on this site telling me I need to do some SFC work in order to fix the problem. The tutorial I was following is this one: http://www.vistax64.com/tutorials/130824-chkdsk-will-not-run-startup-vista.html

I start following the instruction for the SFC part, and SFC craps out at 17% saying "Windows Resource Protection could not perform the requested operation." Great... So I go back to the tutorial and click the "How to Repair and Verify the Integrity of Vista System Files with System File Checker" link which takes me to this tutorial: http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html

The only thing it said there about if SFC cannot complete is to read the .cbs log and see where the problem is. I'm having trouble reading the log and was wondering if you guys can help me to pin point the problem and to move forward towards a complete SFC check and file fix.

Here is my CBS.log report (the parts in question are in red).

2008-06-08 17:26:51, Info CBS Loaded Servicing Stack v6.0.6001.18000 with Core: C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6001.18000_none_095f6148c74a7a64\cbscore.dll
2008-06-08 17:26:51, Info CSI 00000001@2008/6/8:21:26:51.251 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x68e68504 @0x699c8439 @0x699a62a3 @0xac213c @0xac1ebb @0xac1949)
2008-06-08 17:26:51, Info CSI 00000002@2008/6/8:21:26:51.282 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x68e68504 @0x699fe615 @0x699e0dec @0xac213c @0xac1ebb @0xac1949)
2008-06-08 17:26:51, Info CSI 00000003@2008/6/8:21:26:51.282 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x68e68504 @0x6b7c1a0d @0x6b7c1794 @0xac3397 @0xac29f6 @0xac1949)
2008-06-08 17:26:51, Info CBS NonStart: Checking to ensure startup processing was not required.
2008-06-08 17:26:51, Info CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x83fc2c
2008-06-08 17:26:51, Info CBS NonStart: Success, startup processing not required as expected.
2008-06-08 17:26:51, Info CSI 00000005 CSI Store 1109912 (0x0010ef98) initialized
2008-06-08 17:26:53, Info CSI 00000006 [SR] Verifying 100 (0x00000064) components
2008-06-08 17:26:53, Info CSI 00000007 [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:00, Info CSI 00000008 Repair results created:
POQ 0 starts:
0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\b0cebd62aec9c80165000000d4172c0b._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\90b5c962aec9c80166000000d4172c0b.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
2: Move File: Source = [l:208{104}]"\SystemRoot\WinSxS\Temp\PendingRenames\b0d9d062aec9c80167000000d4172c0b.$$_ehome_40103e2da1d121de.cdf-ms", Destination = [l:120{60}]"\SystemRoot\WinSxS\FileMaps\$$_ehome_40103e2da1d121de.cdf-ms"
3: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\b0e4e362aec9c80168000000d4172c0b.program_files_ffd0cbfc813cc4f1.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms"
4: Move File: Source = [l:244{122}]"\SystemRoot\WinSxS\Temp\PendingRenames\1046e662aec9c80169000000d4172c0b.program_files_common_files_d7a65bb2f0e854e7.cdf-ms", Destination = [l:156{78}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_d7a65bb2f0e854e7.cdf-ms"
5: Move File: Source = [l:278{139}]"\SystemRoot\WinSxS\Temp\PendingRenames\90cbef62aec9c8016a000000d4172c0b.program_files_common_files_microsoft_shared_818c5a0e45020fba.cdf-ms", Destination = [l:190{95}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_microsoft_shared_818c5a0e45020fba.cdf-ms"
6: Move File: Source = [l:286{143}]"\SystemRoot\WinSxS\Temp\PendingRenames\70b2fb62aec9c8016b000000d4172c0b.program_files_common_files_microsoft_shared_ink_3c86e3db0b3b254c.cdf-ms", Destination = [l:198{99}]"\SystemRoot\WinSxS\FileMaps\program_files_common_files_microsoft_shared_ink_3c86e3db0b3b254c.cdf-ms"
7: Move File: Source = [l:292{146}]"\SystemRoot\WinSxS\Temp\PendingRenames\90d60263aec9c8016c000000d4172c0b.program_files_common_files_microsoft_shared_ink_en_7a951cedcb9a5105.cdf-ms", Destination = [l:204{102}]"\
2008-06-08 17:27:00, Info CSI SystemRoot\WinSxS\FileMaps\program_files_common_files_microsoft_shared_ink_en_7a951cedcb9a5105.cdf-ms"

POQ 0 ends.
2008-06-08 17:27:00, Info CSI 00000009 [SR] Verify complete
2008-06-08 17:27:01, Info CSI 0000000a [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:01, Info CSI 0000000b [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:09, Info CSI 0000000c Repair results created:
POQ 1 starts:

POQ 1 ends.
2008-06-08 17:27:09, Info CSI 0000000d [SR] Verify complete
2008-06-08 17:27:10, Info CSI 0000000e [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:10, Info CSI 0000000f [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:12, Info CSI 00000010 Repair results created:
POQ 2 starts:

POQ 2 ends.
2008-06-08 17:27:12, Info CSI 00000011 [SR] Verify complete
2008-06-08 17:27:13, Info CSI 00000012 [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:13, Info CSI 00000013 [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:16, Info CSI 00000014 Repair results created:
POQ 3 starts:

POQ 3 ends.
2008-06-08 17:27:16, Info CSI 00000015 [SR] Verify complete
2008-06-08 17:27:18, Info CSI 00000016 [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:18, Info CSI 00000017 [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:20, Info CSI 00000018 Repair results created:
POQ 4 starts:

POQ 4 ends.
2008-06-08 17:27:20, Info CSI 00000019 [SR] Verify complete
2008-06-08 17:27:21, Info CSI 0000001a [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:21, Info CSI 0000001b [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:22, Error CSI 0000001c@2008/6/8:21:27:22.701 (F) d:\rtm\base\xml\udom_microdom.cpp(4493): Error STATUS_XML_PARSE_ERROR originated in function RtlCreateMicrodom expression: (null)
[gle=0x80004005]
2008-06-08 17:27:29, Info CSI 0000001d [SR] Cannot verify component files for 6cb4457de7631e46df1c1ad011932ef3, Version = 6.0.6000.16609, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2008-06-08 17:27:30, Info CSI 0000001e Repair results created:
POQ 5 starts:

POQ 5 ends.
2008-06-08 17:27:30, Info CSI 0000001f [SR] Verify complete
2008-06-08 17:27:31, Info CSI 00000020 [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:31, Info CSI 00000021 [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:33, Info CSI 00000022 Repair results created:
POQ 6 starts:

POQ 6 ends.
2008-06-08 17:27:33, Info CSI 00000023 [SR] Verify complete
2008-06-08 17:27:34, Info CSI 00000024 [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:34, Info CSI 00000025 [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:36, Info CSI 00000026 Repair results created:
POQ 7 starts:

POQ 7 ends.
2008-06-08 17:27:36, Info CSI 00000027 [SR] Verify complete
2008-06-08 17:27:37, Info CSI 00000028 [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:37, Info CSI 00000029 [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:41, Info CSI 0000002a Repair results created:
POQ 8 starts:
0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\d0153e7baec9c8018e030000d4172c0b._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
1: Move File: Source = [l:218{109}]"\SystemRoot\WinSxS\Temp\PendingRenames\105e4c7baec9c8018f030000d4172c0b.program_files_ffd0cbfc813cc4f1.cdf-ms", Destination = [l:130{65}]"\SystemRoot\WinSxS\FileMaps\program_files_ffd0cbfc813cc4f1.cdf-ms"
2: Move File: Source = [l:238{119}]"\SystemRoot\WinSxS\Temp\PendingRenames\70bf4e7baec9c80190030000d4172c0b.program_files_bitlocker_56992ca67076148c.cdf-ms", Destination = [l:150{75}]"\SystemRoot\WinSxS\FileMaps\program_files_bitlocker_56992ca67076148c.cdf-ms"
3: Move File: Source = [l:254{127}]"\SystemRoot\WinSxS\Temp\PendingRenames\f044587baec9c80191030000d4172c0b.program_files_bitlocker_readmes_d6752017ddcd358f.cdf-ms", Destination = [l:166{83}]"\SystemRoot\WinSxS\FileMaps\program_files_bitlocker_readmes_d6752017ddcd358f.cdf-ms"
4: Move File: Source = [l:250{125}]"\SystemRoot\WinSxS\Temp\PendingRenames\b0075d7baec9c80192030000d4172c0b.program_files_bitlocker_en-us_d74386b4c8d94588.cdf-ms", Destination = [l:162{81}]"\SystemRoot\WinSxS\FileMaps\program_files_bitlocker_en-us_d74386b4c8d94588.cdf-ms"

POQ 8 ends.
2008-06-08 17:27:41, Info CSI 0000002b [SR] Verify complete
2008-06-08 17:27:42, Info CSI 0000002c [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:42, Info CSI 0000002d [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:44, Info CSI 0000002e Repair results created:
POQ 9 starts:

POQ 9 ends.
2008-06-08 17:27:44, Info CSI 0000002f [SR] Verify complete
2008-06-08 17:27:45, Info CSI 00000030 [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:45, Info CSI 00000031 [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:48, Info CSI 00000032 Repair results created:
POQ 10 starts:

POQ 10 ends.
2008-06-08 17:27:48, Info CSI 00000033 [SR] Verify complete
2008-06-08 17:27:48, Info CSI 00000034 [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:48, Info CSI 00000035 [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:54, Info CSI 00000036 Repair results created:
POQ 11 starts:

POQ 11 ends.
2008-06-08 17:27:54, Info CSI 00000037 [SR] Verify complete
2008-06-08 17:27:54, Info CSI 00000038 [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:54, Info CSI 00000039 [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:58, Error CSI 0000003a (F) STATUS_FILE_CORRUPT_ERROR #699134# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowFileNotFound|AllowSharingViolation|AllowAccessDenied), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES|FILE_READ_DATA), oa = @0xa6ebf0->OBJECT_ATTRIBUTES {s:24; rd:NULL; on:[130]"\SystemRoot\WinSxS\x86_microsoft-windows-a..ence-mitigations-c5_31bf3856ad364e35_6.0.6000.16651_none_0a0aeb59f549e544\AcXtrnal.dll"; aOBJ_CASE_INSENSITIVE)}, iosb = @0xa6eba8, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000102]
2008-06-08 17:27:58, Error CSI 0000003b@2008/6/8:21:27:58.237 (F) d:\rtm\base\wcp\sil\merged\ntu\ntsystem.cpp(1817): Error STATUS_FILE_CORRUPT_ERROR originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2008-06-08 17:28:04, Error CSI 0000003c (F) STATUS_FILE_CORRUPT_ERROR #699133# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingFile(...)[gle=0xd0000102]
2008-06-08 17:28:04, Error CSI 0000003d (F) STATUS_FILE_CORRUPT_ERROR #699132# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingFile(flags = (MissingFileIsOk|SharingViolationIsOk|AccessDeniedIsOk), da = (SYNCHRONIZE|FILE_READ_DATA), oa = @0xa6ed94->SIL_OBJECT_ATTRIBUTES {s:20; on:"AcXtrnal.dll"; aOBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_SYNCHRONOUS_IO_NONALERT|FILE_NON_DIRECTORY_FILE), file = NULL, disp = Invalid)
[gle=0xd0000102]

Please help! Thank you for your time!

-Stradigos

If you were trying to highlight the errors, you missed one:

POQ 4 ends.
2008-06-08 17:27:20, Info CSI 00000019 [SR] Verify complete
2008-06-08 17:27:21, Info CSI 0000001a [SR] Verifying 100 (0x00000064) components
2008-06-08 17:27:21, Info CSI 0000001b [SR] Beginning Verify and Repair transaction
2008-06-08 17:27:22, Error CSI 0000001c@2008/6/8:21:27:22.701 (F) d:\rtm\base\xml\udom_microdom.cpp(4493): Error STATUS_XML_PARSE_ERROR originated in function RtlCreateMicrodom expression: (null)
[gle=0x80004005]
2008-06-08 17:27:29, Info CSI 0000001d [SR] Cannot verify component files for 6cb4457de7631e46df1c1ad011932ef3, Version = 6.0.6000.16609, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest may be damaged (TRUE)
2008-06-08 17:27:30, Info CSI 0000001e Repair results created:

Click to expand...

Woops, didn't see that one. Do you know why these are coming up? What should I do? Is it even possible to fix them before SFC scan does a complete scan and attempts to repair them itself? Would that even matter in trying to complete a full scan?

Honestly, I am not all that good with cbs.log files - but I'd venture a guess - if it has that many problems, start over.

If I start over, I'm going back to XP. I find it rather annoying that the only way I can fix a problem is to reinstall the OS. That's so lame, and it shouldn't have to be that way.

I'll wait around till I get a second opinion. Thanks for your input.

Hi Stradigos,

With this much corruption and errors you will probably never get the way it was, and spend a lot of time trying. Usually at this point, it is best to format and do a clean install to get everything to work properly again.

Do you have any ideas of the cause of the corruption on your C: drive? Any programs that you ran that might gave caused it?

Sorry,
Shawn

I have no idea what may have caused this. I'm surprised anything is corrupt in the first place. Everything is operating just fine and I didn't even know I had errors until I got into this chkdsk/sfc thing.

Is there any potential risk of continuing with normal operation under these conditions? Will it get worse? Will programs start to act weird?

Would a reinstall of Vista work? That way I don't have to reformat...

I would run the disk tools on your hard drive from the manufacturer and do a Trendmicro free scan to see if you have Trojan Horses.

Stradigos,

In addition to Michael's post:

Some programs like a registry cleaning program can cause problems like this.

Usually with that much corruption and errors, you can start to see more problems pop up on you. You can try doing a Repair install outlined in this tutorial to see if it can repair it for you to try and avoid a clean install. I would try to backup what you do not want to lose to be safe though.

http://www.vistax64.com/tutorials/88236-repair-install-vista.html

Hope this helps,
Shawn

Don't use registry cleaners in Vista. You have to disable UAC to prevent security issues. I would start by backing up your data and important files.

clear the event viewer and restart. Work the problems in order of earliest first.

I have used a registry cleaner, CCleaner to be more exact. I thought it was doing a good job of cleaning up old registry entries. There is so much residue left behind from old programs, I thought I would use that to remove them.

So your saying not to anymore? Or just make sure to disable UAC before doing it...? Which one?

I've been backing up my files for the last half hour getting ready for a reinstall. If that doesn't work, I'll just nuke it and restart from scratch. Oh the joys of owning a MS product...

EDIT: Holy crap, I just went to my even viewer and looked under system and there is about 70,000 log entries saying my drive is corrupt and unusable! What the HECK!?

Okay, so is this a hardware issue then? Should I be looking into a new hard drive for my laptop? If that's the case, it should be under warrenty still... Is there something I can do to prove that my hard drive needs a replacement so it can be covered by warrenty? Maybe reformatting wouldn't be a good idea then because it would cover up the errors wouldn't it?

And you said to clear the even log and restart my computer... how do I clear the event log? And should I?

Right click on each category in event viewer. Clear but don't save. Reboot. It will post just your current problems. Don't worry about the old stuff. You don't need them. Start with the first event error in time order.

OK, I cleared the log, rebooted and looked at the log again. Within 6 minutes I get 8 messages saying: "The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume OS."

The task scheduler for chkdsk isn't working, making it hard for it to perform one during a reboot. Would the recovery console on the Vista DVD allow me to run it at boot time? The whole reason I wanted a full SFC scan was because that would supposedly allow this task scheduler and safe mode boot to work properly but... I can't get there yet lol.

start
all programs
accessories
Right click on command prompt. Choose run as administrator

in box chkdsk c:/r.

Say yes to the prompt to run on reboot. Restart. If you have D: or another run on all partitions.

Well the problem with that was none of the check disk scheduled tasks were working due to autochk.exe being corrupt. I learned that if you pop the Vista DVD in, it will give you a command prompt. So I did, finally got into a fricking boot time command prompt and ran chkdsk myself. There were some errors, but it corrected them. The good sign though was that there was no bad sectors. *sigh of relief*.

So now I'm running SFC /scannow. It was finally able to make a complete scan! Woot! But now I get the message that it found errors but where unable to correct them. I think I saw a tutorial here on that. I'm going to try and go through that and finish correcting the errors. If I have any more questions, I'll be sure to post in this thread =]

I'll keep you guys updated until my problem is fully resolved.

Way to stay with it - you'll be a techie yet :P

Seriously, though, you'll want to start figuring out why you are having such issues on a new machine - that is *definitely* not a good sign....

I agree. I'm going to get to the bottom of this. I just took another look at my event log, and there are a ton of warnings saying that an error was detected while page filing... more evidence of a bad hard drive? Maybe...

I'm going to do another scan for bad sectors tonight. Hopefully it's nothing bad...

Anyone know of a free hard drive bad sector scanner that will work on vista? Or should I just rely on chkdsk?

Stradigos said:

Anyone know of a free hard drive bad sector scanner that will work on vista? Or should I just rely on chkdsk?

Click to expand...

It depends of the type of HDD.
Could you post the reference/manufacturer?

Actually, most HDD manufacturers have their own diagnostics utilities that you can download from their websites - start tooling around whatever manufacturer's website, or else tell us and we'll pull the link.