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

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.

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.

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:

http://support.microsoft.com/contactus/?ws=supportNote 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 name

File version

File size

Date

Time

Platform

Report.system.wireless.xml

Not applicable

59,620

10-Jun-2009

21:41

Not applicable

Rules.system.wireless.xml

Not applicable

159,924

10-Jun-2009

21:41

Not applicable

Wlan.mof

Not applicable

12,880

10-Jun-2009

21:41

Not applicable

Wlanapi.dll

6.1.7600.16385

81,408

14-Jul-2009

01:16

x86

Wlanhlp.dll

6.1.7600.16385

84,480

14-Jul-2009

01:16

x86

Wlanmsm.dll

6.1.7600.20783

428,032

18-Aug-2010

04:25

x86

Wlansec.dll

6.1.7600.16385

392,192

14-Jul-2009

01:16

x86

Wlansvc.dll

6.1.7600.16385

829,440

14-Jul-2009

01:16

x86

Wlansvc.ptxml

Not applicable

26,623

13-Jul-2009

20:50

Not applicable

For all supported x64-based versions of Windows 7

File name

File version

File size

Date

Time

Platform

Report.system.wireless.xml

Not applicable

59,620

10-Jun-2009

21:03

Not applicable

Rules.system.wireless.xml

Not applicable

159,924

10-Jun-2009

21:03

Not applicable

Wlan.mof

Not applicable

12,880

10-Jun-2009

21:03

Not applicable

Wlanapi.dll

6.1.7600.16385

114,176

14-Jul-2009

01:41

x64

Wlanhlp.dll

6.1.7600.16385

119,296

14-Jul-2009

01:41

x64

Wlanmsm.dll

6.1.7600.20783

414,720

18-Aug-2010

05:19

x64

Wlansec.dll

6.1.7600.16385

448,000

14-Jul-2009

01:41

x64

Wlansvc.dll

6.1.7600.16385

886,784

14-Jul-2009

01:41

x64

Wlansvc.ptxml

Not applicable

26,623

13-Jul-2009

20:40

Not applicable

Wlan.mof

Not applicable

12,880

10-Jun-2009

21:41

Not applicable

Wlanapi.dll

6.1.7600.16385

81,408

14-Jul-2009

01:16

x86

Wlanhlp.dll

6.1.7600.16385

84,480

14-Jul-2009

01:16

x86

Wlanmsm.dll

6.1.7600.20783

428,032

18-Aug-2010

04:25

x86

Wlansec.dll

6.1.7600.16385

392,192

14-Jul-2009

01:16

x86

Wow64_wlansvc.ptxml

Not applicable

26,623

13-Jul-2009

20:50

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 7

Additional files for all supported x86-based versions of Windows 7

File name

X86_359f3642badc30ae8beaa8cfe77defe8_31bf3856ad364e35_6.1.7600.20783_none_5c4f016513a1595b.manifest

File version

Not applicable

File size

695

Date (UTC)

19-Aug-2010

Time (UTC)

00:37

Platform

Not applicable


File name

X86_microsoft-windows-wlansvc_31bf3856ad364e35_6.1.7600.20783_none_9ca23a5f7f591b3a.manifest

File version

Not applicable

File size

214,358

Date (UTC)

19-Aug-2010

Time (UTC)

00:43

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 7

File name

Amd64_c5b29d73e16be6d9230beb624abb13b1_31bf3856ad364e35_6.1.7600.20783_none_448cefa26eb9bc68.manifest

File version

Not applicable

File size

1,040

Date (UTC)

19-Aug-2010

Time (UTC)

00:37

Platform

Not applicable


File name

Amd64_microsoft-windows-wlansvc_31bf3856ad364e35_6.1.7600.20783_none_f8c0d5e337b68c70.manifest

File version

Not applicable

File size

214,362

Date (UTC)

19-Aug-2010

Time (UTC)

00:37

Platform

Not applicable


File name

Wow64_microsoft-windows-wlansvc_31bf3856ad364e35_6.1.7600.20783_none_031580356c174e6b.manifest

File version

Not applicable

File size

210,956

Date (UTC)

19-Aug-2010

Time (UTC)

00:37

Platform

Not applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×