Windows Update Failure (error 80072EE2)

bengershon · 02 Jun 2014

I have been trying to get Windows Update to work for the past few days, with no luck. It seems to have started to go wrong after a series of updates were installed on 21st May.

I am attaching part of the WindowsUpdate.log file, which includes the last successful update and the first unsuccessful attempt.

I have tried absolutely everything that has been suggested on the net. MrFixit, System Update Readiness tool, deleting the SoftwareDistribution files, winsock reset, clearing DNS cache, virus scan, disk check, SFC scan, and really everything I could find. I also tried uninstalling the Windows (but not Office) updates which were installed on 15th May. Loads and loads of reboots. Nothing seems to work! I now note that another Windows 7 on the same internal network, which is only rarely connected to the external internet, seems to have suffered a similar fate, but a Windows 8 machine is quite fine.

NoelDP · 02 Jun 2014

Your CheckSUR log is clear - but your SFC scan shows the following problems.

Code:

 Line 14540: 2014-05-29 21:25:01, Info                  CSI    000003dd [SR] Repairing 5 components
 Line 14541: 2014-05-29 21:25:01, Info                  CSI    000003de [SR] Beginning Verify and Repair transaction
 Line 14544: 2014-05-29 21:25:01, Info                  CSI    000003e0 [SR] Cannot repair member file [l:36{18}]"powershell_ise.exe" of Microsoft-Windows-GPowerShell-Exe, 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 14547: 2014-05-29 21:25:01, Info                  CSI    000003e2 [SR] Cannot repair member file [l:50{25}]"TS_UnusedDesktopIcons.ps1" of Microsoft-Windows-MaintenanceDiagnostic, 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 14550: 2014-05-29 21:25:01, Info                  CSI    000003e4 [SR] Cannot repair member file [l:44{22}]"TS_BrokenShortcuts.ps1" of Microsoft-Windows-MaintenanceDiagnostic, 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 14553: 2014-05-29 21:25:01, Info                  CSI    000003e6 [SR] Cannot repair member file [l:30{15}]"DiagPackage.dll" of Microsoft-Windows-NetworkDiagnostics-Package, Version = 6.1.7601.17514, 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 14556: 2014-05-29 21:25:01, Info                  CSI    000003e8 [SR] Cannot repair member file [l:38{19}]"Windows Balloon.wav" of Microsoft-Windows-Shell-SoundThemes-Garden, 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 14559: 2014-05-29 21:25:02, Info                  CSI    000003ea [SR] Cannot repair member file [l:38{19}]"NlsLexicons004a.dll" of Microsoft-Windows-NaturalLanguage6, Version = 6.1.7601.17514, 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

I'll post a fix protocol when I can get to it.

bengershon · 02 Jun 2014

Thanks. I did notice those, but none seemd significant in any way.

BUT ...

Literally minutes ago, after about 4 days of trying to fix this problem, and without doing anything except checking (on another computer) if anyone had replied to this thread, I suddenly noticed that I had 6 updates available! They all installed OK, and Windows Update now allows me to check for updates again.

I really have no idea how it happened. I did make some changes to the network adapter settings, but I did that AFTER the updates had been flagged! The only thing I did (maybe playfully) was to play with the Windows Update settings: I set it to 'Never check for updates' and then altered that back to 'download but let me decide ...'. Could that have cleared something which may have got 'stuck'?

NoelDP · 02 Jun 2014

The 80072ee2 error is typically caused by connection errors rather than anything else - so I'm not surprised at all by that.

I'm working on your fix protocol now

NoelDP · 02 Jun 2014

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

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

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

bengershon · 02 Jun 2014

Running sfc now. In the meantime, each reboot seems to lose my IPv4 settings, which makes the network inaccessible until I reset the settings. I have no idea what is now causing that to go wrong ... (wrong forum anyway!). I shall report when I get the results of the sfc scan

bengershon · 02 Jun 2014

I also noticed the TS_UnusedIcons and TS_BrokenShortcuts listed.

They are DELIBERATE alterations! Please don't tell me that the fix you gave me has 'zapped' them! How can I get them back now? From my backups? Sorry about no noticing that earlier and telling you.

Anyway, the scan just finished, so here is the log file:

NoelDP · 02 Jun 2014

Why on earth would you want to alter those files?
Yes, you'd have to restore them from backup.

There's still one faulty file -

Code:

 Line 32452: 2014-06-03 01:33:09, Info                  CSI    000003bf [SR] Beginning Verify and Repair transaction
 Line 32455: 2014-06-03 01:33:09, Info                  CSI    000003c1 [SR] Cannot repair member file [l:30{15}]"DiagPackage.dll" of Microsoft-Windows-NetworkDiagnostics-Package, Version = 6.1.7601.17514, 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 somehow missed that one earlier

Back in a minute or so with the repair for that one.

NoelDP · 02 Jun 2014

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

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

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

bengershon · 02 Jun 2014

NoelDP said:

Why on earth would you want to alter those files?
Yes, you'd have to restore them from backup.

To prevent Windows from removing icons it thinks I no longer want from the desktop! I found the suggestion on a forum ages ago and it is a real life saver. My desktop is very organised, but much of the software accessible from the desktop is used very infrequently, so Windows quietly deletes the shortcuts. Thanks for the new fix. I will get back to you after I run it (but may not be until Thusrsday though).