Tell me about the issue and I’ll help you find the solution you need.
Wireless connection is lost when the wireless session times out in Windows 7 or Windows Server 2008 R2
Content provided by Microsoft
Applies to: Windows Server 2008 R2 Service Pack 1Windows Server 2008 R2 DatacenterWindows Server 2008 R2 StandardWindows Server 2008 R2 EnterpriseWindows Server 2008 R2 FoundationWindows 7 Service Pack 1Windows 7 UltimateWindows 7 EnterpriseWindows 7 ProfessionalWindows 7 Home PremiumWindows 7 Home BasicWindows 7 StarterMore
This article describes an issue that occurs when the wireless session times out in Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. A hotfix is available to fix this issue. Before you install this hotfix, see the Prerequisites section.
This issue occurs when a Windows 7-based computer is connected to a wireless network by using the Wi-Fi Protected Access II (WPA2) protocol and the wireless access point (AP) starts a new exchange of WPA2 keys. In the four-way handshake, the Windows 7-based computer sends a Message 2 (M2) with an invalid message integrity check (MIC) and secure bit.
Note This issue may occur every 12 hours or more frequently, and it takes one minute to regain the network connectivity.
This issue occurs because the WPA2 key context is not set correctly before the four-way handshake rekeys. Certain variables are not reset after the previous four-way handshake. This causes the secure bit to be set incorrectly and the stale Pairwise Transient Key (PTK) to be used to calculate the MIC in the M2 key messages. Some (specifically but not limited to Cisco) APs reject the M2 messages because of these errors.
Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get 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 don't 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 don't see your language, it's because a hotfix isn't available for that language.
To apply this hotfix, install Service Pack 1 in Windows 7 or Windows Server 2008 R2.
To use the hotfix in this package, you don't have to make any changes to the registry.
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix doesn't replace a previously released hotfix.
The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.
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:
6.1.760 1.23 xxx
Windows 7 or Windows Server 2008 R2
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
See the terminology that Microsoft uses to describe software updates.
What changes we have made to fix this issue
This fix addresses an incorrectly set security flag in the M2 message of the rekey handshake. This in turn produces an incorrectly calculated MIC. Some Cisco APs reject the M2 message because of these errors. The fix sets the M2 flag correctly during a rekey handshake.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.