I recently configured a new/fresh Windows 2008 STandard Server (32 Bit). After the latest patches are applied, the next reboot, it just stayed at "Configuring Updates Stage 3 of 3 0% complete Do not turn off Computer ". It's almost 4 hours withthe same problem. Rebooted it already and it's the same. I can't even go to Safe mode even after selecting it. That message just keeps popping. I know that this is a know issue with Vista and windows 7. Any suggestions.

Microsoft made available update 937287, a prerequisite item for the deployment of Windows Vista Service Pack 1. The update impacted the Windows Vista installation software feature, namely the operating system's component designed to manage additional updates, language packs and even service packs when it comes down to the installation and uninstallation process. Set up as a prerequisite for Vista SP1, Microsoft confirmed that it was killing the delivery of KB937287 for the platform's servicing stack update due to an error involving the message “configuring updates stage 3 of 3. 0% complete” and the machine moving into an endless reboot loop. One simple way to avoid the issue is to install KB937287 separately from the other updates, and not permit its delivery and deployment through Automatic Updates. In addition, Microsoft has come up with three methods to save Vista from the infinite reboot loop induced by the KB937287 Vista SP1 update. After users have regained access to their operating systems, they only need to integrate KB937287 as a standalone update, it is available: 32-bit and 64-bit. “Insert the Windows Vista installation disc in the DVD drive, and then restart the computer. Configure the Language to install, Time and currency format, and Keyboard or input method options. Click Repair your computer. Select the of the Windows Vista operating system that you want to repair, and then click Next. Click System Restore, then on the System Restore page, click Next. Select a restore point at which you know that the operating system was working, and then click Next. If you are prompted for a disk to restore, select the disk to which the operating system is installed, and then click Next. On the Confirm your restore point page, click Finish. When the restoration process is complete, click Restart,” Microsoft explained. The second method of regaining access and functionality to your Vista operating system involves using the Repair or System Restore feature in Safe Mode. Just reboot the computer and press the F8 key before you see the Windows Logo. In this manner, you will be presented with the Advanced Boot Options screen. Select to start Windows Vista in Safe Mode. Make your way to System Restore, choose a restore point before the updates were installed and let the feature do all the heavy lifting. After you restart, you should have regained functionality to your copy of Vista. And if both these methods fail, there is always lucky number three: renaming the Pending.xml file, and then editing the registry. “Insert the Windows Vista installation disc in the DVD drive, and then restart the computer. Press any key when you are prompted to restart from the disc. When you are prompted, configure the Language to install, Time and currency format, and Keyboard or input method options Choose Repair your computer. On the System Recovery Options page, click the version of the Windows Vista operating system that you want to repair, and then click Next. On the System Recovery Options page, click Command Prompt. Type cd C:\windows\winsxs, and then press ENTER. Type ren pending.xml pending.old, and then press ENTER. Type regedit, and then press ENTER. Select HKEY_LOCAL_MACHINE. On the File menu, click Load Hive. Locate the following folder:
C:\windows\system32\config\components. When you are prompted for a name, type Offline_Components. In Registry Editor, locate and then delete the following registry subkey:
HLKM\Offline Components\AdvancedInstallersNeedResolving. In Registry Editor, locate and then delete the following registry subkey: HKLM\Offline Components\PendingXmlIdentifier,” Microsoft added.

Well, there's no hurt in trying. I will try to see if I can install (or even if it's available updates for Windows 2008) KB937287 this separately. I've google and searched and so far this KB is the common denominiation of an issue. We'll keep you posted.

Thanks this might be a start. I contacted Microsoft because it already caused us 4 activations of our license. What I'm going to do is not run the updates anymore until this issue comes in the forefront. Right now, I can't find any solutions either here or outside of Expert Exchange. I googled it and tried other resources but most of the time, this kind of issue happens mostly with Vista and SBS 2008.

I thought at first that Disabling IPV 6 on the TCP/IP network was causing this. After re-enabling it, I was able to install all the updates and logged in but now, the problem is that it get stuck on "Server collection via Server Manager". After that I can't do anything anymore. I rebooted several times and still the same issue. So I was back to square one.

I'm installing the Windows 2008 Standard on a VMWare server (just an fyi).

What I found out is that when applying the SSL certificate (wildcard) and when you reboot, the server hangs. With the new Terminal server, the issue that we’re facing is when applying our wildcard SSL certificate. When you apply the wildcard SSL cert, it works fine (everything from external access of application). But when you restart the server, , it hangs at ‘Applying computer settings’ or most of the time you’ll be able to login but it hangs on ‘Data collection’ of Server Manager’ and then the Terminal server is asking for the activation again. Even though we just activated the TS and the 10 CAL license.

What I ended up doing was to disabled the NIC card of the VM and reset the TS (VM). Once I’m logged in, I removed the eGain.com wildcard SSL cert and replaced it with a test/dummy certificate. I re-enabled the NIC card and reboots the server. After the reboot, the server works fine, the TS Server is working and it shows that the 10 CAL licenses had been applied.

But if you re-apply again the wildcard, the same issue happens again.

I have reconfigured 4 times already. I configured the TS from server without any updates all the way to fully updated Windows 2008 Standard server but with the same result with theWildcard SSL certificate. It looks like the wildcard SSL certificate is disabling the TS and causing this issue.

When we're about to troubleshoot this with Microsoft Tech Support, it worked fine all of a sudden. What I did differently was just re-applied the SSL certificate several times and tweak with the confiruation a bit (meaning tried some certificate and then came back to the wildcard certificate). It's working now. Even the Microsoft Tech Support does not know what happen. I would safe that this case is closed.

My Problem is either patch KB983589 or KB890830
I ran out of time to diagnose which one, since upon applying the patch it renders the machine unworkable/unusable and I had deadline to install the server.
I have hidden these patches for the time being and turned off any automated updates. My hosting company is going to give me access to an image of the server when I have some time, so that I can debug this problem.
One is security update for .NET Framework 3.5 SP1 (for Window s Server 2008 SP2)
The other is the Windows Malicious Software Removal Tool ( I doubt it would be this one - since it doesn't cause a reboot.)

I wasn't doing anything with SSL at that stage, although I have taken my SSL cert and applied it later to enable an SSL website.

I am using web edition 2008
I don't have the access to get to the VM Console, but it is VMWare 3.5 ESX, so perhaps that is something related there.

When we're about to troubleshoot this with Microsoft Tech Support, it worked fine all of a sudden. What I did differently was just re-applied the SSL certificate several times and tweak with the confiruation a bit (meaning tried some certificate and then came back to the wildcard certificate). It's working now. Even the Microsoft Tech Support does not know what happen. I would safe that this case is closed.

As an aside, I have a tech looking a problem with the license not activating. Turns out it is because I didn't install R2 and I have a license. I can't imagine this has anything to do with it, but I thought I would mention.

Recently, I was asked to look into SCCM 2007 by my employer, having a degree of experience of earlier versions of SMS and some previous SCCM knowledge I didn't expect the procedure to involve to much time.
I read a number of guides concerning it…

This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job.
The first step is to acquire the necessary licen…

This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008.
Determine the location of the FSMO roles by lo…