Help With About (4) SFC /Scannow Errors Windows 7 Pro 64-bit SP1

Hah! ye of little faith
Here's the CheckSUR error...

Code:

Unavailable repair files:
	servicing\packages\Package_5_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
	servicing\packages\Package_5_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat

...and here's the SFC errors...

Code:

	Line 3683: 2015-09-19 07:52:26, Info                  CSI    00000368 [SR] Beginning Verify and Repair transaction
	Line 3688: 2015-09-19 07:52:26, Info                  CSI    0000036b [SR] Cannot verify component files for eda0994a5dcb3a3451128b283ebaf43d, Version = 6.1.7601.17966, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
	Line 3691: 2015-09-19 07:52:27, Info                  CSI    0000036d [SR] Cannot repair member file [l:36{18}]"Amd64\HPZSCWN7.DTD" of prnhp002.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch

It's unusual for a Manifest file to show an error in SFC without it appearing in CheckSUR also - but I see this CheckSUR is a couple of days old, so may be a little out of date.
I'll post a fix for the CheckSUR problems first, as they may have a bearing on the SFC.

Back soon.

I've uploaded a file - smkaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder smkaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

Good - that fixed the mum/cat file error (although there's still no mention of the problem Manifest file )

Now for the driver problem...
I've uploaded a file - smkab.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\smkab
hit the enter key - if you get a 'Not Found' error try
DIR D:\smkab
or
DIR E:\smkab

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\smkab <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

Yeh - that's to be expected as the CheckSUR can't do normal file replacements, unfortunately.
See my last post for the fix for the driver file - and once that's out of the way I'll see about the problem with the manifest file.

You don't normally need the disk for that, unless your system has no System Reserved partition?
YOu can create a Repair disk, anyhow... System Repair Disc - Create