5.3 KiB
WSABuilds 
WSA Sideloader Usage Guide
With WSA Sideloader, you can install any APK file onto WSA, as well as XAPK, APKM and APKS files.
This guide will show you how to use it.
How to Download and Install WSA-Sideloader
You can download WSA Sideloader in 3 different ways:
| Operating System | Downloads |
|---|---|
  |
 |
|
 |
|
 |
Setup
Step 1. Once installed, you should see this screen:
Note
: If you get a message that says WSA is not installed, check that you have downloaded and installed WSA correctly as per the WSABuilds instructions.
Step 2. Next, open WSA Settings from the start menu or by typing wsa-settings:// in your browser's address bar, select Developer and enable Developer mode.
Step 3. Now, you can click the Browse button to select your APK file. You can also double click a file in File Explorer to automatically open WSA Sideloader with the APK file already selected.
Step 4. The first time you install an APK, it will ask to allow ADB debugging. Allow it and attempt the installation again. Check the always allow box if you don't want to manually accept the permission every time you install an app.
Step 5. It should take a few seconds to install the APK. Once it says The application has been successfully installed, you can click Open app. Bundle files may take longer depending on the file size.
Note
: If WSA is off, WSA Sideloader will start it for you. After 30 seconds, the installation will automatically continue.
You can find all your installed WSA apps on the start menu, as well as via the "Installed apps" button in WSA Sideloader:
Updating WSA Sideloader
From time to time, there may be updates that improve the reliability of the app, as well as ensuring it works properly with future releases of WSA.
Therefore, it's highly recommended you keep it up to date.
- If you installed WSA Sideloader using MS Store, you can update the app via the store.
- If you installed through other methods, the sideloader will notify you of an update the next time you launch it.
Troubleshooting
If you get an error like the one below, check that you have allowed the ADB authorization and enabled Developer Mode. Also try disabling and enabling USB debugging under manage developer settings as that can sometimes fix issues with the ADB connection.
If you get a message saying No connection could be made because the target machine actively refused it, follow this guide
If you continue to face problems, make a note of the error info displayed in WSA Sideloader and join the Discord server below for further assistance.