Windows 7 Sp1 update- error 80073712 CSI Payload File Missing

mbrown · 07 Mar 2013

I am at a lost. I've been avoiding updating the SP1 for months. Today, I finally decided to figure out the issue. I have run the Update Troubleshooter. The Readiness tool and checksur.

I'm getting the error code: 80073712
I found out that means the Component Store is corrupt.

Here is the CBS file:

Attachment 258339

The CheckSUR says I am missing:
(f) CSI Payload File Missing 0x00000000 efisys.bin amd64_microsoft-windows-b..ironment-dvd-efisys_31bf3856ad364e35_6.1.7601.17514_none_c0c6eceaf97c4827
(f) CSI Payload File Missing 0x00000000 System.Data.Services.Design.dll x86_netfx35linq-system.data.services.design_31bf3856ad364e35_6.1.7601.17514_none_fbd7ac850c4fad9b

I am lost as to how to find those files and how to fix the corruption. My Windows 7 was installed when I purchased the laptop. I'm sure I have a backup disk somewhere, but I would have to find it. I would prefer not to have to install or reinstall if it is possible to fix it.

I appreciate any help.

NoelDP · 07 Mar 2013

No worries - we'll provide any files required. :) (say he, hopefully!)
Back in a few minutes, with any luck.

mbrown · 07 Mar 2013

I appreciate it.

NoelDP · 07 Mar 2013

I've uploaded a file - mbraa.zip - to my SkyDrive at Noel's SkyDrive
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:\mbraa
hit the enter key - if you get a 'Not Found' error try
DIR D:\mbraa
or
DIR E:\mbraa

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

XCOPY <drive>:\mbraa <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 run the CheckSUR tool again.
Post the full CBS.log and CheckSUR.log files so we can check that things went as expected.

mbrown · 07 Mar 2013

Will do. Give me a few minutes and I will. Thanks so much!

mbrown · 08 Mar 2013

OK. I ran the SFC/Scannow and it looks like it came back with no problems.

I've been trying to run CheckSur for hours. It either runs for ever or barely even installs.
Here is the result from the last one which I had to stop after two hours.

Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-03-08 04:50

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Payload File Missing 0x00000000 System.Data.Services.Design.dll x86_netfx35linq-system.data.services.design_31bf3856ad364e35_6.1.7601.17514_none_fbd7ac850c4fad9b

I'm trying to run it again. Here is the CBS file, in the meantime:
Attachment 258427

Also, I ran the update again and I got the same error code at about 75%.

mbrown · 08 Mar 2013

Finally able to fully run the Check SUR. Here are the results:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-03-08 09:41

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Payload File Missing 0x00000000 System.Data.Services.Design.dll x86_netfx35linq-system.data.services.design_31bf3856ad364e35_6.1.7601.17514_none_fbd7ac850c4fad9b

Summary:
Seconds executed: 3193
Found 1 errors
CSI Payload File Missing Total count: 1

NoelDP · 08 Mar 2013

50+ minutes isn't so bad :)

The problem is that you haven't followed the instructions - so we have no real idea what's happened.

One file that we replaced appears to have worked - but the other is in limbo.
Please try the exact same instructions again, and let's see if anything more happens :)

mbrown · 09 Mar 2013

I followed the instructions again and I am getting the exact same result.
It copies the same 3 files and SFC/Scannow says there are no issues.
CheckSUR says there is a payload file missing.

Are you sure that file is one of the files you had me copy?

NoelDP · 09 Mar 2013

Ooops! - you're right.

I gave you the x64 version of the file, rather than the x86 version.
(No harm done, at least!)

I think I've got the right one this time :)

I've uploaded a file - mbrab.zip - to my SkyDrive at Noel's SkyDrive
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:\mbrab
hit the enter key - if you get a 'Not Found' error try
DIR D:\mbrab
or
DIR E:\mbrab

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

XCOPY <drive>:\mbrab <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 SkyDrive Public folder, and post a new link
Also run a new MGADiag report, and post the result.

(Sorry about that!)