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.

Wireless connection is not queried by an application that uses the GetConnectionProfiles method in Windows 8.1 or Windows Server 2012 R2


View products that this article applies to.

Symptoms

Assume that you run an application that uses temporary profiles to set up a wireless connection on a computer that's running Windows 8.1 or Windows Server 2012 R2. Then, you run another application that uses the GetConnectionProfiles method to query the connection. In this situation, the method does not enumerate connections that are using temporary profiles. Therefore, the retrieved list does not display the active wireless connection.

↑ 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 hotfix, you must be running one of the following operating systems:

  • Windows 8
  • Windows Server 2012

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.16 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
Windows.networking.connectivity.dll6.3.9600.16523409,60031-Jan-201409:04x86
For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Windows.networking.connectivity.dll6.3.9600.16523409,60031-Jan-201409:04x86
For all supported ARM-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Windows.networking.connectivity.dll6.3.9600.16523390,14431-Jan-201408:17Not Applicable

Additional file information

Additional file information for Windows 8.1 and Windows Server 2012 R2

Additional files for all supported x86-based versions of Windows 8.1
File namePackage_1_for_kb2930152~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size1,837
Date (UTC)31-Jan-2014
Time (UTC)23:38
PlatformNot Applicable
File namePackage_for_kb2930152_rtm~31bf3856ad364e35~x86~~6.3.1.0.mum
File versionNot Applicable
File size1,462
Date (UTC)31-Jan-2014
Time (UTC)23:38
PlatformNot Applicable
File nameX86_71d7799a26f4592fa35877383de70359_31bf3856ad364e35_6.3.9600.16523_none_c2b1d341480315b9.manifest
File versionNot Applicable
File size711
Date (UTC)31-Jan-2014
Time (UTC)23:38
PlatformNot Applicable
File nameX86_microsoft-windows-n..orking-connectivity_31bf3856ad364e35_6.3.9600.16523_none_c75ade9941ce63a3.manifest
File versionNot Applicable
File size54,768
Date (UTC)31-Jan-2014
Time (UTC)23:38
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File nameAmd64_71d7799a26f4592fa35877383de70359_31bf3856ad364e35_6.3.9600.16523_none_1ed06ec5006086ef.manifest
File versionNot Applicable
File size713
Date (UTC)01-Feb-2014
Time (UTC)01:43
PlatformNot Applicable
File nameAmd64_a1889a456674819897bb842f66a10d07_31bf3856ad364e35_6.3.9600.16523_none_4f5430734c6b17c1.manifest
File versionNot Applicable
File size715
Date (UTC)01-Feb-2014
Time (UTC)01:43
PlatformNot Applicable
File nameAmd64_microsoft-windows-n..orking-connectivity_31bf3856ad364e35_6.3.9600.16523_none_23797a1cfa2bd4d9.manifest
File versionNot Applicable
File size54,770
Date (UTC)01-Feb-2014
Time (UTC)01:43
PlatformNot Applicable
File namePackage_1_for_kb2930152~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,089
Date (UTC)01-Feb-2014
Time (UTC)01:43
PlatformNot Applicable
File namePackage_2_for_kb2930152~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,077
Date (UTC)01-Feb-2014
Time (UTC)01:43
PlatformNot Applicable
File namePackage_for_kb2930152_rtm~31bf3856ad364e35~amd64~~6.3.1.0.mum
File versionNot Applicable
File size2,442
Date (UTC)01-Feb-2014
Time (UTC)01:43
PlatformNot Applicable
File nameX86_microsoft-windows-n..orking-connectivity_31bf3856ad364e35_6.3.9600.16523_none_c75ade9941ce63a3.manifest
File versionNot Applicable
File size54,768
Date (UTC)01-Feb-2014
Time (UTC)01:43
PlatformNot Applicable
Additional files for all supported ARM-based versions of Windows 8.1
File nameArm_9018ee19f71b2d4ade4fe6a46dfba789_31bf3856ad364e35_6.3.9600.16523_none_7bef3759f6721d65.manifest
File versionNot Applicable
File size711
Date (UTC)31-Jan-2014
Time (UTC)23:55
PlatformNot Applicable
File nameArm_microsoft-windows-n..orking-connectivity_31bf3856ad364e35_6.3.9600.16523_none_c75d50f141cb8269.manifest
File versionNot Applicable
File size54,768
Date (UTC)31-Jan-2014
Time (UTC)23:55
PlatformNot Applicable
File namePackage_1_for_kb2930152~31bf3856ad364e35~arm~~6.3.1.0.mum
File versionNot Applicable
File size1,837
Date (UTC)31-Jan-2014
Time (UTC)23:55
PlatformNot Applicable
File namePackage_for_kb2930152_rtm~31bf3856ad364e35~arm~~6.3.1.0.mum
File versionNot Applicable
File size1,462
Date (UTC)31-Jan-2014
Time (UTC)23:55
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 : 2930152
Revision : 1
Created on : 1/7/2017
Published on : 3/12/2014
Exists online : False
Views : 218