Error message when you run a command at the Command Prompt window in Windows Server 2008 Server Core: "The specified service does not exist as an installed Service"

Consider the following scenario:

• You have a server that is running Windows Server 2008 Server Core.
• You log on to the server as a system administrator.
• You try to run a command at the command prompt. For example, you run the regedit command.

In this scenario, you may receive the following error message:When you click OK, you receive the following error message:

This problem occurs because the value of the EnableLUA registry entry that controls the User Account Control (UAC) setting is changed. The UAC feature is not available in Windows Server 2008 Server Core. Therefore, the EnableLUA registry entry is not expected to cause any UAC related behavior in Windows Server 2008 Server Core. However, if the value of the EnableLUA registry entry is changed, you frequently encounter problems when you run commands at the Command Prompt window. Depending on the command that you run, you receive the "Access is denied" error message or other related error messages. This is not the expected behavior.

The value the EnableLUA registry entry is possibly changed in one of the following situations:

• You manually change the value.
• The value is changed by Group Policy objects.

After you apply this hotfix, the EnableLUA registry entry setting is ignored in Windows Server 2008 Server Core.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, the computer must be running one of the following operating systems:

• Windows Server 2008
• Windows Server 2008 Service Pack 2 (SP2)

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfix.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table.

Windows Server 2008 file information note

• The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
  Collapse this tableExpand this table

  Version	Product	SR_Level	Service branch
  6.0.600 1 . 18xxx	Windows Server 2008	SP1	GDR
  6.0.600 1 . 22xxx	Windows Server 2008	SP1	LDR
  6.0.600 2 . 18xxx	Windows Server 2008	SP2	GDR
  6.0.600 2 . 22xxx	Windows Server 2008	SP2	LDR

• Service Pack 1 is integrated into the original release of Windows Server 2008.
• The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For all supported x86-based versions of Windows Server 2008

For all supported x64-based versions of Windows Server 2008

For all supported Itanium-based versions of Windows Server 2008

To work around this issue, use one of the following methods.

Method 1

Note Use this method when the following conditions are true:

• You added the server to an organization unit (OU).
• The UAC feature is enabled on all the servers in the OU by using Group Policy objects.

To work around this issue, move the server out of the OU.

Method 2

Note Use this method when the following condition is true:

• You manually changed the value of the EnableLUA registry entry.

To work around this issue, follow these steps:

1. Open the Windows Registry of the server from a remote computer. To do this, follow these steps:
   1. On a remote computer, open Registry Editor.
   2. On the File menu, click Connect Network Registry.
   3. In the Select Computer dialog box, type the name of the server under Enter the object name to select, and then click OK.
2. In Registry Editor, locate the following registry subkey under the node that represents the server:
   
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. Set the value of the EnableLUA registry entry to 0.
4. Restart the server.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: -

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008

Additional files for all supported Itanium-based versions of Windows Server 2008