FIX: The pointer may not always become the hourglass symbol on a device that is running Windows CE .NET 4.2

On a device that is running Microsoft Windows CE .NET 4.2, the pointer may not always become the hourglass symbol when the device is running an application. The pointer does not become the hourglass symbol until you restart the device.

Note The pointer should always become the hourglass symbol when an application is busy.

This problem occurs because a race condition in the initialization of the Graphics, Windowing, and Events Subsystem (GWES) pointer window prevents the pointer from becoming the hourglass symbol.

Software update information

A supported software update is now available from Microsoft as Windows CE .NET 4.2 Platform Builder Monthly Update (October 2006). You can confirm this by scrolling to the "File information" section of this article. The package file name contains the product version, date, Knowledge Base article number, and processor type. The package file name format is:For example: Wincepb50-060503-kb917590-armv4i.msi is the ARMV4i Windows CE 5.0 Platform Builder fix that is documented in KB article 917590 and that is contained in the May 2006 monthly update. To resolve this problem immediately, click the following article number for information about obtaining Windows CE Platform Builder and core operating system software updates:

File information

The English version of this package has the file attributes (or later file attributes) that are listed in the following table. The English version of this update 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.

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

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