Solved SFC - Windows Resource Protection found corrupt files

[tjg79]

Hi, I just installed the latest updates and performed a clean install of the NVIDA driver package and now I'm having issues with the System File Checker. Attached are the screenshots. Has anyone else had a problem with these latest optional updates? I don't know for certain that the SFC issues are the result of the latest updates or something else?

What's the recommend course of action? I haven't attempted it yet, but I'm thinking of trying a system restore to see if it clears the corrupt files. As you can see from the screenshot, I've run SFC /SCANNOW a few times and in some cases, it indicates that it successfully repaired the corrupted files, but when I perform a subsequent run, the results indicate that the corrupted files issue persists.

What's the best course of action?

Regards

 

[torchwood]

Hi TJG79,

please run KB947821, a repair tool
REBOOT

rerun sfc /scannow.

Then post the cbs ans SURT details.

they are in C >> windows >> logs >> CBS ...(top log cbs and surt)

Roy

 

[tjg79]

Hi Roy,

Thanks for the quick reply. While I was waiting for a reply, I rebooted and then ran the SFC again with the same results. First run I get the indication that it fixed the corrupted files, but on the confirmation run, I get a different result.

Now I'll run KB947821 and post the results.

Regards,

Tim

 

[tjg79]

OK, after running KB947821 and rebooting, I get the same result. Attached are the CBS and SURT details.

Do you have a fix? The last time this happened, I ended up reloading the OS.

Regards







View attachment CheckSUR.log


View attachment 401402

 

[tjg79]

OK, here's a better CBS file. The previous one I posted didn't include the latest run, because I failed to refresh the folder before I copied the file. This one has a bit more information.

View attachment 401403

 

[torchwood]

Hi TJG79,

looking at both logs, SURT was clear and SFC repaired what it found.
Scannow has been known to report false positives.
The repairs all concerned your USBhub, try updating the drivers


as a quick backup run this tool, copy/paste the output
http://www.sysnative.com/niemiro/apps/SFCFix.exe

Roy

 

[tjg79]

Well, the issue is resolved, but I'm not sure why. Since it was an issue that appeared to be related to the Windows Update, I called Microsoft and the tech rep's solution was to run sfc /scannow and it that didn't work, perform a Repair Install of the OS. That's a crap solution. Since it did appear to be a USB hub issue, I first removed and reinstalled all the VIA drivers and software for my USB add-in card. That wasn't the fix. So, with the Microsoft guy on the phone, we attempted a System Restore to 20 Oct. I got an indication that the System Restore was unsuccessful. So, the next solution was to restore from a good image taken on 12 October, but that's where the Microsoft guy bailed, because they don't want any liability and he wouldn't even refresh my memory about how to do a restore from an image. So, I was going to attempt to do the restore from an image, but I wanted to try something else first. After taking a closer look at the CBS log file, I didn't see anything that indicated VIA USB hub, but there are 8 Microsoft USB hub drivers. So, I started from the top in device manager and after the second MS USB hub driver was uninstalled, I lost the mouse. So, I rebooted and started removing them from the bottom up. The last driver removed was the mouse, so I rebooted again and ran the SFC with another unsuccessful result. I attempted to run SFC again, but it indicated that I had a repair reboot to do first. I'd never seen that before. So, I rebooted and the SFC was successful. The other odd observation is that although the System Restore indicated it wasn't successful and no files were restored, it does appear that the files were restored, because I've got the optional updates offered again and my display driver is back to where I started. So, I'll do the Windows update again to see what happens, then run SFC and confirm everything is still good and then update the NVIDIA display driver. I suspect direct fix was just to uninstall all he MS USB hub drivers and reboot a couple times with runs of SFC. Regards