Symptoms

You have a Windows 7 Service Pack 1-based computer that uses a third-party 802.11n wireless network adapter. When you enable Federal Information Processing Standards (FIPS) mode for the adapter, the third-party adapter reverts to 802.11g mode instead of 802.11n mode.

Cause

This problem occurs because the following features are not supported when you use a third-party 802.11n network adapter in FIPS mode:

  • Quality of Service (QoS) priority tagging

  • Aggregated MAC Service Data Unit (A-MSDU) de-aggregation


Resolution

To resolve this problem, upgrade the third-party 802.11n wireless network adapter to a driver that supports the features that are mentioned in the "Cause" section (QoS priority tagging and A-MSDU de-aggregation) in FIPS mode, and then apply the hotfix that is described in this section.

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, go to 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

To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1). For information about how to obtain Windows 7 Service Pack 1, see Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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 7 file information notesImportant 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 files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version

    Product

    SR_Level

    Service branch

    6.1.760
    1.
    18xxx

    Windows 7

    SP1

    GDR

    6.1.760
    1.
    22xxx

    Windows 7

    SP1

    LDR

  • 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 7" 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 7

File name

File version

File size

Date

Time

Platform

Nwifi.sys

6.1.7601.18148

270,336

08-May-2013

03:28

x86

Nwifi.sys

6.1.7601.22319

270,336

08-May-2013

03:42

x86

For all supported x64-based versions of Windows 7

File name

File version

File size

Date

Time

Platform

Nwifi.sys

6.1.7601.18148

323,072

08-May-2013

04:09

x64

Nwifi.sys

6.1.7601.22319

323,072

08-May-2013

03:53

x64


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

See Description of the standard terminology that is used to describe Microsoft software updates.

Additional file information for Windows 7

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

File name

Update-bf.mum

File version

Not applicable

File size

1,599

Date (UTC)

09-May-2013

Time (UTC)

09:53

Platform

Not applicable

File name

X86_63cf893c2e939da00c5882cb390e4fe3_31bf3856ad364e35_6.1.7601.22319_none_6ad3091de8d5e7fd.manifest

File version

Not applicable

File size

700

Date (UTC)

09-May-2013

Time (UTC)

09:53

Platform

Not applicable

File name

X86_e9347780a7898705c83afa23418c21d8_31bf3856ad364e35_6.1.7601.18148_none_b8cd8aa33908fb2e.manifest

File version

Not applicable

File size

700

Date (UTC)

09-May-2013

Time (UTC)

09:53

Platform

Not applicable

File name

X86_microsoft-windows-native-80211_31bf3856ad364e35_6.1.7601.18148_none_50f385ffed497d7f.manifest

File version

Not applicable

File size

65,695

Date (UTC)

08-May-2013

Time (UTC)

06:04

Platform

Not applicable

File name

X86_microsoft-windows-native-80211_31bf3856ad364e35_6.1.7601.22319_none_519e94bf064ddff4.manifest

File version

Not applicable

File size

65,695

Date (UTC)

08-May-2013

Time (UTC)

07:07

Platform

Not applicable

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

File name

Amd64_e3b4f2ee947941583d01066b0b46a15f_31bf3856ad364e35_6.1.7601.22319_none_f5975f4cd515d7c1.manifest

File version

Not applicable

File size

704

Date (UTC)

09-May-2013

Time (UTC)

09:53

Platform

Not applicable

File name

Amd64_f7514f74e6a5ec12bf3aad6926c995c2_31bf3856ad364e35_6.1.7601.18148_none_5844cb589bd22e99.manifest

File version

Not applicable

File size

704

Date (UTC)

09-May-2013

Time (UTC)

09:53

Platform

Not applicable

File name

Amd64_microsoft-windows-native-80211_31bf3856ad364e35_6.1.7601.18148_none_ad122183a5a6eeb5.manifest

File version

Not applicable

File size

65,699

Date (UTC)

08-May-2013

Time (UTC)

07:00

Platform

Not applicable

File name

Amd64_microsoft-windows-native-80211_31bf3856ad364e35_6.1.7601.22319_none_adbd3042beab512a.manifest

File version

Not applicable

File size

65,699

Date (UTC)

08-May-2013

Time (UTC)

06:41

Platform

Not applicable

File name

Update-bf.mum

File version

Not applicable

File size

1,813

Date (UTC)

09-May-2013

Time (UTC)

09:53

Platform

Not applicable


Need more help?

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

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×