Solved Wrap up to the SURT suggestion (and IE11)

[motorhomer17]

taking the two issues people have come back to me with

SURT

The SURT has not fixed the problem; the same 4 updates fail as before i.e. :
- Definition Update for Microsoft Office 2010 (KB982726) 32-Bit Edition,
- Security Update for Microsoft Outlook 2010 (KB2837597) 32-Bit Edition
- Update for Microsoft Office 2010 (KB2589352) 32-Bit Edition
- Update for Microsoft Office 2010 (KB2597087) 32-Bit Edition

Log files don't mean a lot to me. But here goes for anyone who can interpret. Attached are the simple log files in plain and CBS zips after the SURT run - before and after failed software update

IE11 and YouTube: Someone asked for a better description of the problem. Best done with an example: If I open YouTube and attempt to type a search string e.g. Joe Bloggs, it locks up with a YouTube failing to respond pop-up at the bottom. On the other hand, if I type a search string into Google e.g. Joe Bloggs on YouTube, then I can click any of the links and YouTube runs perfectly, and more to the point, will accept any new search string.

In the mean time, I'll go look for updates after next Patch Tues/Wed so I can shut my machines down sensibly

 

[NoelDP]

SURT found nothing wrong - and the CBS logs contain no useful data.

Please follow the Windows Update Posting Instructions and post the requested data

 

[motorhomer17]

Sorted by the latest suggestions

Hi guys
Thanks for the latest suggestion. The scannow found and fixed the problem.

After the scannow I got clean (i.e. very few lines with the word "failure") log file extensions. I did repeat the SURT and scannow in order; nothing new appeared to be found with very few extra lines to the logfile.

The four troublesome downloads appear to have installed properly

I ought to say - very nice clear instructions in all the SevenForums "how to" guides - thanks again - they took me step by step through stuff well above my pay-grade. Now to go and do the same on the laptop

Attached are the command prompt script and the logfile

 

[NoelDP]

Great!
Here's the problem child...

2013-11-18 12:59:09, Info                  CSI    00000306 [SR] Repairing 1 components
2013-11-18 12:59:09, Info                  CSI    00000307 [SR] Beginning Verify and Repair transaction
2013-11-18 12:59:09, Info                  CSI    00000308 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:22{11}]"dbghelp.dll" from store
2013-11-18 12:59:09, Info                  CSI    00000309 Repair results created:
POQ 130 starts:
     0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\f558b6f85de4ce017f390000ec14ac11._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
    1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\f558b6f85de4ce0180390000ec14ac11.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
    2: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\b61bbbf85de4ce0181390000ec14ac11.$$_syswow64_21ffbdd2a2dd92e0.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_syswow64_21ffbdd2a2dd92e0.cdf-ms"
    3: Hard Link File: Source = [l:240{120}]"\SystemRoot\WinSxS\x86_microsoft-windows-imageanalysis_31bf3856ad364e35_6.1.7601.17514_none_4a6381a588654ba6\dbghelp.dll", Destination = [l:70{35}]"\??\C:\Windows\SysWOW64\dbghelp.dll"
 POQ 130 ends.

Good luck!

 

[motorhomer17]

....and the Laptop has responded to the same treatment. I've not attached the logfile but can do so.

The only thing that has gone wrong / oddly of late was the installation of Kaspersky KAV 2014. That install was problematic on both machines. Was that the cause? or the first symptom of this problem? I guess I'll never know.

 

[NoelDP]

I suspect it may be a bit of both. I have heard of problems associated with Kaspersky, but they are thankfully rare.
Has any other AV EVER been installed in this machine?

 

[motorhomer17]

No AV other than Kaspersky on these machines. Updates previous years were snag-free

I've had a closer look at the dates and the Windows Update History. Kaspersky licence renewal (and uplift to KAV 2014) was 35 days ago, since which time the Windows Update History showed no consistent problems until the 14th Nov i.e. this batch of problems. The particular update that first failed was:-
Update for Microsoft Office 2010 (KB2597087) 32-Bit Edition Installation date: ‎14/‎11/‎2013 13:01 Installation status: Failed. After that, things progressively went downhill with more and more failures mixed with fewer and fewer successful updates; until the recent fixes of course. On reflection, I think that KAV 2014 was probably a red herring

hope that helps

 

[NoelDP]

I can't see any particular reason why that update should either cause or be affected by the file problem - but Windows is fairly inscrutable that way!

What matters is that it's fixed now.

Good luck.