Consider the following scenario:

• You install the Group Policy Management Tools feature on a computer that is running Windows Server 2008 or Windows Vista Service Pack 1 (SP1).
  Note: This feature is included with Microsoft Remote Server Administration Tools.
• You use the text filter function in the Group Policy Management Editor window.
  Note: When the text filter function is applied, only the items that match the filter criteria are returned.
• You set the default input language to a language other than English (United States). For example, you set the default input language to English (Canada) or to French (Canada).

In this scenario, the text filter function may not return any results in the Group Policy Management Editor window. However, you expect the items that match the filter criteria to be returned in the Group Policy Management Editor window.

Notes:

• This issue does not occur if the default input language is English (United States).
• Not all languages other than English (United States) are affected by this issue.

You develop an application that uses the SetICMMode function. In this application, the SetICMMode function is frequently called when the second parameter is set to the ICM_ON constant. When you run this application on a Windows Vista-based or a Windows Server 2008-based computer, the system memory is quickly exhausted.

When the issue occurs, the private working set for the corresponding process increases.

Note: This issue does not occur in Windows XP or in Windows Server 2003.

You develop an application that uses the UpdateLayeredWindowIndirect function to update a layered window. However, when you run the application in Windows Vista or in Windows Server 2008, the function does not correctly display the layered window.

This issue occurs when the following conditions are true:

• In the UPDATELAYEREDWINDOWINFO structure, you use both the pptSrc parameter and the prcDirty parameter.
• The pptSrc parameter does not use the default value (0, 0).
• The Desktop Window Manager (DWM) feature is enabled.

Additionally, when the issue occurs, you cannot manipulate the parameters to output the correct result.

The WaitForMultipleObjects() function does not work correctly together with pseudohandles in Windows XP, in Windows Server 2003, or in Windows Vista.

Consider the following sample code.

int _tmain(int argc, _TCHAR* argv[])
{
      
      HANDLE hnd[1]; 
	long res; 
	hnd[0] = GetCurrentProcess(); 

        res = WaitForMultipleObjects(1, hnd, FALSE, 3000);
      return 0;
}

After you run the sample code, you expect the function to return after three seconds. However, it returns a “WAIT_FAILED” error, and it does not wait.

If Windows Mail is set as the default e-mail client on a computer that is running Windows Vista, the MAPI_E_FAILURE error code is generated when you run an application that calls the MAPIFindNext function.

Note: This function retrieves the next message identifier or the first message identifier of a specified type of incoming message.

In Windows Vista, you may notice a small delay when you call the ReceiveFrom function of the CAsyncSocket class in the Microsoft Foundation Classes (MFC) library.