please Windows 7 SFC Unable to Fix Files in a work machine

a8nsli · Aug 2, 2013

hello all, I have a PC that need work very urgently. Have you installed windows 7 home premium 32 bit.
The problem is that nothing but allow the user to start the session and closes the explorer, the reopen windows after 5 seconds and gives the same error.
Windows explorer stopped working.

I have tried everything, create a new user, clean viruses and spyware, and much more.

When I pass the tool SFC / SCANNOW tells me that you can not repair errors.

creates this log CBS

Someone can help me, thanks in advance

NoelDP · Aug 3, 2013

Here's the problem lines from the CBS.log

Code:

 Line 4320: 2013-08-02 11:36:47, Info                  CSI    000003b6 [SR] Repairing 3 components
 Line 4321: 2013-08-02 11:36:47, Info                  CSI    000003b7 [SR] Beginning Verify and Repair transaction
 Line 4324: 2013-08-02 11:36:47, Info                  CSI    000003b9 [SR] Cannot repair member file [l:18{9}]"ehSSO.dll" of Microsoft-Windows-ehome-ehsso, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 4327: 2013-08-02 11:36:48, Info                  CSI    000003bb [SR] Cannot repair member file [l:20{10}]"msv1_0.dll" of Microsoft-Windows-Security-NTLM, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 4330: 2013-08-02 11:36:48, Info                  CSI    000003bd [SR] Cannot repair member file [l:22{11}]"Utilman.exe" of Microsoft-Windows-UtilMan, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix protocol later.

a8nsli · Aug 5, 2013

Thank you very much, while waiting for the fix someone could tell me with the information that the partner has provided NoelDP if it can be corrected manually. thanks

NoelDP · Aug 5, 2013

Ooops - sorry, about the delay!
It slipped off my radar, and I'm at work at the moment, so I'll have to get back to you later.

a8nsli · Aug 5, 2013

Do not worry, I appreciate your help. regards

a8nsli · Aug 5, 2013

the truth is that I have urges me enough, I stand 5 employees

NoelDP · Aug 6, 2013

I've uploaded a file - a81aa.zip - to my SkyDrive at Noel's SkyDrive

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:\a8iaa

hit the enter key - if you get a 'Not Found' error try

DIR D:\a8iaa

or

DIR E:\a8iaa

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

XCOPY <drive>:\a8iaa <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

a8nsli · Aug 6, 2013

Thank you so much, it worked. I have no words to thank you.
This world is a better place with people like you. regards

NoelDP · Aug 6, 2013

Please post the new log :)

Also, check that Windows Update is working properly.

a8nsli · Aug 6, 2013

Here are the log, still setting some error but I can access the system and run the programs I care more. You'll make a copy of all missing data for saving me before failure. Thank you again.
regards

Upps will not let me upload it, are 13mb put it in my dropbox

https://www.dropbox.com/sh/2mhvb6kdthidtyd/hqPwx0tdvr

NoelDP · Aug 6, 2013

There's still a number of errors present.

Code:

 Line 59055: 2013-08-06 13:29:04, Info                  CSI    000002c0 [SR] Repairing 3 components
 Line 59056: 2013-08-06 13:29:04, Info                  CSI    000002c1 [SR] Beginning Verify and Repair transaction
 Line 59059: 2013-08-06 13:29:04, Info                  CSI    000002c3 [SR] Cannot repair member file [l:18{9}]"ehSSO.dll" of Microsoft-Windows-ehome-ehsso, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 59062: 2013-08-06 13:29:04, Info                  CSI    000002c5 [SR] Cannot repair member file [l:20{10}]"msv1_0.dll" of Microsoft-Windows-Security-NTLM, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 59065: 2013-08-06 13:29:04, Info                  CSI    000002c7 [SR] Cannot repair member file [l:22{11}]"Utilman.exe" of Microsoft-Windows-UtilMan, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

These are the same errors as previous - so either the swap didn't 'take', or the problem lies elsewhere.

Please download and save the CheckSUR tool from System Update Readiness Tool fixes Windows Update errors in Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply

Also please run the following commands....

DIR C:\a8iaa
DIR C:\Windows\winsxs\a8* /S

...and post the results....

Here are some instructions to make life easier :)
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

a8nsli · Aug 6, 2013

Here are the log,

NoelDP · Aug 8, 2013

ChecSUR gices the system a clean bill of health - please run the commands I asked you to do, and post the results.

Search

Search

please Windows 7 SFC Unable to Fix Files in a work machine

a8nsli

Member

Attachments

NoelDP

Windows Update Analyst, Contributor

a8nsli

Member

NoelDP

Windows Update Analyst, Contributor

a8nsli

Member

a8nsli

Member

NoelDP

Windows Update Analyst, Contributor

a8nsli

Member

NoelDP

Windows Update Analyst, Contributor

a8nsli

Member

NoelDP

Windows Update Analyst, Contributor

a8nsli

Member

Attachments

NoelDP

Windows Update Analyst, Contributor