Unable to repair all files with SCANNOW. Help repair corrupt files pls

Recently my laptop developed a problem wherein in would not shut down properly. It logged out of Windows with no trouble, but froze on the System Shutting Down screen, and I had to power it off with the power button. I tried this a couple of times to make sure that it wasn't a fluke. It was not. I took it to a repair shop and learned that the hard drive was failing.

I replaced the hard drive myself, by far the techie-est thing I've ever done, just so you know my level of ability (some, but not a lot). I have an external NAS and was able to successfully perform a full system restore. My system is back up and running, and everything seems to be working well, but the machine still cannot power off properly. It's still freezing up on the System Shutting Down screen.

I found SevenForums through a Google search, and followed the suggestions I found for my problem. I ran SCANNOW several times (5), and problem files remained. I went into safe mode and ran SCANNOW there. When I clicked on Shut Down from safe mode, the system was able to power itself correctly (yea!), but it still will not do so not in safe mode.

I've reached the point where I could really use some help. I've created sfcdetails.txt from the CBS log and attached it to this message. There are 2 iterations of SCANNOW represented in this file. The section of the log with a date of 9/17 is from the last run in regular mode yesterday, and the section dated 9/18 is the run in safe mode this morning.

A friend looked at the file and thinks that I have 2 files that are corrupted, but isn't sure and doesn't know what I need to do to fix them. I have a Windows 7 disk that came with my computer, but it has printed on it "not for reinstallation of programs or drivers." I believe it is only for a full reinstallation of Windows.

Sorry if this is too detailed and includes more than you ever need to know, but I wanted to be sure you'd have the info you need to help. I've gone as far as I can with this on my own. Thank you SO MUCH for any help you can provide!

Sincerely,

(Ms.) Hayes Theiling

The files reported to be corrupted in your logs are actually not corrupt. This is a known issue and requires no action on your part.

But if you so wish, you can install both KB3022345 and KB3068708 (replaced KB3022345), and hide them (if/when re-offered) in Windows Update.

As for your issue, try a clean startup - Troubleshoot Application Conflicts by Performing a Clean Startup

Why your System doesn't shut down, I don't know. But it is at least not tied to those 2 files.

After the updates, try the clean startup I linked in earlier post. Troubleshoot Application Conflicts by Performing a Clean Startup
And then load BIOS defaults afterwards if still no go. How to Clear Your Computer?s CMOS to Reset BIOS Settings

Thank you for your additional reply. The updates installed just fine last night, so I will proceed today with the directions on the troubleshooting links that you sent. I will let you know how I fare. Again, thank you so much for all of you help! Bye for now...

Hayes

Just wanted to let you know that I had success with my problem today. I was having such a hard time getting Avast antivirus disabled as a part of the Clean Startup process that I threw in the towel and completely uninstalled it. As soon as I did that, my system shut down normally. When I went back to a normal start-up, my system still shut down as it should.

I researched other free antivirus programs and decided to stay with Avast, if it would work. I reinstalled the program and was able to shut the system down normally a couple of times with it back on my machine. If the problem recurs, I'll switch to a different antivirus program.

Once again, thank you so much for taking the time to help me. I would never have been able to work this out for myself and am truly grateful for your kindness. Bless you!

Sincerely,

Hayes Theiling

Glad to hear it is fixed. Anti virus software is hard to disable with msconfig and even then may still cause problems vecause they go deep in the OS.