Consider the following scenario. You configure a computer that is running Windows Vista or Windows Server 2008 to use the pen service (Wisptis.exe). Then, you restart the computer. In this scenario, an access violation occurs during startup. When the access violation occurs, the Wisptis.exe process exits, and you receive an error message that resembles the following:

Microsoft Tablet PC Input Component was closed
To help protect your computer, Data Execution Prevention has closed Microsoft Tablet PC Input Component. Click to learn more.

Consider the following scenario:

• On a Windows Vista-based computer, or on a Windows Server 2008-based computer, you run an application that uses the Open Database Connectivity (ODBC) API.
• The application uses the SQLSetConnectAttr function to set an attribute.
• You pass an SQL_NTS constant as the StringLength parameter to the SQLSetConnectAttr function.

In this scenario, an access violation may occur if you pass an INTEGER value to the ValuePtr parameter of the SQLSetConnectAttr function.

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

You start Windows Vista from a Microsoft Windows Preinstallation Environment (Windows PE) 2.0 image by using the flat file boot method. When you do this, an access violation occurs.

In Windows Vista, when you right-click a shared color printer and then click Properties, an access violation occurs in the Explorer.exe process.

When you run the Sysprep command on a Windows Vista-based computer, you receive an error message that resembles the following:

A fatal error occurred while trying to sysprep the machine

Additionally, an error code that resembles the following is logged in the Setupact.log file:

0×80070020
ERROR_SHARING_VIOLATION

Note: The Setupact.log file is located along the following path:
C:\Windows\Panther\Setupact.log