Post-Installation Issues
This guide covers common problems that occur after WSA has been successfully installed.No Internet
Problem
WSA and Android apps have no internet connectivity, or show “No Internet” in the WSA Settings.Solution 1: Uninstall Hyper-V Network Adapters
Uninstall Hyper-V adapters
- Find all drivers with “Hyper-V” in the name
- Right-click each one
- Select “Uninstall Driver”
Solution 2: Check Firewall Settings
- Windows Firewall
- Third-Party Antivirus
Check Inbound Rules
- Go to “Inbound Rules” tab
- Find entries for “Windows Subsystem for Android”
- Ensure they are Enabled and set to Allow for both TCP and UDP
The number of firewall entries may vary on your device. Ensure all WSA-related entries are enabled.
Solution 3: Change Android DNS Settings
Configure Private DNS
- Go to “Network and Internet”
- Select “Private DNS”
- Choose “Private DNS provider hostname”
- Enter:
dns.google - Click Save
Solution 4: Toggle Advanced Networking
Find Advanced Networking setting
- WSA 2305+: Go to “Advanced settings” → “Experimental features”
- WSA 2304 and older: Located in the “System” tab
Virtualization Errors
Problem
WSA fails to start with virtualization-related errors, even when virtualization is enabled in Task Manager.Solution
Remove WSA
- Right-click “Windows Subsystem for Android Settings”
- Select “Uninstall”
- Delete the extracted WSA folder
Disable Windows features
Go to “Turn Windows features on and off” and disable:
- Hyper-V
- Virtual Machine Platform
- Windows Hypervisor Platform
- Windows Subsystem for Linux
Disable virtualization in BIOS
- Boot into BIOS/UEFI
- Disable virtualization (VT-x, AMD-V, SVM)
- Save and exit
Enable Control Flow Guard
Go to: Windows Security → Apps & browser control → Exploit protectionEnsure Control Flow Guard is enabled.
Modify registry
Open Registry Editor (
regedit) and make these changes:Location 1: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends- Change
Startvalue from3to0
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\DeviceGuard- Set
EnableVirtualizationBasedSecurityto0 - If it doesn’t exist, create a new
DWORD (32-bit)value with this name
Re-enable Windows features
Go to “Turn Windows features on and off” and enable the features from Step 2.Restart your computer.
For AtlasOS Users
For AtlasOS Users
If the steps above don’t work:
- Go to the AtlasOS configuration folder
- Run the “Enable Hyper-V and VBS” CMD file
- Restart your PC
- Try running WSA again
WSA Crashes
Problem: WSA Stopped Working
WSA was working fine, but suddenly stops working or crashes on startup.Solution
Follow the same steps as Virtualization Errors, but you do not need to remove WSA first.Disable Windows features
Turn off: Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform, Windows Subsystem for Linux
Modify registry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FsDepends- Change
Startfrom3to0
You can change it back to 3 if it makes no difference
Settings App Crashes
Problem
WSA Settings app crashes and Android apps do not load after installation. Refer to the detailed guide for this specific issue.WSA Does Not Load After Install
Problem
No splashscreen appears and WSA doesn’t load after installation. Refer to the detailed guide for this specific issue.Missing Icons
Problem
Android app icons are missing from the Start Menu. Refer to the Missing Icons guide for the solution.Keyboard Not Working
Problem
Keyboard input doesn’t work in WSA or Android apps. Refer to the Keyboard Not Working guide for the solution.Target Machine Actively Refused Connection
Problem
ADB connection fails with “target machine actively refused connection” error. Refer to the detailed guide for this specific issue.Google Play Issues
Problem
Google Play Store or Google Play Services not working properly. Refer to the Google Play Issues guide for solutions.Need More Help?
Join Discord
Get help from the community
Open Issue
Report bugs on GitHub