The display setting of a Windows Embedded CE 6.0 R3-based device changes when you connect the device to a Windows-based computer


Symptoms


Consider the following scenario:
  • You run the Pictor service on a Windows Embedded CE 6.0 R3-based device.
  • The device supports multiple display resolutions.
  • You connect the device to a Windows-based computer.
In this scenario, the display setting of the device changes.

Resolution


Software update information

A supported software update is now available from Microsoft as Windows Embedded CE 6.0 Platform Builder Monthly Update (March 2011). 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:
Product version-yymmdd-kbnnnnnn-processor type
For example: Wincepb50-060503-kb917590-armv4i.msi is the ARMV4i Windows Embedded 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 Embedded CE Platform Builder and core operating system software updates:
837392 How to locate core operating system fixes for Microsoft Windows Embedded CE Platform Builder products


Note This Windows Embedded CE 6.0 Monthly Update is also available for download from the following Microsoft Download Center website:

The update adds a new DisableDisplayChange registry key in the DWORD type to the following path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PictorService
The default value of the registry key is 0.

If the DisableDisplayChange registry key is set to 1, the current resolution of the device is reported to the computer and the display setting of the device does not change.

If the DisableDisplayChange registry key is set to 0, the behavior does not change. All resolutions that the device supports are reported to the computer and the display setting of the device changes to the display setting of the computer.

Prerequisites

To apply this software update, you must have all previously issued software updates for this product installed.

Restart requirement

After you install this software update, you must perform a clean build of the whole platform. To do this, use one of the following methods:
  • On the Build menu, click Clean Solution, and then click Build Solution.
  • On the Build menu, click Rebuild Solution.
You do not have to restart the computer after you apply this software update.

Update replacement information

This update does not replace any updates.

File information

The English version of this software update package 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.
Installer files
File nameFile sizeDateTime
Wincepb60-110311-kb2475955-armv4i.msi841,21611-Mar-201121:18
Wincepb60-110311-kb2475955-mipsii.msi831,48811-Mar-201121:18
Wincepb60-110311-kb2475955-mipsii_fp.msi832,00011-Mar-201121:18
Wincepb60-110311-kb2475955-mipsiv.msi835,07211-Mar-201121:18
Wincepb60-110311-kb2475955-mipsiv_fp.msi835,58411-Mar-201121:18
Wincepb60-110311-kb2475955-sh4.msi821,24811-Mar-201121:18
Wincepb60-110311-kb2475955-x86.msi799,23211-Mar-201121:18
Files that are included in this hotfix package
File nameFile sizeDateTimePath
Windows embedded ce 6.0_update_kb2475955.htm8,85711-Mar-201121:26110311_kb2475955
Pictorservice.lib681,80210-Mar-201115:42Public\Rdp\Oak\Lib\Armv4i\Debug
Pictorservice.lib543,79410-Mar-201115:42Public\Rdp\Oak\Lib\Armv4i\Retail
Pictorservice.lib675,00610-Mar-201115:42Public\Rdp\Oak\Lib\Mipsii\Debug
Pictorservice.lib537,89610-Mar-201115:42Public\Rdp\Oak\Lib\Mipsii\Retail
Pictorservice.lib675,07610-Mar-201115:43Public\Rdp\Oak\Lib\Mipsii_fp\Debug
Pictorservice.lib538,04610-Mar-201115:43Public\Rdp\Oak\Lib\Mipsii_fp\Retail
Pictorservice.lib678,66010-Mar-201115:43Public\Rdp\Oak\Lib\Mipsiv\Debug
Pictorservice.lib541,46610-Mar-201115:43Public\Rdp\Oak\Lib\Mipsiv\Retail
Pictorservice.lib678,73010-Mar-201115:44Public\Rdp\Oak\Lib\Mipsiv_fp\Debug
Pictorservice.lib541,61610-Mar-201115:43Public\Rdp\Oak\Lib\Mipsiv_fp\Retail
Pictorservice.lib621,98010-Mar-201115:44Public\Rdp\Oak\Lib\Sh4\Debug
Pictorservice.lib511,72010-Mar-201115:44Public\Rdp\Oak\Lib\Sh4\Retail
Pictorservice.lib610,33010-Mar-201115:42Public\Rdp\Oak\Lib\X86\Debug
Pictorservice.lib512,03210-Mar-201115:42Public\Rdp\Oak\Lib\X86\Retail

Status


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

More Information


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

824684 Description of the standard terminology that is used to describe Microsoft software updates