[SOLVED] Window updates Fail code 80073712 on KB3006121 & KB2852386

vannet10 · Feb 13, 2015

Hi,

I'm new here and would like to say hello to everyone. I hope someone could help me out with my window updates problem.

My problem is I could not successfully update KB3006121 & KB2852386. This problem probably is link to how I wipe out my window 8 and install window 7.
I have follow the instruction here to diagnose he problem and here is the SFCfix Log:

SFCFix version 2.4.2.1 by niemiro.
Start time: 2015-02-13 23:39:23.738
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.

AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 10
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-02-13 23:42:52.985
----------------------EOF-----------------------

Wanted to attach the CBS zip folder but the upload doesn't work.
I paste the CheckSUR file contact here:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-02-12 23:17

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_1_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_1_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB3006121_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB3006121_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.cat

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.18648_none_f444a3cc02b20fea.manifest x86_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.18648_none_f444a3cc02b20fea
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.18648_none_50633f4fbb0f8120.manifest amd64_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.18648_none_50633f4fbb0f8120
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.22856_none_f4c171fd1bd9961e.manifest x86_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.22856_none_f4c171fd1bd9961e
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.22856_none_50e00d80d4370754.manifest amd64_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.22856_none_50e00d80d4370754

Summary:
Seconds executed: 786
Found 10 errors
CSI Manifest All Zeros Total count: 4
CBS MUM Corrupt Total count: 3
CBS Catalog Corrupt Total count: 3

Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.18648_none_f444a3cc02b20fea.manifest
winsxs\manifests\amd64_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.18648_none_50633f4fbb0f8120.manifest
winsxs\manifests\x86_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.22856_none_f4c171fd1bd9961e.manifest
winsxs\manifests\amd64_microsoft-windows-charmap_31bf3856ad364e35_6.1.7601.22856_none_50e00d80d4370754.manifest
servicing\packages\Package_1_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_1_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB3006121_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB3006121_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_1_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_1_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB3006121_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB3006121_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB3006121~31bf3856ad364e35~amd64~~6.1.1.0.cat

If the above info is not enough, please let me know and I will fill in.
Hopefully someone could help me and thanks in advance.

Leng

tom982 · Feb 13, 2015

Hello Leng, welcome to Sysnative!

This should fix everything:

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Please download the attached file, Packs.zip and save this to your Desktop.
Right-click on the file and select Extract All...
Tick the box labelled Show extracted files when complete then click Extract
A window will open showing two folders, Manifests and Packages
Open the Manifests folder and copy the files into the following folder (if there are any files)

C:\Windows\Temp\CheckSur\Winsxs\Manifests
Open the Packages folder and copy the files into the following folder (if there are any files)

C:\Windows\Temp\CheckSur\Servicing\Packages
Run the System Update Readiness Tool (SURT) again.
When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

C:\Windows\Logs\CBS\CheckSUR.persist.log

You will probably be shown the error code 0x8024200D after performing this fix, if so, please download and install the update from this link:

https://www.microsoft.com/en-us/download/confirmation.aspx?id=45062

It must be downloaded using Internet Explorer.

Packs.zip: https://dl.dropboxusercontent.com/u/16537616/Fixes/SFCFix/Scripts/vannet10/Packs.zip

Tom

vannet10 · Feb 14, 2015

tom982 said:
Hello Leng, welcome to Sysnative!

This should fix everything:

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Please download the attached file, Packs.zip and save this to your Desktop.

Right-click on the file and select Extract All...

Tick the box labelled Show extracted files when complete then click Extract

A window will open showing two folders, Manifests and Packages

Open the Manifests folder and copy the files into the following folder (if there are any files)

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

Open the Packages folder and copy the files into the following folder (if there are any files)

C:\Windows\Temp\CheckSur\Servicing\Packages

Run the System Update Readiness Tool (SURT) again.

When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

C:\Windows\Logs\CBS\CheckSUR.persist.log

You will probably be shown the error code 0x8024200D after performing this fix, if so, please download and install the update from this link:

https://www.microsoft.com/en-us/download/confirmation.aspx?id=45062

It must be downloaded using Internet Explorer.

Packs.zip: https://dl.dropboxusercontent.com/u/16537616/Fixes/SFCFix/Scripts/vannet10/Packs.zip

Tom

Hi Tom,

This is Great! I did fixed those errors in the log file and I managed to successfully update KB3006121. However, KB2852386 still failed to update. This time, I got the error code '800B0100'. This code is different from the one you anticipated. So, should I use the same window update link that you provided here or you would like to suggest a different one?

I managed to attach the CheckSUR file this time. Please advice and once again thank you for the great help.

Leng

tom982 · Feb 14, 2015

Hello Leng,

Oh my, it's been a while since I had one of these! No ignore my last post, that fixed one of the errors but one I didn't spot is yet to be fixed (same error code, different location). This should do the trick:

Software Distribution rename

Click Start -> Type in CMD in the search -> Right click on cmd.exe and choose Run as Administrator
Entre in the following commands:
net stop wuauserv
ren %SystemRoot%\SoftwareDistribution\Download DL.bak
ren %SystemRoot%\SoftwareDistribution\DataStore DS.bak
net start wuauserv

(Thanks to Go The Power for the instructions, I stole them )

When that's done, try to update and if it still fails then upload your CBS log please:

C:\Windows\Logs\CBS\CBS.log

Tom

vannet10 · Feb 16, 2015

tom982 said:
Hello Leng,

Oh my, it's been a while since I had one of these! No ignore my last post, that fixed one of the errors but one I didn't spot is yet to be fixed (same error code, different location). This should do the trick:

Software Distribution rename

Click Start -> Type in CMD in the search -> Right click on cmd.exe and choose Run as Administrator

Entre in the following commands:
net stop wuauserv
ren %SystemRoot%\SoftwareDistribution\Download DL.bak
ren %SystemRoot%\SoftwareDistribution\DataStore DS.bak
net start wuauserv

(Thanks to Go The Power for the instructions, I stole them )

When that's done, try to update and if it still fails then upload your CBS log please:

C:\Windows\Logs\CBS\CBS.log

Tom

Hi Tom,

Again thanks for the advice. It did solve the problem and I managed to successfully update. However, a new problem came up. A BSOD.

I have attached that BSOD here. What do you think could be the problem this time?

Regards
Leng

tom982 · Feb 16, 2015

Great! 0x800B0100 is usually a nice easy one to fix so I'm glad you're up and running again.

That looks like it was caused by your (presumably outdated) Intel Rapid Storage Technology (RST) driver, but I'm not great at BSOD analysis. Fortunately for you, you're at the right place! When this forum was setup it was meant to be BSOD focused and we have some of the best in the business here.

It would be best if you started a new thread for this issue and posted the information they need: https://www.sysnative.com/forums/bs...ons-windows-10-8-1-8-7-and-windows-vista.html

Let me know if you have any issues, or if you don't get a reply and I'll try and pester someone to look at it for you (or do it myself if I can).

Tom

vannet10 · Feb 16, 2015

tom982 said:
Great! 0x800B0100 is usually a nice easy one to fix so I'm glad you're up and running again.

That looks like it was caused by your (presumably outdated) Intel Rapid Storage Technology (RST) driver, but I'm not great at BSOD analysis. Fortunately for you, you're at the right place! When this forum was setup it was meant to be BSOD focused and we have some of the best in the business here.

It would be best if you started a new thread for this issue and posted the information they need: https://www.sysnative.com/forums/bs...ons-windows-10-8-1-8-7-and-windows-vista.html

Let me know if you have any issues, or if you don't get a reply and I'll try and pester someone to look at it for you (or do it myself if I can).

Tom

Hi Tom,

I have created a new post as you recommended in the BSOD section. Will see if someone pickup. If not, I guess might have to trouble you again:) Thanks as always and I will update you or if anything.

Leng

tom982 · Feb 17, 2015

No problem Leng, I see Jared has taken on your thread now and I'm sure he'll get you up and running in no time at all :)

vannet10 · Feb 22, 2015

Yes, He did and I'm fixing it now with his solution. Again Tom, thanks for the help. This is a great forum!

Leng

Search

Search

[SOLVED] Window updates Fail code 80073712 on KB3006121 & KB2852386

vannet10

Member

tom982

Emeritus

vannet10

Member

Attachments

tom982

Emeritus

vannet10

Member

Attachments

tom982

Emeritus

vannet10

Member

tom982

Emeritus

vannet10

Member