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.

HKSCS characters are displayed incorrectly by PDF APIs in Windows


View products that this article applies to.

This article describes an issue that occurs when you use a Windows Store application that uses the PDF APIs to display Hong Kong Supplementary Character Set (HKSCS) characters in Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2. You can resolve this issue by using the update in this article. Before you install this update, check out the Prerequisites section.

↑ Back to the top


How to obtain this update

Important If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.

Method 1: Windows Update

This update is provided as an Important update on Windows Update. For more information about how to run Windows Update, see How to get an update through Windows Update.

Method 2: Microsoft Download Center

The following files are available for download from the Microsoft Download Center:.
Operating systemUpdate
All supported x86-based versions of Windows 8.1Download Download the package now.
All supported x64-based versions of Windows 8.1 Download Download the package now.
All supported x64-based versions of Windows Server 2012 R2Download Download the package now.
Note The update for Windows RT 8.1 can be obtained only from Windows Update.

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 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.

Update detail information

Prerequisites

To apply this update, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.

Registry information

To install this update, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this update.

Update replacement information

This update does not replace a previously released update.

Windows 8.1 and Windows Server 2012 R2 file information notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.3.960 0.17xxxWindows RT 8.1, Windows 8.1, and Windows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For more information about the update's file information, see the "File information" section.

↑ Back to the top


File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.
Windows8.1 file information
ARM Windows8.1
File nameFile versionFile sizeDateTimePlatform
Windows.data.pdf.dll6.3.9600.178195,608,44803-May-201514:52Not Applicable
x86 Windows8.1
File nameFile versionFile sizeDateTimePlatform
Windows.data.pdf.dll6.3.9600.178195,264,38403-May-201514:57x86
x64 Windows8.1
File nameFile versionFile sizeDateTimePlatform
Windows.data.pdf.dll6.3.9600.178197,784,44803-May-201515:07x64
Windows.data.pdf.dll6.3.9600.178195,264,38403-May-201514:57x86

Additional file information
ARM Windows8.1
File propertyValue
File nameArm_58b0bc73ede3c638b930eccefeaa298b_31bf3856ad364e35_6.3.9600.17822_none_7518ca9e9622ed74.manifest
File versionNot Applicable
File size696
Date (UTC)06-May-2015
Time (UTC)00:30
PlatformNot Applicable
File nameArm_microsoft-windows-data-pdf_31bf3856ad364e35_6.3.9600.17822_none_8b35cb70af16c91d.manifest
File versionNot Applicable
File size9,720
Date (UTC)05-May-2015
Time (UTC)14:54
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size1,594
Date (UTC)06-May-2015
Time (UTC)00:30
PlatformNot Applicable
x86 Windows8.1
File propertyValue
File nameUpdate.mum
File versionNot Applicable
File size1,594
Date (UTC)06-May-2015
Time (UTC)00:30
PlatformNot Applicable
File nameX86_140c5f00edafb444e81eedef7ed9e978_31bf3856ad364e35_6.3.9600.17822_none_f0880eb270e2a7c5.manifest
File versionNot Applicable
File size696
Date (UTC)06-May-2015
Time (UTC)00:30
PlatformNot Applicable
File nameX86_microsoft-windows-data-pdf_31bf3856ad364e35_6.3.9600.17822_none_8b335918af19aa57.manifest
File versionNot Applicable
File size9,720
Date (UTC)05-May-2015
Time (UTC)14:57
PlatformNot Applicable
x64 Windows8.1
File propertyValue
File nameAmd64_140c5f00edafb444e81eedef7ed9e978_31bf3856ad364e35_6.3.9600.17822_none_4ca6aa36294018fb.manifest
File versionNot Applicable
File size698
Date (UTC)06-May-2015
Time (UTC)00:30
PlatformNot Applicable
File nameAmd64_dbf405c244a42e0a457a19ced72ba63d_31bf3856ad364e35_6.3.9600.17822_none_6a0b74886944fae2.manifest
File versionNot Applicable
File size700
Date (UTC)06-May-2015
Time (UTC)00:30
PlatformNot Applicable
File nameAmd64_microsoft-windows-data-pdf_31bf3856ad364e35_6.3.9600.17822_none_e751f49c67771b8d.manifest
File versionNot Applicable
File size9,724
Date (UTC)05-May-2015
Time (UTC)15:08
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,281
Date (UTC)06-May-2015
Time (UTC)00:30
PlatformNot Applicable
File nameX86_microsoft-windows-data-pdf_31bf3856ad364e35_6.3.9600.17822_none_8b335918af19aa57.manifest
File versionNot Applicable
File size9,720
Date (UTC)05-May-2015
Time (UTC)14:57
PlatformNot Applicable

↑ 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


More Information

Cause

This issue occurs because the character glyph has a Unicode representation that is greater than 65,535. Therefore, it requires two UTF-16 strings or one UTF-32 string to represent the glyph correctly.

↑ Back to the top


References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kbfix, kbsurveynew, kbexpertiseinter, atdownload, kb

↑ Back to the top

Article Info
Article ID : 3049989
Revision : 2
Created on : 4/9/2020
Published on : 4/9/2020
Exists online : False
Views : 228