Solved Windows 7 x64 Update Failures (KB2977629,KB2977728)

[HopWorks]

I have been working two Windows 7 x64 update failures. After jumping through a hoop or two turning off the avast service, I have tried to update these packages after a clean boot and still failed. I have run the SRUT and SFC a few times each (interlaced, one after the other) before zipping up the CBS you see here.
Here are the two items and their error code information. Attached is the CBS.zip file after removing all 5 cabs to fit under 8 mb.

Cumulative Security Update for Internet Explorer 11 for Windows 7 for x64-based Systems (KB2977629)
Installation date: ?10/?6/?2014 8:03 AM
Installation status: Failed
Error details: Code C004F01F
Update type: Important

Update for Windows 7 for x64-based Systems (KB2977728)
Installation date: ?10/?6/?2014 7:56 AM
Installation status: Failed
Error details: Code 800B0100
Update type: Recommended

Thank you for your time and assistance. Hopefully I may learn of the cause and the steps you will reply with, so I may deal with this issue on my own next time.

 

[NoelDP]

Here's the error-list from the CheckSUR log...

Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_7.1.7601.18519_none_e092b1245983d329.manifest
 winsxs\manifests\x86_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_7.1.7601.18519_none_847415a0a12661f3.manifest
 winsxs\manifests\amd64_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_7.1.7601.22730_none_e0fdad6372b9c3ed.manifest
 winsxs\manifests\x86_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_7.1.7601.22730_none_84df11dfba5c52b7.manifest
 servicing\packages\Package_1_for_KB2977728~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2977728~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2977728~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2977728~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2977728_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2977728_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2977728~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2977728~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2977728~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2977728~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2977728~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2977728~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2977728_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2977728_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2977728~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2977728~31bf3856ad364e35~amd64~~6.1.1.0.cat

I'll post a fix protocol for it later.

 

[NoelDP]

I've uploaded a file - hwkaa.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 hwkaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

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

 

[HopWorks]

After looking at the log files, your fix seemed to do the trick. I am upping them to be sure. I will post more if I am still having issues. Thank you so much for your time and efforts! I will analyze what you posted against what my previous logs were to figure out how to do this myself next time.

Thanks again!!!

 

[HopWorks]

The same two updates are still appearing via Windows Update. I will try to update those again and see what happens. I will post another CheckSUR log set if issues persist. Thanks again for your assistance!!

 

[HopWorks]

UPDATE: I rebooted, then went to Windows Update. Still 2 updates to do so I tried to install them. After it was finished, the dialog window said 2 succeeded but had to reboot. When I did, the updates failed and reverted changes. Some improvement though. KB2977728 has updated successfully. KB2977629 is still failed status. Running CheckSUR again ... done, attached.

 

[NoelDP]

The CheckSUR log is clear - let's have a new SFC log ...



SFC -System File Checker - Instructions
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
SFC /SCANNOW
and hit the Enter key
Wait for the scan to finish - make a note of any error messages - and then reboot.

Upload the C:\Windows\Logs\CBS\CBS.log file (compressed, please!) to your reply

 

[HopWorks]

The sfc ran with errors again. Here is the CBS.log file, compressed.

 

[NoelDP]

Here's the errors...

 Line 3405: 2014-10-07 13:30:21, Info                  CSI    0000034a [SR] Repairing 2 components
 Line 3406: 2014-10-07 13:30:21, Info                  CSI    0000034b [SR] Beginning Verify and Repair transaction
 Line 3409: 2014-10-07 13:30:21, Info                  CSI    0000034d [SR] Cannot repair member file [l:50{25}]"msmpeg2vdec-ppdlic.xrm-ms" of Microsoft-Windows-MSMPEG2VDEC, Version = 7.1.7601.18519, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 3412: 2014-10-07 13:30:21, Info                  CSI    0000034f [SR] Cannot repair member file [l:30{15}]"msmpeg2vdec.dll" of Microsoft-Windows-MSMPEG2VDEC, Version = 7.1.7601.18519, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix protocol for these when I can - it may not be until tomorrow evening.

 

[HopWorks]

I'll post a fix protocol for these when I can - it may not be until tomorrow evening.

No hurry sir. I might just be able to fix myself. Actually, I will wait so I do not damage anything further. Thanks again! I certainly appreciate it!

 

[NoelDP]

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



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



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

 

[HopWorks]

OK NoelDP, followed your instructions to the letter. Here is the new CBS.log (compressed and attached). Thank you!

EDIT: I was going to run Windows Update again but decided to wait until you give the 'all clear'.

 

[NoelDP]

The files don't seem to have changed - I double-checked the uploaded files nad they are OK, so it must be something wrong at your end.

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

DIR C:\hwkab
DIR C:\Windows\Winsxs\hwkab

post the results - it may tell us what went wrong.


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.

 

[HopWorks]

OK, I think it is just a path issue. I do not have "hwkab" as a sub-folder in "C:\Windows\Winsys\". Instead, I have the folder that is inside "C:\hwkab", as in "amd64_microsoft-windows...". I followed the instructions with the exception that I had to use "F" as a drive letter, not sure why the drive letter was not "C", and I believe I was in "C:\hwkab" in error when I ran the XCOPY command. So to confirm... the whole "hwkab" folder needs to be in "C:\Windows\Winsys\"?

EDIT: AHA! Never get up out of a sound sleep and do this stuff! I see my error. WINSXS not WINSYS

C:\>dir \hwkab
 Volume in drive C has no label.
 Volume Serial Number is 9CAC-80DA

 Directory of C:\hwkab

10/08/2014  01:32 AM    <DIR>          .
10/08/2014  01:32 AM    <DIR>          ..
10/08/2014  01:32 AM    <DIR>          amd64_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_7.1.7601.18519_none_e092b1245983d329
               0 File(s)              0 bytes
               3 Dir(s)   7,158,505,472 bytes free

C:\>dir \windows\winsys
 Volume in drive C has no label.
 Volume Serial Number is 9CAC-80DA

 Directory of C:\windows\winsys

10/08/2014  02:42 AM    <DIR>          .
10/08/2014  02:42 AM    <DIR>          ..
10/08/2014  02:42 AM    <DIR>          amd64_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_7.1.7601.18519_none_e092b1245983d329
               0 File(s)              0 bytes
               3 Dir(s)   7,158,632,448 bytes free

 

[HopWorks]

Corrected my path mistake and stayed in the root of "F" (which is "C" actually) when I ran the xcopy this time. I still do not see a hwkab sub folder in c:\windows\winsxs. I ran the sfc and attached the compressed CBS.log. Also attached and hopefully not useless is my dir of c:\windows\winsxs, the xcopy output, and the sfc CLI output, zipped into additional.zip.

 

[NoelDP]

Here's the detail from the latest CBS.log

2014-10-08 08:49:39, Info                  CSI    00000338 [SR] Repairing 1 components
2014-10-08 08:49:39, Info                  CSI    00000339 [SR] Beginning Verify and Repair transaction
2014-10-08 08:49:39, Info                  CSI    0000033a Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_7.1.7601.18519_none_847415a0a12661f3\msmpeg2vdec-ppdlic.xrm-ms do not match actual file [l:50{25}]"msmpeg2vdec-ppdlic.xrm-ms" :
  Found: {l:32 b:bXfLXfDEjWkxnsVaj78tV3ml+9Q11J387uD3RVSvdwo=} Expected: {l:32 b:a8+4iZ0CPJmdHap91ExuNjOn21I8u19eTeMcQDCQ7Qs=}
2014-10-08 08:49:39, Info                  CSI    0000033b [SR] Cannot repair member file [l:50{25}]"msmpeg2vdec-ppdlic.xrm-ms" of Microsoft-Windows-MSMPEG2VDEC, Version = 7.1.7601.18519, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-08 08:49:39, Info                  CSI    0000033c Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-msmpeg2vdec_31bf3856ad364e35_7.1.7601.18519_none_847415a0a12661f3\msmpeg2vdec.dll do not match actual file [l:30{15}]"msmpeg2vdec.dll" :
  Found: {l:32 b:DID6cPpPctQqJvz5IunWJBRZar5VS31g8wFC34mtgD0=} Expected: {l:32 b:KXhKttK3DbvYmokzQfMGPyv03NtqdVP4vYZvk45R83o=}

Both files are still affected - but now the components number (the first line above) reads the correct '1' rather than the earlier '2'

Ahah!! - I see what I was missing before!

Your corrections obviously did work at some point - but I'd missed the fact that both the x86 and amd64 variants of the files were affected - which would also explain the drop in affected component numbers.


I'll post a new fix for these one in a few minutes.

 

[NoelDP]

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



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



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

 

[HopWorks]

This is encouraging! CBS.log is attached. Looks like this last one did the trick. Hopefully you see the same thing.

C:\Windows>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

 

[NoelDP]

Looks good to me, too!

POQ 138 ends.
2014-10-08 10:49:52, Info                  CSI    00000325 [SR] Verify complete
2014-10-08 10:49:52, Info                  CSI    00000326 [SR] Repairing 0 components
2014-10-08 10:49:52, Info                  CSI    00000327 [SR] Beginning Verify and Repair transaction
2014-10-08 10:49:52, Info                  CSI    00000328 Repair results created:
POQ 139 starts:
 
POQ 139 ends.
2014-10-08 10:49:52, Info                  CSI    00000329 [SR] Repair complete

With luck, Windows Update will now work properly - do a new Check for updates, and attempt to install ONLY the oldest update found.

If it fails, post the error code, and the KB number involved.
Also post the C:\Windows\windowsupdate.log file.

Good luck!

 

[HopWorks]

Will do NoelDP. Thank you so much sir for the assist, and I will try to learn all that I can from re-reading this thread and the saved log files. I am sure it will happen again and want to be able to handle it.

I almost forgot to ask... what causes this issue? Is there something I could have done to avoid it?

EDIT: The updates worked fine, no issues. Awesome. Thanks again!