Consider the following scenario:

• You have a computer that is running Windows Vista Enterprise 64-bit edition.
• You type mstsc /? at the 32-bit command prompt (%windir%\SysWOW64\Cmd.exe) to view the mstsc command syntax.

In this scenario, the Remote Desktop Connection Usage dialog box that contains the mstsc command syntax is not displayed.

Note: The Remote Desktop Connection Usage dialog box appears when you type mstsc /? at the 64-bit command prompt (%windir%\System32\Cmd.exe).

When you install a 64-bit edition of Windows Vista from a 32-bit based installation media, you may have to provide mass storage controller drivers for the 32-bit operating system and for the 64-bit operating system. This article describes how to install third-party mass storage drivers for the 64-bit editions of Windows Vista. Keep reading →

Consider the following scenario. You develop an application that uses the VDMEnumProcessWOW function to enumerate virtual DOS machines (VDMs) that are running 16-bit Windows tasks. However, when the application runs on a computer that is running a 32-bit version of Windows Vista, the application returns no output. Or, the application returns incorrect output.

For example, you may experience this problem when you use the application to return a list of 16-bit Notepad instances.

Consider the following scenario. You are running a 32-bit version of Microsoft Internet Explorer on a computer that is running a 64-bit version of a Microsoft Windows operating system. You enable the Make proxy settings per-machine (rather than per-user) Group Policy settings. In this scenario, you cannot access the Internet through a proxy server.

• GeForce Release 175.12 (32-bit)
  The beta of GeForce Release 175.12 for Vista 32-bit.
  (tags: 32-bit Driver GeForce Nvidia Video )
• GeForce Release 175.12 (64-bit)
  The beta of GeForce Release 175.12 for Vista 64-bit.
  (tags: Driver GeForce Nvidia Video )

Keep reading →

The beta of GeForce Release 175.12 for Vista 32-bit. Keep reading →

This update addresses issues and improves compatibility with Microsoft Windows XP and Microsoft Windows Vista running on a Mac computer using Boot Camp. It is highly recommended for all Boot Camp users. Keep reading →

When a 32-bit application is writing the %ProgramFiles% registry value on a computer that is running a 64-bit version of Windows Vista, Windows Vista automatically changes this string to %ProgramFiles(x86)%. This behavior cannot be changed.

This behavior also occurs in the 64-bit versions of Windows Server 2003 and of Windows XP.

Consider the following scenario:

• You install a 64-bit version of Windows Vista.
• You install printer drivers.
• In a 32-bit program, you open the Print dialog box.

In this scenario, you experience one of the following symptoms:

• If you click Properties two times, two Properties dialog boxes appear. Then, the 32-bit program stops responding. Also, the printer drivers and the Splwow64.exe process stop responding. Moreover, you experience high CPU usage.
• If you open a Print dialog box in Internet Explorer, click Preferences, close the Preferences dialog box by clicking a button, and then click Preferences again, Internet Explorer stops responding.
• If you click the Advanced tab in a Microsoft Office program, the program may stop responding. When you try to close the program that has stopped responding, you receive an error message that resembles the following:
  

  You cannot close because a dialog box is open. Click OK, switch to [application] and then close the dialog.

When you use a 32-bit program to play a DVD movie in a 64-bit version of Windows Vista, you do not hear any audio.