KB2656351 (dotnet framework security update) Killing Outlook 2010?

[allend66]

this update has crippled my Outlook (Pro 2010 x86) twice, but it's an important update.. Had to system restore as I'd installed afew updates and patches at the same time.

Has anyone else had problems with it?
What if anything can I do, except not install it?

Regards
D

 

[clunkfish]

I don't think it's the update - I have installed it and am using Outlook (as part of Office Professional Plus 2010, 32 bit) without problems.

Have you changed any other aspects of your machine's configuration: anti-virus, firewall, ISP....?

 

[Corazon]

I had a minor problem with this specific update - which wasn't the first time, as it happened with another .NET 4 security update a few months ago.

In both cases, they installed successfully, only for Windows Update trying to spring the same update on me again after a reboot. It wanted to install over and over again despite already having successfully done so, so I had to hide the update to stop it from reappearing.

And these weird things people describe only seem to happen with Windows updates for .NET 4, no other updates - Microsoft is doing something screwy here, me doth think.

However, installing the update hasn't broken any other functionality for me so far.

 

[allend66]

Hmmm.. It fefinately was this update, on the second attempt I installed each one of the 7 pending updates separately and rebboted after each, then tried to launch Outlook. It hung on this update and worked after system restore, so I've hidden it as bad news to be avoided.

No, no other system changes...

Thanks for the replies, and happy new year to all.
D

 

[niemiro]

Hello!


Two causes for a repeatedly offered successful update. Either the update is bad, and Microsoft will re-release it within a week or so (it was a very rushed update, I can tell you that now), and you should notice the file size change and the update will suddenly install, or you have an inconsistent transactional log file. The latter is easily fixed.

• Open an Elevated Command Prompt: Elevated Command Prompt
• Type fsutil resource setautoreset true %systemdrive%\ and press enter.

Restart your computer, install the update again, and tell me whether it is re-offered again.

You can see more details at my temporary tutorial here: Windows Update - Fix a Repeatedly Offered Update

I shall reply back to you if and when this update is re-released.

Richard

 

[allend66]

Niemiro - thanks, but to clarify, my problem isn't being repeatedly offered an update, even after installing it, it's that the update cabbaged my Outlook 2010. System restoring to before this update solved it, and it was the only difference to cause problems.

I've since right clicked the offending update in WinUpdate to hide it and it hasn't prompted me to install it again.

Thanks for the input though!
I'll wait to see if the update is rereleased and make a decision then.

Regards
D

 

[niemiro]

Niemiro - thanks, but to clarify, my problem isn't being repeatedly offered an update, even after installing it, it's that the update cabbaged my Outlook 2010. System restoring to before this update solved it, and it was the only difference to cause problems.

I've since right clicked the offending update in WinUpdate to hide it and it hasn't prompted me to install it again.

Thanks for the input though!
I'll wait to see if the update is rereleased and make a decision then.

Regards
D

Hello again!

Sorry about that. I read your thread too quickly, noticed this:

In both cases, they installed successfully, only for Windows Update trying to spring the same update on me again after a reboot. It wanted to install over and over again despite already having successfully done so, so I had to hide the update to stop it from reappearing.

and jumped to conclusions.

My appologies.

Richard

 

[allend66]

But you're quoting Corazon, not me!

No worries, glad for the imput!

 

[niemiro]

But you're quoting Corazon, not me!

No worries, glad for the imput!

facepalm. What else can I say!?