After upgrade to xp pro cannot install windows updates

I install this on the workstation and get the network drivers going. Do NOT join the Domain, stay in workgroup mode. Go to windows update and get shunted to the Support page. Scroll down and run one of the automated "Fix It" options. It is still broken after this. I run the SP3 update on top of the SP3 install and reboot.

After this update works. I have done this on three systems and it seems to work consistently. I don't know if this is a permanent fix as once a system is updated, we disable and lock down auto updates so I don't care about further updates. We only do them when we rebuild a system or to fix a specific problem.

Once you are all done updating, you can join the domain if you need to. Is this Microsoft's way of wean us off of XP or force us to use autoupdates? Wish Microsoft would make a statement about this one way or another. Linn P. As far as I can tell it is a recent phenomenon. I have an image I built from scratch about a month ago that has no issues. It seems to be the initial contact with Windows Update that is at issue.

I also noticed that after installing the Update Agent, I do not get the initial prompt to install the latest updating software. Maybe the issue is with the initial check for update software, since the system is new and does not have it, it fails and the check that used to occur is not properly working? Someone needs to call to call and find out what is up!

I'm puzzeled by all this. I make a living from reinstalling Windows. Someone call ! Saturday, August 6, AM. OK guys, this was bugging me all day. Please check and confirm if this fixes the problem for you guys. I tried this and it worked! Saturday, August 6, PM. This worked for me. Thank you to the intrepid one who found the fix! Sunday, August 7, AM. Anyway, thanks again for your help, you pulled it out of the fire,, Bob Northern California.

Workaround Found! Eddie Stevens Cleveland Computer, Inc. Monday, August 8, AM. Get your updates while you can : It seems like there's two Windows Update Agents 3. There's a version 6. Thanks, Linn. Monday, August 8, PM. That will fix it if you have tried everything above and it still doesn't work. Thanks everyone. I'll post what happens. Saturday, August 13, PM. Update, it works! Hi Guys and girls if there are any? I had this issue last week on a toshiba laptop i had to reload.

I tried several different resolutions provided by microsoft however none seened to work. This moning however I had a result when i found this artical. I guess if you have a few machines to do you could script the install thankfully I only had 1. Hope this helps Regards, Paul Fisher here is the artical. Monday, August 15, AM. Tuesday, August 16, AM. Thanks saldrich70! I re-formatted twice, tried windows auto update, re-registered every. That was the trick!

Tuesday, August 16, PM. Wednesday, August 17, PM. Thursday, August 18, PM. I lost hours days install uninstall I am very angry , I have more to do. Here, it is AM. Bad Microsoft, bad Friday, August 19, AM. Monday, August 22, AM. Same Problem here. Is MS aware of this issue?? Monday, August 22, PM. Remember the first time setting it up that you were supposed to uncheck the "let windows manage your wireless connection" this time check it back. Exit out of the dlink client dlink will have to do some kind of firmware version update to fix this.

Setup the wireless client as you did with the dlink client, choose SSID, type of network, type of encryption, and etc. You should start receiving packets now. All in all SP2 is pretty large leap forward then SP1, the wireless client is a lot more sophisticated then the one for SP1 which just was total crap. Oh and the windows firewall will work fine, but since your behind a router that has a firewall you technically don't need a firewall on your pc unless your running an ad hoc network and you only allow certain ports and protocols which by the way the windows firewally can do.

It does pretty much what zone alarm can do and that is make you look invisible to the outside world. RE: Windows XP wireless problems after windows update: I have been reading all these posts regarding the wireless connections, and finally I think I found the answer to my wireless problem.

Four servers are connected through the ethernet ports and two are connected using All of the devices come up normally under boot and run correctly. Its only when the servers go into standby mode that I lose my wireless connections, and they never come back when I try to use them. Finally here is the answer. Microsoft writes in article Q that all XP-based computers that go on standby and are remotely connected to internet connections, are silently disconnected when the processors go to standby.

Microsoft states this is by design. You must manually reconnect any remote access connections before you can use them again. I hope this helps some of your questions. It appears that SP2 doesn't like WEP keys created with a passphrase, but will accept 64 bit key manually. Router access point is Netgear WGR Hope this helps save others many hours of stuffing around. RE: Windows XP wireless problems after windows update: To add to the neverending list of frustrating experiences here As soon as I installed SP2, it stopped working and I couldn't get it to work again no matter what I tried.

The symptoms were that the wireless network would connect, and get a DHCP address, but would not communicate. Furthermore, if I ever lost the connection, it would endlessly rescan and never reestablish, even if the laptop was sitting on top of the access point. Interestingly enough, I could ping the access point's IP address, but I could not ping the gateway or any other machines on the network.

I also could not ping back to the laptop from other machines on the network. I had the Windows firewall turned off also tried turned on--didn't seem to matter. I tried fiddling around with the routing tables, but that didn't fix it either.

The final combination that I tried that worked was this there may be a simpler way :- : 1 Go into the Device manager, and uninstall the device. I left it set as "Manual" instead of "Automatic". All should be back to normal and working.

Without disabling the Wireless Zero Config service, it didn't matter that I had turned off "Don't have Windows configure wireless", since it still was interfering with things working. About five hours total wasted, but now I'm a happy camper again RE: Windows XP wireless problems after windows update: andygryc -- tried your solution.

Most of my symptoms have been described by nearly all of you above. Tray icon showed a strong signal and connection, but no access to web and no networks showing up when I open network connections. Worked with D-Link for literally hours, nothin' doin'.

Encryption, no encryption, every setting imaginable and in Windows they are freely distributed in numerous and to me, illogical places. I'm under no illusions. It's late and I may follow up further tomorrow, but maybe tonight.

Stay tuned. RE: Windows XP wireless problems after windows update: OK, tried ejecting the card and plugging back in without a reboot. Not working now, and nothing I do is getting it back. I'm not sure whose problem this is, but Microsoft really has to bear the brunt. This was all working for me prior to SP RE: Windows XP wireless problems after windows update: bcastner -- thanks for the link.

I have followed all of it and tried what it suggests, to no avail. I note that no D-Link products are in the Windows catalog as XP certified, and that most other brands are not either. The only thing I've seen in this thread that I haven't tried is to eliminate the hotfix file. I'll try that if it exists and if that doesn't work, then I will try re-installing WinXP, and not update to SP2 until someone here says, "Yay! Turned off encryption on router and laptop, turned off all firewalls, etc.

Crossed fingers and hoped. Didn't help. Nothing working. Upgraded not clean install -- upgraded -- to XP Pro. Also gave the network a profile. After about a minute the system recognized the card and network. Ran IE 6. Hope this helps. BUT it broke everything on the laptop again. I've been trying the various combinations of settings to see if anything will work, but nothing does and the D-Link AirPlus utility won't run, either.

I changed the router first, and in retrospect i probably should have changed the laptop to WEP first and then changed everything else. Tired, going to bed. Will call Buffalo in the morning to see if they can assure me that a completely Buffalo system with Ethernet Adaptor and Cardbus card on the two wireless-connected computers will work. Really disappointed about the Ethernet adaptor not working with WPA. On these units, bridging does not support WPA. Once everything was working reliably, I re-installed SP2 on the laptop, and everything continues to work through sleeping, shut-down, restarts, etc.

I can't honestly say what was the crucial change in getting things going -- was it going to XP Pro? No matter. I'm happy now. Hope something in here will help someone else. The connection was dropping but I assumed it was due to a weak signal, as I had move the computer during the process, or possible not having applied SP2 and all the hotfixes et al.

I was gutted that the connection kept on dropping after the software, drivers and everything was completely up to date and the router was moved to improve the signal. Once the connection was lost only a reboot would get it back.

What was particularly strange was that I could ping the router and the modem but not the name server or anything else beyond the modem. All I can say is that I have read this entire thread without a disconnect saying something now and written this reply without a disconnect. I don't really know the answer to this, but I can't see any reason to keep the WZC service running if you aren't going to use it.

As an act of desperation I tried updating his windows XP pro and I could actually update it I must be missing something very obvious or something not so obvious. I know I've haven't specified what exact equipment here. I'll try to get all the specifics later and get back on here Thanks in advance. I always had trouble with that when the DHCP lease would renew on my router. Switching to a static addresss solved it. I know I am sending packets but not recieving any.

Before I had this problem, and used a WinsockFix program. Now it isn't working. When I look at my ipconfig, it recognize all the appropriate info, except the DNS and gateway are empty. What am I doing wrong? I upgraded to the latest firmware but still no joy. Any ideas? Please address my pet hate, "a cable is loose, you lose your keys" RE: Windows XP wireless problems after windows update: Suffering very similar symptoms here too.

Tried everything in this thread, and the MS KB article, but hasn't worked. Using bit WEP. Like others the DLink and Windows icons in the sys tray say everything is connected fine, but nothing seems to work. But there is a few interesting things i've noticed that differ from what others have previously described. The PC does get an IP address from the router. Pinging the router fails, but checking the packet packet counts in the network connection status reveals one response from the router immediately when ping is first run, then after each timeout yes this kinda sounds like a firewall prob, but have them disabled.

Also, if the G is disabled, then reenabled in the device manager, everything works until the next reset!? Problem was that we couldn't connect to a Netgear wgrv4 router used as an access point every morning until the router was rebooted. Then it worked fine. I was using WEP 64bit encryption, but also the access control list. I updated the firmware on the router a step backwards and on my wireless card, disabled the Wireless Zero Config Service, using the card's software instead.

As of September , the latest major update for Windows 8 is the confusingly named Windows 8. If you've already updated to Windows 8.

See instructions for manually installing Windows 8. If you are not already running Windows 8. When that's done, update to Windows 8. Microsoft is not planning another big update to Windows 8, like a Windows 8. New features, if available, will instead be pushed through updates on Patch Tuesday. If it IS a preactivated one you won't see Activation Status.

While these can be installed on name brand hardware Dell, HP, etc. Originally they could but Microsoft deactivated all of those XP keys to prevent piracy, since it was discovered later that those keys would activate anything on any hardware.

Even with all current updates applied from Windows Updates, Windows XP still has many, many open vulnerabilities in it. If you have to run it, you may be interested in spending an evening reviewing the information on the Unofficial Windows XP Service Pack 4 located here:.

Look for Community Update Packs. Even today as of this writing Microsoft has closed most if not all known vulnerabilities in Windows XP but the problem is that the fixes are scattered through many multiple hotfixes many of which were released for specific Large Corporation demands where they still have to run XP for specific applications as well as the Point Of Sale and embedded releases of XP.

The Unofficial Service Pack 4 is an attempt to consolidate those together. While it's not endorsed by Microsoft it is still a useful tool for those instances where hardware requires the use of XP for example, older Modbus cards, etc.

Trust me, nobody including Microsoft is going to come up with a reasonable justification for replacing a 5 million dollar industrial plant controlled by an XP system just to upgrade the controller PC with Windows Office Office Exchange Server.

Not an IT pro? Resources for IT Professionals. Sign in. United States English.