Disable Wireless When Connected to LAN in XP and Vista

Note: Visit BridgeChecker page for most up to date version and documentation.

Disable Wireless When Connected to LAN in XP and Vista

We are releasing a Windows XP and Vista program called BridgeChecker that extends the “Disable Upon Wired Connect” capability that is available for Broadcom wireless cards to any brand wireleless card when the ethernet interface is connected.


BridgeChecker is a windows utility that can automatically disable/enable wireless interfaces. Whenever your computer is connected to an Ethernet port and the link state is good, the utility can automatically turns off the IEEE 802.11 wireless network interface. This conserves IP address allocation, reduces security risks, resolves dual interface routing issues, and prolongs battery life.

BridgeChecker Settings

The settings screen can be accessed by right clicking on the WLAN Book “globe” icon in the task bar.

BridgeChecker Task Bar Globe Icon

Task Bar Menu Options

BridgeChecker Task Bar Menu

Program Settings

WLAN Book BidgeChecker Settings

BridgeChecker Requirements

— Program tested on Windows XP and Vista operating systems
— Requires .NET Framework 2.0 or above
.NET 3.5 Service Pack 1 (Full Package) direct download from Microsoft
— Windows Vista users that have UAC enabled are required to manually allow RunCMD.exe to run as Administrator. See screen shots below.

Running BridgeChecker Program as an Administrator in Windows Vista

In Windows Vista the “RunCMD.exe” file is located in the C:\Program Files\WLAN Book\BridgeChecker\ folder.



Recommended Usage Scenarios

The program can be used in the following scenarios.

  • disable wireless when connected to lan
  • disable wireless when docked
  • disable wireless when ethernet detected
  • disable wireless when wired
  • disable wireless when on LAN
  • disable wireless when cable connected
  • disable wireless when in docking station
  • disable wireless when ethernet plugged in
  • disable wlan when lan connected

Known Issues with BridgeChecker v1.0.4.22

— Detects enabled VMware virtual interfaces as enabled physical interfaces causing program to disable wireless card. Work around is to disable VMware interface when not in use.
— If computer has more than one wireless card, the program may not enable/disable correct card or may enable/disable both cards.

Comments, Bugs, and Feature Requests

Please use post comment feature below to let use know if the BridgeChecker program met your requirements. When commenting pelase let us know your Windows operating system version and wireless card brand and model if possible.

Comments about bugs and feature requests are welcome and encouraged. We may be able to enhance this program or recommend other products.

BridgeChecker Download

BridgeChecker Download

24 Replies to “Disable Wireless When Connected to LAN in XP and Vista”

  1. Thank you SO much… I have desperately looking for a way to do just this. Its small, its fast, its perfect! Thanks a million wlanbook.com. I will be recommending this software to my associates!

    Alfie – Network Administrator

  2. I try to test it but I find some error about when connected to lan it disable wireless and loop to enable wireless many time. Please let me know why and how to solve this problem.

  3. Yes – this program works with Windows 7 RC1. I ran it on a Dell Inspiron 9300 with an Intel 2200 wireless NIC while connected via the Broadcom ethernet NIC.

  4. It works fine when i’m not connected to my work VPN. When my VPN interface is connected, I have the looping problem. I’m on a Cisco AnyConnect SSL VPN, but we also use the older cisco client for regular VPN access as well. Is there any way to fix the looping bug for specific interfaces like VPN ones?

  5. Why not just make a pulldown of the ethernet adapter and the wifi adapter to use. No guessing, no surprise adapters… just adapter A is disabled when adapter B is connected, etc.

  6. Agree with isaac no need for whitelist just a drop down to choose card ‘a’ (lan) and card ‘b’ (wireless). You would then not need to have a whitelist or subsequent issues with VPN connections. Running as a service would be better also. (not for the reasons of UAC). just would be more tidier and easier to administer.

  7. If the 3G USB dongle shows up as a “LAN or High Speed Internet” interface in Windows XP Network Connections it is supported in BridgeChecker v1.2. If the 3G device is a “Dial-up” interface in Network Connections then the plan is to support dial-up interfaces in next minor release (coming soon).

  8. Hi

    We are currently running a view tests with BridgeChecker.

    When we install the tool with domain admin rights, not all the cards in our notebooks are recognized.

    If we install it with local admin rights, all the cards in our notebook where found.

    The Notebooks that we are running the tests on, are a Fujitsu Siemens Lifebook E8410, a Lifeboook P7230 and a Lifebook P8020.

    We have the same effect with all types.

    What can we do, to fix this?

    Thank you in advance for your help

  9. The new version does not work on Windows 7 x64. It installed fine but when launching the app I receive an error stating “Microsoft.Jet.OLEDB.4.0” provider is not registered on the local machine. I have read that this problem exists because there is no OLEDB.4.0 driver for x64. I believe that if you change your code from “Any CPU” to specify “x86” that it will run in 32-bit mode and work. Currently “Any CPU” will run by default in 64-bit mode.


  10. This tool does not work under Win7 x64 (it requires Jet DB 4.0 – imho useless when you can’t even set exceptions like VMware or VPN interfaces, but no x64 version is available).

Comments are closed.