Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: Candidates are not displayed for a short input sequence in the IME in Windows Embedded Compact 2013

FIX: Candidates are not displayed for a short input sequence in the IME in Windows Embedded Compact 2013

View products that this article applies to.

Introduction

This article describes an issue in which candidates are not displayed for a short input sequence in the IME in Windows Embedded Compact 2013. An update is available to resolve this issue. Before you install this update, all previously issued updates for this product must be installed.

↑ Back to the top

Symptoms

You use the Input Method Editor (IME) to enter characters on a device that's running Windows Embedded Compact 2013. After you enter a long sequence of characters, candidates are not displayed for a short input sequence.

↑ Back to the top

Software update information

Download information

Windows Embedded Compact 2013 Monthly Update (March 2016) is now available from Microsoft. To download this Windows Embedded Compact 2013 monthly update, go to Microsoft OEM Online or MyOEM.

Prerequisites

This update is supported only if all previously issued updates for this product have also been installed.

Restart requirement

After you apply this 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 other 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.

Files that are included in this update package
File nameFile sizeDateTimePath
Msimesp.map47,07714-Mar-201609:39Public\Shell\Oak\Target\X86\Checked
Msimepy.map44,51414-Mar-201609:39Public\Shell\Oak\Target\X86\Checked
Msimepy.rel9,67614-Mar-201609:39Public\Shell\Oak\Target\X86\Checked
Msimesp.rel10,86514-Mar-201609:39Public\Shell\Oak\Target\X86\Checked
Msimesp.dll139,26414-Mar-201609:39Public\Shell\Oak\Target\X86\Checked
Msimepy.dll131,07214-Mar-201609:39Public\Shell\Oak\Target\X86\Checked
Msimesp.map40,74014-Mar-201609:39Public\Shell\Oak\Target\X86\Retail
Msimepy.map39,32214-Mar-201609:39Public\Shell\Oak\Target\X86\Retail
Msimepy.rel8,02314-Mar-201609:39Public\Shell\Oak\Target\X86\Retail
Msimesp.rel9,00914-Mar-201609:39Public\Shell\Oak\Target\X86\Retail
Msimesp.dll135,16814-Mar-201609:39Public\Shell\Oak\Target\X86\Retail
Msimepy.dll126,97614-Mar-201609:39Public\Shell\Oak\Target\X86\Retail
Msimesp.map48,50814-Mar-201609:38Public\Shell\Oak\Target\X86\Debug
Msimepy.map45,94514-Mar-201609:38Public\Shell\Oak\Target\X86\Debug
Msimepy.rel12,17014-Mar-201609:38Public\Shell\Oak\Target\X86\Debug
Msimesp.rel13,67814-Mar-201609:38Public\Shell\Oak\Target\X86\Debug
Msimesp.dll155,64814-Mar-201609:38Public\Shell\Oak\Target\X86\Debug
Msimepy.dll143,36014-Mar-201609:38Public\Shell\Oak\Target\X86\Debug
Msimesp.map70,28314-Mar-201609:41Public\Shell\Oak\Target\Armv7\Checked
Msimepy.map66,08514-Mar-201609:41Public\Shell\Oak\Target\Armv7\Checked
Msimepy.rel5,44214-Mar-201609:41Public\Shell\Oak\Target\Armv7\Checked
Msimesp.rel6,02214-Mar-201609:41Public\Shell\Oak\Target\Armv7\Checked
Msimesp.dll139,26414-Mar-201609:41Public\Shell\Oak\Target\Armv7\Checked
Msimepy.dll131,07214-Mar-201609:41Public\Shell\Oak\Target\Armv7\Checked
Msimesp.map60,25414-Mar-201609:40Public\Shell\Oak\Target\Armv7\Retail
Msimepy.map57,50114-Mar-201609:40Public\Shell\Oak\Target\Armv7\Retail
Msimepy.rel4,68814-Mar-201609:40Public\Shell\Oak\Target\Armv7\Retail
Msimesp.rel5,15214-Mar-201609:40Public\Shell\Oak\Target\Armv7\Retail
Msimesp.dll139,26414-Mar-201609:40Public\Shell\Oak\Target\Armv7\Retail
Msimepy.dll126,97614-Mar-201609:40Public\Shell\Oak\Target\Armv7\Retail
Msimesp.map89,89514-Mar-201609:39Public\Shell\Oak\Target\Armv7\Debug
Msimepy.map84,93814-Mar-201609:39Public\Shell\Oak\Target\Armv7\Debug
Msimepy.rel5,93514-Mar-201609:39Public\Shell\Oak\Target\Armv7\Debug
Msimesp.rel6,57314-Mar-201609:39Public\Shell\Oak\Target\Armv7\Debug
Msimesp.dll155,64814-Mar-201609:39Public\Shell\Oak\Target\Armv7\Debug
Msimepy.dll147,45614-Mar-201609:39Public\Shell\Oak\Target\Armv7\Debug

↑ Back to the top

Status

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

↑ Back to the top

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kbqfe, kbsurveynew, kbnotautohotfix, kbfix, kbexpertiseadvanced, atdownload, kb

↑ Back to the top

Article Info
Article ID : 3148978
Revision : 1
Created on : 1/7/2017
Published on : 4/18/2016
Exists online : False
Views : 147