Windows 7 Home Premium Update Failure

Your CheckSUR shows the following problems...

Code:

Unavailable repair files:
 servicing\packages\Package_for_KB2719177~31bf3856ad364e35~amd64~~9.4.1.0.mum
 servicing\packages\Package_for_KB2719177~31bf3856ad364e35~amd64~~9.4.1.0.cat

The CBS.log showing the following problem

Code:

 Line 99001: 2013-02-09 21:22:13, Info                  CSI    00000198 [SR] Beginning Verify and Repair transaction
 Line 99004: 2013-02-09 21:22:19, Info                  CSI    0000019a [SR] Cannot repair member file [l:24{12}]"wbemcons.dll" of Microsoft-Windows-WMI-Consumers, Version = 6.1.7600.16385, 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 99007: 2013-02-09 21:22:21, Info                  CSI    0000019c [SR] Cannot repair member file [l:24{12}]"wbemcons.dll" of Microsoft-Windows-WMI-Consumers, Version = 6.1.7600.16385, 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 99008: 2013-02-09 21:22:21, Info                  CSI    0000019d [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.WindowsFoundationDelivery"
 Line 99013: 2013-02-09 21:22:21, Info                  CSI    000001a0 [SR] Could not reproject corrupted file [ml:520{260},l:56{28}]"\??\C:\windows\System32\wbem"\[l:24{12}]"wbemcons.dll"; source file in store is also corrupted
 Line 99021: 2013-02-09 21:22:22, Info                  CSI    000001a2 [SR] Verify complete

I'll produce fix protocols for them a bit later.

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

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

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

....and for the second part....


I've uploaded a file - fcfab.zip - to my SkyDrive at Noel's SkyDrive
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 fcfab in the same place.
Open this folder - there should be one folders inside it ( Packages)

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

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

It's OK - the CheckSUR logs were in your CBS folder as expected :)
The copy present in the uploaded file looks as if it was taken before running the fix above - please upload the latest CheckSUR.log file (no need for the rest, yet)




The CBS log is showing a new batch of errors...

Code:

 Line 5189: 2013-02-10 16:39:03, Info                  CSI    00000330 [SR] Beginning Verify and Repair transaction
 Line 5192: 2013-02-10 16:39:03, Info                  CSI    00000332 [SR] Cannot repair member file [l:14{7}]"osk.exe" of Microsoft-Windows-osk, Version = 6.1.7600.16385, 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 5195: 2013-02-10 16:39:03, Info                  CSI    00000334 [SR] Cannot repair member file [l:20{10}]"vsswmi.dll" of Microsoft-Windows-ShadowCopyWMIProvider, Version = 6.1.7600.16385, 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 5198: 2013-02-10 16:39:03, Info                  CSI    00000336 [SR] Cannot repair member file [l:24{12}]"Storprop.dll" of Microsoft-Windows-Storprop, Version = 6.1.7600.16385, 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 5201: 2013-02-10 16:39:03, Info                  CSI    00000338 [SR] Cannot repair member file [l:24{12}]"wbemcons.dll" of Microsoft-Windows-WMI-Consumers, Version = 6.1.7600.16385, 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 5204: 2013-02-10 16:39:03, Info                  CSI    0000033a [SR] Cannot repair member file [l:24{12}]"wbemtest.exe" of Microsoft-Windows-WMI-Tools, Version = 6.1.7600.16385, 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 5207: 2013-02-10 16:39:03, Info                  CSI    0000033c [SR] Cannot repair member file [l:24{12}]"wbemcntl.dll" of Microsoft-Windows-WMI-Management-Snapins, Version = 6.1.7600.16385, 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 5210: 2013-02-10 16:39:03, Info                  CSI    0000033e [SR] Cannot repair member file [l:24{12}]"wbemdisp.dll" of Microsoft-Windows-WMI-Scripting, Version = 6.1.7600.16385, 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 5213: 2013-02-10 16:39:03, Info                  CSI    00000340 [SR] Cannot repair member file [l:18{9}]"WPDSp.dll" of Microsoft-Windows-WPD-WmdmApplicationCompatibility, Version = 6.1.7600.16385, 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
 Line 5217: 2013-02-10 16:39:03, Info                  CSI    00000342 [SR] Cannot repair member file [l:24{12}]"MFC90FRA.DLL" of Microsoft.VC90.MFCLOC, Version = 9.0.30729.4148, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll work on a new protocol for those and come back with itlater.

Not to disturb Noel, but it looks like your copy of Microsoft Office Enterprise 2007 is not validated.
Microsoft Office Enterprise 2007 - 103 Blocked VLK

I would uninstall that one and keep the legit Microsoft Office Home and Student 2007, as it says 100 Genuine.

I've almost given up commenting on Office Enterprise 2007 - I think there are more counterfeit installs than there ever were legitimate ones, and MS abandoned the OGA program a couple of years ago (replacements were costing too much I suspect!) as soon as Office 2010 was launched and changed the paradigm.
Yes, the install is counterfeit, but MS don't seem to care any more (I think they look at it as a loss-leader), and it doesn't affect the larger Windows issues.

Working on my Step-daughter's computer, over the weekend, because she couldn't get MS updates .... I found that her copy of Office was never validated. Once I did that, all updates were installed!

There's a world of difference between activation and validation :) - and lack of either doesn't necessarily imply non-genuine.