Originally Posted by nigelb
Originally Posted by John59Wayne
The problem with the Windows Automatic Downloads offering three outdated security patches has now been rectified. Workarounds such as the three of you have mentioned are no longer necessary.
Originally Posted by micksoutham
EDIT: As is often the case, when something like this hits the Press, action is taken to rectify the fault very quickly. More info here: Windows XP update loop
Last edited by Xircal; 2012-05-24 at 03:07.
Reason: Amended link to a more detailed explanation
I found the following to work: Go to http://support.microsoft.com/kb/910339 where Microsoft offers remedies. When I applied Method 3 under "How to troubleshoot the problem if the update was installed" under "remedies" the problem went away. Note that I did first run the "Microsoft Fix it 50202" , but I don't know that it was necessary to do so.
I had the same three repeats on one XP computer. I used KB910339 to repair the problems. It was repaired by Fixit under aggressive mode.
I had the same problem & windows update history said installed but then said I needed to download again and install.
I tried most of everything here and Google search but no fix.
Manual install, Reinstall windows update, Mr Fixit etc.
This finally worked for me:
The update downloads are saved in C:\Documents and Settings\*your user name*\Local Settings\temp
Or create a link to: "%USERPROFILE%\Local Settings\temp"
or: Start -> Run -> %temp%
Delete all the files in the temp directory.
(Google to be sure that is safe - I did)
Only thing that worked.
Windows update says OK now.
The Following User Says Thank You to JohnSSS For This Useful Post:
Reoffered or Failed MS Updates Advice
Woody Leonhard lists KB 2572073, 2633880, and 2518864 as DO NOT INSTALL as of May 22, 2012. Underlying issues may exist with KB 2604092 (MS12-035). (Susan Bradley's current Windows Secrets (Paid) Patch Watch Column has some details.)
In other words, DO NOT download or install the May 2012 late-month MS Updates. ESPECIALLY NOT for Windows XP.
Update: These patches have been withdrawn from MS Updates over the days following their release. Sorry, Automatic Updaters, but you got hosed. Try changing your MS Updates Settings to Notify But Do Not Download if you feel put out over this. Check monthly for updates, and manually accept the safe ones.
IMPORTANT: Currently, Woody Leonhard has four blog entries about these three .NET patches issued on May 22, 2012. DO NOT APPLY these updates if they are not already automatically installed. Other advice on what to do is offered at Woody's site and at Infoworld TechWatch. Susan Bradley may have additional current advice on these updates. WAIT for updates to these patches. They probably will not be offered again to anyone who was not hit by them already.
But if you got hit:
There are several things users can do to try to deal with reoffered MS Updates patches. One is to get rid of (uninstall from Add/Remove Programs) .NET Framework. But if you have Apps which need .NET (I do) these options may help in some cases:
1) Manually run MS Updates through the IE browser. This automatically updates the necessary local components to have MS Updates run correctly on your local machine. You need to allow Active-X Controls to be added or modified to make this work properly.
2) Do try a second or even a third time to get the updates installed. Sometimes they work after failing initially. Some updates need other updates to be installed before they can themselves be installed. Do not try more than three times, as this will generally not help.
3) Between attempts, fully shut down and restart the computer, waiting for all processes to complete.
4) Check with Microsoft's KB articles and with Windows experts online for known issues, such as the Keyboard Layout issue with recent .NET updates. Other known issues include OEM System Files for which some System Kernel Mode Driver Updates (one was posted in this thread) skip updating, as OEM files are manufacturer-modified and replacing them with generic updates can wreck the computer's OEM Windows installation. These patches may be reoffered until your manufacturer updates their drivers (not likely for older PC's and laptops). As a last resort, you may hide these patches rather than tinker with the drivers in older machines. There are also a few recent patches (again, .NET mostly) which have "minimum system requirements" before they will successfully install. These patches have KB Articles explaining reoffers and Error Messages. KB Articles may also include MS Fixits to repair damages caused by failed updates installations.
5) There is a .NET Ripout Tool so you can uninstall.NET Framework and reinstall it from the beginning, but this is a lengthy and tedious process. Susan Bradley has referenced this tool in her Windows Secrets paid content columns.
6) Various MS Updates downloads, temp files and updates logs may also be an issue, as in Post #34 in this thread. Good advice on cleanup there.
7) Some patches have stand-alone installers, which may be downloaded from KB Articles, then run in Windows Safe Mode. This works around files which cannot be modified by patch installers, because thesse files are in use, or Windows Services are blocking access to these files. Safe Mode installations are just like normal Windows installations, except that they are performed while in Safe Mode (F8 during boot).
8) Check with Woody Leonhard's blog (www.askwoody.com) and Susan Bradley's paid Windows Secrets content articles about recent patches. Especially .NET. Both authors are recommending not hiding the updates, but not trying to install certain patches right now. These authors will update their postings as Microsoft fixes (or not) these patches. If an update was installed and is reoffered, the same advice applies -- ignore the reoffers right now, and wait for further instructions. No need to hide the patches unless they are driving you nuts when they pop up in Automatic Updates. Changing to another MS Updates setting (notify but do not download) may prevent this sort of annoyance in the future. But you would have to run MS Updates manually and uncheck patches still not deemed ready to install, then go back and install the skipped patches as they are updated or deemed safe.
So you have several options of what to do about reoffered partches, and Woody and Susan offer excellent advice if you are having issues. My personal opinion -- unless you are having issues with some patches (but not with patching generally) it is still wise for most users to leave MS Updates on Automatic, in spite of occasional issues like these.
Get the idea I've had my own patching issues over the years with Windows XP in an OEM laptop? Well, that is exactly the case.
Last edited by bobprimak; 2012-05-25 at 12:01.
Reason: additional information
-- Bob Primak --
Originally Posted by hedy5
Why on earth would you do that? After all, this isn't a English grammar forum is it?
Originally Posted by curiousclive
Hedy5's mother tongue may not be English and allowances should be made for that. Criticising a user because of a few spelling mistakes in a post is tenuous at best.
I found Margit's (Hedy5) post readable, and to me, that's all that counts. We should be trying to help here in the Lounge, not correct spelling and grammar. My typing is far from perfect, but no one has ever criticized (American spelling) my errors just because they are there. Tolerance of each others' minor errors is a part of civility, as long as the errors do not convey false or misleading information.
@Margit (Hedy5) --
It looks like you've been around personal computers for a very long time. You must have a lot of practical knowledge and advice to offer us in the Lounge. I hope you will post when you know something we all need to learn.
Last edited by bobprimak; 2012-05-28 at 13:55.
-- Bob Primak --
Got mine working via browser based update
I had the same problem. After several rounds I decided I'd try Microsoft Update, the version that runs in your web browser. After I did that I didn't get the update notices any more. I don't know why that worked and the other didn't. Sometimes if it works, I don't ask why.
More likely, the faulty updates had by that time already been withdrawn.
Originally Posted by LHuisingh