After logging on for the first time, if you change the background color to a solid color other than black, the background changes back to solid black after the second logon.

Note: To configure the desktop background to a solid color, follow these steps:

1. Right-click on the Desktop then click on [Personalize].
2. Click on [Desktop Background] then select [Solid Colors] under [Location].
3. Choose one of the solid colors listed other than black.

Consider the following scenario. You have a computer that is running Windows Server 2008 or Windows Vista. The Stored User Names and Passwords feature is enabled. Additionally, this feature has stored various user names and passwords. Then, you encounter one or more of the following problems:

• You cannot log on to a computer when you use a domain user account. The log on process stops responding at the phase of processing group policies. However, you can log on to the computer when you use a local user account.
• The Network Location Awareness service stops responding. Additionally, you cannot stop this service.
• Several services stop responding. After a while, the system stops responding.
• When you browse the shared SYSVOL folder on a domain controller, the Windows Explorer (explorer.exe) stops responding.
• When you disable a network adapter, the disable operation stops responding.
• When you work in the Network and Sharing Center, the Network and Sharing Center stops responding.

In this scenario, you have to restart the computer to resolve this problem. These problems frequently occur on servers where many log on operations and log off operations occur. For example, this problem frequently occurs on a terminal server.

After resuming a computer running Windows Vista from sleep (S3) or hibernation (S4), with the monitor powered off, you cannot see a logon screen and will not be able to logon.

A black screen is displayed after you enter your user credentials in the logon dialog box on a computer that is running Windows Vista or Windows Server 2008. When this issue occurs, you can still move the mouse pointer. However, you cannot start applications such as Windows Explorer. After a while, the operating system stops responding.

In a network environment, you enable some group policies in the following location:

User Configuration\Administrative Template\System\Removable Storage Access

However, if you add the removable storage drive to a client computer that is running Windows Vista or Windows Server 2008 during the period between the system start and the user logon, you find that you can still perform related operations to the removable storage drive.

For example, consider the following scenario:

• You enable the policy “Removable Disks: Deny write access”
• You start a client computer that is running Windows Vista
• You insert a USB storage drive into the computer
• You log on to the system

In this scenario, you can still write files to the USB, or create files on the USB storage drive. However, you expect to see an “Access is denied” message.

Consider the following scenario:

• You apply the following policy to a computer that is running Windows Server 2008 or Windows Vista:
  

  Computer Configuration\Windows Settings\Security Settings\Software Restriction Policies\Enforcement

• For this policy, in the Apply software restriction policies to the following section, you select the All software files option.

In this scenario, you encounter a slow application startup or a slow logon. The slow logon occurs when users have their local drives mapped to a network share.

Note: You can use Process Monitor to determine whether your computer has the issue. To do this, you start Process Monitor before you start an application. Your computer has the issue if you find a log that is in the Process Monitor and that resembles the following:

CreateFile C:C:\WINDOWS\SYSTEM32\IMM32.DLL NAME INVALID
CreateFile C:\?? NAME INVALID

The logging has both features (1: incorrect file path (such as C:C:\WINDOWS\…). 2. “Name

You log on to your Windows Vista desktop computer by using your regular domain account. When use other credentials to map to a Distributed File System (DFS) share, you receive the following error message:

ERROR_NO_SUCH_LOGON_SESSION winerror. A specified logon session does not exist. It may already have been terminated.

On a computer that is running Windows Vista or Windows Server 2008, you map a network drive to a Web share, and then you select the Reconnect at logon option. Then, you restart the computer, or you log off and then log back on again. In this situation, the mapped drive is displayed as a red X. Additionally, you may receive the following error message:

Could not reconnect all network drives

Additionally, when you double-click to the mapped drive to access it, you may receive the following error message:

An error occurred while reconnecting Drive: to https://localhost/share
Web Client Network: The operation being requested was not performed because the user has not been authenticated.
This connection has not been restored.

When this problem occurs, you have to disconnect and then remap the Web share.

This problem may occur if the Web share requires certificate-based Secure Sockets Layer (SSL) authentication.

On a computer that is running Windows Server 2008 or Windows Vista Service Pack 1 (SP1), you repeatedly encounter stop error code 0×00000050 during the user logon or logoff process. Then, the computer restarts automatically.

When this issue occurs, the following event may be logged in the System log:

Log Name: System
Source: Microsoft-Windows-Kernel-General
Date: date & time
Event ID: 5
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: computer name
Description: {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\user name\ntuser.dat' was corrupted and it has been recovered. Some data might have been lost.

Note: This issue frequently occurs on Windows Server 2008-based terminal servers.

When you try to log on to a Windows Vista-based computer or a Windows Server 2008-based computer, the logon process may take a long time because of incremental network traffic.

This problem occurs when you have large number of offline files on the computer.

To determine whether you are experiencing this problem, open a network monitor tool. Then, stop and restart the Windows Search service. If you notice lots of network traffic, you are experiencing this issue.