-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Not work Windows 10 22H2 Build 19045.4957 "AMD processor" #457
Comments
Run Add-AppxPackage -ForceApplicationShutdown -ForceUpdateFromAnyVersion -Register .\AppxManifest.xml in PowerShell and get erro 0x80070020 |
Why don't you try this? WSABuilds LTS Build #4 After double clicked on |
Sorry, i do not know how to fix that. I assume you've already enabled I just found this resolution but I can't verify if it solves your problem or not so I don't recommend following it Let's wait, maybe someone will help you. If you can't find a solution at all, you can change the OS and try WSABuilds LTS Build #4 for Windows 11 x64 or follow the official method available for windows 11 https://gist.github.com/HimDek/eb8704e2da1d98240153165743960e17 |
WSA will probably not run on your system as your CPU is from 2012. But anyways (if you still want to try), to bypass the PRI resource merge (Your WSA app language will be always be English):
Let me know if this has helped solve your issue. |
i delete resources.pri file and resources.pri entry from filelist.txt |
Describe the bug
i try install fallowing all steps corrects
the android subsystem stay loading and after disappear and not install any play store for me =(
my pc is Windows 10 22H2 Build 19045.4957 "AMD processor" AM3+ AMD FX-8320
work only for Intel ?
thanks!
Steps to reproduce the issue
unknow
Expected behaviour
fix
Downloaded Build Of WSA
WSABuilds LTS Build #3 (03/06/24) for Windows 10 x64
Windows build number
Windows 10 22H2 Build 19045.4957
PC Specification
Windows 10 22H2 Build 19045.4957 "AMD processor" AM3+ AMD FX-8320 "8GB RAM DDR3"
Additional context
No response
The text was updated successfully, but these errors were encountered: