Login to Account Create an Account
Windows updates failing
Posted 15 October 2010 - 03:27 PM
Posted 09 November 2010 - 11:08 PM
Posted 10 November 2010 - 02:14 PM
Sorry if this constitutes a thread hijacking, but it has to do exactly with the subject of the title --
Today, my two Vista computers have repeatedly failed to install this month's Malicious Software Removal Tool (error code 80200053). When I click on "Get help with this error," there is no reference to the actual code number. Restarting the PCs to try again didn't make any difference.
Is this happening to you (or to anybody else reading this), and what can one do about it? It's a bit concerning that it would be precisely the tool for malicious software that's being prevented from installing.
Posted 10 November 2010 - 02:34 PM
Posted 10 November 2010 - 05:20 PM
I honestly don't know, but until we actually see WUSA log of a manual installation of a problem MSU failing, there's nothing more we can do to figure it out. Complaining it's not working without providing data means you're not as likely to get useful help - hence why I've asked for the WUSA /log logs of a failing install.
I'll have to research this WUSA log stuff, never heard of the concept before today.
I was mainly hoping to see if you or anybody else had experienced this issue, which occurred with today's MRT update, and if anybody knew anything about it. I guess it's too early in the process to tell, but since both of my Vista PCs had the problem, then it suggests the possibility that it might be a more widespread issue.
Posted 10 November 2010 - 05:38 PM
Posted 10 November 2010 - 07:24 PM
I have no clue as to what I might have done to both machines that would screw up this update, and no clue as to how to go about investigating it. This is the first time an MRT install has failed on either PC.
How does one utilize that WUSA thing? I did a Search, clicked on it, and it fails with some error message about needing the "full path" of the MSU file. Not a very informative message, actually. What do I enter for "update"? How would I find out the correct name of whatever it is that I would put in there??
This is all very frustrating. And Microsoft is absolutely no help with its vague message about Windows Update encountering an "unknown error."
Totally out at sea here. I could use some guidance!
UPDATE: The WUSA thing may now be moot. The Vista laptop is currently running the Windows Live online safety scanner (first time I've ever tried that); but the Vista tower was unable to download the files for that. However, the Vista tower was able to download the MRT manually, and it's running as I write this. I'll report back if it finds anything.
Edited by JorgeA, 10 November 2010 - 07:25 PM.
Posted 10 November 2010 - 07:39 PM
wusa.exe <package>.msu /log:<log file path and name>.log
Posted 10 November 2010 - 07:49 PM
Posted 10 November 2010 - 11:27 PM
I ran the OneLiveCare scanner by Microsoft on the Vista laptop. It didn't find any malware, but it did perform some repairs on the Registry. Afterward, I was able to download the MRT via the usual (automated-with-permission) method, and it's running as I write this. How about that.
As for the Vista tower, I went to the update page, did a manual download of the MRT, and then was able to run the program. It didn't find anything wrong. But out of curiosity I tried to download it through the automated process, and it still failed. Nor can I get the OneLiveCare installation. Hmm...
But the main crisis seems to have passed. I'll still check out the informative WUSA links you both gave me, for the next time something like this happens. You can never have too many options.
Thanks very much!
Posted 13 November 2010 - 10:30 PM
Hi.. you can try FixWin Utility from the below link
I work at a computer repair shop and I've been tearing my hair out trying to get this one machine to update. Most updates will install, but there are two DotNet and ActiveX related updates (KB982525 and KB980195) that continue to fail. I've tried re-installing DotNet 3.5 as well as flushing the software distribution, but no dice. When this happens on XP, I can usually take care of it with Dial-A-Fix, which unfortunately isn't Vista-compatible.
hope this will work for you....
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users