You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, do you think WSA can run on Windows 10? I patched the WSAClient to skip the SO verification (RTLGetVersion). When I click 'Manage developer settings' the Client starts loading and a new 'vmmem' is created but closes after a short time.
I am looking into this right now, too. You clearly got further than me: I extracted the wsa msixbundle package (the 1.2GB version), then extracted WsaPackage_1.7.32815.0_x64_Release-Nightly.msix, modified the manifest in there to <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.19044.1319" MaxVersionTested="10.0.22000.120" />, deleted the other manifest files and tried to install with:
But this gives me (after enabling developer mode):
add-appxpackage : Fehler bei Bereitstellung. HRESULT: 0x80073CF6, Das Paket konnte nicht registriert werden.
error 0x80080204: While preparing to process the request, the system failed to register the windows.customInstall
extension due to the following error: Das Manifest des Appx-Pakets ist ungültig.
(sorry can't find a way to change the language of just powershell)
It says the manifest of the appx-package is invalid.
I am looking into this right now, too. You clearly got further than me: I extracted the wsa msixbundle package (the 1.2GB version), then extracted WsaPackage_1.7.32815.0_x64_Release-Nightly.msix, modified the manifest in there to <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.19044.1319" MaxVersionTested="10.0.22000.120" />, deleted the other manifest files and tried to install with:
But this gives me (after enabling developer mode):
add-appxpackage : Fehler bei Bereitstellung. HRESULT: 0x80073CF6, Das Paket konnte nicht registriert werden.
error 0x80080204: While preparing to process the request, the system failed to register the windows.customInstall
extension due to the following error: Das Manifest des Appx-Pakets ist ungültig.
(sorry can't find a way to change the language of just powershell) It says the manifest of the appx-package is invalid.
Open the manifest and delete <desktop6:Extension Category="windows.customInstall"> <desktop6:CustomInstall Folder="CustomInstall" desktop8:RunAsUser="true"> <desktop6:RepairActions> <desktop6:RepairAction File="WsaSetup.exe" Name="Repair" Arguments="repair" /> </desktop6:RepairActions> <desktop6:UninstallActions> <desktop6:UninstallAction File="WsaSetup.exe" Name="Uninstall" Arguments="uninstall" /> </desktop6:UninstallActions> </desktop6:CustomInstall> </desktop6:Extension>
I got it to install that way, but when I click "files" in Windows Subsystem for Android I get an error that "Windows Subsystem for Android isn't compatible with Windows Server".
Thank you @nunofaria007, was able to install, now getting the same error as @zanhecht. Looks like you are still a step ahead? What did you do here: "I patched the WSAClient to skip the SO verification (RTLGetVersion)."?
Thank you @nunofaria007, was able to install, now getting the same error as @zanhecht. Looks like you are still a step ahead? What did you do here: "I patched the WSAClient to skip the SO verification (RTLGetVersion)."?
I used IDA Pro 6.8 to check the disassembly and found the function where WSAClient checks the Windows version and replaced the relevant instructions with a bunch of NOPs. This allows the client to start loading, but it stops after a few seconds. I still don't know why and I would have to debug the process to gather more information. But my skill is very, very limited. I guess I won't get past this point.
HexEdit WSAClient.exe looking for BD DC 00 00 00 F0 55, and replace F0 55 with 00 00
F0 55 = 22000 (0x55F0) (build number)
It won't matter though because when you start wsaclient, it tries to run wsaservice and fails. Bunch of other things need to happen, like run init and boot the kernel in .\tools, get those system/vendor.img loaded and and then there's a vhdx that needs to be mounted if you hope to run anything in userland.
I guess some parts of WSA is implemented in the Windows and every appx package with a special permission can use it. then if it's like this you won't be able to run WSA on a version of Windows without that parts.
One of the commenters wrote that WSLg is required for WSA to work, which is only available in build 21390.
In fact, it's not really Windows 10, but an earlier version of Windows 11. Instead of using the preview version, I prefer to use the stable version (release) of Windows 11, which has fewer bugs than the preview version.
Anyway, I will turn this issue into a discussion, speak freely.
Activity
dreamflasher commentedon Oct 26, 2021
I am looking into this right now, too. You clearly got further than me: I extracted the wsa msixbundle package (the 1.2GB version), then extracted
WsaPackage_1.7.32815.0_x64_Release-Nightly.msix, modified the manifest in there to<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.19044.1319" MaxVersionTested="10.0.22000.120" />, deleted the other manifest files and tried to install with:add-appxpackage -Register "D:\Desktop\wsa\WsaPackage_1.7.32815.0_x64_Release-Nightly\AppxManifest.xml"But this gives me (after enabling developer mode):
(sorry can't find a way to change the language of just powershell)
It says the manifest of the appx-package is invalid.
Could you elaborate which files you patched how?
nunofaria007 commentedon Oct 26, 2021
Open the manifest and delete
<desktop6:Extension Category="windows.customInstall"> <desktop6:CustomInstall Folder="CustomInstall" desktop8:RunAsUser="true"> <desktop6:RepairActions> <desktop6:RepairAction File="WsaSetup.exe" Name="Repair" Arguments="repair" /> </desktop6:RepairActions> <desktop6:UninstallActions> <desktop6:UninstallAction File="WsaSetup.exe" Name="Uninstall" Arguments="uninstall" /> </desktop6:UninstallActions> </desktop6:CustomInstall> </desktop6:Extension>zanhecht commentedon Oct 26, 2021
I got it to install that way, but when I click "files" in Windows Subsystem for Android I get an error that "Windows Subsystem for Android isn't compatible with Windows Server".
dreamflasher commentedon Oct 26, 2021
Thank you @nunofaria007, was able to install, now getting the same error as @zanhecht. Looks like you are still a step ahead? What did you do here: "I patched the WSAClient to skip the SO verification (RTLGetVersion)."?
nunofaria007 commentedon Oct 26, 2021
I used IDA Pro 6.8 to check the disassembly and found the function where WSAClient checks the Windows version and replaced the relevant instructions with a bunch of NOPs. This allows the client to start loading, but it stops after a few seconds. I still don't know why and I would have to debug the process to gather more information. But my skill is very, very limited. I guess I won't get past this point.
3dluvr commentedon Oct 27, 2021
HexEdit WSAClient.exe looking for BD DC 00 00 00 F0 55, and replace F0 55 with 00 00
F0 55 = 22000 (0x55F0) (build number)
It won't matter though because when you start wsaclient, it tries to run wsaservice and fails. Bunch of other things need to happen, like run init and boot the kernel in .\tools, get those system/vendor.img loaded and and then there's a vhdx that needs to be mounted if you hope to run anything in userland.
In theory...
xmine64 commentedon Oct 28, 2021
I guess some parts of WSA is implemented in the Windows and every appx package with a special permission can use it. then if it's like this you won't be able to run WSA on a version of Windows without that parts.
MlgmXyysd commentedon Nov 1, 2021
I don't think it's possible
xmine64 commentedon Nov 1, 2021
@MlgmXyysd It's not that impossible, as WSA is provided as an external installable package.
3dluvr commentedon Nov 1, 2021
It appears it works on Win10 build 21390, but at that point you might as well run Win11.
https://old.reddit.com/r/bashonubuntuonwindows/comments/qe5hs5/i_got_windows_subsystem_for_android_running_on/
One of the commenters wrote that WSLg is required for WSA to work, which is only available in build 21390.
MlgmXyysd commentedon Nov 1, 2021
In fact, it's not really Windows 10, but an earlier version of Windows 11. Instead of using the preview version, I prefer to use the stable version (release) of Windows 11, which has fewer bugs than the preview version.
Anyway, I will turn this issue into a discussion, speak freely.