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. Authentication fails for Windows 8.1 or Windows 8 clients that are configured for SSO authentication on a wireless network

Authentication fails for Windows 8.1 or Windows 8 clients that are configured for SSO authentication on a wireless network

View products that this article applies to.

Symptoms

Windows 8.1 or Windows 8 clients that are configured for SSO authentication on a wireless network may not successfully authenticate to the network. This problem occurs most frequently when a user tries to log on by using invalid credentials and then later tries to log on by using valid credentials. This problem occurs only for noncached credentials or during a first-time user logon.

↑ Back to the top

Cause

This problem occurs because the Netlogon and DNS client services rely on notifications to keep network data current. Because these notifications are not delivered in real-time, these services could receive them long after the network is connected. If the network data is not up to date at the time of logon, authentication to the network fails.

↑ Back to the top

Resolution

To resolve this issue in Windows 8.1, install update 2919355.
To resolve this issue in Windows 8, install the hotfix that is described in this article.

Update information for Windows 8.1

For more information about how to obtain update 2919355, click the following article number to view the article in the Microsoft Knowledge Base:
2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014


Hotfix information for Windows 8

A supported hotfix is available from Microsoft Support. 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
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

To apply this hotfix, you must have Windows 8 installed.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top

File information
The English (United States) 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 and Windows Server 2012 file information and notes

Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" 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.2.920 0.16 xxxWindows 8 and Windows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows 8 and Windows Server 2012RTMLDR
  • 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 8 and Windows Server 2012" 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.
For all supported x86-based versions of Windows 8
File nameFile versionFile sizeDateTimePlatform
Authui-ppdlic.xrm-msNot Applicable2,89401-Feb-201405:34Not Applicable
Authui.dll6.2.9200.209312,036,22401-Feb-201404:56x86
Actxprxy.dll6.2.9200.20931753,66401-Feb-201404:56x86
Pdc-mw.ptxmlNot Applicable3,99704-Feb-201323:32Not Applicable
Pdc.sys6.2.9200.2065257,57602-Mar-201309:26x86
Netlogon.dll6.2.9200.20931634,36801-Feb-201404:57x86
Twinui-ppdlic.xrm-msNot Applicable2,88901-Feb-201405:34Not Applicable
Twinui.dll6.2.9200.209318,857,08801-Feb-201404:58x86
Windows.systemtoast.autoplay.lnkNot Applicable1,45406-Feb-201323:26Not Applicable
Windows.systemtoast.share.lnkNot Applicable1,54706-Feb-201323:26Not Applicable
Report.system.wireless.xmlNot Applicable59,62006-Jul-201220:00Not Applicable
Rules.system.wireless.xmlNot Applicable159,93406-Jul-201220:00Not Applicable
Wfdprov.dll6.2.9200.2055525,60006-Nov-201204:24x86
Wlan.mofNot Applicable12,88006-Jul-201220:00Not Applicable
Wlanapi.dll6.2.9200.20931203,26401-Feb-201404:58x86
Wlanhlp.dll6.2.9200.205559,72806-Nov-201204:00x86
Wlanmsm.dll6.2.9200.20931386,56001-Feb-201404:58x86
Wlansec.dll6.2.9200.20555375,29606-Nov-201204:24x86
Wlansvc.dll6.2.9200.209311,204,22401-Feb-201404:58x86
Wlansvc.ptxmlNot Applicable31,35205-Nov-201223:36Not Applicable
For all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Authui-ppdlic.xrm-msNot Applicable2,89401-Feb-201407:26Not Applicable
Authui.dll6.2.9200.209312,304,51201-Feb-201405:19x64
Actxprxy.dll6.2.9200.209312,146,81601-Feb-201405:19x64
Pdc-mw.ptxmlNot Applicable3,99702-Feb-201301:37Not Applicable
Pdc.sys6.2.9200.2065169,86402-Mar-201310:48x64
Netlogon.dll6.2.9200.20931743,93601-Feb-201405:20x64
Twinui-ppdlic.xrm-msNot Applicable2,88901-Feb-201407:26Not Applicable
Twinui.dll6.2.9200.2093110,098,68801-Feb-201405:21x64
Windows.systemtoast.autoplay.lnkNot Applicable1,45406-Feb-201323:30Not Applicable
Windows.systemtoast.share.lnkNot Applicable1,54706-Feb-201323:30Not Applicable
Report.system.wireless.xmlNot Applicable59,62006-Jul-201220:02Not Applicable
Rules.system.wireless.xmlNot Applicable159,93406-Jul-201220:02Not Applicable
Wfdprov.dll6.2.9200.2055530,72006-Nov-201204:25x64
Wlan.mofNot Applicable12,88006-Jul-201220:02Not Applicable
Wlanapi.dll6.2.9200.20931273,92001-Feb-201405:21x64
Wlanhlp.dll6.2.9200.205559,72806-Nov-201204:03x64
Wlanmsm.dll6.2.9200.20555470,01606-Nov-201204:25x64
Wlansec.dll6.2.9200.20555446,46406-Nov-201204:25x64
Wlansvc.dll6.2.9200.209311,387,00801-Feb-201405:21x64
Wlansvc.ptxmlNot Applicable31,35205-Nov-201223:35Not Applicable

Additional file information

Additional file information for Windows 8 and for Windows Server 2012

Additional files for all supported x86-based versions of Windows 8
File nameX86_microsoft-windows-a..on-authui-component_31bf3856ad364e35_6.2.9200.20931_none_da3f0bcdfa36389d.manifest
File versionNot Applicable
File size64,443
Date (UTC)01-Feb-2014
Time (UTC)05:36
PlatformNot Applicable
File nameX86_microsoft-windows-activexproxy_31bf3856ad364e35_6.2.9200.20931_none_0f75f457d4a8d52a.manifest
File versionNot Applicable
File size811,870
Date (UTC)01-Feb-2014
Time (UTC)05:52
PlatformNot Applicable
File nameX86_microsoft-windows-pdc_31bf3856ad364e35_6.2.9200.20931_none_a49ab0e64692a4c5.manifest
File versionNot Applicable
File size52,692
Date (UTC)03-Feb-2014
Time (UTC)19:31
PlatformNot Applicable
File nameX86_microsoft-windows-security-netlogon_31bf3856ad364e35_6.2.9200.20931_none_fb1f782b225866eb.manifest
File versionNot Applicable
File size38,622
Date (UTC)01-Feb-2014
Time (UTC)05:22
PlatformNot Applicable
File nameX86_microsoft-windows-twinui_31bf3856ad364e35_6.2.9200.20931_none_710f3898a3bfa836.manifest
File versionNot Applicable
File size96,585
Date (UTC)01-Feb-2014
Time (UTC)05:36
PlatformNot Applicable
File nameX86_microsoft-windows-wlansvc_31bf3856ad364e35_6.2.9200.20931_none_99ac033aef449fcc.manifest
File versionNot Applicable
File size219,982
Date (UTC)03-Feb-2014
Time (UTC)19:31
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 8 and of Windows Server 2012
File nameAmd64_microsoft-windows-a..on-authui-component_31bf3856ad364e35_6.2.9200.20931_none_365da751b293a9d3.manifest
File versionNot Applicable
File size64,451
Date (UTC)01-Feb-2014
Time (UTC)07:56
PlatformNot Applicable
File nameAmd64_microsoft-windows-activexproxy_31bf3856ad364e35_6.2.9200.20931_none_6b948fdb8d064660.manifest
File versionNot Applicable
File size811,872
Date (UTC)01-Feb-2014
Time (UTC)08:12
PlatformNot Applicable
File nameAmd64_microsoft-windows-pdc_31bf3856ad364e35_6.2.9200.20931_none_00b94c69fef015fb.manifest
File versionNot Applicable
File size52,696
Date (UTC)03-Feb-2014
Time (UTC)20:45
PlatformNot Applicable
File nameAmd64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.2.9200.20931_none_573e13aedab5d821.manifest
File versionNot Applicable
File size38,628
Date (UTC)01-Feb-2014
Time (UTC)08:01
PlatformNot Applicable
File nameAmd64_microsoft-windows-twinui_31bf3856ad364e35_6.2.9200.20931_none_cd2dd41c5c1d196c.manifest
File versionNot Applicable
File size96,599
Date (UTC)01-Feb-2014
Time (UTC)07:56
PlatformNot Applicable
File nameAmd64_microsoft-windows-wlansvc_31bf3856ad364e35_6.2.9200.20931_none_f5ca9ebea7a21102.manifest
File versionNot Applicable
File size219,986
Date (UTC)03-Feb-2014
Time (UTC)20:45
PlatformNot Applicable
File nameWow64_microsoft-windows-security-netlogon_31bf3856ad364e35_6.2.9200.20931_none_6192be010f169a1c.manifest
File versionNot Applicable
File size19,021
Date (UTC)01-Feb-2014
Time (UTC)05:22
PlatformNot Applicable
File nameWow64_microsoft-windows-twinui_31bf3856ad364e35_6.2.9200.20931_none_d7827e6e907ddb67.manifest
File versionNot Applicable
File size90,888
Date (UTC)01-Feb-2014
Time (UTC)05:36
PlatformNot Applicable
File nameWow64_microsoft-windows-wlansvc_31bf3856ad364e35_6.2.9200.20931_none_001f4910dc02d2fd.manifest
File versionNot Applicable
File size216,373
Date (UTC)03-Feb-2014
Time (UTC)20:45
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

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

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2928248
Revision : 1
Created on : 1/7/2017
Published on : 4/15/2014
Exists online : False
Views : 233