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.

Start screen customization is disabled for a Windows Embedded 8.1 Industry Pro-based computer


View products that this article applies to.

This article describes a hotfix that re-enables the Start screen customization in Windows Embedded 8.1 Industry Pro. For detailed information about how to customize the Start screen, see the More information section.

↑ Back to the top


About this hotfix

This hotfix allows the Start screen customization policy to be enabled on non-domain-joined Windows Embedded 8.1 Industry Pro installations. This functionality will continue to be limited to domain-joined computers for other Windows 8.1 Pro-based installations as that is described in KB article 3008289.

↑ Back to the top


Hotfix information

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

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 website: 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

There is no prerequisite to install this hotfix.

Registry information

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

Restart requirement

You may 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 global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 8.1 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • 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.16 xxxWindows 8.1 RTMGDR
    6.3.960 0.17xxxWindows 8.1 RTMGDR
  • 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 all supported x86-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Shell32.dll6.3.9600.1795819,794,38417-Jul-201521:59x86
Windows.systemtoast.explorer.lnkNot applicable1,45021-Aug-201323:49Not applicable
Windowsshell.manifestNot applicable67018-Jun-201312:32Not applicable
For all supported x64-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Shell32.dll6.3.9600.1795822,369,60817-Jul-201521:58x64
Windows.systemtoast.explorer.lnkNot applicable1,45022-Aug-201306:54Not applicable
Windowsshell.manifestNot applicable67018-Jun-201315:00Not applicable
Shell32.dll6.3.9600.1795819,794,38417-Jul-201521:59x86

Additional file information

Additional file information for Windows 8.1
Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_2da088e53d41f2ecce029586105894f7_31bf3856ad364e35_6.3.9600.17958_none_cb16f7d6b4ffe560.manifest
File versionNot applicable
File size695
Date (UTC)17-Jul-2015
Time (UTC)22:12
PlatformNot applicable
File nameX86_microsoft-windows-shell32_31bf3856ad364e35_6.3.9600.17958_none_00ed54ed2d799d11.manifest
File versionNot applicable
File size1,360,120
Date (UTC)17-Jul-2015
Time (UTC)22:18
PlatformNot applicable
File nameWindowsshell.manifest
File versionNot applicable
File size670
Date (UTC)18-Jun-2013
Time (UTC)12:32
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1
File propertyValue
File nameAmd64_5fed6d1f1a6b62061d0c72431f2d11c5_31bf3856ad364e35_6.3.9600.17958_none_0a9ef108045213e3.manifest
File versionNot applicable
File size699
Date (UTC)17-Jul-2015
Time (UTC)22:12
PlatformNot applicable
File nameAmd64_eb43834d6459271d3abb9f0143fc4187_31bf3856ad364e35_6.3.9600.17958_none_d5cf264ccbf78260.manifest
File versionNot applicable
File size699
Date (UTC)17-Jul-2015
Time (UTC)22:12
PlatformNot applicable
File nameAmd64_microsoft-windows-shell32_31bf3856ad364e35_6.3.9600.17958_none_5d0bf070e5d70e47.manifest
File versionNot applicable
File size1,352,062
Date (UTC)17-Jul-2015
Time (UTC)22:21
PlatformNot applicable
File nameWow64_microsoft-windows-shell32_31bf3856ad364e35_6.3.9600.17958_none_67609ac31a37d042.manifest
File versionNot applicable
File size1,321,915
Date (UTC)17-Jul-2015
Time (UTC)22:21
PlatformNot applicable
File nameWindowsshell.manifest
File versionNot applicable
File size670
Date (UTC)18-Jun-2013
Time (UTC)15:00
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


References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kbqfe, kbsurveynew, kbfix, kbautohotfix, kbhotfixserver, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3071345
Revision : 1
Created on : 1/7/2017
Published on : 8/11/2015
Exists online : False
Views : 213