Consider the following scenario:

• You are running Windows Server 2003, Windows Vista, or Windows Server 2008 on a computer that has a multi-core processor installed.
• You put the computer to standby, and then you resume the computer.
• You put the computer to standby again, and then you try to resume the computer.

In this scenario, the computer stops responding (hangs), and the monitor never turns on again.

This problem occurs after you apply hotfix 951126 on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

951126 A multiprocessor computer that is running a Microsoft Windows operating system stops responding on a black screen after you resume the computer from hibernation

Consider the following scenario:

• You have a computer that is running a 64-bit version of Windows Vista or a 64-bit version of Windows Server 2003.
• A 32-bit process calls the GetRawInputDeviceList function.

In this scenario, memory corruption occurs.

This article describes the Microsoft Jet 4.0 Database Engine issues that are fixed in the Jet 4.0 Database Engine hotfix package that is dated October 23, 2007.

This article describes the following items about the hotfix package:

• The issues that the hotfix package fixes.
• The prerequisites for installing the hotfix package.
• Whether you must restart the computer after you install the hotfix package.
• Whether the hotfix package is replaced by any other hotfix package.
• Whether you must make any registry changes.
• The files that the hotfix package contains.

On a Windows Vista-based computer, when you try to connect to a computer that is running Windows XP or Windows Server 2003 through a Remote Desktop Protocol (RDP) connection, the RDP connection fails. Also, you receive the following error message:

The security policy of your computer requires you to type a password on the Windows Security dialog box. However, the remote computer you want to connect to cannot recognize credentials supplied using the Windows Security dialog box. For assistance, contact your system administrator or technical support

This problem occurs when the Require trusted path for credential entry Group Policy setting is enabled on the Windows Vista-based computer.

Consider the following scenario:

• You are running a Windows Vista-based computer that has the Windows Server 2003 Administration Tools Pack installed.
• On this computer, you open administrative Microsoft Management Console (MMC) snap-ins.

In this scenario, some icons in these MMC snap-ins are displayed incorrectly. Or, these icons are missing.

For example, you may be unable to determine from a user account’s icon whether that user account is disabled. In this situation, you have to open the properties dialog box for the user account and then confirm whether the user account is disabled.

This problem has been observed with the following MMC snap-ins:

• Active Directory Users and Computers
• Active Directory Domains and Trusts
• Active Directory Sites and Services
• Active Directory Schema

• DNS

Consider the following scenario:

• In a Windows Server 2003 domain, you configure a Folder Redirection Group Policy object.
• You have more than 256 security groups configured in the Folder Redirection Group Policy object.

However, when a user logs on to the domain from a Windows Vista-based client computer, the folders are not redirected to the location that is configured in the Group Policy object.

Note: This issue does not occur on a Windows XP-based client computer.

One of my readers brought up in the chatroom that he’s faced with an undocumented bug. He’s using the Italian version of Windows Vista, and said that when he uses the command prompt to copy files, and it prompts you ‘Yes|No|All’ on whether or not to copy the file, the command doesn’t properly respond to your input. If he says ‘No’, the command copies the file anyway! I checked Microsoft’s Knowledge Base, and did find one article that perfectly describes the issue, but the article isn’t for Vista, it is for Windows Server 2003. Keep reading →