XP Windows Updates Error on 2x computers

xxsilk109xx

New Member
Reaction score
1
Location
Savannah, GA
I have 2x windows xp computers that I have done a nuke and pave on here in the shop, they are two different computers from different customers.
Neither one has ANYTHING installed except windows, they have both been activated over the internet just fine.

When I try to get windows updates, the green bar across the screen goes for about 5 minutes, then it says there was an error
0x80072EE2
Claims it cant display the webpage.

I have the same modem and router I have had and have made no changes to either, such as proxy settings etc.

I have used google and on the first computer tried everything that this site suggests.
Code:
http://www.updatexp.com/0x80072ee2.html

I was wondering if anyone was having the same problem, maybe a MS problem? Or is there something that I have not done yet.
 
Can you pull up any other sites?
Did you use factory partition for reload?
In the past I have had a computer or two get a virus in this partition and jack up the Windows updates even though it was fresh install of OS.
Had to clear all the partitions and re-create, reload.
Amazingly Windows updates displayed w/out issues.

Good Luck!
 
How up to date are the service packs? Meaning do you have the most recent one? I did a Server 2003 instal on VMware and had the same issues, until I got the most recent service pack in it. I know yours is XP and mine was Server 2003 BUT maybe this could be the issue. It's may not be the issue, but I thought I would comment.


---
I am here: http://maps.google.com/maps?ll=38.425743,-83.739004
Sent from my iPhone using Tapatalk
 
SOLVED - Seems it was a problem with windows update servers or something, I tooled around with that ancient beast and its NIC card and left them alone, came back to them and they are now doing updates!!

M$ - you owe me a beer
 
Great news +1 more beer lol




They owe me a case of beer. My favorite was when we upgraded to SP3 on XP years ago and they changed the 802.1x (we used for network port authentication) to be a separate service...

It sucked big-time when hundreds of computers started without the 802.1x service started... Had to disable 802.1x on the switches to get the computes off the Guest VLAN to even see Active Directory again! Then had to tweak the Local Security Policy to make it all better and wait until they ALL had the policy before re-enabling 802.1x


^^^^ I would say they owe us a truckload (or at least a palate) of cold beer... Nothing like coming into work one day with hundreds of PCs not seeing the network.
 
Back
Top