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.

An application that uses the WLAN API displays an incorrect location for the current user after you resume a Windows 7-based computer from a new access point on a wireless network


View products that this article applies to.

Symptoms

Consider the following scenario in a wireless network environment. You use a portable computer that is running Windows 7. You put the computer into hibernation in location 1, and then you resume the computer in location 2. The network access points in location 1 and location 2 are different. In this scenario, an application that uses the Microsoft Wireless LAN (WLAN) API to display the current location of the user may not work as expected.

For example, you sign in to Microsoft Office Communicator on a Windows 7-based computer by using a wireless network. You put the computer into hibernation. Then, you move to a different building, and you resume the computer from a location that uses a new access point. In this scenario, Communicator shows that you are still signed in from location 1.

↑ Back to the top


Cause

This issue occurs because the WLAN API provides an old BSSID to the application after you move the computer to a new access point.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. 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, visit 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

There are no prerequisites to apply this hotfix.

Registry information

To use the hotfix in this package, you do not 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 does not 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 7 file information notes
Important Windows 7 hotfixes and Windows Server 2008 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 is listed under "Windows 7/Windows Server 2008 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 MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows 7" section. 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 7
File nameFile versionFile sizeDateTimePlatform
Report.system.wireless.xmlNot applicable59,62010-Jun-200921:41Not applicable
Rules.system.wireless.xmlNot applicable159,92410-Jun-200921:41Not applicable
Wlan.mofNot applicable12,88010-Jun-200921:41Not applicable
Wlanapi.dll6.1.7600.1638581,40814-Jul-200901:16x86
Wlanhlp.dll6.1.7600.1638584,48014-Jul-200901:16x86
Wlanmsm.dll6.1.7600.20783428,03218-Aug-201004:25x86
Wlansec.dll6.1.7600.16385392,19214-Jul-200901:16x86
Wlansvc.dll6.1.7600.16385829,44014-Jul-200901:16x86
Wlansvc.ptxmlNot applicable26,62313-Jul-200920:50Not applicable
For all supported x64-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Report.system.wireless.xmlNot applicable59,62010-Jun-200921:03Not applicable
Rules.system.wireless.xmlNot applicable159,92410-Jun-200921:03Not applicable
Wlan.mofNot applicable12,88010-Jun-200921:03Not applicable
Wlanapi.dll6.1.7600.16385114,17614-Jul-200901:41x64
Wlanhlp.dll6.1.7600.16385119,29614-Jul-200901:41x64
Wlanmsm.dll6.1.7600.20783414,72018-Aug-201005:19x64
Wlansec.dll6.1.7600.16385448,00014-Jul-200901:41x64
Wlansvc.dll6.1.7600.16385886,78414-Jul-200901:41x64
Wlansvc.ptxmlNot applicable26,62313-Jul-200920:40Not applicable
Wlan.mofNot applicable12,88010-Jun-200921:41Not applicable
Wlanapi.dll6.1.7600.1638581,40814-Jul-200901:16x86
Wlanhlp.dll6.1.7600.1638584,48014-Jul-200901:16x86
Wlanmsm.dll6.1.7600.20783428,03218-Aug-201004:25x86
Wlansec.dll6.1.7600.16385392,19214-Jul-200901:16x86
Wow64_wlansvc.ptxmlNot applicable26,62313-Jul-200920:50Not 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


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 7

Additional files for all supported x86-based versions of Windows 7
File nameX86_359f3642badc30ae8beaa8cfe77defe8_31bf3856ad364e35_6.1.7600.20783_none_5c4f016513a1595b.manifest
File versionNot applicable
File size695
Date (UTC)19-Aug-2010
Time (UTC)00:37
PlatformNot applicable

File nameX86_microsoft-windows-wlansvc_31bf3856ad364e35_6.1.7600.20783_none_9ca23a5f7f591b3a.manifest
File versionNot applicable
File size214,358
Date (UTC)19-Aug-2010
Time (UTC)00:43
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7
File nameAmd64_c5b29d73e16be6d9230beb624abb13b1_31bf3856ad364e35_6.1.7600.20783_none_448cefa26eb9bc68.manifest
File versionNot applicable
File size1,040
Date (UTC)19-Aug-2010
Time (UTC)00:37
PlatformNot applicable

File nameAmd64_microsoft-windows-wlansvc_31bf3856ad364e35_6.1.7600.20783_none_f8c0d5e337b68c70.manifest
File versionNot applicable
File size214,362
Date (UTC)19-Aug-2010
Time (UTC)00:37
PlatformNot applicable

File nameWow64_microsoft-windows-wlansvc_31bf3856ad364e35_6.1.7600.20783_none_031580356c174e6b.manifest
File versionNot applicable
File size210,956
Date (UTC)19-Aug-2010
Time (UTC)00:37
PlatformNot applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2385405
Revision : 3
Created on : 9/28/2018
Published on : 9/28/2018
Exists online : False
Views : 184