Symptoms

You install an application that uses Microsoft Virtual WiFi technology on a computer that is running Windows 7 or Windows Server 2008 R2. However, the application does not work after the computer restarts. Additionally, you receive an error message that resembles the following:

The hosted network couldn't be started. The group or resource is not in the correct state to perform the requested operation.

Notes

  • This issue may occur when a Plug and Play (PNP) resource rebalance occurs during the startup process. The PNP resource rebalance is usually triggered by a change to the hardware configuration.

  • If you open Device Manager when this issue occurs, you notice that the Virtual WiFi Adapter is not created.

Cause

This issue occurs because the Virtual Wi-Fi filter driver does not create the Virtual Wi-Fi Adapter correctly when a PNP resource rebalance occurs during the startup process.

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 Web site:

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 one of the following operating systems:

  • Windows 7

  • Windows 7 Service Pack 1 (SP1)

  • Windows Server 2008 R2

  • Windows Server 2008 R2 Service Pack 1 (SP1)

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must 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 and Windows Server 2008 R2 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 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
    0.
    16xxx

    Windows 7 and Windows Server 2008 R2

    RTM

    GDR

    6.1.760
    0.
    20xxx

    Windows 7 and Windows Server 2008 R2

    RTM

    LDR

    6.1.760
    1.
    17xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    GDR

    6.1.760
    1.
    21xxx

    Windows 7 and Windows Server 2008 R2

    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 Server 2008 R2 and 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

VWi-Fibus.sys

6.1.7600.16385

19,968

13-Jul-2009

23:52

x86

VWi-Fiflt.sys

6.1.7600.16747

48,640

25-Jan-2011

04:35

x86

VWi-Fimp.sys

6.1.7600.16747

14,336

25-Jan-2011

04:35

x86

VWi-Fibus.sys

6.1.7600.16385

19,968

13-Jul-2009

23:52

x86

VWi-Fiflt.sys

6.1.7600.20887

48,640

25-Jan-2011

04:32

x86

VWi-Fimp.sys

6.1.7600.20887

14,336

25-Jan-2011

04:32

x86

VWi-Fibus.sys

6.1.7600.16385

19,968

13-Jul-2009

23:52

x86

VWi-Fiflt.sys

6.1.7601.17549

48,640

25-Jan-2011

04:40

x86

VWi-Fimp.sys

6.1.7601.17549

14,848

25-Jan-2011

04:40

x86

VWi-Fibus.sys

6.1.7600.16385

19,968

13-Jul-2009

23:52

x86

VWi-Fiflt.sys

6.1.7601.21648

48,640

25-Jan-2011

04:22

x86

VWi-Fimp.sys

6.1.7601.21648

14,848

25-Jan-2011

04:22

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

VWi-Fibus.sys

6.1.7600.16385

24,576

14-Jul-2009

00:07

x64

VWi-Fiflt.sys

6.1.7600.16747

60,416

25-Jan-2011

05:01

x64

VWi-Fimp.sys

6.1.7600.16747

17,920

25-Jan-2011

05:01

x64

VWi-Fibus.sys

6.1.7600.16385

24,576

14-Jul-2009

00:07

x64

VWi-Fiflt.sys

6.1.7600.20887

60,416

25-Jan-2011

05:03

x64

VWi-Fimp.sys

6.1.7600.20887

17,920

25-Jan-2011

05:03

x64

VWi-Fibus.sys

6.1.7600.16385

24,576

14-Jul-2009

00:07

x64

VWi-Fiflt.sys

6.1.7601.17549

60,416

25-Jan-2011

09:34

x64

VWi-Fimp.sys

6.1.7601.17549

18,432

25-Jan-2011

09:34

x64

VWi-Fibus.sys

6.1.7600.16385

24,576

14-Jul-2009

00:07

x64

VWi-Fiflt.sys

6.1.7601.21648

60,416

25-Jan-2011

04:54

x64

VWi-Fimp.sys

6.1.7601.21648

18,432

25-Jan-2011

04:54

x64

Workaround

To work around this issue, disable and then enable the wireless network adapter in Device Manager. After you do this, Microsoft Virtual Wi-Fi Adapter is created automatically.

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 and for Windows Server 2008 R2

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

File name

Update.mum

File version

Not applicable

File size

2,285

Date (UTC)

26-Jan-2011

Time (UTC)

21:51

Platform

Not applicable

File name

X86_088394ea1747667d8ee9919ede06816d_31bf3856ad364e35_6.1.7601.17549_none_5200c7d50ff60a9f.manifest

File version

Not applicable

File size

693

Date (UTC)

26-Jan-2011

Time (UTC)

21:51

Platform

Not applicable

File name

X86_2a24fd7c04f7d7bf7f5de261132e5384_31bf3856ad364e35_6.1.7601.21648_none_46f99fdcdaec10d9.manifest

File version

Not applicable

File size

693

Date (UTC)

26-Jan-2011

Time (UTC)

21:51

Platform

Not applicable

File name

X86_7a251c641b73394d36605c42863fe906_31bf3856ad364e35_6.1.7600.20887_none_e55250174ebf3dcc.manifest

File version

Not applicable

File size

693

Date (UTC)

26-Jan-2011

Time (UTC)

21:51

Platform

Not applicable

File name

X86_ecdd973202288e255c3854062a4607ce_31bf3856ad364e35_6.1.7600.16747_none_85489db1b894e93b.manifest

File version

Not applicable

File size

693

Date (UTC)

26-Jan-2011

Time (UTC)

21:51

Platform

Not applicable

File name

X86_microsoft-windows-vWi-Fi_31bf3856ad364e35_6.1.7600.16747_none_5f984c2224b64c30.manifest

File version

Not applicable

File size

10,072

Date (UTC)

26-Jan-2011

Time (UTC)

21:54

Platform

Not applicable

File name

X86_microsoft-windows-vWi-Fi_31bf3856ad364e35_6.1.7600.20887_none_5ff6a93d3df45bbe.manifest

File version

Not applicable

File size

10,072

Date (UTC)

26-Jan-2011

Time (UTC)

21:54

Platform

Not applicable

File name

X86_microsoft-windows-vWi-Fi_31bf3856ad364e35_6.1.7601.17549_none_6180a9bc21daeaca.manifest

File version

Not applicable

File size

10,072

Date (UTC)

26-Jan-2011

Time (UTC)

21:54

Platform

Not applicable

File name

X86_microsoft-windows-vWi-Fi_31bf3856ad364e35_6.1.7601.21648_none_6209463d3af9713d.manifest

File version

Not applicable

File size

10,072

Date (UTC)

26-Jan-2011

Time (UTC)

21:54

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_2089a55b82534eefdba5159ce03a4788_31bf3856ad364e35_6.1.7600.20887_none_848239e053d205c0.manifest

File version

Not applicable

File size

697

Date (UTC)

26-Jan-2011

Time (UTC)

21:51

Platform

Not applicable

File name

Amd64_420e68b429c3ea0362a24372a8948d6c_31bf3856ad364e35_6.1.7601.17549_none_93393c8fb872584f.manifest

File version

Not applicable

File size

697

Date (UTC)

26-Jan-2011

Time (UTC)

21:51

Platform

Not applicable

File name

Amd64_59efb8215a9c8ec128614564a09b33d6_31bf3856ad364e35_6.1.7600.16747_none_ae594843fe2e0a55.manifest

File version

Not applicable

File size

697

Date (UTC)

26-Jan-2011

Time (UTC)

21:51

Platform

Not applicable

File name

Amd64_9d059531971188a1836a0126f4b01996_31bf3856ad364e35_6.1.7601.21648_none_edc9ded4d74bd609.manifest

File version

Not applicable

File size

697

Date (UTC)

26-Jan-2011

Time (UTC)

21:51

Platform

Not applicable

File name

Amd64_microsoft-windows-vWi-Fi_31bf3856ad364e35_6.1.7600.16747_none_bbb6e7a5dd13bd66.manifest

File version

Not applicable

File size

10,074

Date (UTC)

26-Jan-2011

Time (UTC)

21:52

Platform

Not applicable

File name

Amd64_microsoft-windows-vWi-Fi_31bf3856ad364e35_6.1.7600.20887_none_bc1544c0f651ccf4.manifest

File version

Not applicable

File size

10,074

Date (UTC)

26-Jan-2011

Time (UTC)

21:52

Platform

Not applicable

File name

Amd64_microsoft-windows-vWi-Fi_31bf3856ad364e35_6.1.7601.17549_none_bd9f453fda385c00.manifest

File version

Not applicable

File size

10,074

Date (UTC)

26-Jan-2011

Time (UTC)

21:52

Platform

Not applicable

File name

Amd64_microsoft-windows-vWi-Fi_31bf3856ad364e35_6.1.7601.21648_none_be27e1c0f356e273.manifest

File version

Not applicable

File size

10,074

Date (UTC)

26-Jan-2011

Time (UTC)

21:52

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

2,717

Date (UTC)

26-Jan-2011

Time (UTC)

21:51

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!

×