PC Tools- Detecting Wi-Fi Roaming on the Client During Zoom/Teams/WebEx Calls
& How To Fix Issue- Detailed Steps
Roaming is decided by the client device — so that’s where investigation should begin.
Picture from Meta Al
Here is a client-focused companion post that keeps the emphasis squarely on what to check on the endpoint itself when diagnosing roaming during Zoom or Teams calls.
Detecting Wi-Fi Roaming on the Client During Video Calls
When a video meeting freezes, becomes robotic, or briefly disconnects, one possible cause is that the client device roamed to another access point mid-call.
Because roaming decisions are made by the device — not the Wi-Fi infrastructure — troubleshooting must begin on the client.
This guide outlines exactly what to check on the endpoint.
1. Confirm a BSSID Change
The single most important indicator of roaming is a BSSID change.
SSID = network name (CorpNet)
BSSID = specific access point radio
If the BSSID changes during the call, the device roamed.
On Windows
Open Command Prompt and run:
netsh wlan show interfaces
Example output:
Name : Wi-Fi
State : connected
SSID : CorpNet
BSSID : 34:ab:cd:12:ef:01
Signal : 82%
Radio type : 802.11ax
Receive rate (Mbps) : 1200
Transmit rate (Mbps) : 1200
During a disruption, run it again.
If you see:
BSSID : 34:ab:cd:45:67:89
The device roamed.
If BSSID did not change, roaming was not the cause.
2. Check Windows Event Viewer for Roam Events
Navigate to:
Event Viewer →
Applications and Services Logs →
Microsoft → Windows → WLAN-AutoConfig → Operational
Look for entries like:
WLAN AutoConfig service has successfully connected to a wireless network.
Reason: The network driver disconnected.
or:
Roamed from BSSID 34:ab:cd:12:ef:01 to 34:ab:cd:45:67:89
Key indicators:
“Disconnected”
“Roamed”
“Reassociated”
Driver-initiated transitions
Pay attention to timestamps.
Do they align with when Zoom displayed “Internet Unstable”?
Time correlation is critical.
3. On macOS
Open Terminal and run:
/System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I
You’ll see:
SSID: CorpNet
BSSID: 34:ab:cd:12:ef:01
agrCtlRSSI: -61
lastTxRate: 780
If the BSSID changes during a disruption, roaming occurred.
For historical events:
log show --predicate 'subsystem == "com.apple.wifi"' --last 15m
Look for:
Roam
Disassociate
Reassociate
BSSID change
4. Check for Oscillation
Repeated BSSID switching between two APs (sometimes called “ping-pong roaming”) is a red flag.
Example pattern:
9:30:02 → AP-3
9:31:10 → AP-5
9:32:05 → AP-3
If this aligns with repeated audio freezes, roaming is likely contributing.
How Zoom, Teams, and Webex React to Client Roaming
All three platforms — Zoom, Microsoft Teams, and Cisco Webex — are sensitive to packet continuity. None of them control Wi-Fi roaming; they simply react to changes in network stability. However, their adaptation behaviors differ slightly.
During a roam event:
Zoom may:
Freeze video momentarily
Display “Internet Unstable”
Drop bitrate aggressively
Take a few seconds to re-stabilize video resolution
Zoom tends to make instability visible. It prioritizes maintaining media quality, and when packet loss or jitter exceeds thresholds, it signals the condition clearly to the user.
Microsoft Teams may:
Reduce video resolution quickly
Prioritize audio continuity
Mask brief interruptions
Avoid displaying warning messages in short disruptions
Teams often appears smoother during short roam events because it downshifts media quality more gradually and sometimes hides minor instability.
Cisco Webex may:
Temporarily freeze or pixelate video
Maintain audio as long as possible
Reduce frame rate before reducing resolution
Re-negotiate media streams during longer interruptions
Webex is generally conservative in protecting audio continuity. During short roam events, users may notice video quality degradation before experiencing audio impact. In longer roam interruptions, Webex may re-establish media streams, which can appear as a brief reconnect.
In Short:
Zoom tends to visibly alert users to instability.
Teams often degrades more quietly and adapts progressively.
Webex prioritizes audio preservation and may reduce video performance first.
All three platforms are designed to tolerate normal Wi-Fi mobility. However, unnecessary or poorly timed roaming events can exceed their tolerance thresholds and become user-visible.
Most importantly:
None of these applications initiate roaming.
They only respond to the network conditions created by it.
The Most Important Principle
Roaming must correlate with disruption.
If:
BSSID changed at 9:30
The meeting froze at 9:30
You likely have your cause.
If no BSSID change occurred, roaming was not responsible.
Items to Dial with PCs to Assist with Roaming Wireless NICS
Windows
Reduce Roaming Aggressiveness
Disable Power Saving on the Adapter
Set Windows Power Plan to Maximum Performance
Update the NIC Driver
Disable Preferred Band Steering Overrides
Confirm Stability
macOS
Forget and Re‑Add the Network
Reorder Preferred Networks
Disable Automatic Joining of Similar Networks
Reset Network Preferences
Check for Roaming Events
Keep macOS Updated
Detail:
Below are clear, step-by-step actions for both Windows and macOS to reduce overly aggressive roaming and improve call stability during Zoom, Teams, or Webex meetings.
How to Stabilize an Aggressive Wi-Fi NIC (Windows)
1. Reduce Roaming Aggressiveness
Open Device Manager
Expand Network Adapters
Right-click your Wi-Fi adapter → Properties
Go to the Advanced tab
Find Roaming Aggressiveness
Change from:
“Highest” or “Medium-High”
→ to Medium-Low or Lowest
Click OK
This prevents the NIC from roaming when signal strength is still acceptable.
2. Disable Power Saving on the Adapter
Aggressive power management can mimic roaming or trigger micro-disconnects.
In Device Manager
Wi-Fi adapter → Properties
Go to the Power Management tab
Uncheck:
“Allow the computer to turn off this device to save power”
Click OK
3. Set Windows Power Plan to Maximum Performance
Go to Control Panel → Power Options
Select High Performance
Click Change plan settings
→ Change advanced power settings
Expand:
Wireless Adapter Settings
Set:
Plugged in → Maximum Performance
On battery → Maximum Performance
4. Update the NIC Driver (Very Important)
Generic Windows drivers can roam poorly.
Identify adapter model:
Device Manager → Network Adapter
Go to the device manufacturer’s website (Dell, HP, Lenovo, etc.)
Download the latest OEM Wi-Fi driver
Install and reboot
OEM drivers are often tuned better for enterprise environments.
OEM drivers (from Dell, HP, Lenovo, etc.) are generally more stable than generic OS-provided drivers.
5. Disable “Preferred Band Steering” Overrides (If Available)
Some Intel adapters allow band preference tuning.
In Advanced settings, look for:
Preferred Band → Set to Prefer 5 GHz
Transmit Power → Set to Highest
This helps anchor the device on stronger, higher-capacity bands.
6. Confirm Stability
After adjustments:
Run during a meeting:
netsh wlan show interfaces
Watch:
BSSID
Signal strength
Transmit rate
If BSSID no longer changes unnecessarily, roaming has stabilized.
How to Stabilize Roaming on macOS
macOS does not expose “roaming aggressiveness” directly, but you can improve stability with the following steps.
1. Forget and Re-Add the Network
This resets profile corruption.
System Settings → Network
Click Wi-Fi
Click Details
Remove the network
Reconnect fresh
2. Reorder Preferred Networks
macOS may roam if it believes another known network is preferable.
System Settings → Network
Wi-Fi → Details
Move your primary network to the top
Remove unused or duplicate SSIDs
3. Disable Automatic Joining of Similar Networks
In Wi-Fi settings:
Turn off “Ask to Join Networks” (if enabled)
Remove overlapping SSIDs that may cause confusion
4. Reset Network Preferences (If Roaming Persists)
⚠️ This removes saved Wi-Fi networks.
Turn Wi-Fi off
In Finder → Go → Go to Folder
Enter:
/Library/Preferences/SystemConfiguration/
Delete:
com.apple.airport.preferences.plist
NetworkInterfaces.plist
preferences.plist
Reboot
Reconnect to Wi-Fi
5. Check for Roaming Events
During a call:
/System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I
Watch for:
BSSID changes
RSSI fluctuations
6. Keep macOS Updated
Apple continuously refines roaming logic. Ensure:
System Settings → General → Software Update → Current version installed.
Signs the Adjustments Worked
After tuning:
No unnecessary BSSID changes during meetings
No ping-pong roaming between two APs
Fewer “Internet Unstable” warnings
Stable transmit rate and RSSI