EastCoasthandle
New Member
- Joined
- Apr 21, 2005
- Messages
- 6,885 (0.99/day)
| System Name | MY PC |
|---|---|
| Processor | E8400 @ 3.80Ghz > Q9650 3.60Ghz |
| Motherboard | Maximus Formula |
| Cooling | D5, 7/16" ID Tubing, Maze4 with Fuzion CPU WB |
| Memory | XMS 8500C5D @ 1066MHz |
| Video Card(s) | HD 2900 XT 858/900 to 4870 to 5870 (Keep Vreg area clean) |
| Storage | 2 |
| Display(s) | 24" |
| Case | P180 |
| Audio Device(s) | X-fi Plantinum |
| Power Supply | Silencer 750 |
| Software | XP Pro SP3 to Windows 7 |
| Benchmark Scores | This varies from one driver to another. |
At times I had found problems trying to get XP to auto update. It would go through the emotions of telling you there are 80+ updates and would go through the process of updating them but would either fail to install or fail to download them. Many have had this problem and in most cases nothing less then a complete format and reinstall of XP would solve this problem. I was so frustrated of this because it would only happen after I had to do a Repair.
When the updates refused to install it was as if something was blocking it. As if a program or firewall was telling it to not install at all. The error message that iT failed to install/update was CONFUSING to me. I launched a 3+ hour investigation into this and came up with many so called solutions that didn't work for me. However, I came across one thread on the issue and someone suggested to look at the actual update log to see what error message(s) were appearing. This was the start to recovery of the problem.
%\windowsupdate.log
from the "run" command would give you a history of all your attempts to download those updates and any errors that occurred during the process.
To make a long story short, the problem was simple. After you do a repair you have to re-register your copy of XP. Did you notice how the repair process mimicks the install process (how it formats, installs files, reboot, install more files, verify date, time, hardware, etc)? When the repair is finished you should get a screen asking you to validate your copy of XP just like in the initial install but it doesn't. That's when the problem of installing updates occur. In order for me to download updates again I had to re-validate my copy of XP (just like I did when I installed it the first time). In order to do this I came across a post from what may have been an MS tech:
-net stop wuauserv
-%windir%\system32\wups.dll
-net start wuauserv
This finally allowed me to update. If you notice, the process bar doesn't fill up for every update it downloads any more. The process bar now accounts for the entire lists of downloads and you can now use it to gauge the entire update process instead of individual files.
I hope this helps someone else as it helped me.
When the updates refused to install it was as if something was blocking it. As if a program or firewall was telling it to not install at all. The error message that iT failed to install/update was CONFUSING to me. I launched a 3+ hour investigation into this and came up with many so called solutions that didn't work for me. However, I came across one thread on the issue and someone suggested to look at the actual update log to see what error message(s) were appearing. This was the start to recovery of the problem.
%\windowsupdate.log
from the "run" command would give you a history of all your attempts to download those updates and any errors that occurred during the process.
To make a long story short, the problem was simple. After you do a repair you have to re-register your copy of XP. Did you notice how the repair process mimicks the install process (how it formats, installs files, reboot, install more files, verify date, time, hardware, etc)? When the repair is finished you should get a screen asking you to validate your copy of XP just like in the initial install but it doesn't. That's when the problem of installing updates occur. In order for me to download updates again I had to re-validate my copy of XP (just like I did when I installed it the first time). In order to do this I came across a post from what may have been an MS tech:
-net stop wuauserv
-%windir%\system32\wups.dll
-net start wuauserv
This finally allowed me to update. If you notice, the process bar doesn't fill up for every update it downloads any more. The process bar now accounts for the entire lists of downloads and you can now use it to gauge the entire update process instead of individual files.
I hope this helps someone else as it helped me.
Last edited:
