Credentials for an 802.1X EAP wireless connection are lost after Windows RT 8.1 OOBE

Symptoms

Consider the following scenario:

You start a Windows RT 8.1-based device in the out-of-box experience (OOBE).
You use the necessary credentials to connect the device to an 802.1X Extensible Authentication Protocol (EAP) wireless connection.
The EAP wireless connection uses per-user credentials authentication.
After OOBE finishes, the device restarts.
You log on to the device.

In this scenario, the credentials are lost. Therefore, the wireless connection is lost.

Note This issue does not occur if the 802.1X EAP network uses machine credentials.

Cause

This issue occurs because an uninitialized variable causes a registry key to not be read.

Resolution

Update information

How to obtain this update

To resolve this issue, install update rollup 2903939. For more information about how to obtain this update rollup package, click the following article number to go to the article in the Microsoft Knowledge Base:

2903939 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: December 2013

Prerequisites

To apply this update, you must be running Windows RT 8.1.

Registry information

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

Restart requirement

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

Update replacement information

This update does not replace a previously released update.

File information

The global version of this update 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 RT 8.1 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:
Version Product Milestone Service branch
6.3.960 0.16 xxx Windows RT 8.1 RTM GDR
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows RT 8.1" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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.

Version	Product	Milestone	Service branch
6.3.960 0.16 xxx	Windows RT 8.1	RTM	GDR

For Windows RT 8.1

File name	File version	File size	Date	Time	Platform
Credentialmigrationhandler.dll	6.3.9600.16443	26,624	24-Oct-2013	08:32	Not applicable

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

Additional file information

Additional file information for Windows RT 8.1

File property	Value
File name	Arm_760774ab0019ae0521f740e228814e2a_31bf3856ad364e35_6.3.9600.16443_none_75cd644e5257d6ee.manifest
File version	Not applicable
File size	714
Date (UTC)	24-Oct-2013
Time (UTC)	23:33
SHA-1 hash	Not applicable
MD5 hash	Not applicable
File name	Arm_microsoft-windows-c..ialmigrationhandler_31bf3856ad364e35_6.3.9600.16443_none_08c30eee126372e1.manifest
File version	Not applicable
File size	3,953
Date (UTC)	24-Oct-2013
Time (UTC)	12:00
SHA-1 hash	Not applicable
MD5 hash	Not applicable

Properties

Article ID: 2903601 - Last Review: Dec 10, 2013 - Revision: 1

Applies to

Windows RT 8.1

Feedback

Was this information helpful?