Skip to main content
ADB (Android Debug Bridge) provides the most powerful and flexible way to install apps on WSA. This method is ideal for developers, power users, and anyone who wants to automate app installation.

Prerequisites

  • WSA installed and running
  • ADB installed on your Windows system
  • Developer mode enabled in WSA

Installing ADB

If you don’t have ADB installed, follow the XDA guide to install ADB on Windows. Verify installation by opening Windows Terminal and running:
adb version

Setting Up ADB with WSA

1

Enable Developer Mode

  1. Launch Windows Subsystem for Android from the Start Menu
  2. Click on Developer in the sidebar
  3. Enable Developer mode by toggling the switch
  4. Take note of the IP address and port shown in the Developer mode section
The IP address will look like 127.0.0.1:58526 (port number varies)
2

Pair ADB with WSA

Open Windows Terminal and pair your device using the IP and port from Developer mode:
adb pair <IP:port>
Example:
adb pair 127.0.0.1:58526
You may be prompted to enter a pairing code shown in the WSA settings.
3

Connect ADB to WSA

After pairing, connect to WSA:
adb connect <IP:port>
Example:
adb connect 127.0.0.1:58526
4

Verify Connection

Confirm WSA is connected:
adb devices
You should see your WSA device listed with “device” status:
List of devices attached
127.0.0.1:58526    device

Installing APKs using ADB

Once ADB is connected, you can install any APK file.
1

Download the APK

Download the Android app APK file to your Windows computer.
2

Get File Path

In File Explorer:
  1. Navigate to the downloaded APK
  2. Hold Shift and right-click on the APK file
  3. Select Copy as path
The path will be copied to your clipboard in quotes.
3

Install with ADB

Open Windows Terminal and run:
adb install <file path>
Example:
adb install "C:\Users\YourName\Downloads\app.apk"
Right-click in Windows Terminal to paste the file path from your clipboard.
4

Wait for Installation

ADB will upload and install the app. You’ll see:
Performing Streamed Install
Success
The app is now installed and available in your Start Menu.

Common ADB Commands

List Installed Packages

adb shell pm list packages
Filter by package name:
adb shell pm list packages | grep -i "app_name"

Uninstall an App

adb uninstall <package_name>
Example:
adb uninstall com.example.app

Install APK with Specific Options

Replace existing app:
adb install -r app.apk
Grant all permissions:
adb install -g app.apk
Allow downgrade:
adb install -d app.apk

Push Files to WSA

adb push "C:\path\to\file" /sdcard/

Pull Files from WSA

adb pull /sdcard/file.txt "C:\destination\"

Access WSA Shell

adb shell
Once in the shell, you can run Android commands directly:
su                    # Switch to root (if Magisk is installed)
ls /system            # List system files
pm list packages      # List packages

Advanced Usage

Installing Multiple APKs

Create a batch script to install multiple APKs:
install-apps.bat
@echo off
echo Installing apps...
adb install "path\to\app1.apk"
adb install "path\to\app2.apk"
adb install "path\to\app3.apk"
echo Done!
pause

Installing Split APKs

For apps with multiple APK files (split APKs):
adb install-multiple base.apk config.apk
Or install all APKs in a folder:
adb install-multiple *.apk

Debugging App Issues

View real-time logs:
adb logcat
Filter logs by package:
adb logcat | grep "com.example.app"
Clear log buffer:
adb logcat -c

After Installation

Once you’ve installed a file manager and web browser using ADB, you can:
  1. Browse the web from within Android
  2. Download apps directly in WSA
  3. Install apps normally without using ADB
  4. Install Aurora Store to access Google Play apps without a Google account

Suggested First Apps

microG

Open-source Google services replacement

Aurora Store

Access Google Play without Google account

FX File Explorer

Full-featured file manager with cloud support

Bromite

Privacy-focused Chromium browser

Troubleshooting

  • Ensure WSA is running (open WSA Settings)
  • Verify Developer mode is enabled
  • Check that you’re using the correct IP and port
  • Try disconnecting and reconnecting:
    adb disconnect
    adb connect <IP:port>
    
  • Ensure the APK is compatible with Android (check WSA Android version)
  • Try installing with -r flag to replace existing installation
  • Check if you have enough storage space
  • Some apps may not work on WSA due to architecture or hardware requirements
  • Some operations require root access
  • Install a WSA build with Magisk for root capabilities
  • Use adb shell then su to gain root access
  • WSA resets the port number when it restarts
  • Check Developer settings for the current IP and port
  • Reconnect using the new port number
  • Consider keeping WSA Settings open to prevent automatic shutdown

Wireless ADB (Advanced)

You can use wireless ADB debugging if your WSA IP address is accessible:
adb tcpip 5555
adb connect <WSA_IP>:5555
Note: The default localhost IP (127.0.0.1) already works wirelessly for WSA.

Need Help?

Join the WSA Community Discord for troubleshooting assistance

Build docs developers (and LLMs) love