Support > Knowledge Base

Knowledge Base

Search the Knowledge Base:

Guided Search

Products:

Search In:

VMware Authorization Service Might Take a Long Time to Start on Windows 2000 Servers

Details

After rebooting a Windows 2000 server, the VMware Authorization Service (vmware-authd) might take several minutes to start. You will not be able to run any virtual machines until this service has started.

Solution

This is a known issue on Windows 2000 servers. vmware-authd needs another system component (WMI) to start in a timely fashion.

Caution: This article contains information about modifying the Windows registry. Before you modify the registry, make a backup copy of it and be sure that you understand how to restore the registry if a problem occurs. Instructions for making backups of the registry and restoring the registry are available on the Microsoft Web site at http://support.microsoft.com/default.aspx?scid=kb;en-us;136393.

To work around this problem:

Copy the following text into Notepad:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VMAuthdService]
"DependOnService"=hex(7):76,00,6d,00,78,00,38,00,36,00,00,00,77,00,6d,00,69,00,00,00,00,00

Save the file as FixAuthdNotStartup.reg. This new registry file modifies the Service dependencies so the VMware Authorization service depends on WMI.
Caution: This registry fix is only for Windows 2000 servers. Do not run the registry file on any other operating systems.
Double-click the file to run it.
Reboot the system.

Keywords

vs100

Feedback

Actions

KB Article: 1282693
Updated: Aug 14, 2009

Products:
VMware Server
Product Versions:
VMware Server 1.0.x (Windows)

Did this article help you?
This article resolved my issue. This article did not resolve my issue. This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)