Problem with Windows update

I have done all the usual updates, but everytime I go on to the update site it keeps stating that the same .NET files need updating.

I have now updated these files several times, and they install as normal

All the other updates show as completed.

I suspect that something akin to a LOG file is showing incorrect information.

Any way of correcting this slight problem?

Download CCLeaner lite from :

http://www.piriform.com/ccleaner/builds

Run the cleaner tool, and the registry cleaner. If that doesn't work, uninstall .NET (not sure if you have 1.0 or 2.0 3.5 or 4.0, but you can any or all). The tools area of CCLeaner will show the .NET framework items to uninstall. Then run the cleaner, registry cleaner again, reboot, then run windows update.

I appear to have all of the versions, perhaps that is the problem.

Not sure. If Microsoft wanted one to supercede another they would do it. Start with 4.0 and see how things go. Then 3.5 etc.

Will give it a go, and report back.

What is all this .NET stuff for ?
I have not installed any of the huge updates, can't see it makes any difference for regular
usage.
Regards,
Martin

.NET is a programming framework. If a program requires .NET it should install it.

OP - I've had this sort of problem in the past with some .NET updates. Sometimes the easiest thing is just to tell Update not to offer them in future.

Forgot to mention it is Win XP,

I had .NET 2, 3, 3.5, AND 4 installed plus various service packs.

I deleted everything but 4

Win update then downloaded all previous versions, but would not install them.

Update site is still saying they are needed???

If I take the direct route, I can find .net 4 to download.

On the download page for vers. 3.5 it states that there is a newer version .NET4

I am totally confused.

.NET Framework cleanup tool

http://blogs.msdn.com/b/astebner/archive/2008/08/28/...

For what it is worth, and as I understand it...

.NET 1.1 is an independent framework with no connection to 2.0/3.0/3.5.

You cannot uninstall 2.0 or 3.0 and keep 3.5 as all are one framework. 3.0 and 3.5 are not full frameworks. They are extensions to 2.0.

.NET 4.0 is an independent full framework with no connection to 2.0/3.0/3.5.

If you Download .NET Framework 3.5 Service Pack 1 (Full Package) it will install .NET 2.0 SP2 and 3.0 SP2 as prerequisite.

So it may be the order in which you installed earlier versions is causing the problem?

How about trying to install a full 3.5 SP1 and full 4.0?

You could also try a Repair. (Control Panel / Add Remove / Repair)

I have now "cleaned" all of the .net files using the .NET CLEANUP TOOL

see:http://forums.thinkbroadband.com/windows/t/3970217-re-problem-with-windows-update.html

I now will start again, thanks for your info.

In reply to a post by Brunel:

I deleted everything but 4

Ahh, well I said start with 4 and work back. The logic being that in theory any updates coming in would be for the most recently released version. It's not watertight logic, but the odds are favourable.

The .NET versions, as said elsewhere are not superceding each other in the typical sense. For some reason they are there independently. That's why I figured the newest version might the one to start with.

I used the cleaner, as mentioned.

Then installed 3.5 SP1 which installed 3, 3.5 etc.

The WIN update advised .NET4 which I did.

Now update still wants 3.5 etc.

I give up...!!!

Do you get any error messages or codes?

In reply to a post by Anonymous:

What is all this .NET stuff for ?

It's a framework/platform for running Windows applications. It sits on top of Win32 and was designed to be more secure and to be portable. It's basically an attempt to define 'The platform of the future' by Microsoft.

It's not a bad attempt, actually. Performance can be a bit iffy and personally I prefer RAII over garbage collection but it is easier to write for. For once in their existence Microsoft actually produced an orthogonal and logically consistent API. They had to poach a developer from Borland to do it, though

I think MS's problem is that they employ so many developers. It means they lack incentive to share and re-use code. As a result you end up with a hodge-podge of APIs, several different ways of doing the same thing and bizarre kludges. Borland always had a smaller team of developers so they were used to sharing and leveraging each other's code. They couldn't afford to invent things more than once and to be consistent so that developers could move between projects easily.

Sadly Borland basically failed and MS survived. That probably tells you all you need to know about software development

Edited by Andrue (Mon 21-Feb-11 15:00:58)