New customer problem with Windows Update

[nbtc971]

I just purchased a 1 core VPS and connected to it after it was finished installing. The first thing I'm trying to do is run Windows Update and install the updates it finds. After clicking install updates it just runs and runs for 15-20 minutes this gives me an error. I'm trying now to limit the updates to just a few small ones and it's doing the same thing. I've even hit the Stop Installation button after I could tell it wasn't working after attempting to install a small update, and it still just runs and won't stop whatever it's trying to do.

This is on a new 2008 R2 server that was just purchased. I did look at the windows update history and it appears that maybe this server was in use before because there are many updates in its history. Maybe I don't know how virtual servers work, but I did think this was going to be a clean install.

Any help is appreciated.

My IP is: 74.91.114.249

[nbtc971]

Just tried a little 40k install.. won't work. I need to update windows to get procon to work.

[nbtc971]

I believe I have fixed this by shutting down the windows update service, then going to windows/software distribution and moving that folder to my desktop, then restarting the service and running windows update again.

If you can control this, it might be a good idea to remove that directory for new builds so others won't experience this problem in the future.

[nbtc971]

I'm hoping I didn't speak too soon. Windows Update did download all the updates, but again it might be stuck on "preparing to install".

[Edge100x]

I haven't seen this particular Windows Update bug before. Have you tried rebooting already?

The server wasn't in use by another customer before. You just have an update history because we installed them when we created the image.

[nbtc971]

I will try a reboot..

[nbtc971]

er... well rebooting seems to of fixed it. Normally with any problem like that restarting would of been the first thing I did, but since it had just booted up from a clean install, I didn't figure it would do anything. My bad.

Actually, it looks like the clean install might require a restart because there was an option to 'install updates and shut down' so apparently each new VPS windows 2008 R2 might want to restart their server as soon as it's built.

Thanks.