Installed VirtualBox on Windows 7, no wireless connection

Discussions related to using VirtualBox on Windows hosts.
Post Reply
wildesdd
Posts: 2
Joined: 18. Jan 2013, 15:26

Installed VirtualBox on Windows 7, no wireless connection

Post by wildesdd »

After I installed VirtualBox yesterday on Windows 7 64-bit, I noticed that my wireless connection is now disabled. I can't seem to turn it back on either from the button on the laptop, nor in the Network Connections page of the Control Panel.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Installed VirtualBox on Windows 7, no wireless connectio

Post by mpack »

Did you restart the host since then? And note that I mean a proper restart, not hibernate/restore.
wildesdd
Posts: 2
Joined: 18. Jan 2013, 15:26

Re: Installed VirtualBox on Windows 7, no wireless connectio

Post by wildesdd »

mpack wrote:Did you restart the host since then? And note that I mean a proper restart, not hibernate/restore.
Yes, I tried rebooting the host a couple of times, first a restart then after a complete shutdown.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Installed VirtualBox on Windows 7, no wireless connectio

Post by mpack »

In that case I guess that the VirtualBox Bridge Mode redirection filter driver doesn't like your wireless NIC for some reason. A common reason is that a filter driver has already been installed for some other software, and some kind of limit on filter layers has been reached.

Try going to Control Panel | Networking, and open the properties dialog for your wireless NIC, General tab (*). Find and untick the "VirtualBox Bridged Networking Driver" in the stack associated with this NIC. After a host reset you should hopefully find that your host can use wireless again. However you will be unable to use bridged networking in VirtualBox (with this NIC) until you find out what the conflict is. Concentrate on filter drivers that aren't shipped as standard with Win7.

(*) MS tends to rename dialogs etc, so find the best match on your Windows version.
Post Reply