CBS log reflects 2 problems (Attention: @Torchwood)

Roy--
I've forked this off the other thread.

1-SFC says it found errors that can't be fixed.

2-I haven't installed security updates in over a year. I have installed several others, but I keep them down to a minimum, as I don't use any other M$ programs. I haven't panicked about the security updates since meeting a lot of users online who don't install them at all. (I used XP for 4 years after the security updates stopped, just was careful where I went.)

I already tried a Repair Install a few months ago, and it didn't work. I've chosen to keep the problem if need be, rather than wiping the drive and redoing.

The identical installation of Win7 on my Gateway (see my sig) is newer, and doesn't have these 2 problems. Of course. Maybe I can import some non-corrupted files from there, or is that too simple?

I removed part of the CBS log before 6/27 for size, but the errors noted were similar. I have a bunch of cabfiles too, going back to 6/22.

What about all the "Failed to open package" lines in the log?

Tried installation of SURT. "The update is not compatible to your computer."

Ran the M$ Update Repair Tool, which says it fixed problems. Still can't run SURT.

Stuck for a half-hour at "Initializing installation." Finished after about an hour. It claims it's installed. Latest security update KB4503292 still doesn't install.