OOBE crashes when you enter SIM card PIN in Windows 8.1

This article describes an issue that occurs on a Windows 8.1-based device in the out-of-box experience (OOBE). A hotfix is available to fix this issue. The hotfix has a prerequisite.
Symptoms
Consider the following scenario:
  • You have a Windows 8.1-based device connected to a network. 
  • Access to the network is controlled by a SIM card.
  • The SIM card has a PIN associated with it. The PIN must be entered before network access is allowed.
  • You start the device for the first time.
In this scenario, when you're prompted to enter the PIN, an error occurs during OOBE and OOBE crashes. 
Resolution
To fix this issue, we have released a hotfix. Even though this issue is observed only in Windows 8.1, the hotfix also applies to Windows RT 8.1 and Windows Server 2012 R2.

Note This hotfix has to be installed by the OEM. You can’t install this hotfix on your own because it has to be in place before OOBE starts.

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.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get 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 don't 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 don't see your language, it's because a hotfix isn't available for that language.

Prerequisites

To apply this hotfix, 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 use the hotfix in this package, you don't 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 doesn't 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 and Windows Server 2012 R2 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's 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 and Windows Server 2012 R2RTMGDR
    6.3.960 0.17xxxWindows 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 aren't listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Wwanconn.dll8.1.9600.18036373,24822-Aug-201515:53x86
Wwanmm.dll8.1.9600.180391,119,23226-Aug-201517:53x86
Wwanpref.dll8.1.9600.1741541,98429-Oct-201401:38x86
Wwanui.ptxmlNot applicable3,23721-Aug-201323:54Not applicable
For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Wwanconn.dll8.1.9600.18036455,68022-Aug-201515:59x64
Wwanmm.dll8.1.9600.180391,156,60826-Aug-201514:18x64
Wwanpref.dll8.1.9600.1741550,68829-Oct-201402:17x64
Wwanui.ptxmlNot applicable3,23722-Aug-201306:58Not applicable
For all supported Windows RT 8.1
File nameFile versionFile sizeDateTimePlatform
Wwanconn.dll8.1.9600.18036331,77622-Aug-201515:41Not applicable
Wwanmm.dll8.1.9600.180391,096,70426-Aug-201514:17Not applicable
Wwanpref.dll8.1.9600.1638440,96022-Aug-201302:50Not applicable
Wwanui.ptxmlNot applicable3,23721-Aug-201323:44Not applicable

Additional file information

Additional file information for Windows 8.1 and for Windows Server 2012 R2
Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_f1a86543a2668e0325c0b51f712cbb21_31bf3856ad364e35_6.3.9600.18039_none_125fab2a00ae81e3.manifest
File versionNot applicable
File size694
Date (UTC)27-Aug-2015
Time (UTC)02:51
PlatformNot applicable
File nameX86_microsoft-windows-wwanui_31bf3856ad364e35_6.3.9600.18039_none_0691173322707eae.manifest
File versionNot applicable
File size42,908
Date (UTC)27-Aug-2015
Time (UTC)02:55
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File propertyValue
File nameAmd64_d92d209b8322fe677f938222c95438c6_31bf3856ad364e35_6.3.9600.18039_none_1fbf1f00fe5d4d4b.manifest
File versionNot applicable
File size698
Date (UTC)27-Aug-2015
Time (UTC)02:51
PlatformNot applicable
File nameAmd64_microsoft-windows-wwanui_31bf3856ad364e35_6.3.9600.18039_none_62afb2b6dacdefe4.manifest
File versionNot applicable
File size42,912
Date (UTC)27-Aug-2015
Time (UTC)02:58
PlatformNot applicable
Additional files for all supported Windows RT 8.1
File propertyValue
File nameArm_93e61eed4bc0cf919119e32a8bf0de25_31bf3856ad364e35_6.3.9600.18039_none_22736cf0423b2bcf.manifest
File versionNot applicable
File size694
Date (UTC)27-Aug-2015
Time (UTC)02:51
PlatformNot applicable
File nameArm_microsoft-windows-wwanui_31bf3856ad364e35_6.3.9600.18039_none_0693898b226d9d74.manifest
File versionNot applicable
File size42,908
Date (UTC)27-Aug-2015
Time (UTC)02:51
PlatformNot applicable
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
See the terminology that Microsoft uses to describe software updates.
Properties

Article ID: 3084953 - Last Review: 10/13/2015 22:47:00 - Revision: 1.0

Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1, Windows RT 8.1

  • kbqfe kbsurveynew kbfix kbautohotfix kbhotfixserver kbexpertiseinter KB3084953
Feedback