Windows update "Checking for updates..." for hours...
-
I have some machine that used to belong to a domain. The machine is retired, and some users want to take the machine home. I nuked the drive with DBAN (Dereck Boot and Nuke). The drivers seem to be recognized just fine. No BSOD or error so far. But the problem I am having with is Windows Update.
I suspect that because the device was joined to a domain with its own WSUS.. maybe that's why the windows could not detect the WSUS and keep Checking for Update...Any thought?
-
Forgot to mention. It is a Dell machine. I use Dell recovery disc they provided.
-
Dumb question time: Have you tried rebooting it?
I have a couple of servers that I have to do this with every time I run Updates.
-
I have had machines when they connect to windows update take a long time to actually connect and start downloading updates.
-
@dafyre said:
Dumb question time: Have you tried rebooting it?
I have a couple of servers that I have to do this with every time I run Updates.
I have tried rebooting and shutting it down already.
@brianlittlejohn said:
I have had machines when they connect to windows update take a long time to actually connect and start downloading updates.
I ran the update since morning. It has been around 6 hours already. Still no sign of it actually downloading something.
-
@LAH3385 said:
@dafyre said:
Dumb question time: Have you tried rebooting it?
I have a couple of servers that I have to do this with every time I run Updates.
I have tried rebooting and shutting it down already.
@brianlittlejohn said:
I have had machines when they connect to windows update take a long time to actually connect and start downloading updates.
I ran the update since morning. It has been around 6 hours already. Still no sign of it actually downloading something.
This is a known issue with MS update servers, but I have never seen anything officially posted about it.
A friend of mine that runs his own computer shop uses WSUS Offline. There was a conversation in a thread here lately on this subject.
-
@JaredBusch said:
@LAH3385 said:
@dafyre said:
Dumb question time: Have you tried rebooting it?
I have a couple of servers that I have to do this with every time I run Updates.
I have tried rebooting and shutting it down already.
@brianlittlejohn said:
I have had machines when they connect to windows update take a long time to actually connect and start downloading updates.
I ran the update since morning. It has been around 6 hours already. Still no sign of it actually downloading something.
This is a known issue with MS update servers, but I have never seen anything officially posted about it.
A friend of mine that runs his own computer shop uses WSUS Offline. There was a conversation in a thread here lately on this subject.
I will give it a shot and post its progress/feedback. Thanks
-
@JaredBusch said:
@LAH3385 said:
@dafyre said:
Dumb question time: Have you tried rebooting it?
I have a couple of servers that I have to do this with every time I run Updates.
I have tried rebooting and shutting it down already.
@brianlittlejohn said:
I have had machines when they connect to windows update take a long time to actually connect and start downloading updates.
I ran the update since morning. It has been around 6 hours already. Still no sign of it actually downloading something.
This is a known issue with MS update servers, but I have never seen anything officially posted about it.
A friend of mine that runs his own computer shop uses WSUS Offline. There was a conversation in a thread here lately on this subject.
It's working
may take a while before it's finish. -
I have seen an update search take as much as two hours....
-
Windows update has has several updated clients since Windows 7 Sp1 was released. The old WU client takes forever to update this.
Your best bet is to download the latest version manually. Take the PC offline, reboot, leave it offline, then install the WU. Reboot again, now plug the network back in. It could still take 2+ hours to find updates.
-
I had a Windows 7 SP1 lock up on me a few weeks ago. I did everything in this thread 1-2 times and it eventually started working. I let it sit 24 hours before I started and It wouldn't move until I installed the hot fixes.
