Help Installing 'Important' Updates - Errors 80004005 & 80073712

[jacko900000]

*Firstly, If this is in the wrong section I apologize I'm new*

I've been trying to do these updates now for several months, I get the same errors everytime and each time I turn off my PC i get "installing 4 updates"

I'll be honest, I don't know what the updates are for or when they even do. My computers working fine without the updates but it bugs me to know they're there and I can't do anything.

I have looked into it in the past but always ended up giving up on it.

I joined the forum yesterday and The Guy (member) resolved my issue withing a couple of hours and his reply was the first one !

I'm not totally dumb with computers, I know my way around one. I've done graphic design before, php, mySQL, c++, HTML, Java, CSS etc so I'm not 'blonde' as the UK would say.

Anyways back onto the error, I've uploaded a couple of pictures. I get the error within about 3 minutes of clicking to update so don't know where its going wrong.

1) When I click on 'Windows Update' first thing I see.

2) Around 3 to 10 minutes after clicking 'Install updates' I get this.

3) Review important updates.

4) Review optional updates.

I have clicked the "get help with this error" but then it brings the "windows help" box up showing completely different errors which are not any of the above.

Any help appreciated & as said above sorry if its in wrong section just report it and I'm sure a moderator will move it to the correct section.

 

[NoelDP]

Please follow the http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html and post the requested data

 

[jacko900000]

Please follow the http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html and post the requested data

Ok so..
I've done some of the following and messed up my computer (again)
Said updates were completed and to reboot my PC so I did, When my PC come back on the desktop was really messed up.
I had all my desktop icons but with no text, The time in the lower right didn't display, when I clicked the start orb it glowed like it should but nothing happened & when I clicked the Chrome icon for browser I got BSOD

I'll go more into what I've done now.

1)
I went to the link above and did #1 first (1. System Update Readiness Tool (SURT))
I went to the Microsoft (link above) RESOLOUTION > For Windows 7, Windows Vista, Windows Server 2008, Windows Server 2008 RS
First downloaded All supported x86-based versions of Windows 7 which gave me an error saying it wasn't compatible with my computer (Attached image of my msinfo32 below
I then went to download All supported x64-based versions of Windows Server 2008 R2 which allowed me to install, I did the updates and said that 1 wasn't needed/important and prompted me to reboot my PC which leaded my PC to the error above then to the BSOD.

Before re-booting my PC I also did the SFC Scan #2 on the list from the link above.

I have attached my CBS log below along with some screen shots.

I had to base my computer (which I HATE doing) then hold F8 to enter recovery mode and recover my PC to yesterday for my desktop to be able to work again.

I also got a new error this time which was Error code 9c57 which after looking around at the error is something to do with updating IE on windows 7.

I hope somebody can help, Each time it looks like the updates have installed I get the 'corrupted desktop' which leads to BSOD then I can't do a thing unless I roll back my PC to a previous date

I have attached a picture of the BSOD I got after my desktop had 'corrupted'
Also attached the CBS log.

 

[NoelDP]

You have some fairly sever problems with your machine.
The CBS.log file you uploaded doesn't contain the data from the SFC scan - which has been archived to the CBS.persist logs

There are too many errors in the post-boot CBS to quote them all, but here are the more important....

 Line 4890: 2013-03-25 12:15:43, Error                 CBS    Failed. Attempted to uninstall a version of a non-driver component that is not installed, version: 0X600011db042a1, component: amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7600.17057_none_a4e55ed934239d78, owner: Package_11_for_KB2729094~31bf3856ad364e35~amd64~~6.1.1.0.2729094-22_neutral_GDR [HRESULT = 0x80004005 - E_FAIL]
 Line 4901: 2013-03-25 12:15:43, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80004005 - E_FAIL]
 Line 6735: 2013-03-25 12:15:56, Error                 CSI    00000026 (F) Unable to load manifest for component [ml:280{140},l:184{92}]"amd64_2c673872ed0d470728698c38541b8433_b03f5f7f11d50a3a_6.1.7601.21660_none_a27fa4dbfa3cff43"[gle=0x80004005]
 Line 6736: 2013-03-25 12:15:56, Error                 CSI    [EMAIL="00000027@2013/3/25:12:15:56.899"]00000027@2013/3/25:12:15:56.899[/EMAIL] (F) d:\win7sp1_gdr\base\wcp\componentstore\storelayout.cpp(2714): [B]Store corruption detected in function ComponentStore::CRawStoreLayout::[/B]FetchManifestContent expression: 0
 Line 6738: 2013-03-25 12:16:00, Error                 CSI    00000028 (F) HRESULT_FROM_WIN32(14098) #87728# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::GetDeploymentInformation(flags = 0, class = ICSIINVENTORY_GET_DEPLOYMENT_INFORMATION_CLASS_CLOSURE (1), information = {dwFlags=00000000})
 Line 6751: 2013-03-25 12:16:00, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

If we can't get the CheckSUR to run properly (and yes, you need the 64-bit version), then I suspect that your first recourse will be a repair install (which I would almost expect to fail)

Please first check that your disk is healthy.


Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

CHKDSK C: /R

and hit the Enter key.
You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, press Enter, and then reboot.

The CHKDSK will take a few hours depending on the size of the drive, so be patient!

After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -


Please open Event Viewer
In the left pane, navigate to the Windows Logs
right-click on Applications and select 'Save all events as...' save as Apps.evtx
repeat for the System logs - save as Sys.evtx
Compress both files, and attach to your reply.

 

[jacko900000]

You have some fairly sever problems with your machine.
The CBS.log file you uploaded doesn't contain the data from the SFC scan - which has been archived to the CBS.persist logs

There are too many errors in the post-boot CBS to quote them all, but here are the more important....

 Line 4890: 2013-03-25 12:15:43, Error                 CBS    Failed. Attempted to uninstall a version of a non-driver component that is not installed, version: 0X600011db042a1, component: amd64_microsoft-windows-g..validatefntcache-03_31bf3856ad364e35_6.1.7600.17057_none_a4e55ed934239d78, owner: Package_11_for_KB2729094~31bf3856ad364e35~amd64~~6.1.1.0.2729094-22_neutral_GDR [HRESULT = 0x80004005 - E_FAIL]
 Line 4901: 2013-03-25 12:15:43, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80004005 - E_FAIL]
 Line 6735: 2013-03-25 12:15:56, Error                 CSI    00000026 (F) Unable to load manifest for component [ml:280{140},l:184{92}]"amd64_2c673872ed0d470728698c38541b8433_b03f5f7f11d50a3a_6.1.7601.21660_none_a27fa4dbfa3cff43"[gle=0x80004005]
 Line 6736: 2013-03-25 12:15:56, Error                 CSI    [EMAIL="00000027@2013/3/25:12:15:56.899"]00000027@2013/3/25:12:15:56.899[/EMAIL] (F) d:\win7sp1_gdr\base\wcp\componentstore\storelayout.cpp(2714): [B]Store corruption detected in function ComponentStore::CRawStoreLayout::[/B]FetchManifestContent expression: 0
 Line 6738: 2013-03-25 12:16:00, Error                 CSI    00000028 (F) HRESULT_FROM_WIN32(14098) #87728# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::GetDeploymentInformation(flags = 0, class = ICSIINVENTORY_GET_DEPLOYMENT_INFORMATION_CLASS_CLOSURE (1), information = {dwFlags=00000000})
 Line 6751: 2013-03-25 12:16:00, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

If we can't get the CheckSUR to run properly (and yes, you need the 64-bit version), then I suspect that your first recourse will be a repair install (which I would almost expect to fail)

Please first check that your disk is healthy.


Click on Start > All Programs > Accessories
Right-click on the Command Prompt entry
Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.

At the Command prompt, type

CHKDSK C: /R

and hit the Enter key.
You will be told that the drive is locked,
and the CHKDSK will run at he next boot - hit the Y key, press Enter, and then reboot.

The CHKDSK will take a few hours depending on the size of the drive, so be patient!

After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -


Please open Event Viewer
In the left pane, navigate to the Windows Logs
right-click on Applications and select 'Save all events as...' save as Apps.evtx
repeat for the System logs - save as Sys.evtx
Compress both files, and attach to your reply.

I'm just doing the SFC scan now which is at 73%
If the above CHKDSK scan will take several hours should I re-post my CBS here after the SFC scan has finished? I have a 1TB HDD and I don't know how long the scan will take.

You said the problem is sever .. how bad is it on your recommendation?

 

[NoelDP]

We won't know until all the results are in - but that error in the log (Store corruption detected in function ComponentStore) doesn't bode well for an easy fix.

 

[jacko900000]

We won't know until all the results are in - but that error in the log (Store corruption detected in function ComponentStore) doesn't bode well for an easy fix.

Ok thank you.
I've attached the zip file again with the log file also another picture from the CMD.

If this has no help I'll do what you said above but I'll wait for your response.

Thanks, If its a complicated thing to fix I'll just back up all my data ( 700GB's worth !) and just reinstall...

 

[NoelDP]

Here's the Summary data from the SFC scan....

 Line 3545: 2013-03-25 12:55:55, Info                  CSI    00000316 [SR] Repairing 6 components
 Line 3546: 2013-03-25 12:55:55, Info                  CSI    00000317 [SR] Beginning Verify and Repair transaction
 Line 3551: 2013-03-25 12:55:55, Info                  CSI    0000031a [SR] Cannot verify component files for 571297603cad7f1f8d4cfb973f6ff3f4, Version = 6.1.7601.17559, 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 3556: 2013-03-25 12:55:55, Info                  CSI    0000031d [SR] Cannot verify component files for 760ff523356fce1389ab94f0ac0e5344, Version = 6.1.7601.17578, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 3561: 2013-03-25 12:55:56, Info                  CSI    00000320 [SR] Cannot verify component files for Microsoft-Windows-Printing-XpsPrint, Version = 6.1.7601.17578, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 3564: 2013-03-25 12:55:56, Info                  CSI    00000322 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:22{11}]"uxtheme.dll" from store
 Line 3567: 2013-03-25 12:55:56, Info                  CSI    00000324 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:22{11}]"themeui.dll" from store
 Line 3570: 2013-03-25 12:55:56, Info                  CSI    00000326 [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:22{11}]"segoeui.ttf" from store
 Line 3573: 2013-03-25 12:55:56, Info                  CSI    00000328 [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"seguisym.ttf" from store
 Line 3576: 2013-03-25 12:55:56, Info                  CSI    0000032a [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"segoeuib.ttf" from store
 Line 3579: 2013-03-25 12:55:56, Info                  CSI    0000032c [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"segoeuii.ttf" from store
 Line 3582: 2013-03-25 12:55:56, Info                  CSI    0000032e [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"segoeuiz.ttf" from store
 Line 3599: 2013-03-25 12:55:57, Info                  CSI    00000330 [SR] Repair complete

As you can see, there's three manifest files which are damaged - and the system is requesting a reboot to complete one of the repairs it has made.

The earlier error doesn't appear in this log, which is a good sign (I think!)

Make a System Restore point, and then try running the CheckSUR tool again - it has more chance of working this time, I think.
Post both the CheckSUR.log and CheckSUR.persist.log files

 

[jacko900000]

Here's the Summary data from the SFC scan....

 Line 3545: 2013-03-25 12:55:55, Info                  CSI    00000316 [SR] Repairing 6 components
 Line 3546: 2013-03-25 12:55:55, Info                  CSI    00000317 [SR] Beginning Verify and Repair transaction
 Line 3551: 2013-03-25 12:55:55, Info                  CSI    0000031a [SR] Cannot verify component files for 571297603cad7f1f8d4cfb973f6ff3f4, Version = 6.1.7601.17559, 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 3556: 2013-03-25 12:55:55, Info                  CSI    0000031d [SR] Cannot verify component files for 760ff523356fce1389ab94f0ac0e5344, Version = 6.1.7601.17578, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 3561: 2013-03-25 12:55:56, Info                  CSI    00000320 [SR] Cannot verify component files for Microsoft-Windows-Printing-XpsPrint, Version = 6.1.7601.17578, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
 Line 3564: 2013-03-25 12:55:56, Info                  CSI    00000322 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:22{11}]"uxtheme.dll" from store
 Line 3567: 2013-03-25 12:55:56, Info                  CSI    00000324 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:22{11}]"themeui.dll" from store
 Line 3570: 2013-03-25 12:55:56, Info                  CSI    00000326 [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:22{11}]"segoeui.ttf" from store
 Line 3573: 2013-03-25 12:55:56, Info                  CSI    00000328 [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"seguisym.ttf" from store
 Line 3576: 2013-03-25 12:55:56, Info                  CSI    0000032a [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"segoeuib.ttf" from store
 Line 3579: 2013-03-25 12:55:56, Info                  CSI    0000032c [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"segoeuii.ttf" from store
 Line 3582: 2013-03-25 12:55:56, Info                  CSI    0000032e [SR] Repairing corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\fonts"\[l:24{12}]"segoeuiz.ttf" from store
 Line 3599: 2013-03-25 12:55:57, Info                  CSI    00000330 [SR] Repair complete

As you can see, there's three manifest files which are damaged - and the system is requesting a reboot to complete one of the repairs it has made.

The earlier error doesn't appear in this log, which is a good sign (I think!)

Make a System Restore point, and then try running the CheckSUR tool again - it has more chance of working this time, I think.
Post both the CheckSUR.log and CheckSUR.persist.log files

Ok so.
I created a manual restore point.
Re-booted my PC and when it came back on I got the 'corrupted desktop' I've been going on about.
I though ok I'll just run in safe mode and restore to yesterday as I did this morning... but NOOO !!!

The restore point i just created thats the only one I can select even when I click the little box to view older restore points..

Please help !
I have very important information on my PC that I can't loose.
All I want to do is re-store it to an older date but I am very limited with what I do, I can't even press the start button in safe mode now.

Is they a way on bootup e.g F8 to prompt the recovery to an older date?!

 

[NoelDP]

You should have the option to 'Repair my Computer' from an F8 boot.
See what it can do with Startup repair (if you have no visible Restore points in normal mode, then I doubt that any more will be available from RE, but you can always try it)

 

[jacko900000]

You should have the option to 'Repair my Computer' from an F8 boot.
See what it can do with Startup repair (if you have no visible Restore points in normal mode, then I doubt that any more will be available from RE, but you can always try it)

Hit a brick wall, lost all my data
I've literally tried everything, I can't even back my data up everything just displays wrong and gives me no text so I don't know what I'm clicking.

I have a 70GB external HDD was wondering if I boot windows from that will I be able to access my data on main HDD to back them up ?

 

[NoelDP]

You should be able to - assuming the disk hasn't died.

Make sure that you disconnect the 'old' drive when installing Windows on the temporary drive - reconnect it afterwards.

 

[jacko900000]

You should be able to - assuming the disk hasn't died.

Make sure that you disconnect the 'old' drive when installing Windows on the temporary drive - reconnect it afterwards.

Its ok managed to get things recovered but having more issues now

http://www.sevenforums.com/backup-r...eing-used-after-back-up-help.html#post2340096