Some Windows 11 users are reporting that the WSA (Windows Subsystem for Android) functionality is not working at all on Windows 11. Most affected users are reporting that the WSA popup appears but then nothing happens.

How to Fix WSA Not Working on Windows 11? - 1

Windows Subsystem for Android not Working on Windows 11

After investigating this particular issue thoroughly, it turns out that there are actually multiple potential scenarios that might ultimately cause this type of behavior on Windows 11. Here’s a shortlist of scenarios that might end up breaking the WSA (Windows Subsystem for Android) functionality on Windows 11:

  • VPN software interference – One unlikely culprit but one of the most common causes of this particular issue on Windows 11 is some kind of VPN interference. NorthVPN and a few other similar tools are known to conflict with the Windows Subsystem for Android functionality. Unfortunately, there isn’t a way to resolve the conflict other than forcing the uninstallation of the conflicting VPN software.
  • Outdated Microsoft Store framework – As it turns out, this particular issue can also be related to an outdated Microsoft Store outdated framework. Keep in mind that Microsoft has released a critical update for the WSA integration that needs to be installed in order to be able to use the Android Subsystem (especially if you’re using the latest available Windows 11 build).
  • Corrupted WSA temporary files – If you’ve already used the WSA infrastructure and have successfully run some Android apps before you started experiencing this issue, chances are you’re dealing with some remnant temporary files that have stopped the Android subsystem in its tracks. To fix this, you’ll need to reset the entire Android Subsystem.
  • Corrupted WSA installation – Another scenario that is known to cause this problem is a corrupted WSA installation that was interrupted. Additionally, you can find this issue occurring right after an AV suite ended up quarantining some files belonging to the WSA infrastructure. In this case, you should take the time to reinstall the android subsystem.
  • Overprotective AV suite – As it turns out, VPN software is not the only thing that might ultimately interfere with the WSA functionality on Windows 11. As it turns out, there are several 3rd party AV suites that will simply prevent the Windows Subsystem for Android from running smoothly. In this case, the only fix that works consistently is uninstalling the interfering 3rd party antivirus suite.

Now that we weren’t over every potential scenario that might be responsible for this type of issue, let’s go over the actual fixes that should allow you to fix the Windows Subsystem for Android on Windows 11:

Resolve VPN conflict (if applicable)

If you’ve been using a VPN (virtual private network) tool keep in mind that there’s a high chance that it’s conflicting with the WSA functionality on Windows 11.

Note: Most commonly, NordVPN is reported for being responsible for this particular type of conflict.

We don’t have an official explanation from Microsoft on why this problem is occurring, but the connection is clear since we found dozens of affected users reporting that the problem was fixed immediately after they uninstalled the VPN suite.

I’m sure this type of conflict will eventually get patched by Microsoft eventually, but until that happens, the only viable fix is to simply uninstall the conflicting VPN software to ensure that the Windows Subsystem for Android is not interfered with.

If this scenario is applicable, follow the instructions below for specific instructions on uninstalling the VPN app that is most likely conflicting with the WSA infrastructure:

  1. Press Windows key + R to open up a Run dialog box. Next, type ‘appwiz.cpl’ and press Enter to open up the Programs and Features menu. Open up the Programs and Features menu
  2. If you’re prompted by the User Account Control (UAC) , click Yes to grant admin access.
  3. Once you’re finally inside the Programs and Features menu, scroll down through the list of installed programs and locate the VPN software.
  4. After you manage to locate the correct listing associated with your VPN, right-click on it and choose Uninstall from the context menu. Uninstall the VPN software
  5. Follow the on-screen prompts to complete the uninstallation, then reboot your PC and see if the WSA functionality is now fixed.

If the same kind of issue is still occurring even after you uninstalled the VPN tool (or this method was not applicable), move down to the next potential fix below.

Update the Microsoft Store Framework

If the first method was not applicable in your case or it didn’t allow you to fix the issue, the next thing you should troubleshoot for is a potentially outdated Microsoft Store framework.

Keep in mind that just recently, Microsoft has released a critical framework infrastructure update that essentially makes using the WSA integration impossible if it’s missing from your Windows 11 installation.

If you have updated your Windows 11 computer up to date but you have postponed the updates available for the Microsoft Store, that’s probably the reason why you’re experiencing issues with the Windows Subsystem for Android.

If you’re looking for specific instructions on how to update your Microsoft Store framework, follow the instructions below:

  1. Press Windows key + R to open up a Run dialog box. Next, type ‘ms-windows-store:’ inside the text box and press Enter to open up the Microsoft Store component. Accessing the Microsoft Store
  2. Once you’re inside the home screen of the Microsoft Store, click on Library (bottom-left) corner of the screen.
  3. Next, move over to the right-hand section and click on the Update All hyperlink to install every pending update for apps and the MS framework. Install every pending Microsoft Store update
  4. Once every pending Microsoft update is installed, reboot your PC and see if the Windows Subsystem for Android functionality is fixed once the next startup is complete.

If the same kind of problem is still occurring even after you installed the pending Microsoft Store framework updates, move down to the next potential fix below.

Reset the Android Subsystem

As it turns out, this particular issue can also be caused by a couple of temporary files that were generated after you deployed Android games via the WSA infrastructure.

Note: This method is only applicable to the WSA functionality used to work on your PC before stopping abruptly.

We managed to uncover a lot of user reports confirming that in their case, the problem was actually being caused by temp files related to the Android Subsystem. Upon resetting the entire WSA infrastructure, they managed to fix the problem permanently.

To reset the Android subsystem, you’ll need to do it from the Installed Apps tab of the Settings menu.

For specific steps on how to do this, follow the instructions below:

  1. Press Windows key + I to open up the Settings menu on Windows 11.
  2. Once you’re inside the Settings menu, click on Apps from the side menu on the left. Note: Keep in mind that in case you don’t see the side menu on the left, you’ll need to click on the action icon (top-left corner of the screen)
  3. After you successfully select the Apps menu, move over to the right-hand section and click on Installed apps. Open up the Installed apps menu
  4. Once you’re inside the Installed Apps tab, use the search function at the top to search for ‘android’.
  5. From the list of results, click on the action icon associated with Windows Subsystem for Android, then click on Advanced Options from the context menu that just appeared. Accessing the Advanced Options for Windows Subsystem for Android
  6. Once you’re inside the Advanced Options menu, scroll down to the Reset section, then click on the Reset button.
  7. At the confirmation prompt, click on Reset once again to start the process of resetting the Windows Subsystem for Android and clearing the cache files. Resetting the Android for Subsystem
  8. Once the operation is complete, reboot your PC and see if the WSA component has been fixed once the next startup is complete.

If you’re still dealing with the same kind of issue, move down to the next potential fix below.

As it turns out, this type of issue can only be resolved by uninstalling the entire WSA infrastructure, rebooting your system, and reinstalling the full component once again.

This type of fix has been confirmed for being successful by a lot of users that were previously able to use the subsystem for Android on Windows 11 before the component completely broke.

If you find yourself in this particular scenario, follow the instructions below:

  1. Press Windows key + I to open up the Settings menu.
  2. Once you’re inside the Settings menu, click on Apps from the side menu on the left.
  3. Next, move over to the right-hand section and click on Apps & features menu. Open up the Apps & Features menu
  4. Inside the Apps & Features section, type ‘amazon’ inside the search function, then hit Enter to find the Amazon Appstore. Uninstall the Amazon Appstore
  5. Next, move down and click on the action button associated with Amazon Appstore and click Uninstall from the context menu that just appeared.
  6. At the confirmation prompt, confirm your choice by clicking on Uninstall once again, then wait until the uninstallation is complete.
  7. Reboot your PC and wait until the next boot process is complete.
  8. After your PC boots back up, press Windows key + R to open up the Run dialog box. Next, type ‘ms_windows-store:’ and press Enter to open up the Microsoft Store component. Accessing the Microsoft Store
  9. Once you’re inside the Microsoft Store component, use the search function at the top to search for Amazon Appstore, then hit the Install button. Install the Amazon Appstore
  10. Wait until the installation is complete, then reboot your PC once again before checking if the WSA component is finally fixed.

Uninstall 3rd party antivirus suite (if applicable)

If you’ve come this far without a viable fix, one last thing that you should absolutely troubleshoot for is a potential interference caused by an overprotective 3rd party antivirus suite.

Unfortunately, there is no way to exclude the WSA files from the scope of your 3rd party AV (since a lot of kernel dependencies are used), so the only way to fix this problem (if it’s applicable) is to simply uninstall the overprotective suite.

Follow the instructions below to uninstall the overprotective 3rd party antivirus suite that’s supposedly interfering with the Windows subsystem for Android:

  1. Press Windows key + R to open up a Run dialog box. Next, type ‘appwiz.cpl’ and press Enter to open up the Programs and Features menu on Windows 11. Opening up the Programs and Features menu
  2. If you’re prompted by the User Account Control, click Yes to grant admin access.
  3. Once you’re inside the Programs and Features menu, scroll down through the list of installed programs to locate the interfering AV suite.
  4. After you locate the problematic AV suite, right-click on it and choose Uninstall from the context menu. Uninstall the antivirus conflicting with WSA
  5. Follow the uninstallation prompts to complete the process, then reboot your PC and see if the WSA component is fixed once the next startup is complete.

How to Fix “Printer is in an error state” Issue?

The error “ WinRAR Error: Next Volume Is Required ” usually appears when you’re extracting a multi-part RAR archive and WinRAR can’t find (or can’t correctly identify) the next file in the sequence . This often happens when a volume is missing , stored in a different folder , or renamed in a way that breaks the archive’s expected order .

How to Fix WSA Not Working on Windows 11? - 2

In this guide, we’ll go over the most reliable fixes confirmed by affected users, along with what each method is doing behind the scenes so you can choose the right one for your situation.

Important: To extract multi-volume archives, you should always start extraction from the first file in the set. This is usually file.part1.rar , or (in older sets) the main .rar file that comes before .r01 , .r02 , and so on.

1. Download and Place the Missing RAR File

WinRAR needs all parts of a multi-volume archive to complete extraction. This error usually appears when one of the volumes in a set like .part2.rar , .r01 , .r02 , .001 , and similar naming formats is missing . Downloading the missing volume and placing it in the same folder as the other parts allows WinRAR to continue extracting normally .

  1. Look at the error message or review the list of archive parts in the folder.
  2. Identify which volume is missing (for example, part2.rar , .r02 , .001 , etc.).
  3. Go back to the website or source where you downloaded the archive.
  4. Locate and download the exact missing file using the same naming format as the others.
  5. Make sure the new file name matches the pattern of the rest. Example: If you have file.part1.rar and file.part3.rar , the missing one must be file.part2.rar .
  6. Move the downloaded missing volume into the same folder as the other archive parts.
  7. Confirm that all parts are in a single folder before extracting.
  8. Right-click the first file in the series (usually part1 or the main .rar file) and select Extract Here or Extract to Folder .
  9. WinRAR should now detect all volumes and continue extraction normally .

2. Manually Browse & Select the Next Volume

Use this method only if the next volume already exists , but WinRAR is failing to detect it automatically. This can happen due to incorrect naming , the file being in a different location , or a temporary file access issue. Manually browsing helps WinRAR locate the correct volume and resume extraction without interruption .

  1. Right-click the first file in the series (usually .rar or part1.rar ) and select Extract Here or Extract to Folder .
  2. When WinRAR cannot find the next volume, it will show the “ Next Volume Is Required ” message.
  3. A small window will appear, allowing you to manually select the next volume .
  4. Use the file explorer window to locate the folder where the other archive parts are saved.
  5. Select the next part based on the naming order (example: select file.part2.rar after file.part1.rar ).
  6. Make sure the selected file matches the naming format of the archive (no extra characters like (1) and no mismatched numbering).
  7. WinRAR will resume extraction using the selected volume .
  8. If additional volumes are missing or stored separately, WinRAR may prompt you again. Repeat the same process until extraction completes.

3. Rename the RAR files in Order

WinRAR relies on a proper naming sequence (such as file.part1.rar , file.part2.rar , file.part3.rar ) to extract multi-volume archives. If a file is named incorrectly, contains extra characters, or is out of order, WinRAR may fail to locate the next volume and show this error. Renaming the files correctly helps WinRAR follow the sequence and extract the archive without interruptions .

Note: Renaming only changes the file name , not the file contents. The goal is to restore the correct sequence so WinRAR can detect the next volume.

  1. Go to the folder where all the RAR files are saved.
  2. Make sure all parts of the archive are present and stored in the same folder .
  3. Check how the parts are currently named . Common patterns include:
file.part1.rar, file.part2.rar, file.part3.rar
file.rar, file.r01, file.r02, file.r03
  1. Look for files that don’t match the expected numbering pattern (for example, file.part01.rar , file.part1(1).rar , or unrelated names).
  2. Rename each file so it follows the same order without extra characters or mismatched numbering. Example:
Incorrect: file.part1.rar, file.part3.rar, file.part2(1).rar
Correct: file.part1.rar, file.part2.rar, file.part3.rar
  1. Make sure the text before the number is exactly the same for all files.
  2. Only the last part number should change.
  3. Right-click the first file in the series (usually part1.rar or the main .rar file) and select Extract Here .
  4. WinRAR should now recognize the sequence and continue extraction normally .

If you still get the same prompt: the archive set is likely incomplete (a part was never downloaded or was removed), or one of the volumes is corrupt and must be re-downloaded from the original source.