SFC /SCANNOW stops at 64% - Windows Resource Protection found corrupt files

barrejf

Active member
Joined
Mar 15, 2014
Posts
28
Location
USA
I have a Windows Vista Home SP2 (x86 -32bit) system which reports the following error when running SFC /SCANNOW:

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

I ran the
System Update Readiness tool (CheckSUR) prior to the SFC scan. Attached you will find both the log files (checksur.log and cbs.log). I've run numerous virus/malware scans and chkdsk without a finding.

Any assistance you can provide to help me resolve this problem is most appreciated.


 

Attachments

Thanks so much for the quick response! I will run the script momentarily and post the log when complete.
 
Hello again!

Please download the attached .zip file to your Desktop, then click, hold, drag, and drop it on top of SFCFix.exe.

Post the log when complete.

Thank you!

Richard
 

Attachments

Hi Richard,

Shortly after performing the steps in your earlier post, KB2442962 downloaded and installed. I re-booted shortly thereafter and have not been able to access my system since. Attempts to start in "safe mode" or use "last known good configuration" have all failed.

Any advice you can offer will be most appreciated.
 
Hi Richard,

I was able to boot the system using UBCD4WIN and reviewed the CBS log (copy attached). It appears as though KB2522422 was installed, not KB2442962 as reported in my earlier e-mail.

My apologies for the mistake.

Regards,

Jim
 

Attachments

Hi Richard,

Got my system back performing a System Restore to 6:30pm last night.

Regards,

Jim
 
Hi Richard,

Here are the latest SFC /SCANNOW results. I appreciate any assistance you can offer!

Regards,

Jim
 

Attachments

I noticed that folder C:\Windows\winsxs\Temp\PendingRenames has 2606 files in it. I tried deleting the files listed below, but receive "file in use" errors.

C:\Windows\System32\SMI\Store\Machine\*.tm*
C:\Windows\System32\SMI\Store\Machine\*.blf
C:\Windows\System32\SMI\Store\Machine\*.regtrans-ms

Regards,

Jim
 
Hello again Jim :)

Unfortunately, the script didn't go through due to a bug in the tool (and there's nobody to blame other than myself since I wrote that tool!). Whilst I get it fixed, we can use this other script to work around the problem.

Please run this SFCFix script and post the logfile.

Thank you.

Richard
 

Attachments

Hi Richard,

I can't thank you enough for your continued efforts to help fix this problem. I ran the updates, but received an error msg
and was prompted to download an updated version of sfcfix.exe. See msg below.

Welcome to SFCFix by niemiro and sysnative.com.

Checking for updates . . .
New update available. Downloading . . .

Failed to download update. Please update manually from
https://www.sysnative.com/forums/downloads/sfcfix/
Press any key to exit . . .

I downloaded the updated SFCFix.exe and dropped the files you provided on the new exe. I then ran sfc /scannow. I received an error at during the verification stage - "64% - Windows Resource Protection found corrupt files".

Attached you will find the sfc results and a copy of CBS.log.
 

Attachments

I found a RootKit on the system. I've spent the past several days scanning for viruses and malware. I now believe the system is clean. Attached you will find the latest sfcdetails.txt, CBS.log and CheckSUR.log. Any assistance you can offer will be most appreciated!
 

Attachments

Attached you will find the latest CBS.log and CheckSUR.log. The SFC problem appears to be resolved. The latest problem is the fact I am only able to boot up my system by pressing F8 and selecting "Disable Driver Signature Enforcement".

I'd appreciate any advice as to how I can solve this problem.

Thanks to Richard for all your assistance in resolving the problems I had with SFC.

Regards,

Jim
 

Attachments

Hello again Jim :)

I'm very sorry that I haven't posted here for a while. I've been exceptionally busy revising for exams and covering staff absence here. Anyway, exceptionally well done on getting most of your problems fixed.

barrejf said:
The latest problem is the fact I am only able to boot up my system by pressing F8 and selecting "Disable Driver Signature Enforcement".

This is caused by something very specific. First, as I'm sure you've already gathered, it's caused by a driver which doesn't have a valid digital signature. Although this can be caused by lots of reasons, there's only one likely reason. Digital signatures cost big money, but all normal drivers have to have them to operate (after all, you can't make a device which needs Windows booting into disabled driver signature enforcement mode just to work).

The answer is that it's part of your rootkit infection. The malware authors aren't going to pay for a digital signature, so instead they run without one, then hack the system to disable the check.

Your infection is currently in a half removed state. The hack to make the driver work properly even though it doesn't have a digital signature has been removed, but the driver itself, the core of the actual rootkit, lives on.

Now, please can I urge you in the strongest of terms not to try to remove this yourself at this time. It's already in quite a precarious state, and one wrong move will, without a shadow of a doubt, stop this computer booting entirely. It should still be possible to fix then, just it won't be nearly as straightforward. The automated tools have already failed to do a complete & clean removal on your system. What you really need is an experienced human analyst to take a look, track down all remaining parts of the driver, then remove them in one single shot. The whole point here is that the remains of this rootkit cannot be removed in parts, it's got to be taken out in one fell swoop, otherwise the system goes belly up.

I would therefore recommend following these instructions: https://www.sysnative.com/forums/security-arena/2507-malware-removal-posting-instructions.html

and posting a new thread in our Security Arena. It won't be me helping you as I don't do malware removal, but one of the specialists in proper rootkit removal (most likely Corrine or Will Watts).

Please tell them that your computer only boots in Disable Driver Signature Enforcement mode, and that you partially removed a rootkit infection, ideally, providing logs for whatever tools you ran. They'll know straight away what they're up against :)

Good luck!

Richard
 
Hi Richard,

Thanks for the prompt response! I will follow the Malware Removal Posting Instructions you reference in your earlier post.

I cannot thank you enough for all your help!

Thanks!

Jim
 
Back
Top