When you try to add one or more 32-bit printer drivers on a 64-bit printer server, you receive the following error message:

The folder you specified doesn’t contain a compatible software driver for your device.

Assume that you are running a 32-bit application on a computer that is running a 64-bit version of Windows Vista. You print some photographs in the application. However, the application displays a print properties page, and then the application stops responding (hangs).

This problem can occur with any applications that open the print properties page that is built in the operating system. For example, this problem occurs when you try to print a photograph in Windows Live Photo Gallery 2009 on a computer that is running a 64-bit version of Windows Vista. However, Windows Live Photo Gallery 2009 stops responding at the following message:

Getting ready to print…

Consider the following scenario:

• You use Remote Desktop Connection Client for Mac 2.0 to make a terminal server session to a computer that is running Windows Server 2008 x64 Edition or Windows Vista x64 Edition.
• You enable the audio redirection feature on both the server-side computer and the client-side computer.

In this scenario, the audio redirection feature does not work after a terminal server session is made. If you use the same Macintosh client to connect a terminal server that is running Windows Server 2008 x86 Edition, the audio redirection feature works.

When you start Windows Live Movie Maker on a 64-bit Windows operating system, the following error is logged in the Application log:

Log Name: Application
Source: SideBySide
Event ID: 35
Task Category: None
Level: Error
Keywords: Classic
Description:
Activation context generation failed for “C:\Program Files (x86)\Windows Live\Photo Gallery\MovieMaker.Exe”.Error in manifest or policy file “C:\Program Files (x86)\Windows Live\Photo Gallery\WLMFDS.DLL” on line 8. Component identity found in manifest does not match the identity of the component requested. Reference is WLMFDS,processorArchitecture=”AMD64″,type=”win32″,version=”1.0.0.1″. Definition is WLMFDS,processorArchitecture=”x86″,type=”win32″,version=”1.0.0.1″. Please use sxstrace.exe for detailed diagnosis.

You try to remotely view the printer Security tab on a print server that is running an x86-based edition of Windows Vista or of Windows Server 2008 from one of the following client operating systems:

• Windows 7, x64-based editions
• Windows Server 2008 R2, x64-based or IA-64-based editions

When you do this, you receive the following error message on the Security tab:

The requested security information is either unavailable or can’t be displayed.

Note: You do not receive this error when you remotely view the printer Security tab on a print server that is running an x86-based edition of Windows 7.

After you apply update 973879 on a computer that is running an x64-based version of Windows Vista or of Windows Server 2008, you may receive a “Stop 0×0000007e” or “Stop 0×00000050″ error message within 10 minutes after system startup.

You are using Visual Studio 2008 and Team Explorer 2008, both of which are installed on a x64 Windows Vista workstation. You connect to Team Foundation Server 2008 and attempt to check items into TFS Source Code Control.

Consider the following scenario.

• On a computer that is running a 64-bit version of Windows Vista, you try to browse a Web site by using a 32-bit version of Windows Internet Explorer.
• There is no Internet connection, and you receive a page that displays an error message in Internet Explorer.
• You click the Diagnose connection Problems button on the error message page, and then click View available wireless networks.

In this scenario, the “Diagnose connection Problems” program does not run correctly.

Consider the following scenario:

• You have a computer that is running a 64-bit version of Windows Server 2008 or Windows Vista.
• On this computer, a process calls the CreateProcessWithTokenW function to create a child process that runs under Windows 32-bit on Windows 64-bit (WOW64).
• The WOW64 child process is created to redirect standard input (STDIN), standard output (STDOUT), and standard error (STDERR).

In this scenario, the redirections do not work in the WOW64 child process. Therefore, any applications or services that depend on the redirection feature do not work.

You notice slow performance when you render a .jpg file on a computer that is running an x64-based version of Windows Server 2008 or of Windows Vista. Additionally, the performance is slower than when you render the same .jpg file on a computer that is running an x86-based version of Windows Server 2008 or of Windows Vista.