Persistent Windows update.

I have downloaded and, supposedly, installed KB2742596 four or five times now.

A few seconds later, the yellow warning shield reappears in my task bar.

How can I stop this happening?

My operating system is XP SP3 plus all critical updates.

 

Have you tried the Microsoft Fixit for this problem?

http://support.microsoft.com/mats/windows_update/

 

I hadn't tried that fix - I wasn't aware of it, but I just ran it and the problem is till there.

The update is, apparently, on my computer waiting to be installed.

 

Yes, it was via Windows Update.

I downloaded it again from the address you gave.

I didn't think before of looking in Add or Remove Programs, but I did after this latest download/installation.

It tells me that it was installed on 09/01/2013, but the yellow shield and the update system still tell me otherwise rolleyes

 

Right click on update and select "Hide" and you won't see it again.

 

Where, exactly, is the word "update" to which you refer?

 

On the Microsoft Update page I am presented with a High Priority update for Windows XP Security Update for Microsoft .NET Framework 2.0 SP2 on Windows Server 2003 and Windows XP x86 (KB2742596)

Right clicking on it opens up a "normal" right click menu which has Open, Copy Shortcut, All Accelerators, Add to Favorites etc etc.

No sign of Hide.

 

How to "Hide" a windows update

1) Click the yellow sheild
2) Select the "Custom Install" radio button.
3) Click "Next"
A list of updates that are downloaded and ready to be installed appears4) UNcheck the checklbox next to the unwanted update.
The update expands in detail
5) Click "Close"
6) Click the "Don't notify me of these updates again" checkbox and click OK.


BEFORE you hide it, here are two solutions form other pages:

Run the .NET Framework Repair tool:)
[/U]http://www.microsoft.com/en-us/download/details.aspx?id=30135

Install the Windows Installer 4.5 (originally meant for Server 2008, caveat emptor):
http://www.microsoft.com/en-us/download/details.aspx?id=8483

Hiding an update is a second best choice to fixing.
These updates prevent security breaches. If this security breach commonly fails, it becomes a more tempting target of hackers

 

ADDENDUM:

The .NET repair utility failed for me and I had previously seen a reference to the manual standalone install for this update.

http://www.microsoft.com/en-us/download/details.aspx?id=36275

I did not mention it because these manual installers are always available and have never worked for me when Windows Update failed, but when al else fails, go ahead and do the thing you're sure won't work.

Waddya know.
It claimed to install successfully. A subsequent Windows Update attempt did not list it as needed and after a reboot windows update STILL did not ask for it.

Try the standalone. It works, this once.

 

Many thanks William,

The first link in your post of yesterday effected a cure.

I'm glad it did; to hide the offered update would be to effectively hide a problem in my system, which isn't at all satisfactory.

 

plodr...I have installed them all, because I have programs that require them all...or at least up to Framework 4.0.

Everything is really smooth, and, for XP, I think .NET will be the framework for program writers to build for in the future. I don't know much about it, but this was interesting to find for me:

at this link:

http://msdn.microsoft.com/en-us/library/dd460693.aspx

I know nothing about these subjects, but this was a nice peek inside the .NET framework to see why anybody would pay attention to it...

 

Yes plodr, I, too, subscribe to Windows Secrets, and have done since they swallowed up Fred Langa.

While much of its content is above me, it neverthless is quite useful to me.

I often think that Bradley's concern over Microsoft's balls-ups borders on paranoia. Although it can tax one's patience, Microsoft eventually sorts things out.

But then I'm a dilettante user. If my income and/or wellbeing depended on a computer I would perhaps pay more heed to her.

The home computer is the most versatile tool ever invented , but, as far as most users are concerned, I suggest that it can also be the most unreliable

 

Glad it worked, dmb.

Interesting stuff on .NET 4.
So dll library code that allows programmers to weave bits of multithreaded code into an older program that previous slogged along...

That's pretty powerful stuff.

I've looked at windowssecrets before but not religiously. The .NET update rundown sounds like good reading for insomniacs, but probably worth fighting the eyelids..

 

Thanks for the input plodr. That sounds like an intuitive approach to installing .NET updates. Don't download them unless you absolutely must.

I don't remember which programs require .NET, but I recall seeing it listed a number of times for programs I have installed (requires .NET 3.5 or .NET 4.0). MS Office uses it, and I have installed a Win 8 knock off freeware called Win 8 Transformation Pack 6.5 that uses it.