Windows Resource Protection found corrupt files but was unable to fix some of them.

[MaverikOG]

Windows 7 Home Premium 64-bit computer has been having some issues with one of the profiles. When the user logs in the computer sometimes it will just freeze while trying to log in (blue circle spinning) Hard restart required to ultimately log in. This occurs pretty much daily.
I ran a sfc /scannow while logged in with the affected profile. The profile is NOT an admin, but I ran the CMD as admin. Message when completed reads, "Windows Resource protection found corrupt files but was unable to fix some of them. Details are included in the CBS Log......"
I've attached the CBS.Zip here as directed. I'd appreciate any help I can get here. Thanks in advance.

Jared

 

[jcgriff2]

Windows 7 Home Premium 64-bit computer has been having some issues with one of the profiles. When the user logs in the computer sometimes it will just freeze while trying to log in (blue circle spinning)

That sounds like a typical APPHANG.

Other user profiles on that system are OK...?

If so, it seems that user account may be corrupted or contain something the other user accounts don't.

What happens when you log into that user account in Safemode w/ Networking? Does the APPHANG occur?

Regards. . .

jcgriff2

 

[MaverikOG]

I didn't try starting in safe mode, but yes, the other profiles on this PC (both Administrator level) are not experiencing any of the same symptoms. Although The two accounts that are fine are not utilized as often as the account having the issue. What can be done to check or verify apphang?

Thanks

Jared

 

[NoelDP]

I've seen a few cases of this error recently - perhaps it's the result of a malware infestation?

 Line 50453: 2013-10-08 15:21:25, Info                  CSI    00000305 [SR] Repairing 1 components
 Line 50454: 2013-10-08 15:21:25, Info                  CSI    00000306 [SR] Beginning Verify and Repair transaction
 Line 50457: 2013-10-08 15:21:25, Info                  CSI    00000308 [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.1.7601.17514, 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

I'll post a fix for it later today.

In the meantime, please also run the CheckSUR tool

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.

 

[NoelDP]

I've uploaded a file - mogaa.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:\mogaa

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

DIR D:\mogaa

or

DIR E:\mogaa





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





XCOPY <drive>:\mogaa <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 SkyDrive Public folder, and
post a new link


Also run a new MGADiag report, and post the result.