In a C++ Microsoft Jet DAO MFC (CDao) application, insertions and updates may not work on a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008. Additionally, you may receive the following error message:

Note If the application does not capture the exception that is returned by CDao on the insertion or the update, the database will not have the updates that you intended to make.

Back to the top

This problem occurs when all the following conditions are true:

•	The application is written in Microsoft Visual C++ and uses the CDao classes to access a Microsoft Jet database data source.
•	The Use Multi-Byte Character Set value is set for the Character Set project option.
•	The data that the application is inserting or updating was retrieved from a fixed-length defined Text column.
•	The source Text column contains data that is the maximum length that the column allows. For example, a Text(10) column contains a value of 1234567890.
•	Successive insertions or updates occur from the original variable that is returned from the CDaoRecordset object.
•	The target table column is one of the following columns: • The same column from which the original data was retrieved • Another fixed-length column that is defined as a Text column of the same size

Back to the top

To resolve this problem, apply the hotfix that is described in Microsoft Knowledge Base article 943509.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

If you cannot apply the hotfix that is described Microsoft Knowledge Base article 943509, use one of the following methods to work around this problem:

•	Update the application. To do this, copy the retrieved data from the original Visual C++ variable to a new variable. Then, insert or update the data from the new variable.
•	Update the database design. To do this, use one of the following methods: • Modify the column widths to one character larger than any expected data. • Redefine the width as a non-fixed length.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

This article describes updates to APIs that enable Windows-based applications to retrieve historically accurate time stamps.

What time functions are updated?

The following time functions are updated by this update:

• SystemTimeToTzSpecificLocalTime() Converts a time in Coordinated Universal Time (UTC) to a specified time zone’s corresponding local time.
• TzSpecificTimeToSystemTime() Converts a local time to a time in Coordinated Universal Time (UTC).

Note The functions that are listed here use a TIME_ZONE_INFORMATION structure that specifies the START DATE and the END DATE for daylight saving time (DST). By default, the current DST rules are used when no such structure is provided.

When to use these functions in an application

Most date and time stamps that are created and displayed in Windows and in many applications are stored as UTC. Then, they are rendered in local time by using system APIs. Examples of these include Windows file time stamps, Outlook sent and received dates, and event logging time stamps.

Not all built-in, Windows-based applications use these newly updated APIs. However, they are available to all applications, including third-party applications. These functions are useful in many scenarios, such as a user auditing scenario in which the ability to use DST rules for previous years on a current Windows service pack is important.

Generally, if an application requires historically accurate time stamps, these functions should be used.

How to use these functions in an application

For information about syntax, parameters, return value, and examples on how to use these functions in an application, please visit the following Microsoft Developer Network (MSDN) Web sites:

SystemTimeToTzSpecificLocalTime Function

TzSpecificLocalTimeToSystemTime Function

Note This article supersedes article 944340, which describes an earlier version of these APIs. This update improves the performance of the functions, and enables historically accurate time-stamp lookup functionality that was introduced in 944340.

This update applies to the following Windows operating systems:

• Windows XP Service Pack 3 (SP3)
• Windows Server 2003 Service Pack 2 (SP2)
• Windows Vista Service Pack 1 (SP1)
• Windows Server 2008

Hotfix information for Windows XP

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows XP SP3 installed.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces the following hotfix:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows XP with Service Pack 3, x86-based versions

Hotfix information for Windows Server 2003

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have the following installed:

• Windows Server 2003 SP2

  For more information, click the following article number to view the article in the Microsoft Knowledge Base:

  889100  (/Feedback.aspx?kbNumber=889100/ ) How to obtain the latest service pack for Windows Server 2003
• The 944340 hotfix

  For more information, click the following article number to view the article in the Microsoft Knowledge Base:

  944340  (/Feedback.aspx?kbNumber=944340/ ) The time stamps are incorrect after you apply update 928388 and then change the time settings to a year that is earlier than 2007 in Windows XP and in Windows Server 2003

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix replaces the following hotfix:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

Hotfix information for Windows Vista and for Windows Server 2008

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix on Windows Vista-based computer, you must have Windows Vista SP1 installed.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

No prerequisites are required for Windows Server 2008-based computers.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

The .manifest files and the .mum files that are installed in each environment are listed separately in the Additional file information for Windows Server 2008 and for Windows Vista section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported IA-64-based versions of Windows Server 2008

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported IA-64-based versions of Windows Server 2008

Microsoft has released security bulletin MS07-017. The security bulletin contains all the relevant information about the security update. This information includes file manifest information and deployment options. To view the complete security bulletin, visit one of the following Microsoft Web sites:

•	Home users: http://www.microsoft.com/athome/security/update/bulletins/200704oob.mspx (http://www.microsoft.com/athome/security/update/bulletins/200704oob.mspx)
•	IT professionals: http://www.microsoft.com/technet/security/bulletin/ms07-017.mspx (http://www.microsoft.com/technet/security/bulletin/ms07-017.mspx)

Back to the top

Known issues

•

Microsoft is aware of an issue that affects a limited number of printer drivers. When you try to print by using one of these drivers, you may experience the following symptoms: • Your computer automatically restarts. • After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error.A log of this error has been created. Please tell Microsoft about this problem.We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. When you click the link at the bottom of the message box, you see error signature information that resembles the following: BCCode : 0×0000007f (0×00000000, 0×00000000, 0×00000000, 0×00000000) OSVer : 5_1_2600 SP : 0_0 Product : 256_1 • You receive the following Stop error message: A problem has been detected and Windows has been shut down to prevent damage to your computer… Technical information: *** Stop 0×0000007f (0×00000000, 0×00000000, 0×00000000, 0×00000000) UNEXPECTED_KERNEL_MODE_TRAP For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 935843 (/Feedback.aspx?kbNumber=935843/) Stop 0×0000007F error when you print from Windows XP or Windows 2000 with GDI security update 925902 installed

•

After you install this security update on a computer that is running Windows XP with Service Pack 2, certain third-party applications may not start. Additionally, you receive an error message that resembles the following: application_executable_name – Illegal System DLL Relocation The system DLL user32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLL C: Windows System32 Hhctrl.ocx occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL. For more information about this issue, and to see a list of third-party programs that Microsoft has confirmed are affected by this problem, click the following article number to view the article in the Microsoft Knowledge Base: 935448 (/Feedback.aspx?kbNumber=935448/) Certain programs may not start, and you receive an error message on a computer that is running Windows XP Service Pack 2: Illegal System DLL Relocation If you receive a similar message when you use other programs, install update 935448. If we confirm that other programs are affected by this problem, we will update Microsoft Knowledge Base article 935448 with more information.

Back to the top

The revision number and the review dates for this article may reflect minor editorial revisions or structural revisions to this content. The major technical revisions to this content are listed in this table.

Date	Revisions
April 17, 2007	Updated the Known issues section to include information about a Stop error that you may receive after you install this security update. Added this table.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Back to the top

You use the Office Customization Tool (OCT) to create a customization file to configure shortcuts. Then, you use this customization file on a computer that is running Windows Vista. When you do this, the shortcuts for applications in the 2007 Microsoft Office system are not generated in the designated location.

For example, you create a customization file to install Microsoft Office OneNote 2007 and to generate a custom OneNote shortcut in the following location:

After you use this customization file, you notice that the OneNote shortcut is not generated in the following location as expected:

Instead, you notice that the shortcut is generated in the following location:

Back to the top

This issue occurs because Windows Installer recognizes the shortcut destination as a Start Menu location. Therefore, Windows Installer adjusts the destination profile to correspond with the installation.

Installations of the 2007 Office system are per-computer. Therefore, the shortcuts are put in the CommonAppDataFolder folder instead of in the AppDataFolder folder.

Back to the top

To work around this issue, follow these steps:

1.	Use the Add files section of the OCT instead of the Configure shortcuts section to install the shortcuts.
2.	Perform a regular test installation, and then copy the .lnk files that are created. Add these files to the Add files section of the OCT by using the following destination: [AppDataFolder] Microsoft Windows Start Menu Programs
3.	Use the Configure shortcuts section to remove any shortcuts that you do not want installed.

After all per-user files and all registry entries are added by using the OCT, the shortcuts are copied to a user’s profile the next time that the user runs a 2007 Office application.

If you want the shortcuts to be copied to the profile before the user starts a 2007 Office application, you can add a registry entry that will run a one-time start of a 2007 Office application during the logon process.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To run a one-time start of a 2007 Office application during the logon process, use the Add registry entries section of the OCT to add a registry entry that resembles the following registry entry:

Back to the top

Consider the following scenario:

•	On a Windows Vista-based computer, you set the Default input language setting to Chinese (PRC) – Chinese (Simplified) – US Keyboard.
•	On this same computer, you start a .NET WinForm application. Then, you set the focus to a text box in the application.
•	You switch the Input Method Editor (IME) to Chinese (Simplified) – Microsoft Pinyin IME, and then you set the IME Conversion Mode to full-shape mode.
•	You switch the focus to another application, and then you return the focus to the text box.

In this scenario, the IME Conversion Mode is unexpectedly changed to half-shape mode.

Note This issue occurs only the first time that you switch the focus. If the application continues running, the IME status is maintained as expected.

Back to the top

This issue occurs because the IME does not send the WM_IME_NOTIFY message the first time that you switch the IME conversion mode. Therefore, the .NET WinForm application does not obtain the latest IME conversion status. Instead, the application stores the incorrect IME status. Therefore, the application restores the incorrect IME status when a user returns the focus to the application.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Vista service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

File name	File version	File size	Date	Time	Platform
Package_1_for_kb949232_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,753	19-Feb-2008	16:48	Not Applicable
Package_1_for_kb949232~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,474	19-Feb-2008	16:48	Not Applicable
Package_2_for_kb949232_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,916	19-Feb-2008	16:48	Not Applicable
Package_2_for_kb949232~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,641	19-Feb-2008	16:48	Not Applicable
Package_3_for_kb949232_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,758	19-Feb-2008	16:48	Not Applicable
Package_3_for_kb949232~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,479	19-Feb-2008	16:48	Not Applicable
Package_4_for_kb949232_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,758	19-Feb-2008	16:48	Not Applicable
Package_4_for_kb949232~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,481	19-Feb-2008	16:48	Not Applicable
Package_5_for_kb949232_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,758	19-Feb-2008	16:48	Not Applicable
Package_5_for_kb949232~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,481	19-Feb-2008	16:48	Not Applicable
Package_6_for_kb949232_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,754	19-Feb-2008	16:48	Not Applicable
Package_6_for_kb949232~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	2,476	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_client_0_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,407	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_client_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,426	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_client_1_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,348	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_client_1~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,367	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_client_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,682	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_client~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,713	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_sc_0_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,402	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,422	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_sc_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,404	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_sc~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,423	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_server_0_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,406	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_server_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,425	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_server_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,412	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_server~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,431	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpesrv_0_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,403	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpesrv_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,422	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpesrv_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,411	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpesrv~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,430	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpe_0_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,401	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpe_0~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,420	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpe_bf~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,405	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpe~31bf3856ad364e35~x86~~6.0.1.0.mum	Not Applicable	1,424	19-Feb-2008	16:48	Not Applicable
Update-bf.mum	Not Applicable	3,484	19-Feb-2008	16:48	Not Applicable
Update.mum	Not Applicable	3,571	19-Feb-2008	16:48	Not Applicable
X86_0b2761d10c4c9342908eed599aa8aa03_31bf3856ad364e35_6.0.6000.20775_none_820713161c68a820.manifest	Not Applicable	715	19-Feb-2008	16:48	Not Applicable
X86_30e79cf8f63d1c15bab15fc64fc92a10_31bf3856ad364e35_6.0.6001.18021_none_2ed4f54ee601d1d2.manifest	Not Applicable	715	19-Feb-2008	16:48	Not Applicable
X86_49f9b9e9f92549766752b02a20088197_31bf3856ad364e35_6.0.6000.16642_none_bc54cbd925a106cd.manifest	Not Applicable	715	19-Feb-2008	16:48	Not Applicable
X86_e3b2b99a0b069691e4ea452bcd1119d1_31bf3856ad364e35_6.0.6001.22117_none_057140cd823a0f27.manifest	Not Applicable	715	19-Feb-2008	16:48	Not Applicable
X86_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.0.6000.16642_none_73b43257f1bd2b1a.manifest	Not Applicable	29,560	19-Feb-2008	05:28	Not Applicable
X86_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.0.6000.20775_none_7420603d0af06abc.manifest	Not Applicable	29,560	19-Feb-2008	05:14	Not Applicable
X86_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.0.6001.18021_none_75af108beed46ad2.manifest	Not Applicable	29,560	19-Feb-2008	05:34	Not Applicable
X86_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.0.6001.22117_none_76497eff07e486b5.manifest	Not Applicable	29,560	19-Feb-2008	05:13	Not Applicable
Msctf.dll	6.0.6000.16642	805,888	19-Feb-2008	05:01	x86
Msctf.dll	6.0.6000.20775	806,400	19-Feb-2008	04:48	x86
Msctf.dll	6.0.6001.18021	806,912	19-Feb-2008	04:55	x86
Msctf.dll	6.0.6001.22117	806,912	19-Feb-2008	04:47	x86

Windows Vista, x64-based versions

File name	File version	File size	Date	Time	Platform
Amd64_031981a04ae97cf842fa3402e628f1ee_31bf3856ad364e35_6.0.6000.20775_none_f8812f60c9981024.manifest	Not Applicable	1,078	19-Feb-2008	16:48	Not Applicable
Amd64_0486f958fafb1327f72478794f067a0c_31bf3856ad364e35_6.0.6000.20775_none_7d48a7976e43e335.manifest	Not Applicable	719	19-Feb-2008	16:48	Not Applicable
Amd64_111cff5fd31a607cccc6c516fba3cae2_31bf3856ad364e35_6.0.6001.22117_none_c2530414840e09c4.manifest	Not Applicable	1,078	19-Feb-2008	16:48	Not Applicable
Amd64_29c9e49715bff19da2a6bc0e8cdeaedb_31bf3856ad364e35_6.0.6000.16642_none_df21d1349b677b86.manifest	Not Applicable	1,078	19-Feb-2008	16:48	Not Applicable
Amd64_8b05b94732d1fdc5d25049c203bc99db_31bf3856ad364e35_6.0.6001.18021_none_4728f6940f00e396.manifest	Not Applicable	719	19-Feb-2008	16:48	Not Applicable
Amd64_a121b6fe58ef06920d5eb18a4aa0b2a3_31bf3856ad364e35_6.0.6001.22117_none_331c49e30862b37e.manifest	Not Applicable	719	19-Feb-2008	16:48	Not Applicable
Amd64_aed1f14509b74328b93688574e14f348_31bf3856ad364e35_6.0.6001.18021_none_de0ddc93c3571421.manifest	Not Applicable	1,078	19-Feb-2008	16:48	Not Applicable
Amd64_bc6252f20aa3b5e674e101c4f909da5a_31bf3856ad364e35_6.0.6000.16642_none_d557c888fa94967d.manifest	Not Applicable	719	19-Feb-2008	16:48	Not Applicable
Amd64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.0.6000.16642_none_cfd2cddbaa1a9c50.manifest	Not Applicable	29,584	19-Feb-2008	05:11	Not Applicable
Amd64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.0.6000.20775_none_d03efbc0c34ddbf2.manifest	Not Applicable	29,584	19-Feb-2008	05:19	Not Applicable
Amd64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.0.6001.18021_none_d1cdac0fa731dc08.manifest	Not Applicable	29,584	19-Feb-2008	06:05	Not Applicable
Amd64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.0.6001.22117_none_d2681a82c041f7eb.manifest	Not Applicable	29,584	19-Feb-2008	06:03	Not Applicable
Package_1_for_kb949232_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,763	19-Feb-2008	16:48	Not Applicable
Package_1_for_kb949232~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,488	19-Feb-2008	16:48	Not Applicable
Package_2_for_kb949232_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,155	19-Feb-2008	16:48	Not Applicable
Package_2_for_kb949232~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	3,123	19-Feb-2008	16:48	Not Applicable
Package_3_for_kb949232_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,995	19-Feb-2008	16:48	Not Applicable
Package_3_for_kb949232~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,959	19-Feb-2008	16:48	Not Applicable
Package_4_for_kb949232_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,995	19-Feb-2008	16:48	Not Applicable
Package_4_for_kb949232~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,961	19-Feb-2008	16:48	Not Applicable
Package_5_for_kb949232_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,995	19-Feb-2008	16:48	Not Applicable
Package_5_for_kb949232~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,961	19-Feb-2008	16:48	Not Applicable
Package_6_for_kb949232_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,764	19-Feb-2008	16:48	Not Applicable
Package_6_for_kb949232~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	2,490	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_client_0_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,415	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_client_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,434	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_client_1_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,356	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,375	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_client_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,692	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_client~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,723	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_sc_0_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,410	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,430	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_sc_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,412	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_sc~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,431	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_server_0_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,414	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,433	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_server_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,420	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_server~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,439	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpesrv_0_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,411	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,430	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpesrv_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,419	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,438	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpe_0_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,409	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpe_0~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,428	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpe_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,413	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpe~31bf3856ad364e35~amd64~~6.0.1.0.mum	Not Applicable	1,432	19-Feb-2008	16:48	Not Applicable
Update-bf.mum	Not Applicable	3,510	19-Feb-2008	16:48	Not Applicable
Update.mum	Not Applicable	3,597	19-Feb-2008	16:48	Not Applicable
Msctf.dll	6.0.6000.16642	1,052,160	19-Feb-2008	04:53	x64
Msctf.dll	6.0.6000.20775	1,052,672	19-Feb-2008	04:57	x64
Msctf.dll	6.0.6001.18021	1,040,384	19-Feb-2008	05:22	x64
Msctf.dll	6.0.6001.22117	1,040,384	19-Feb-2008	05:17	x64

Windows Vista, IA-64-based versions

File name	File version	File size	Date	Time	Platform
Ia64_1d7fcd1f5f66f1d1ba167fcf060e5c05_31bf3856ad364e35_6.0.6001.22117_none_4884c5a43ec93d9c.manifest	Not Applicable	717	19-Feb-2008	16:48	Not Applicable
Ia64_4949d2d0fc5a3705c4719e54f6f170f7_31bf3856ad364e35_6.0.6001.18021_none_85f90703f50cbbe7.manifest	Not Applicable	717	19-Feb-2008	16:48	Not Applicable
Ia64_4f25c470ed0eda6aee932c8534d886b6_31bf3856ad364e35_6.0.6001.18021_none_62f4d2a5e156901a.manifest	Not Applicable	1,076	19-Feb-2008	16:48	Not Applicable
Ia64_603928dc9053d3ca7fb1ac99b57ae2ba_31bf3856ad364e35_6.0.6001.22117_none_f3cf674846e9032b.manifest	Not Applicable	1,076	19-Feb-2008	16:48	Not Applicable
Ia64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.0.6001.18021_none_75b0b481eed273ce.manifest	Not Applicable	29,572	19-Feb-2008	06:05	Not Applicable
Ia64_microsoft-windows-t..icesframework-msctf_31bf3856ad364e35_6.0.6001.22117_none_764b22f507e28fb1.manifest	Not Applicable	29,572	19-Feb-2008	05:31	Not Applicable
Package_1_for_kb949232_bf~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,758	19-Feb-2008	16:48	Not Applicable
Package_1_for_kb949232~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	2,481	19-Feb-2008	16:48	Not Applicable
Package_2_for_kb949232_bf~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,990	19-Feb-2008	16:48	Not Applicable
Package_2_for_kb949232~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	2,952	19-Feb-2008	16:48	Not Applicable
Package_3_for_kb949232_bf~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,990	19-Feb-2008	16:48	Not Applicable
Package_3_for_kb949232~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	2,952	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_sc_0_bf~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,406	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,425	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_sc_bf~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,407	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_sc~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,427	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_server_0_bf~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,410	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,429	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_server_bf~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,415	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_server~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,435	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpesrv_0_bf~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,407	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpesrv_0~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,426	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpesrv_bf~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,414	19-Feb-2008	16:48	Not Applicable
Package_for_kb949232_winpesrv~31bf3856ad364e35~ia64~~6.0.1.0.mum	Not Applicable	1,434	19-Feb-2008	16:48	Not Applicable
Update-bf.mum	Not Applicable	2,372	19-Feb-2008	16:48	Not Applicable
Update.mum	Not Applicable	2,423	19-Feb-2008	16:48	Not Applicable
Msctf.dll	6.0.6001.18021	2,059,776	19-Feb-2008	05:23	IA-64
Msctf.dll	6.0.6001.22117	2,060,288	19-Feb-2008	05:02	IA-64

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

For more information about the WM_IME_NOTIFY message, visit the following Microsoft Web site:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Source: Microsoft Support

Back to the top

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Back to the top

On a Windows Vista-based Tablet PC, links to Tablet PC applications are broken.  Specifically, the following links are broken: Flicks Training, Ink Watson, Pen Training, Shape Collector, and Touch Training. To view the links, click Start, click All programs, click Accessories, and then click Tablet PC.

On a Windows Vista-based desktop computer, the Tablet PC folder is empty. To view the folder, click Start, click All programs, and then click Accessories.

Back to the top

When the Tablet PC Optional Components feature is disabled by using the Turn Windows features on or off option, the Tablet PC folder is not removed and is empty.

Back to the top

To work around this issue, delete the Tablet PC folder. To do this, follow these steps:

1.       Click Start, click All programs, and then click Accessories.

2.       Right click Tablet PC, and then click Delete.

3.       Click Yes when you are prompted for a confirmation.

If you want to restore the Tablet PC applications, enable the Tablet PC Optional Components feature. To do this, follow these steps:

1.        Click Start, type Programs and Features in the Start Search box, and then click Programs and Features in the Programs list. 

2.        Under Tasks, click Turn Windows features on or off.

If you are prompted for an administrator password, type the password. If you are prompted for confirmation, click Continue. 

3.       Click to select the Tablet PC Optional Components check box, and then click OK.

Back to the top

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

On a Windows Vista-based computer, you cannot use keyboard shortcuts to select more than one item in Windows Explorer. For example, you cannot use the CTRL+A keyboard shortcut to select all the items in a Windows Explorer window. Also, you cannot select multiple items in a Windows Explorer window by holding the SHIFT key or the CTRL key while you click the items.

Back to the top

This problem occurs because certain applications add a key to the registry. The key prevents you from selecting multiple items in Windows Explorer.

Back to the top

To resolve this issue, use the Reset Folders command. To use the Reset Folders command, follow these steps:

1.	In the Windows Explorer window where this issue occurs, click Organize, and then click Folder and Search Options.
2.	On the View tab, click Reset Folders.

Note You may have to repeat these steps if you experience this problem again. The applications that cause this problem may insert the key into the registry whenever they run.

Back to the top

Source: Microsoft Support

Back to the top

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Back to the top

On a Windows Vista-based Tablet PC, links to Tablet PC applications are broken.  Specifically, the following links are broken: Flicks Training, Ink Watson, Pen Training, Shape Collector, and Touch Training. To view the links, click Start, click All programs, click Accessories, and then click Tablet PC.

On a Windows Vista-based desktop computer, the Tablet PC folder is empty. To view the folder, click Start, click All programs, and then click Accessories.

Back to the top

When the Tablet PC Optional Components feature is disabled by using the Turn Windows features on or off option, the Tablet PC folder is not removed and is empty.

Back to the top

To work around this issue, delete the Tablet PC folder. To do this, follow these steps:

1.       Click Start, click All programs, and then click Accessories.

2.       Right click Tablet PC, and then click Delete.

3.       Click Yes when you are prompted for a confirmation.

If you want to restore the Tablet PC applications, enable the Tablet PC Optional Components feature. To do this, follow these steps:

1.        Click Start, type Programs and Features in the Start Search box, and then click Programs and Features in the Programs list. 

2.        Under Tasks, click Turn Windows features on or off.

If you are prompted for an administrator password, type the password. If you are prompted for confirmation, click Continue. 

3.       Click to select the Tablet PC Optional Components check box, and then click OK.

Back to the top

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

When you try to run a Subsystem for UNIX-based Applications (SUA) application on a Windows Vista-based computer, the application may stop responding.

Back to the top

This problem occurs because SUA is designed to run automatically when one or more of the following conditions are true:

•	You restart the computer after SUA is installed.
•	An application that runs with administrative credentials starts SUA.

SUA does not start if the following conditions are true:

•	A user who does not have administrative credentials installs the SUA subsystem.
•	The computer has not been restarted after SUA is installed.
•	You have not run an SUA application by using administrator credentials.

Therefore, an SUA application that you run without administrative credentials may stop responding.

Back to the top

To resolve this problem, use one of the following methods:

•	Method 1 Restart the Windows Vista-based computer. By default, SUA starts when you restart the computer.
•	Method 2 Install the optional SUA software development kit (SDK). The following file is available for download from the Microsoft Download Center: Download the Utilities and SDK for Subsystem for UNIX-based Applications in Microsoft Windows Vista package now. (http://go.microsoft.com/fwlink/?LinkId=59121) Release Date: December 14, 2006 For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: 119591 (/Feedback.aspx?kbNumber=119591/) How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
•	Method 3 Run the Posix command from an elevated command prompt. To do this, follow these steps: 1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for confirmation, type the password, or click Continue. 2. At the command prompt, type posix /u /c /bin/loginenv, and then press ENTER. For more information about the elevated command prompt in Windows Vista, visit the following Microsoft Web site: http://technet2.microsoft.com/WindowsVista/en/library/00d04415-2b2f-422c-b70e-b18ff918c2811033.mspx (http://technet2.microsoft.com/WindowsVista/en/library/00d04415-2b2f-422c-b70e-b18ff918c2811033.mspx) By default, SUA starts when you run the Posix command from an elevated command prompt.

Back to the top

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the Applies to section.

Back to the top

For more information about SUA, visit the following Microsoft Web site:

For more information about Utilities and SDK for UNIX-based Applications, visit the following Microsoft Web site:

Back to the top

Source: Microsoft Support

Back to the top

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Back to the top

On a computer running a 64-bit version of Microsoft Windows, you use the Microsoft .NET Framework 2.0 Configuration tool to configure the .NET Framework security policy.

Back to the top

The changes made using the .NET Framework 2.0 Configuration tool do not apply to a 64-bit .NET Framework 2.0 application. 64-bit .NET Framework applications are assemblies compiled in Visual Studio with the Target CPU set to Any CPU (and running on a 64-bit computer), x64 or Itanium.

Back to the top

The Microsoft .NET Framework 2.0 Configuration tool only applies to 32-bit assemblies (i.e. assemblies compiled with the Target CPU set to x86). This is also true for the mscorcfg.msc MMC snap-in located in the Program Files Microsoft.NET SDK v2.0 64 bit bin folder.

This behavior is by design.

Back to the top

Run Caspol.exe for the 64-bit version of the .NET Framework 2.0 to configure security policy for 64-bit applications.

1. Open a 64-bit .NET framework SDK command prompt or the Visual Studio x64 Command prompt.
2. Run caspol.exe to make the policy changes.

You can verify changes to the security policies saving them out to a text file and comparing. To save the policies to a text file, run the following command using both the 32-bit and 64-bit versions of Caspol.exe

Caspol –all –l > c: policy.txt

Back to the top

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

Source: Microsoft Support

Back to the top

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Back to the top

When you run a full-screen application, such as a game, the Windows Sidebar may flash or appear on top of the application or game briefly.

Back to the top

Full screen applications or games which do not create a full-screen window may cause the Windows Sidebar to unexpectedly receive an indication that the mouse is over the Windows Sidebar. When this happens the Windows Sidebar will try an animation to fade in, which is normal behavior. However, an issue will underlying technologies (layered windows) will cause the Sidebar to flash into view despite the application or game being topmost.

Back to the top

The Windows Sidebar can be closed before you run the application or game, or can be set to be Sidebar is always on top of other windows . Or, the code for the application or game can be modified to create a full-screen window, rather than a topmost window the size of the current screen.

To close the Windows Sidebar, right-click Windows Sidebar, and then click Close Windows Sidebar.

To set the Sidebar is always on top of other windows option, follow these steps:

1. Right-click Windows Sidebar, and then click Properties.

2. Click to select the Sidebar is always on top of other windows check box, and then click OK.

Back to the top

Repro Steps

==========

To reproduce this issue, follow these steps:

1.       Make sure Windows Sidebar is not set to Sidebar is always on top of other windows.

2.        Start application which uses Direct 3D.

3.       Move mouse around, typically toward upper-right of the screen. Sidebar should flash and appear for some time.

Back to the top

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

Source: Microsoft Support

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

When adding a Medium Changer Tape Backup device to a Windows Server 2003 or Server 2008 system, the system’s device manager may not show all components of the device: the tape drive(s) or the changer (robotics). 

Portions of the device are not visible in the device manager.  As such, the Removable Storage service based applications, including Tape Backup software, may not be able to fully utilize the Medium Changer. 

The HBA (host bus adapter) the Medium Changer is connected to is using Storport compatible drivers and the Medium Changer uses a non_hierarchical scsi REPORT_LUNS structure.  When a seemingly valid REPORT_LUNS structure is returned from the target device, it will be used to determine the LUNs available to the operating system. If the target uses a non-hierarchical REPORT_LUNS structure, storport will still use it to identify the LUNs, even though it does not understand the format. This can result in LUN 0 (the tape drive) being correctly identified , but not LUN 1 (the robotic changer device), so it does not show up in device manager or RSM (Removable Storage Manager).

This can be a PCI-E SCSI host bus adapter, or other slot  or interconnect technology.  For example: a Fibre-Channel HBA in a PCI slot. 

 

 

 

 

Install Scsiport drivers for the HBA rather then Storport. 

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

The Search feature of the Handwriting recognition personalization tool is unavailable, and the accuracy of the tool decreases.

Back to the top

This issue occurs when either of the following conditions is true:

•

Windows Vista is activated after the 30-day activation period This issue can occur when you activate Windows Vista at startup after the 30-day activation period. After you install Windows Vista, there is an activation period of 30 days for activating Windows online. Activation is required. If this period expires, the next time that you start the computer, the activation of Windows Vista becomes mandatory. Otherwise, Windows Vista enters reduced functionality mode. When you activate Windows Vista after the 30-day activation period, the Search feature of the Handwriting recognition personalization tool is turned off during Windows Vista activation, and the Search feature does not turn back on. For more information about reduced functionality mode in Windows Vista, click the following article number to view the article in the Microsoft Knowledge Base: 925582 (/Feedback.aspx?kbNumber=925582/) The behavior of reduced functionality mode in Windows Vista

•

Indexing Options are reset to default settings This issue occurs when the Indexing Options for Windows Vista desktop search are reset to default settings. When this occurs, the Search feature of the Handwriting recognition personalization tool may be turned off.

Back to the top

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To resolve this issue, you have to check the Windows Vista registry for a specific registry subkey. If that subkey is present, you have to delete the InputPersonalization registry subkey, and then you must restart Windows Vista.

Note When you delete the InputPersonalization subkey, this forces the Handwriting recognition personalization tool to re-create the InputPersonalization registry subkey. When the InputPersonalization subkey is re-created, the Search feature is reactivated.

To do this, follow these steps:

1.	Click Start, type regedit in the Start Search box, and then press ENTER. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
2.	Locate and then click the following subkey in the registry: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows Search Gathering Manager Applications Windows PluginManagers 3
3.	If the subkey in step 2 is present, locate and then click the following subkey in the registry: HKEY_LOCAL_MACHINE SOFTWARE Microsoft InputPersonalization
4.	On the Edit menu, click Delete, and then click Yes.
5.	Exit Registry Editor.
6.	Restart Windows Vista.

Back to the top

This article contains information about Microsoft Network Monitor 3. Network Monitor 3 is a protocol analyzer. It enables you to capture, to view, and to analyze network data. You can use it to help troubleshoot problems with applications on the network.

This article contains download and support information, installation notes, and general usage information about Network Monitor 3. Network Monitor 3.1 is the latest version.

Back to the top

Network Monitor 3 is a complete overhaul of the earlier Network Monitor 2.x version. Some key features of Network Monitor 3 include the following:

•	Script-based parser model
•	Simultaneous capture sessions
•	Support for Windows Vista
•	Support for 32-bit platforms and for 64-bit platforms
•	Support for network conversations

Download and support information

To download Network Monitor 3.1 visit the following Microsoft Web sites:

Support information for Network Monitor 3 is located at the following Microsoft Connect Web site:

You must sign in to the Web site by using a Windows Live ID. After you sign in, you can apply to participate in the program. To do this, in the Options column of the table, click Apply next to Network Monitor 3. After you enroll in the program, you have access to newsgroups, and you can submit bug reports.

Installation notes

Network Monitor 3.1 can co-exist with earlier versions of Network Monitor. By default, Network Monitor 3.1 is installed in the %Program Files% Microsoft Network Monitor 3.0 folder. Therefore, conflicts do not occur if an earlier version is installed in a different folder on the computer. When you install Network Monitor 3.1, Network Monitor 3 is uninstalled.

Network Monitor 3.1 includes a new driver for Windows Vista-based computers. This new driver supports new features of the Network Driver Interface Specification (NDIS) 6.0 driver. If you are using tools that rely on Network Monitor 2.x NPPTools, the tools will no longer work. To capture network data in Windows Vista, you must use Network Monitor 3.1. Network Monitor 2.x does not capture network data correctly in Windows Vista.

Suggested hardware to run Network Monitor 3.1 is listed as follows:

•	1 GHz or faster processor
•	1 GB or more memory
•	25 MB free space on the hard disk, and additional hard disk space to store capture files

Network Monitor 3.1 is supported on the following operating systems:

•	Windows Vista
•	Microsoft Windows XP
•	Microsoft Windows Server 2003

Warnings and cautions

Currently, we do not recommend that you run Network Monitor 3 on production systems. In scenarios where load is something to consider, use the command-line version of Network Monitor 3 to capture network data. The command-line version is Nmcap.exe. For more information about Nmcap.exe, see the Nmcap.exe command-line tool section.

Network Monitor 3 may consume lots of system resources. Some things to consider are listed as follows.

•	Disk space When you start a capture session, Network Monitor 3 stores frames in a sequence of capture files that are located in the Temp folder. By default, the size of each capture file is 20 MB. By default, if you do not stop the capture session, Network Monitor 3 continues to store capture files in the Temp folder until the free hard disk space on the computer is less than 2 percent. Then, Network Monitor 3 stops the capture session. You can configure the capture file size, the location where the capture files are stored, the free hard disk space limit, and other capture options. To do this, on the Tools menu, point to Options, and then click the Capture tab.
•	Memory use In addition to capturing data, Network Monitor 3 assigns properties to frames, and then uses the properties to group the frames into conversations. Network Monitor 3 displays the conversations and the associated frames in a tree structure in the Network Conversations pane. The Conversations feature of Network Monitor 3 significantly increases memory use. This may cause the computer to become unresponsive. By default, the Conversations feature is turned off. Some higher-level protocol filters require conversation properties. To turn on the Conversations feature, click the Start Page tab, and then click to select the Enable Conversations check box.
•	Processor utilization The Conversations feature of Network Monitor 3 may significantly increase processor utilization when lots of frames are processed. By default, the Conversations feature is turned off, as mentioned in the Memory use section.

General usage

General usage information for Network Monitor 3 is listed as follows.

•	Capture network data As mentioned earlier, Network Monitor 3 may consume lots of system resources. Therefore, if you want to minimize the effect on system resources that may occur when you use Network Monitor 3 to capture data, use the Nmcap.exe command-line tool to capture data. Network Monitor 3 enables you to collect network data and to view the network data in real time as the data is captured. To start a capture session in Network Monitor 3, click the Start Page tab, click Create a new capture tab, and then either click the Start Capture button, or press F10.
•	Filters Network Monitor 3 uses a simple syntax that is expression-based to filter frames. All frames that match the expression are displayed to the user. For more information about filters, do any of the following: • View the topics in the Using Filters section of the Network Monitor 3 User’s Guide. To do this, on the Help menu, click Contents, and then double-click Using Filters. • On the Help menu, point to How Do I , and then click Use Filters. • Use the Capture Filter tab or the Display Filter tab to view standard filters.
•	Conversations By default, the Conversations feature is turned off. This is the default setting because the Conversations feature can consume lots of memory, especially in scenarios when you capture data for long periods of time. To turn on the Conversations feature, click the Start Page tab, and then click to select the Enable Conversations check box. When you turn on the Conversations feature, frames are grouped and displayed in the Network Conversations pane in a tree structure according to the conversations to which they belong. For example, TCP data that uses the same source port and the same destination port is organized into a group. When you click a node in the Network Conversations pane, the corresponding conversation filter is automatically applied to the frames in the Frame Summary pane. Only frames that belong to that particular conversation are displayed.
•	Nmcap.exe command-line tool The Nmcap.exe command-line tool enables you to configure when you want to start a capture session or to stop a capture session. You can also use the Nmcap.exe command-line tool to created chained captures. Chained captures enable you to create multiple capture files. However, the size of the capture files remains small.
•	Network Parsing Language (NPL) Network Monitor 3 parsers are written in a language specifically to make parser development more straightforward. This also provides a level of protection against potential exploitation from malicious code that may occur if parsers were created as DLL files. NPL provides access to parsers. You can view or modify the parsers that are included in Network Monitor 3.

Common issues

Common issues include the following:

•

Protocols may not parse correctly. This issue may occur if either of the following conditions is true: • The Conversations feature is turned off. Certain protocols depend on conversation properties to store state values that may be needed in later frames. For example, TCP needs conversations to store information about retransmitted frames. The filter for TCP Retransmits will not work unless the Conversations feature is enabled. Similarly, the Server Message Block (SMB) protocol cannot translate the response to a Transact command, because the response does not contain the original command. The information is saved in conversation properties. • The parser and the associated protocol may be available under the Microsoft Communications Protocol Program (MCPP) and the Microsoft Work Group Server Protocol Program (WSPP). To learn more about how to become a licensee, visit the following Microsoft Web site: http://www.microsoft.com/about/legal/intellectualproperty/protocols/mcpp.mspx (http://www.microsoft.com/about/legal/intellectualproperty/protocols/mcpp.mspx) These parsers are considered confidential Microsoft intellectual property and are not distributed publicly. Therefore, these parsers are not part of the publicly-released version of Network Monitor 3

•

You receive one of the following error messages when you run Network Monitor 3 on a Windows Vista-based computer: None of the network adapters are bound to the Netmon driver This network adapter is not configured to capture with Network Monitor This issue occurs if either of the following conditions is true: • You are not running Network Monitor 3 as administrator. • You are not a member of the Netmon Users group. For more information, see the Network Monitor 3 releases notes or see the Operating on Windows Vista topic in Network Monitor 3 Help.

Back to the top

For support information about Network Monitor 3, visit the following Microsoft Web sites:

Back to the top

Source: Microsoft Support

Back to the top

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Back to the top

When you run a full-screen application, such as a game, the Windows Sidebar may flash or appear on top of the application or game briefly.

Back to the top

Full screen applications or games which do not create a full-screen window may cause the Windows Sidebar to unexpectedly receive an indication that the mouse is over the Windows Sidebar. When this happens the Windows Sidebar will try an animation to fade in, which is normal behavior. However, an issue will underlying technologies (layered windows) will cause the Sidebar to flash into view despite the application or game being topmost.

Back to the top

The Windows Sidebar can be closed before you run the application or game, or can be set to be Sidebar is always on top of other windows . Or, the code for the application or game can be modified to create a full-screen window, rather than a topmost window the size of the current screen.

To close the Windows Sidebar, right-click Windows Sidebar, and then click Close Windows Sidebar.

To set the Sidebar is always on top of other windows option, follow these steps:

1. Right-click Windows Sidebar, and then click Properties.

2. Click to select the Sidebar is always on top of other windows check box, and then click OK.

Back to the top

Repro Steps

==========

To reproduce this issue, follow these steps:

1.       Make sure Windows Sidebar is not set to Sidebar is always on top of other windows.

2.        Start application which uses Direct 3D.

3.       Move mouse around, typically toward upper-right of the screen. Sidebar should flash and appear for some time.

Back to the top

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

Applications that perform Kerberos Constrained Delegation (KCD) may not finish the Service-for-User (S4U) process on a computer that is running Windows Server 2008 or Windows Server 2003. This issue occurs in the following scenario:

•	The service domain contains hosts that are permitted to use KCD.
•	The user account that is being delegated resides in a trusted forest.
•	The service domain and the account domain are not root domains in their respective forests.
•	The KERB_S4U_LOGON struct is populated as follows: MessageType = KerbS4ULogon ClientUpn = user name ClientRealm = NB domain name

Back to the top

This issue occurs because the Windows operating system does not have the additional mapping data that is required. By default, the additional mapping data is not populated in Active Directory Domain Services (AD DS). Therefore, the operating system is unable to search the whole forest and the whole trust structure to resolve the mappings between unqualified domains and fully qualified domains.

Back to the top

To resolve this issue, follow these steps:

1.	Use the Active Directory Service Interfaces Edit tool to edit the ms-DS-SPNSuffixes attribute in the following configuration container in AD DS: (CN=Partitions, CN=Configuration, DC=DomainNamingContext) Edit the ms-DS-SPNSuffixes attribute to add NB domain names for all domains in the local domain tree.
2.	Repeat step 1 for each root domain in the trusted forest.
3.	Edit the Name Suffix Routing list in the trusting forest to enable all the following suffixes for all the trusted domains: • *.NBDomain suffixes • *.FQDN suffixes
4.	Repeat step 3 for each forest that trusts the forest that is modified in step 1.
5.	Repeat steps 1 through 4 as necessary for the remaining forests and trees.

Back to the top

This article describes the Microsoft Office Word 2007 issues that are fixed in the hotfix package that is dated May 13, 2008.

•	The issues that the hotfix fixes.
•	The prerequisites for installing the hotfix.
•	Whether you must restart the computer after you install the hotfix.
•	Whether the hotfix is replaced by any other hotfix.
•	Whether you must make any registry changes.
•	The files that the hotfix contains.

Back to the top

Issues that this hotfix package fixes

This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

•	In Microsoft Office Word 2007, when you use a Microsoft Visual Basic for Applications (VBA) macro to communicate with an application by using a COM interface, the macro takes a long time to finish. When you run the same macro in Microsoft Office Word 2003, the macro runs much faster.
•	Consider the following scenario: • In Word 2007, a document that is in the portrait orientation has frames that contain vertical text. • Or, in Word 2007, a document that is in the landscape orientation has frames that contain horizontal text. • You print this document to a regular printer or to a Microsoft XPS Document Writer printer. In this scenario, the text may be missing or truncated. This issue also occurs when you save the document in the Microsoft XPS format or in the PDF format.
•	Consider the following scenario. In Word 2007, you enable the AutoSave feature. You open a document that is located in a share folder. You edit a text box in the document. While you edit the text box, Word 2007 starts to save the AutoRecover information automatically. In this scenario, Word 2007 may close unexpectedly.
•	In Word 2007, when you try to open a Word document that is created by an earlier version of Word, Word 2007 stops responding. However, the document can be opened correctly in Word 2002 and in Word 2003.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

There are no prerequisites for installing this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.
The Global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Download information

File name	File version	File size	Date	Time	Platform
Office-kb952701-fullfile-x86-glb.exe	12.0.6300.5000	15,875,864	09-May-2008	21:25	x86

Microsoft Windows Installer .msp file information

File name	File version	File size	Date	Time	Platform
Word.msp	Not Applicable	13,251,584	10-May-2008	00:58	Not Applicable
Wordconv.msp	Not Applicable	6,216,192	10-May-2008	00:58	Not Applicable

After the hotfix is installed, the Global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:

Word.msp

File name	File version	File size	Date	Time	Platform
Msword.olb	12.0.6300.5000	768,024	07-Dec-2007	01:05	x86
Winword.exe	12.0.6315.5000	349,720	09-May-2008	20:00	x86
Wwlib.dll	12.0.6315.5000	17,495,064	09-May-2008	20:00	x86

Wordconv.msp

File name	File version	File size	Date	Time	Platform
Wordcnv.dll	12.0.6315.5000	4,280,856	09-May-2008	20:00	x86
Wordconv.exe	12.0.6300.5000	24,584	13-Dec-2007	01:08	x86

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

In a C++ Microsoft Jet DAO MFC (CDao) application, insertions and updates may not work on a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008. Additionally, you may receive the following error message:

Note If the application does not capture the exception that is returned by CDao on the insertion or the update, the database will not have the updates that you intended to make.

Back to the top

This problem occurs when all the following conditions are true:

•	The application is written in Microsoft Visual C++ and uses the CDao classes to access a Microsoft Jet database data source.
•	The Use Multi-Byte Character Set value is set for the Character Set project option.
•	The data that the application is inserting or updating was retrieved from a fixed-length defined Text column.
•	The source Text column contains data that is the maximum length that the column allows. For example, a Text(10) column contains a value of 1234567890.
•	Successive insertions or updates occur from the original variable that is returned from the CDaoRecordset object.
•	The target table column is one of the following columns: • The same column from which the original data was retrieved • Another fixed-length column that is defined as a Text column of the same size

Back to the top

To resolve this problem, apply the hotfix that is described in Microsoft Knowledge Base article 943509.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

If you cannot apply the hotfix that is described Microsoft Knowledge Base article 943509, use one of the following methods to work around this problem:

•	Update the application. To do this, copy the retrieved data from the original Visual C++ variable to a new variable. Then, insert or update the data from the new variable.
•	Update the database design. To do this, use one of the following methods: • Modify the column widths to one character larger than any expected data. • Redefine the width as a non-fixed length.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

Back to the top

In Windows Server 2008 or Windows Vista SP1, applications or services that use sockets may stop responding.

For example, a Windows Server 2008-based domain controller randomly becomes unresponsive to LDAP requests. After this issue occurs, you have to restart the server.

This issue occurs because of an error in the TCP/IP (Tcpip.sys) driver.

A thread owns a critical section and calls the closesock function. However, the closesock function never returns. Therefore, other threads cannot access the critical section and stop responding.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, you must have Windows Server 2008 or Windows Vista SP1 installed on the computer.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008 and Windows Vista note

The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and Windows Vista

For all supported x64-based versions of Windows Server 2008 and Windows Vista

For all supported Itanium-based versions of Windows Server 2008

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the Applies to section.

For more information about the closesock function, visit the following Microsoft Web site:

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008

Additional files for all supported Itaniuim-based versions of Windows Server 2008

Source: Microsoft Support

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

On Windows, every volume is assigned a unique volume name in the format  Volume {GUID} , where the GUID uniquely identifies that volume.  Under certain circumstances described in the More Information section, it is possible for a volume to be assigned multiple unique volume names and thus be assigned multiple GUIDs.  When this happens, the GetVolumeNameForVolumeMountPoint() Win32 API function will return one of the assigned names, but it may return a name which cannot be used.

This problem is caused by a bug in the GetVolumeNameForVolumeMountPoint Win32 API function on the products listed in the Applies to section of this article.  It occurs only for volumes that have been assigned multiple unique volume names (GUIDs).

The problem has been corrected in the following products:

• Windows Server 2008  — All versions
• Windows Vista Service Pack 1

 

Applications that must run on the affected products can work around this bug in one of two ways.  The first is to open the volume with the CreateFile Win32 function and then calling the DeviceIoControl function to issue the IOCTL_MOUNTMGR_QUERY_POINTS command. 

The second way is by calling GetVolumeNameForVolumeMountPoint twice.  In the first call, pass the target volume name as documented (usually as a the drive letter in the format X: ) in the lpszVolumeMountPoint parameter.  This call will return one of the assigned unique volume names in the lpszVolumeName parameter.  In the second call, pass the volume name returned by the first call in the lpszVolumeMountPoint parameter.  This will cause GetVolumeNameForVolumeMountPoint to return the expected volume name.

The sample below to see how you might call GetVolumeNameForVolumeMountPoint() twice to get the expected results. 

#include <windows.h>
#include <stdio.h>
#include <tchar.h>

int _tmain(int argc, TCHAR* argv[])
{

    TCHAR szGUID1 [MAX_PATH];
    TCHAR szGUID2 [MAX_PATH];

    if (argc != 2)
    {
        wprintf(L%s <x: > n n, argv[0]);
        return 0;
    }

    _tprintf(TEXT(Calling GetVolumeNameForVolumeMountPoint for %s n), argv[1]);

    // On the first call to GetVolumeNameForVolumeMountPoint
    // pass in whatever you would normally pass in
    if (GetVolumeNameForVolumeMountPoint(argv[1], szGUID1, MAX_PATH))
    {
        _tprintf(TEXT( GUID1: %s n n), szGUID1);
    }

    // On the second call, pass in the Volume Name received from the first
    // call to GetVolumeNameForVolumeMountPoint
    if (GetVolumeNameForVolumeMountPoint(szGUID1, szGUID2, MAX_PATH))
    {
        _tprintf(TEXT( GUID2: %s n n), szGUID2);
    }
    return 0;
}

CreateFile, DeviceIoControl, and IOCTL_MOUNTMGR_QUERY_POINTS are documented in the MSDN Library on http://msdn.microsoft.com (http://msdn.microsoft.com) .

A volume can be multiple unique volume names (and thus multiple GUIDs) when it is used by multiple running installations of Windows.  This could happen in the following scenarios and in similar scenarios where multiple installations of Windows have accessed the volume:

• Dual booting two or more copies of Windows which access the drive.
• Using a volume on a shared disk in a cluster where multiple nodes have accessed the volume.
• Moving the disk which hosts the volume from one computer to another.
• In a SAN environment where the volume was assigned to multiple instances of Windows.

In these situations, each running instance of Windows will assign its own GUID to the volume.  Furthermore, each instance will enumerate all of the volume names and mount points assigned to the volume and thus will see multiple GUIDs.  However, not all GUIDs may be used by the specific instance of Windows that is currently running.  This is why the volume name returned by GetVolumeNameForVolumeMountPoint may be incorrect.

The MOUNTVOL.EXE tool always returns the correct volume name.

 

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

The Search feature of the Handwriting recognition personalization tool is unavailable, and the accuracy of the tool decreases.

Back to the top

This issue occurs when either of the following conditions is true:

•

Windows Vista is activated after the 30-day activation period This issue can occur when you activate Windows Vista at startup after the 30-day activation period. After you install Windows Vista, there is an activation period of 30 days for activating Windows online. Activation is required. If this period expires, the next time that you start the computer, the activation of Windows Vista becomes mandatory. Otherwise, Windows Vista enters reduced functionality mode. When you activate Windows Vista after the 30-day activation period, the Search feature of the Handwriting recognition personalization tool is turned off during Windows Vista activation, and the Search feature does not turn back on. For more information about reduced functionality mode in Windows Vista, click the following article number to view the article in the Microsoft Knowledge Base: 925582 (/Feedback.aspx?kbNumber=925582/) The behavior of reduced functionality mode in Windows Vista

•

Indexing Options are reset to default settings This issue occurs when the Indexing Options for Windows Vista desktop search are reset to default settings. When this occurs, the Search feature of the Handwriting recognition personalization tool may be turned off.

Back to the top

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To resolve this issue, you have to check the Windows Vista registry for a specific registry subkey. If that subkey is present, you have to delete the InputPersonalization registry subkey, and then you must restart Windows Vista.

Note When you delete the InputPersonalization subkey, this forces the Handwriting recognition personalization tool to re-create the InputPersonalization registry subkey. When the InputPersonalization subkey is re-created, the Search feature is reactivated.

To do this, follow these steps:

1.	Click Start, type regedit in the Start Search box, and then press ENTER. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
2.	Locate and then click the following subkey in the registry: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows Search Gathering Manager Applications Windows PluginManagers 3
3.	If the subkey in step 2 is present, locate and then click the following subkey in the registry: HKEY_LOCAL_MACHINE SOFTWARE Microsoft InputPersonalization
4.	On the Edit menu, click Delete, and then click Yes.
5.	Exit Registry Editor.
6.	Restart Windows Vista.

Back to the top