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
last one I tried was WSA_2407.40000.4.0_arm64_Release-Nightly-with-KernelSU-v1.0.2-MindTheGapps-13.0-RemovedAmazon
before that I tried the lastest stable build no amazon arm64
Windows build number
24H2 Build26100.2605
PC Specification
Additional context
No response
The text was updated successfully, but these errors were encountered:
I tracked it down to one missing file, apex. it's listed in filelist.txt but not in the archive. i got this machine yesterday, so that's when i installed the latest 7-zip. it doesn't show the file. just to be safe, in WSL i ran apt install xarchiver and used that program to extract the archive. both don't have the apex file, both do show this suspicious garbage file in the root of the .7z:
WSA_2407.40000.4.0_arm64} 976,400 b
edit: just downloaded an older build, turns out apex is probably just an empty directory that is now being omitted from some build process. so...just remove the entry from the file list? don't know if there are other ramifications about that directory.
but things still don't work after doing that, so wonder if something is broken with surface 11.
Describe the bug
I have the same error covered on this page: https://github.com/MustardChef/WSABuilds/blob/master/Documentation/Fix%20Guides/Pre-Install%20Issues/FixInstallps1.md but the steps laid out dont fix it.
Steps to reproduce the issue
same steps laid out here https://github.com/MustardChef/WSABuilds/blob/master/Documentation/Fix%20Guides/Pre-Install%20Issues/FixInstallps1.md
Expected behaviour
to install WSA
Downloaded Build Of WSA
last one I tried was WSA_2407.40000.4.0_arm64_Release-Nightly-with-KernelSU-v1.0.2-MindTheGapps-13.0-RemovedAmazon
before that I tried the lastest stable build no amazon arm64
Windows build number
24H2 Build26100.2605
PC Specification
Additional context
No response
The text was updated successfully, but these errors were encountered: