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.

No Wi-Fi connection if a Wi-Fi profile uses two or more SSIDs in Windows 8.1


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have set up a wireless (Wi-Fi) network profile that contains two or more service set identifiers (SSIDs) that are pushed to a Windows 8.1-based computer by using a Group Policy Object (GPO).
  • You connect the Windows 8.1-based computer to the Wi-Fi profile.
  • You put the computer into sleep mode, and then you wake up the computer after three minutes.

In this scenario, the Wi-Fi connection cannot be established.

↑ Back to the top


Resolution

Hotfix information

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: 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 update in Windows 8.1 or Windows Server 2012 R2, you must first have update 2919355 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.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" 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.1" 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.17 xxxWindows 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 for Windows 8.1 and Windows Server 2012 R2" 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.1
File nameFile versionFile sizeDateTimePlatform
Nwifi.sys6.3.9600.17793375,80808-Apr-201503:02x86
Proximityservice.dll6.3.9600.17415248,83229-Oct-201400:56x86
Report.system.wireless.xmlNot Applicable59,62018-Jun-201312:37Not Applicable
Rules.system.wireless.xmlNot Applicable159,93418-Jun-201312:37Not Applicable
Wfdprov.dll6.3.9600.1741524,06429-Oct-201400:58x86
Wlan.mofNot Applicable12,88018-Jun-201312:37Not Applicable
Wlanapi.dll6.3.9600.17415238,08029-Oct-201400:53x86
Wlanhlp.dll6.3.9600.1741511,26429-Oct-201402:04x86
Wlanmsm.dll6.3.9600.17415304,12829-Oct-201400:49x86
Wlansec.dll6.3.9600.17415383,48829-Oct-201401:01x86
Wlansvc.dll6.3.9600.177931,326,08008-Apr-201501:46x86
Wlansvc.ptxmlNot Applicable31,35221-Aug-201323:39Not Applicable
Wlansvcpal.dll6.3.9600.1741514,84829-Oct-201401:02x86
For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Nwifi.sys6.3.9600.17793445,44008-Apr-201504:28x64
Proximityservice.dll6.3.9600.17415301,56829-Oct-201401:14x64
Report.system.wireless.xmlNot Applicable59,62018-Jun-201315:09Not Applicable
Rules.system.wireless.xmlNot Applicable159,93418-Jun-201315:09Not Applicable
Wfdprov.dll6.3.9600.1741528,67229-Oct-201401:17x64
Wlan.mofNot Applicable12,88018-Jun-201315:09Not Applicable
Wlanapi.dll6.3.9600.17415302,08029-Oct-201401:10x64
Wlanhlp.dll6.3.9600.1741511,26429-Oct-201402:49x64
Wlanmsm.dll6.3.9600.17415374,27229-Oct-201401:03x64
Wlansec.dll6.3.9600.17415445,95229-Oct-201401:23x64
Wlansvc.dll6.3.9600.177931,547,26408-Apr-201502:42x64
Wlansvc.ptxmlNot Applicable31,35222-Aug-201306:45Not Applicable
Wlansvcpal.dll6.3.9600.1741518,94429-Oct-201401:25x64
Wfdprov.dll6.3.9600.1741524,06429-Oct-201400:58x86
Wlan.mofNot Applicable12,88018-Jun-201312:37Not Applicable
Wlanapi.dll6.3.9600.17415238,08029-Oct-201400:53x86
Wlanhlp.dll6.3.9600.1741511,26429-Oct-201402:04x86
Wlanmsm.dll6.3.9600.17415304,12829-Oct-201400:49x86
Wlansec.dll6.3.9600.17415383,48829-Oct-201401:01x86
Wow64_wlansvc.ptxmlNot Applicable31,35221-Aug-201323:39Not Applicable

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 namePackage_1_for_kb3051395~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size1,832
Date (UTC)08-Apr-2015
Time (UTC)10:57
File namePackage_2_for_kb3051395~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size2,039
Date (UTC)08-Apr-2015
Time (UTC)10:57
File namePackage_for_kb3051395_rtm_gm~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size1,681
Date (UTC)08-Apr-2015
Time (UTC)10:57
File namePackage_for_kb3051395_rtm~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size1,686
Date (UTC)08-Apr-2015
Time (UTC)10:57
File nameX86_e1731540753c1409a2905892bd6b012e_31bf3856ad364e35_6.3.9600.17793_none_4ed65afed4b9f310.manifest
File versionNot Applicable
File size705
Date (UTC)08-Apr-2015
Time (UTC)10:57
File nameX86_f069cf76eb850a0a4baeedb68930e87a_31bf3856ad364e35_6.3.9600.17793_none_ead693bb5c81484d.manifest
File versionNot Applicable
File size1,039
Date (UTC)08-Apr-2015
Time (UTC)10:57
File nameX86_microsoft-windows-native-80211_31bf3856ad364e35_6.3.9600.17793_none_e39c8e31aa952c55.manifest
File versionNot Applicable
File size68,270
Date (UTC)08-Apr-2015
Time (UTC)03:55
File nameX86_microsoft-windows-proximity-service_31bf3856ad364e35_6.3.9600.17793_none_147ecf71bb658d66.manifest
File versionNot Applicable
File size3,517
Date (UTC)08-Apr-2015
Time (UTC)11:01
File nameX86_microsoft-windows-wlansvc_31bf3856ad364e35_6.3.9600.17793_none_30d827742088c74d.manifest
File versionNot Applicable
File size237,229
Date (UTC)08-Apr-2015
Time (UTC)11:01
Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameAmd64_af4c6843d390f654e455d28d80addc3a_31bf3856ad364e35_6.3.9600.17793_none_0e092fad25d64041.manifest
File versionNot Applicable
File size709
Date (UTC)08-Apr-2015
Time (UTC)10:57
File nameAmd64_c2f9ddc3632c050890b62a73498ec103_31bf3856ad364e35_6.3.9600.17793_none_8e74a3bbae53f49a.manifest
File versionNot Applicable
File size699
Date (UTC)08-Apr-2015
Time (UTC)10:57
File nameAmd64_fddd4af22ff3da9ddf78ecaad947f920_31bf3856ad364e35_6.3.9600.17793_none_227d0eeba4041cfc.manifest
File versionNot Applicable
File size1,045
Date (UTC)08-Apr-2015
Time (UTC)10:57
File nameAmd64_microsoft-windows-native-80211_31bf3856ad364e35_6.3.9600.17793_none_3fbb29b562f29d8b.manifest
File versionNot Applicable
File size68,274
Date (UTC)08-Apr-2015
Time (UTC)05:21
File nameAmd64_microsoft-windows-proximity-service_31bf3856ad364e35_6.3.9600.17793_none_709d6af573c2fe9c.manifest
File versionNot Applicable
File size3,519
Date (UTC)08-Apr-2015
Time (UTC)11:04
File nameAmd64_microsoft-windows-wlansvc_31bf3856ad364e35_6.3.9600.17793_none_8cf6c2f7d8e63883.manifest
File versionNot Applicable
File size237,233
Date (UTC)08-Apr-2015
Time (UTC)11:04
File namePackage_1_for_kb3051395~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,842
Date (UTC)08-Apr-2015
Time (UTC)10:57
File namePackage_2_for_kb3051395~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,259
Date (UTC)08-Apr-2015
Time (UTC)10:57
File namePackage_3_for_kb3051395~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,045
Date (UTC)08-Apr-2015
Time (UTC)10:57
File namePackage_for_kb3051395_rtm_gm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size1,969
Date (UTC)08-Apr-2015
Time (UTC)10:57
File namePackage_for_kb3051395_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,130
Date (UTC)08-Apr-2015
Time (UTC)10:57
File nameWow64_microsoft-windows-wlansvc_31bf3856ad364e35_6.3.9600.17793_none_974b6d4a0d46fa7e.manifest
File versionNot Applicable
File size231,376
Date (UTC)08-Apr-2015
Time (UTC)11:04

↑ 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 : 3051395
Revision : 1
Created on : 1/7/2017
Published on : 5/12/2015
Exists online : False
Views : 208