Solved Update issues with windows 7 SP1 error 8007002

[Cargo48]

It's been a problem for a while and I've been putting off getting it sorted for a while, I've tried the windows readiness tool and also done a few things like restarting the service. All to no avail.

I was wondering if you guys could help me get this error fixed!


thanks,
Cargo

 

[NoelDP]

Please follow the Windows Update Posting Instructions and post the requested data
If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

 

[Cargo48]

Okay - I've attached the CBS folder but removed some of the older files as you suggested. The SURT takes a while but then just says it was successful, and the update still does not complete and gives the same 80007002 error.


Cargo

 

[NoelDP]

CheckSUR appears to have crashed before completion for some reason.

The SFC san shows the following problem...

 Line 5589: 2014-06-27 18:50:00, Info                  CSI    000002fc [SR] Repairing 1 components
 Line 5590: 2014-06-27 18:50:00, Info                  CSI    000002fd [SR] Beginning Verify and Repair transaction
 Line 5591: 2014-06-27 18:50:00, Info                  CSI    000002fe [SR] Cannot repair member file [l:84{42}]"System.Management.Automation.Resources.dll" of System.Management.Automation.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 5592: 2014-06-27 18:50:00, Info                  CSI    000002ff [SR] Cannot repair member file [l:84{42}]"System.Management.Automation.Resources.dll" of System.Management.Automation.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 5593: 2014-06-27 18:50:00, Info                  CSI    00000300 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Microsoft-Windows-Client-Features-Language-Pack"
 Line 5598: 2014-06-27 18:50:00, Info                  CSI    00000302 [SR] Repair complete

The background CBS data shows a number of problems, beginning (I think!) with this one...

2014-06-27 03:06:12, Error                 CSI    [EMAIL="00000015@2014/6/27:02:06:12.063"]00000015@2014/6/27:02:06:12.063[/EMAIL] (F) d:\win7sp1_gdr\base\wcp\primitiveinstallers\fileinstaller.cpp(1482): Store corruption detected in function CFileInstaller::ChangeFileCompression expression: 0
  MissingFileSystemResource on resource [149]"\winsxs\msil_system.management.automation.resources_31bf3856ad364e35_6.1.7601.17514_en-us_92e4c7898423b181\system.management.automation.resources.dll"[gle=0x80004005]
2014-06-27 03:06:14, Error                 CSI    00000016 (F) STATUS_OBJECT_NAME_NOT_FOUND #10744029# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0x19fd790->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[163]"\??\C:\Windows\WinSxS\msil_system.management.automation.resources_31bf3856ad364e35_6.1.7601.17514_en-us_92e4c7898423b181\System.Management.Automation.Resources.dll"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x19fd770, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000034]
2014-06-27 03:06:14, Error                 CSI    [EMAIL="00000017@2014/6/27:02:06:14.731"]00000017@2014/6/27:02:06:14.731[/EMAIL] (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2014-06-27 03:06:43, Error                 CSI    00000018 (F) STATUS_OBJECT_NAME_NOT_FOUND #10744028# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingFile(...)[gle=0xd0000034]

- which tallies nicely with the SFC error

Hopefully fixing that one will allow CheckSUR to finish next time we run it.

I'll post a fix protocol for it a bit later.

 

[NoelDP]

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



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



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

 

[Cargo48]

Okay thanks for these speedy replies! I have done the steps you have said and it works fine, the directory was D:\ in the end - i have attached the new CBS logs after rebooting,

Thanks
Cargo

 

[NoelDP]

How very strange....
The error is still present in SFC, but CheckSUR now completes properly, and also flags the problem - as well as flagging a second file .

Checking Component Store
(f) CSI Payload File Missing 0x00000000 System.Management.Automation.Resources.dll msil_system.management.automation.resources_31bf3856ad364e35_6.1.7600.16385_en-us_90b3b3c187352de7 
(f) CSI Payload File Missing 0x00000000 System.Management.Automation.Resources.dll msil_system.management.automation.resources_31bf3856ad364e35_6.1.7601.17514_en-us_92e4c7898423b181

I want to play a little before I post a new fix, to see what I can find out.

back later.

 

[NoelDP]

I was hoping to use CheckSUR for the repair, rather than my usual methods, but it seems only to diagnose, rather than effect any repairs.
Since the earlier repair appears to have (at least partially) failed, I think it would be worth checking a few things before diving in at the deep end

Please open an elevated Command Prompt, and run the following commands...

ICACLS C:\Windows\winsxs\msil_system.management.automation.resources_31bf3856ad364e35_6.1.7600.16385_en-us_90b3b3c187352de7  /T
ICACLS C:\Windows\winsxs\msil_system.management.automation.resources_31bf3856ad364e35_6.1.7601.17514_en-us_92e4c7898423b181 /T
  
.

post the results.


Here are some instructions to make life easier
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

 

[Cargo48]

Thanks for this - I've followed the instructions provided and here are the results from the elevated command prompt;

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ICACLS C:\Windows\winsxs\msil_system.management.automation.r
esources_31bf3856ad364e35_6.1.7600.16385_en-us_90b3b3c187352de7 /T
C:\Windows\winsxs\msil_system.management.automation.resources_31bf3856ad364e35_6
.1.7600.16385_en-us_90b3b3c187352de7 NT SERVICE\TrustedInstallerI)(OI)(CI)(F)

BUILTIN\AdministratorsI)(OI)(CI)(RX)

NT AUTHORITY\SYSTEMI)(OI)(CI)(RX)

BUILTIN\UsersI)(OI)(CI)(RX)

Successfully processed 1 files; Failed processing 0 files

C:\Windows\system32>ICACLS C:\Windows\winsxs\msil_system.management.automation.r
esources_31bf3856ad364e35_6.1.7601.17514_en-us_92e4c7898423b181 /T
C:\Windows\winsxs\msil_system.management.automation.resources_31bf3856ad364e35_6
.1.7601.17514_en-us_92e4c7898423b181 NT SERVICE\TrustedInstallerI)(OI)(CI)(F)

BUILTIN\AdministratorsI)(OI)(CI)(RX)

NT AUTHORITY\SYSTEMI)(OI)(CI)(RX)

BUILTIN\UsersI)(OI)(CI)(RX)

Successfully processed 1 files; Failed processing 0 files

C:\Windows\system32>





Thanks,
Cargo48

 

[NoelDP]

OK - that shows and confirms what CheckSUR is telling us, at least.
The question is why did the first attempt at a fix fail?
let's have a lookat what may have happened...
open an Elevated Command Prompt, and run the following commands...

DIR C:\c48aa
DIR C:\Windows\winsxs\c48aa


post the results.

 

[Cargo48]

Here you are!

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>DIR C:\c48aa
Volume in drive C is Packard Bell
Volume Serial Number is 0A60-FD31

Directory of C:\c48aa

27/06/2014 19:50 <DIR> .
27/06/2014 19:50 <DIR> ..
27/06/2014 19:50 <DIR> msil_system.management.automation.resources_
31bf3856ad364e35_6.1.7600.16385_en-us_90b3b3c187352de7
0 File(s) 0 bytes
3 Dir(s) 101,176,057,856 bytes free

C:\Windows\system32>DIR C:\Windows\winsxs\c48aa

 

[NoelDP]

That looks OK - even if it is missing the second set of results (hit the Enter key before copying, please, next time - it makes sure that all commands are properly executed.)

I'll post a new fix a bit later.

 

[NoelDP]

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



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



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

 

[Cargo48]

Been having some problems uploading this file but here it is after a short delay, thanks again!

 

[NoelDP]

Great - things worked this time!

POQ 126 ends.
2014-06-29 14:43:07, Info                  CSI    000002f8 [SR] Verify complete
2014-06-29 14:43:07, Info                  CSI    000002f9 [SR] Repairing 0 components
2014-06-29 14:43:07, Info                  CSI    000002fa [SR] Beginning Verify and Repair transaction
2014-06-29 14:43:07, Info                  CSI    000002fb Repair results created:

with any luck, WU should work properly now.
Do a Check for Updates first, and see what happens.

 

[Cargo48]

Wohoo! The update installed, thanks so much for your help!

 

[NoelDP]

Great! I love it when a plan comes together
Good luck.