Sfc /scannow failed at 99%. Log details included. Kindly help. Thanks!

[Leftie]

Im not sure if im doing this right.

Upon entering the 1st command -
REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1
It says - "The system cannot find the file specified"

Then from your other threads, i decided to remove the space inbetween COMPONENTS.
It says - "The syntax of the command is incorrect"

I have not tried the 2nd command below as im not too sure if i did the 1st command correctly
COPY %userprofile%\desktop\lefaa\COMPONENTS C:\Windows\System32\config

After the above, i went to look at the component files
And the original COMPONENT file seems to have gone missing and a new COMPONENTS.OLD1 appeared.

Awaiting further instructions.
Cheers

 

[NoelDP]

OK- it may simply be that you ran the command earlier, (on the 4th?) and for some reason the system didn't rebuild it. (or that it could never load it since then)
Run the second command - it should work fine.

 

[Leftie]

Its weird but im very certain i did not run that command on the 4th Sep or any other time except for today.
As this is the 1st time in my life im seeing this command. lol

Just in case, ive kept a copy of the original COMPONENTS on my desktop from creating the zip onedrive file earlier on

Will carry on with 2nd command. Fingers crossed.
Thanks

 

[Leftie]

Im terribly sorry Noel, i have no idea why this is happenning.

After pressing enter on the 2nd command, It asks if i want to do an overwrite?
Giving me 3 options <Yes/No/All>

I then went to the system32, config folder and found this COMPONENTS file inside.
But its only 256KB in size.

Should i choose the option Yes?

 

[NoelDP]

Yep - the system re-created the file as a default one.

 

[Leftie]

Hi Noel,

Attached is the zipped CBS file after the 2 commands, a reboot followed by SURT.

I Hope it looks better than before.
Would it be advisable to run a sfc /scannow? Or just leave it as it is for now.

 

[NoelDP]

Run sfc and we'll see

 

[Leftie]

Ran sfc /scannow to no avail.
Reboot to safe mode and ran sfc /scannow also to no avail.

Both immediately says - "Windows Resource Protection could not perform the requested operation"

But hey on a bright side, at least the com is still working.

 

[matts6887]

I know this may be a oversight, or just totally off base; but im gonna try anyway: have you tried doing any sort of repair off the windows disc if you have one handy? Just a thought here is all.

 

[NoelDP]

here's the substance of the CheckSUR log...

Checking Component Store
(f) CSI Payload File Missing 0x00000000 qasf.dll amd64_microsoft-windows-directshow-asf_31bf3856ad364e35_6.1.7601.17514_none_78e385451529fc1e 
(f) CSI Payload File Missing 0x00000000 NAPCRYPT.DLL amd64_napcrypt_31bf3856ad364e35_6.1.7601.17514_none_99fb87a0aad31261 
(f) CSI Payload File Missing 0x00000000 mchgr.inf_loc amd64_mchgr.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_fd11d213229f2cdd 
(f) CSI Missing Component Key 0x00000000 amd64_mdmtdkj4.inf_31bf3856ad364e35_6.1.7600.16385_none_0b3568b5d0c39a8f HKLM\Components\DerivedData\Components 
(fix) CSI Missing Component Key CSI Registry Item Repaired Key created.  There will be more reports as values are replaced.
(f) CSI Missing Identity 0x00000000 identity amd64_mdmtdkj4.inf_31bf3856ad364e35_6.1.7600.16385_none_0b3568b5d0c39a8f 
(fix) CSI Missing Identity CSI Registry Item Repaired amd64_mdmtdkj4.inf_31bf3856ad364e35_6.1.7600.16385_none_0b3568b5d0c39a8f
(f) CSI F Mark Missing 0x00000002 f!mdmtdkj4.inf amd64_mdmtdkj4.inf_31bf3856ad364e35_6.1.7600.16385_none_0b3568b5d0c39a8f 
(fix) CSI F Mark Missing CSI Registry Item Repaired Wrote amd64_mdmtdkj4.inf_31bf3856ad364e35_6.1.7600.16385_none_0b3568b5d0c39a8f\f!mdmtdkj4.inf: mdmtdkj4.inf
(f) CSI Payload File Missing 0x00000000 lsi_scsi.inf_loc amd64_lsi_scsi.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_81ea6d9ef9396ec5 
(f) CSI Payload File Missing 0x00000000 machine.inf_loc amd64_machine.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_a102031c07b6ad1d 
(f) CSI Payload File Missing 0x00000000 lsi_sas2.inf_loc amd64_lsi_sas2.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_61a63821397a90a8 
(f) CSI Missing C Mark 0x00000000 c!mdmtdkj4.inf_31bf3856ad364e35_6.1.7600.16385_0b3568b5d0c39a8f amd64_mdmtdkj4.inf_31bf3856ad364e35_6.1.7600.16385_none_0b3568b5d0c39a8f Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!mdmtdkj4.inf_31bf3856ad364e35_6.1.7600.16385_0b3568b5d0c39a8f successfully added to amd64_mdmtdkj4.inf_31bf3856ad364e35_6.1.7600.16385_none_0b3568b5d0c39a8f

That seems to leave us only with the missing Payload files (which was the aim at this point)
I'm not sure why SFC is still failing - but it may be that one of the files is critical to its function.

I'll post a new fix for that and we'll see how it goes... (later!)

 

[matts6887]

Hey noel; Just a thought here; but is it possible that the sfc scannow could be failing because of one or more "corrupt" files on the disk in which case maybe op could try a windows repair if thats possible at this point?

 

[NoelDP]

I've uploaded a file - m87aa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\m87aa
hit the enter key - if you get a 'Not Found' error try
DIR D:\m87aa
or
DIR E:\m87aa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\m87aa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[NoelDP]

Heh... that's what the fix I just posted id designed to do - repair the known failures.
If that fails, then we start thinking about repair installs.

 

[Leftie]

Thanks loads Noel. No hurry, take it easy.
Am i glad to hear from you that its looking better

Hey Matts, Thanks for the pointer.
Erm, ive only got the windows 7 Home Premium 64bit CD (its OEM and not the retail version)
If i recall correctly, i read somewhere in here that OEM version cant do repairs.
From here onwards, im rather lost. lol

 

[NoelDP]

Just try running the fix as I posted in #52 - that'll fix the problems in CheckSUR (in theory at least) - then we have to worry about why SFC isn't working (which may be fixed by these updates anyhow)

 

[Leftie]

In the repairs enviroment, the D: was used instead of C:
(although the file m87aa was extracted into C: )

The XCOPY was a success. Files were copied & com rebooted.
(forgot to take a picture of it as too anxious) lol

Then sfc /scannow was ran - "Windows Resource Protection could not perform the requested operation"

Attached is the cbs log from Windows --> Logs --> CBS

Any help if i re-run SURT again followed by sfc /scannow?
Cheers

 

[NoelDP]

It may help - please try it and see.
Here's the important errors from the SFC command...

 Line 8206: 2014-09-15 02:05:14, Error                 CSI    00000004 (F) STATUS_OBJECT_NAME_NOT_FOUND #64894# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0x173e950->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[200]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_c3c1597075bcd214\\u3266\u3635\u6d21\u6f73\u7265\u7365\u642e\u6c6c"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 24373488 (0x0173e8f0))[gle=0xd0000034]
 Line 8207: 2014-09-15 02:05:14, Error                 CSI    [EMAIL="00000005@2014/9/14:18:05:14.771"]00000005@2014/9/14:18:05:14.771[/EMAIL] (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(3676): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
 Line 8209: 2014-09-15 02:05:15, Error                 CSI    00000006 (F) STATUS_OBJECT_NAME_NOT_FOUND #64893# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0x173e950->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[200]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-mail-core-dll_31bf3856ad364e35_none_c3c1597075bcd214\\u3266\u3635\u6d21\u6f73\u7265\u7365\u642e\u6c6c"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 24374552 (0x0173ed18))[gle=0xd0000034]
 Line 8210: 2014-09-15 02:05:15, Error                 CSI    [EMAIL="00000007@2014/9/14:18:05:15.05"]00000007@2014/9/14:18:05:15.05[/EMAIL] (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(3676): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
 Line 8212: 2014-09-15 02:05:15, Error                 CSI    00000008 (F) STATUS_OBJECT_NAME_NOT_FOUND #64892# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_READ|DELETE), oa = @0x173edb0, key = NULL, disp = (null))[gle=0xd0000034]
 Line 8213: 2014-09-15 02:05:15, Error                 CSI    00000009 (F) STATUS_OBJECT_NAME_NOT_FOUND #64880# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]

 

[Leftie]

Tried running the SURT followed by sfc to no avail.
Hmm, am running through services, system config, msconfig for any anomaly.

Big Thanks to Noel. Its been a long day.