How to Fix "WSATools Cannot Connect to ADB" & Common Errors

The most common roadblock users encounter when sideloading Android APKs is the infamous message: "WSATools cannot connect to ADB" or "WSA is offline". Fortunately, this is almost always caused by a simple configuration switch or a suspended background process.

Follow these tested solutions below to restore the bridge between WSATools and the Windows Subsystem for Android in minutes.

Solution 1: Wake Up WSA (Start the Subsystem)

By default, Windows 11 suspends WSA when no Android applications are active to conserve battery and memory. If WSATools tries to connect while WSA is dormant, the ADB handshake will timeout.

1. Open the Windows Start Menu and launch Windows Subsystem for Android Settings.
2. At the very top of the window, click on the "Files" icon (or click the test button).
3. Wait 5-10 seconds until the Android Files window opens. This confirms the WSA virtual machine is fully running.
4. Now return to WSATools and retry installing your APK.

Solution 2: Ensure Developer Mode is Toggled ON

ADB debugging is disabled in WSA by default for security reasons. WSATools requires local debugging permissions:

1. Inside WSA Settings, click on Advanced Settings in the left pane.
2. Ensure the Developer Mode toggle is switched to ON.
3. Verify that an IP address is shown below Developer Mode (e.g. 127.0.0.1:58526). If it says "Unavailable", click "Refresh" or ensure WSA is awake.

Solution 3: Terminate Conflicting ADB Processes

If you have software like BlueStacks, NoxPlayer, LDPlayer, or Android Studio installed on your computer, their background ADB server can lock port 5037, preventing WSATools from talking to WSA.

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Click on the Details tab.
3. Look for any running instances of adb.exe.
4. Right-click each adb.exe process and select End Task.
5. Launch WSATools again; it will spin up a fresh, dedicated ADB instance.

Solution 4: Verify Windows Virtual Machine Platform

If WSA fails to start altogether with an error code, Windows Virtual Machine Platform might be disabled:

1. Press Win + R, type optionalfeatures.exe, and press Enter.
2. Scroll down and verify that Virtual Machine Platform is checked.
3. If not, check it, click OK, and reboot your computer.