Taken from the README.md (Program Files\WifiSitter\README.md)
There isn't much to configure in WifiSitter but there is one tunable to configure, there may be some network adapters you want ignored complete, Microsoft WiFi Direct for example. Network adapters are named "Ethernet" or "WiFi", names are too generic so the whitelist is made up of the network adapter descriptions. They are string values located at:
Value names are ignored entirely, they are only used to reference the values and can be anything, incrementing numbers are used by default. Regular expressions were overkill for my needs so matching is done by a case-insensitive .StartsWith(). Note, these values are removed when uninstalling.
One of the first things to check if wifi won’t connect is whether or not there are any virtual Ethernet cards that aren’t listed in the whitelist. The registry values only need to match the beginning of the adapter names so: “VMware Network Adapter”, will match: “VMware Network Adapter VMnet1” and “VMware Network Adapter VMnet8”. By default, WifiSitter ships with two exclusions:
|Microsoft Wi-Fi Direct|
VMWare adapters not being ignored by default is an oversight on my part, I didn’t run into these during testing. The exclusions that shipped by default were hard coded into the application, I’ve made some changes and in the future, the installer will bundle a reg file with any additional exclusions that become necessary. Here’s what’s in there right now:
Windows Registry Editor Version 5.00
"0"="Microsoft Wi-Fi Direct"
"2"="VMware Network Adapter"
If you come across a machine that doesn’t have those values in the whitelist, they can be copied into a .reg file and imported into the computer’s registry.