Windows Updates Nightmare

Started by Simon, May 17, 2012, 23:20:11

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Simon

I'm getting plagued by the same three Windows Updates, that keep wanting to install over and over again, all for .NET Framework 2.0 SP2.  I've tried to uninstall .NET Framework 2.0, but the bloody think won't let me because it says something else is dependant on it, but ever so helpfully, doesn't say what.  I've searched on Google, and the only solutions seem to be to manually install the updates, but I've done that, and they still keep popping up.  Has anyone else had this issue?
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

psp83

Quote from: Simon on May 17, 2012, 23:20:11
I'm getting plagued by the same three Windows Updates, that keep wanting to install over and over again, all for .NET Framework 2.0 SP2.  I've tried to uninstall .NET Framework 2.0, but the bloody think won't let me because it says something else is dependant on it, but ever so helpfully, doesn't say what.  I've searched on Google, and the only solutions seem to be to manually install the updates, but I've done that, and they still keep popping up.  Has anyone else had this issue?

What OS?

If its Windows 7 then you can right click the update and then click hide update.

Simon

Sorry, it's XP, and I can hide the updates, but they're not listed in Add / Remove Programs, so I'm not convinced they're installed.  I've disabled my AV and tried to install, but that makes no difference either. 
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

You can hide updates in XP too, launch MS Update, then, when they're offered, select "don't show me".
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.


Simon

Thanks Paul, I'll try that later. 

Rik, I don't know if that does, but I don't want to hide all updates, just these ones that keep reappearing.
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Gary

Damned, if you do damned if you don't

Simon

Thanks Gary, will try that as well.
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Technical Ben

The only thing that helped me fix a corrupt XP .net instillation was a whole reformat/install. :(
Hope it's just an update stuck, and not a corrupted install.
I use to have a signature, then it all changed to chip and pin.

Rik

Quote from: Simon on May 18, 2012, 07:09:31
Rik, I don't know if that does, but I don't want to hide all updates, just these ones that keep reappearing.

It's done on a case by case basis.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pctech

Unfortunately a lot of stuff uses .net these days so its hard to track it down specifically.

Do you have office installed Simon and if so what version?


Simon

Quote from: Rik on May 18, 2012, 09:35:42It's done on a case by case basis.

:thumb:

Quote from: pctech on May 18, 2012, 10:00:38Do you have office installed Simon and if so what version?

Yes, 2003.

Quote from: Technical Ben on May 18, 2012, 09:30:08The only thing that helped me fix a corrupt XP .net instillation was a whole reformat/install. :(
Hope it's just an update stuck, and not a corrupted install.

:bawl:

I hope it's just a dodgy update.  The problem seems quite widespread.
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

JB

I do a disk image of drive c: just before installing updates. Unless they are especially important I usually wait about four weeks, then do an image and then allow the updates to install.

I've been caught with problems after .Net install/upgrades before which have required a complete reinstall. Won't be caught again.
JB

'Keyboard not detected ~ Press F1 to continue'

Simon

This will be the first time I've had a problem with updates.  Guess I may have been lucky, but if they are security patches, I'd rather have them than not have them.
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

You'll probably find they start working magically in a few days.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pctech

Dependency Walker should tell you http://www.dependencywalker.com/ but you will need to scan your apps one by one.




Simon

As Rik suggests, I may just leave it a few days and see if the magical fixit fairy appears.
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Simon

Thanks for all the suggestions.  In the end, I found a Microsoft Fixit tool on the Microsoft website and that appears to have solved the problem, for now...
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Ah, the Fixit Fairy visited... ;D
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Simon

Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Technical Ben

Quote from: Simon on May 19, 2012, 18:31:01
Thanks for all the suggestions.  In the end, I found a Microsoft Fixit tool on the Microsoft website and that appears to have solved the problem, for now...
:thumb:
Great. That's the one that failed me on my corrupt .net v3.5 install (Antecedently closed the laptop case = it turned off halfway during windows update). :(
I use to have a signature, then it all changed to chip and pin.

Simon

Actually, it didn't work.  :mad:  The bloody things appeared again this evening.  I've just ticked to ignore then now.
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

JB

Quote from: Simon on May 19, 2012, 23:32:41
Actually, it didn't work.  :mad:  The bloody things appeared again this evening.  I've just ticked to ignore then now.

Simon, what is the KB number of the upgrade that didn't work?
JB

'Keyboard not detected ~ Press F1 to continue'

Simon

There are four that keep wanting to re-apply, JB:

KB2604092
KB2518864
KB2572073
KB2633880

All relate to variations of .NET Framework. 
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

JB

Thanks Simon,

I only have XP on a Netbook now but I will be running updates today or tomorrow. I'll report back if I have an issue.
JB

'Keyboard not detected ~ Press F1 to continue'