Windows Subsystem for Android Registry Location

This guide details the exact Windows Registry (regedit) paths used to store the configuration, group policies, and package state data for the Windows Subsystem for Android (WSA). While WSA relies heavily on virtualized disk images (.vhdx) and JSON configuration files for internal Android data, Windows manages system-level integration, deployment settings, and enterprise policies directly inside specific registry hives.

Group Policy and Management Configurations

Administrative policies and managed configuration rules for WSA are stored under the standard Windows Policies key. Administrators can enforce settings such as disabling developer mode or restricting subsystem execution here:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsSubsystemForAndroid

Common values defined in this path include: * AllowDeveloperMode: Controls whether ADB (Android Debug Bridge) and local developer connections are permitted. * BlockSubsystemExecution: Controls whether users can launch the WSA environment.

App Package and User State Data

Because WSA is distributed as a packaged MSIX application (MicrosoftCorporationII.WindowsSubsystemForAndroid), its per-user deployment metadata, state identifiers, and Windows integration details are located in:

HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppModel\SystemAppData\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe

Inside this directory, Windows tracks: * State: Contains serialized configuration parameters and state markers. * LocalState / Persisted: Holds paths linking to the application’s local execution assets.

Subsystem Registration and Virtual Machine Hooks

WSA interacts with the Windows Hypervisor Platform and shares underlying subsystem management pathways with the lightweight utility framework. Subsystem registration identifiers are mapped inside:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Lxss

and

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Lxss

Each registered subsystem or containerized instance creates a unique GUID subkey containing paths to base installation targets and kernel integration settings.

Registry Storage vs. Local Configuration Files

The Windows Registry only stores deployment parameters, system policies, and OS-level hooks for WSA. User-specific runtime settings (such as memory allocation, graphics adapter selection, and subsystem screen settings) are processed by the WSA Settings app and written to the local configuration file located at:

%LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalState\UserSettings.json