You use a Terminal Services mirror driver to access a Windows Vista-based or a Windows Server 2008-based remote computer. After you disconnect the mirror driver from the remote computer, the remote computer may crash. In this case, you receive the following error message on the remote computer:

Stop 0×0000007E (c0000005, Parameter2, Parameter3, Parameter4)
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

For example, assume that you use Live Mesh to access a Windows Vista-based remote computer. After you disconnect the Live Mesh remote session from the remote computer, the remote computer crashes, and you receive the Stop error message.

In the Active Directory domain, you configure different profile paths for a roaming user profile and for a terminal services profile. When a user logs on to a Windows Vista-based client computer by using a Remote Desktop session, Windows Vista uses the profile path that is defined on the Terminal Services Profile tab to load the profile. However, Windows Vista should use the profile path that is defined on the Profile tab to load the profile.

Consider the following scenario.

• You type a keyboard shortcut on a Windows Vista-based computer.
• You are working in a Terminal Services session that was started by using Remote Desktop Connection 6.0 (RDC 6.0).

In this scenario, some keys in the keyboard shortcut may remain active. Therefore, in the Terminal Services session of the Remote Desktop window, some later keystrokes are interpreted as part of the previous keyboard shortcut. For example, this problem occurs if the following conditions are true:

• You lock the local computer by pressing “Windows logo key” + L.
• You unlock the local computer.
• The Remote Desktop window is in the full-screen mode.
• The Remote Desktop window is active.

When you press any key, various Windows keyboard shortcuts occur in the Terminal Services session. For example, when you press E in the Terminal Services session, Windows Explorer starts.