System restore error 0x0070005, leads me to corrupt files. Advice.

Tried to do a system restore today, for a specific reason. Could do it. Got error 0x0070005.

Did some Googling, tried running a DISM command, got error 87: An error occurred while processing the command.

Ran the sfc /scannow command.....Windows Resource Protection found corrupt files, but was unable to fix some of them.

I don't know if the corrupt files are why I can't do a system restore, but I'm assuming it's why, but regardless, I can't do a system restore, and I do have corrupt files.

I couldn't do a system restore a while back, and I was going to look into it, or maybe do a repair install, or whatever, and just sort of forgot about it. The last few days, my computer has a couple instances of getting super slow, and almost freezing. Don't know if it's related, but bottom line is, I'd like my system restore to be back to normal, and fix whatever files are corrupt.

I've attached my sfcdetails.txt, if that helps at all. Weird.....the way I read that, it says it repaired 5 components, which I'm assuming are the corrupt files, but scannow still says there are files it can't repair. Maybe it's two different things, as this is getting out of my comfort zone, that's why I'm here. :)

It tells me access denied to CBS file, for whatever reason.

Also attached the CheckSUR.log, in case that helps at all.

Any advice greatly appreciated.

Thanks in advance!

Snick said:

Hi acillatem,

Not being able to utilize Windows System Restore is exactly why I don't recommend using it. When you need it, as you apparently do, it doesn't work! I always back up my system to an external hard drive.
Recommend either AOMEI free or Macrium Reflect free. External Hard Drive, not External SSD. Longer life less prone to errors.

Here's your corrupt manifest replacements:

download and unzip SURT Replacement Files
Click Start ORB, into searchbox, copy & paste
%windir%\temp\
paste CheckSUR folder into temp
Run SURT tool again. post log please.

Thank you for the reply! I've since been directed to sysnative.com and I got it resolved.

Thanks again! :)