"Android Settings" and "Stop WSA" context menus do not work when WsaClient.exe App execution alias is disabled

[bashenk]

Describe the bug

In Windows Settings, a user can disable the WsaClient.exe app execution alias in the following submenu:
Settings > Apps > Advanced app settings > App execution aliases

If this is disabled, clicking the context menu entry for "Android Settings" or "Stop WSA" in this app creates an unhandled exception, specifically "The system cannot find the file specified.", as would be expected since disabling this setting effectively removes WsaClient.exe from the user's PATH.

I suspect simply using the complete file path would fix this.

Steps to reproduce

1. Disable the App execution alias for Windows Subsystem for Android™ in Windows Settings (location described above)
2. Click the "Android Settings" or "Stop WSA" context menu in this app

Expected behavior

The settings should open or WSA should stop (respective of the context menu chosen) regardless of whether the user has this setting disabled or enabled.

WSA version

2407.40000.4.0 (WSABuilds)

WSA System Control version

1.0.13

Windows build number

26100.6899

Additional context

I also just noticed that this applies to the Stop WSA menu entry as well.

[infinitepower18]

Thanks for reporting. I'll look into it when I have some time.