Missing manifests - error 80070490

Hi. Your site is a real breath of fresh air after the dozens of unhelpful sites that have been leading me round in circles for the past few days! I wonder if you can help me please? I have not been able to install Windows updates for many weeks now. It is possibly the result of a memory card that went kaput, and my subsequent amateur efforts to clean up afterwards . Anyway, the error code that keeps coming up is 80070490. I have attached the necessary files (I think). Thanks in advance, Squiff.

First we'll deal with the Manifests...

Code:

Unavailable repair files:
	winsxs\manifests\amd64_microsoft-windows-installer-engine_31bf3856ad364e35_6.1.7601.22843_none_62089d5be35b3777.manifest
	winsxs\manifests\amd64_microsoft-windows-ie-setup-support_31bf3856ad364e35_11.2.9600.17041_none_a855a9d4736487be.manifest

Then we'll worry about the missing payload files.

I'll post a fix protocol for the manifests a little later.

I've uploaded a file - sqfaa.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 sqfaa in the same place.
Open this folder - there should be one folder inside it (Manifests)

Copy 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.

There's a world of difference - CheckSUR has now fixed the two Manifest problems, so all we have to worry about is the missing payload files, which we have to deal with in a different way.

Please run another SFC /SCANNOW, and post the new CBS.log file, in case the fixed manifests bring new errors to light.
Then we can fix the errors it finds.

SFC found just the one error...

Code:

	Line 138441: 2015-07-14 07:27:35, Info                  CSI    0000035a [SR] Repairing 1 components
	Line 138442: 2015-07-14 07:27:35, Info                  CSI    0000035b [SR] Beginning Verify and Repair transaction
	Line 138443: 2015-07-14 07:27:35, Info                  CSI    0000035c [SR] Cannot repair member file [l:24{12}]"mfc80JPN.dll" of Microsoft.VC80.MFCLOC, Version = 8.0.50727.762, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, file is missing

I'll post a fix protocol for that later, as well as the ones from CheckSUR.

Code:

(f)	CSI Payload File Missing	0x00000000	mshtmlmedia.dll	amd64_microsoft-windows-ie-htmlrenderingmedia_31bf3856ad364e35_11.2.9600.17207_none_a0eb76266e4bb104	
(f)	CSI Payload File Missing	0x00000000	mfc80JPN.dll	amd64_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.762_none_fc42961a63b5a82b

I've uploaded a file - sqfab.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:\sqfab
hit the enter key - if you get a 'Not Found' error try
DIR D:\sqfab
or
DIR E:\sqfab

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

XCOPY <drive>:\sqfab <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