Solved KB2961149 won't install.

[Galane]

Unspecified error, it just won't install. I tried searching for that but Google only comes up with pages in Japanese. WTH? Why is Windows Update trying to install this if it's not for English/US? Yahoo didn't find any pages with an exact match of KB2961149

It's been how many years of Windows Update and Microsoft keeps having this same problem with updates that keep saying they need to be installed but failing, and it can't even tell why it fails.

 

[NoelDP]

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


... and what few details are available are linked to in the update listing in the History log - http://www.microsoft.com/en-us/download/details.aspx?id=42513 - as is the error code that it gave

 

[Galane]

I ran SURT. Appeared to do nothing but take a bunch of time to do it. SFC says everything is fine. So does every Fixit I've tried for Windows Update.

"WindowsUpdate_00000643" "WindowsUpdate_dt000"

The CBS folder zipped is 25.6 megabytes. Since this forum only accepts ZIP attachments up to 8 megabytes, I uploaded it here https://anonfiles.com/file/e0bf9e2482f9af71ce8e07f2940da10e

 

[NoelDP]

CheckSUR does a heck of a lot of work, even while it appears to do nothing
It actually found no errors in your case.
I can find no data from an SFC scan since 4th May - if you ran one, It would appear not to have started, let alone completed. On the other hand, I can also find no other significant errors in the CBS data from that date, either.
I finally found details of an SFC scan dated 3rd May.
As you say, it found nothing amiss.

The 643 error you got is often associated with major corruption - so it's not usual to nee no evidence of the corruption using these tools.
Have you been attempting system repairs using other tools than those provided by MS?

Please upload the C:\Windows\windowsUpdate.log file.

 

[Galane]

Here's that log file.

I'm thinking of trying an in-place "upgrade" to see if that will resolve this and two other issues. One is that despite every test and Microsoft Fixit, resetting, reinstalling etc of WMI finding absolutely nothing wrong with WMI, Autopatcher refuses to work due to some problem with WMI, but everything else using WMI works fine, and Autopatcher works on another system I have with the same Win 7 version. (Autopatcher is in my opinion one of the best utilities ever for Windows, especially when I have to work on a PC where the person only has dialup.)

The other issue just cropped up yesterday. Windows Explorer's icon vanished from the taskbar and I cannot re-pin it to the taskbar. The shortcut is in the proper folder but it remains stubbornly hidden. If I delete that shortcut then launch explorer and right click it in the taskbar, the only option I get is close window. Most any other program I get a varying range of menu options, most always including pin to taskbar.

Then there's the sudden onset of the audio service not starting soon enough to suit Windows so it disables audio output until I run services.msc and manually restart it - but that only happens part of the time.

Sounds like some weird sort of malware designed just to cause annoying little problems, but hides itself very well. I recall vividly the first time I encountered one of the first "stealth" malware nasties capable of protecting itself even in Safe Mode. Pulling the power cord instead of doing a normal shutdown then booting off a live Linux or Windows CD to find and delete its files was the cure for that one, but the #$#^# who need a good flogging soon figured out ways around that trick.

I've been working with computers since 1983 and haven't seen a Windows install accumulate problems as quickly as this particular one, especially not problems that resist being identified as problems and resisting correction and... oh "fun". My laptop (the "problem free" Win 7 system) just bluescreened and rebooted while sitting there doing absolutely nothing. No reason for that to have happened, it just *poof* did it. It doesn't even have the possible excuses of having Classic Shell installed or having not been installed onto an unformatted hard drive. Gahh! Almost enough to make me go back to XP, or 98SE.

 

[NoelDP]

There appear to be a number of other updates awaiting installation?
What happens if you Hide KB2961149 and attempt to install the others?
(the log doesn't give any details at all except for the 643 error message)

 

[Galane]

Hide it and nothing else shows up. I launched Autopatcher with a command to disable its use of WMI and it installed a few critical updates, and I selected several it says are to "resolve issues".

Unhide the problem update, install and... fail again. I'm going to uninstall Microsoft Visual Studio 2010 Tools for Office Runtime (x86) and see if this buggy update to it goes away.

That's assuming it can be uninstalled, the *uninstaller* says installation failed. Must be PC Mover at fault, copied it from XP and rammed it into Win 7 64 bit where it doesn't belong.

 

[NoelDP]

See if this kicks things into submission...



Open an Elevated Command Prompt
Run the following commands

NET STOP WUAUSERV
REN C:\WINDOWS\SoftwareDistribution SDOLD
NET START WUAUSERV

reboot
then wait 10 minutes, and open Windows Updates, and run a Check for Updates.

Install only the oldest update found - and reboot once installed
then go back to Windows updates and install the others.

 

[Galane]

I'm going to have to either wipe this install and start over or figure out what to manually delete from the Registry and the files for Microsoft Visual Studio 2010 Tools for Office Runtime (x86) then run CCleaner and NTREGOPT.

Thanks so much, PC Mover, for not defaulting to not copy this from a 32 to a 64 bit version.

 

[NoelDP]

As far as I know, there's no reason why the VS 2010 32-bit tools shouldn't run in a 64-bit machine - so long as the Office installation is also 32-bit!

 

[Galane]

I have Office 2003, which PC Mover moved over from XP. I could try a reinstall or repair on that.

 

[NoelDP]

Sounds like a plan - but I wouldn't hold out overmuch hope for it, as the repair functions in O2k3 were pretty basic as I remember (I stopped using it when the Beta for 2007 came out).

 

[Galane]

Tried to do a fresh install of the Visual Studio Tools package. Nope, fail. Is there a switch I can use with the install in a command prompt to force it to ignore/overwrite the existing install?

Full (too long to post) log here http://pastebin.com/sK3eaVjj

It ends with

[5/21/2014, 18:1:55]Final Result: Installation failed with error code: (0x80070643), "Fatal error during installation. " (Elapsed time: 0 00:01:15).

 

[Galane]

FixIt 50123 failed to FixIt.

Something I'm wondering is why all these Microsoft setup/install packages are creating their randomly named temporary folders on J: That's a Hitachi 1TB USB drive. No idea why there instead of C:

Also soooo 'nice' that none of those from Microsoft will delete those folders when they're finished.

 

[NoelDP]

Most MS installers automatically pick the drive with the greatest amount of free space to expand to before install, which makes sense to me - but yes, the cleanup function could work a lot better than it does!


Here's the actual detail that caused the error...

  [5/21/2014, 18:1:1]Wait for Item (vstor40_x64.exe) to be available 
[5/21/2014, 18:1:1]vstor40_x64.exe is now available to install
 [5/21/2014, 18:1:1]Creating new Performer for Exe item
 [5/21/2014, 18:1:1]Created new ExePerformer for Exe item
 [5/21/2014, 18:1:1] Action: Performing Action on Exe at j:\1f762d6ae75720a0c125999c7391aa16\vstor40\vstor40_x64.exe
 [5/21/2014, 18:1:1]Launching CreateProcess with command line = vstor40_x64.exe /q
 [5/21/2014, 18:1:54][B]j:\1f762d6ae75720a0c125999c7391aa16\vstor40\vstor40_x64.exe - Exe installer does not provide a log file name[/B]
 [5/21/2014, 18:1:54][B]Exe (j:\1f762d6ae75720a0c125999c7391aa16\vstor40\vstor40_x64.exe) failed with 0x80070643 - Fatal error during installation.[/B] .
 [5/21/2014, 18:1:54]PerformOperation on exe returned exit code 1603 (translates to HRESULT = 0x80070643)

This looks as if it may be a problem with the installer - I'll have to research it and see what I can find.

 

[Galane]

I got it fixed, and unlike soooo many annoying people who just post "Fixed it!" I'm going to say HOW.

I deleted the c:\Program Files (x86)\Common Files\microsoft shared\VSTO folder

Next I installed the latest CCleaner (make sure to do a custom install and NOT install whatever other junk is packed with it, or find the slim install or portable version) and ran its Registry cleaner as many times as it took until it found no more issues. VSTO is all over the Registry. That even removed the entry in Programs and Features.

Third, I ran NTREGOPT as an administrator (6% reduction on this system, I've seen reductions up to 25% in a few cases) and rebooted.

Still got the prompt to install the update. Instead of trying that I downloaded the latest Microsoft Visual Studio 2010 Tools for Office Runtime and it installed without any complaints.

Still got the update prompt so I clicked to install and in a couple of seconds it came back that it's not needed.

Oh, hey. Extra benefit of fixing this. Whatever undetectable issue there was with WMI (every test, check, purge, reset etc of WMI showed nothing wrong) that was preventing Autopatcher from working, it's not there now.