Windows 7 Update Failure

Interesting...
SFC only found this problem...

Code:

 Line 65526: 2014-09-21 21:44:39, Info                  CSI    000002b9 [SR] Repairing 1 components
 Line 65527: 2014-09-21 21:44:39, Info                  CSI    000002ba [SR] Beginning Verify and Repair transaction
 Line 65528: 2014-09-21 21:44:39, Info                  CSI    000002bb [SR] Cannot repair member file [l:32{16}]"DVDMaker.exe.mui" of Microsoft-Windows-OpticalMediaDisc-Wizard.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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 65529: 2014-09-21 21:44:39, Info                  CSI    000002bc [SR] Cannot repair member file [l:32{16}]"DVDMaker.exe.mui" of Microsoft-Windows-OpticalMediaDisc-Wizard.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), 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 65530: 2014-09-21 21:44:39, Info                  CSI    000002bd [SR] This component was referenced by [l:206{103}]"Microsoft-Windows-OpticalMediaDisc-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.OpticalMediaDisc"
 Line 65531: 2014-09-21 21:44:39, Info                  CSI    000002be [SR] Could not reproject corrupted file [ml:520{260},l:72{36}]"\??\C:\Program Files\DVD Maker\en-US"\[l:32{16}]"DVDMaker.exe.mui"; source file in store is also corrupted
 Line 65536: 2014-09-21 21:44:39, Info                  CSI    000002c0 [SR] Repair complete

but CheckSUR found two missing files...

Code:

Checking Component Store
(f) CSI Payload File Missing 0x00000000 DVDMaker.exe.mui amd64_microsoft-windows-o..sc-wizard.resources_31bf3856ad364e35_6.1.7600.16385_en-us_102a16b698e56faf 
(f) CSI Payload File Missing 0x00000000 bitsadmin.exe x86_microsoft-windows-bits-bitsadmin_31bf3856ad364e35_6.1.7600.16385_none_4ce7e7256dbfa16f

Strangely I can find none of the usual data associated with a CheckSUR scan in the CBS log

I'll post a fix for both files later, and we'll see what happens.

While I think of it...


Please open an Elevated (Administrator) Command Prompt window and use the following commands....

net start msiserver
sc qc msiserver
sc queryex msiserver
sc qprivs msiserver
sc qsidtype msiserver
sc sdshow msiserver
ICACLS C:\Windows\system32\msiexec.exe


Copy and paste the output to your reply

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.

That all looks normal.


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



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



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

The CBS log is a mass of this error-type

Code:

 Line 51845: 2014-09-21 14:26:22, Error                 CBS    Failed to shred identity: Microsoft-Windows-InternetExplorer-LanguagePack [HRESULT = 0x80070057 - E_INVALIDARG]

The SFC scan shows that it repaired one error, at least...

Code:

 Line 72854: 2014-09-23 10:59:20, Info                  CSI    000002b6 [SR] Repairing 1 components
 Line 72855: 2014-09-23 10:59:20, Info                  CSI    000002b7 [SR] Beginning Verify and Repair transaction
 Line 72856: 2014-09-23 10:59:20, Info                  CSI    000002b8 [SR] Repairing corrupted file [ml:520{260},l:72{36}]"\??\C:\Program Files\DVD Maker\en-US"\[l:32{16}]"DVDMaker.exe.mui" from store
 Line 72865: 2014-09-23 10:59:20, Info                  CSI    000002ba [SR] Repair complete

Please post the C:\Windows\windowsupdate.log file

The log shows the following two errors...

Code:

2014-09-26 15:27:54:078  760 1178 Agent WARNING: Failed to evaluate Installed rule, updateId = {818701AF-1182-45C2-BD1E-17068AD171D6}.104, hr = 80242013
 
 
 Line 12001: 2014-09-25 10:10:08:305  760 1804 Report REPORT EVENT: {727A4253-744E-4E94-A341-A80F8D5FDA65} 2014-09-25 10:09:49:707-0500 1 182 101 {CC0FD76B-48C7-43CD-98A0-59DB19879391} 202 80070643 AutomaticUpdates Failure Content Install Installation Failure: Windows failed to install the following update with error 0x80070643: Security Update for Microsoft .NET Framework 4.5 and 4.5.1 on Windows 7, Vista, Server 2008, Server 2008 R2 x64 (KB2894854).

643 errors in non-native .NET updates such as this are often best dealt with by completely removing the .NET installation and reinstalling it.
See the article here... .NET Framework Cleanup Tool User's Guide - Aaron Stebner&#39;s WebLog - Site Home - MSDN Blogs