[Bug] `apex` folder got removed when choose 7zip as compression method

[julerobb1]

Steps to reproduce

1. download any version of the 7z files, magisk, kenrl su, non root versions
2. run the run .bat or powershell script
3. ALL FAIL WITH MISSING FILES

how about making something that acutally works insted of me wasting my time attempting to get this working. This was time spent ill never get back.

Expected behaviour

Should install fine, and launch and be rooted

Actual behaviour

Doesnt do any of the abvoe just fails. Even after doing all the troubleshooting steps. 7Zip is not the issue. Its a case of the Dev making something that does not work on every machine.

Windows version

22631.3880

Build Issue number

No response

Version requirement

• I am using latest commit of WSA-Script commit

[github-actions]

Hello julerobb1.
Thanks for sending an issues. Now our admin is inactive, just waiting and he will reply you soon.
Hope you have a nice day.

https://github.com/YT-Advanced/WSA-Script/actions/runs/10115857407

---

[hamza-founder]

The root cause of this reported issue, the steps to workaround and the remedy for a permanent fix:

After tailing the error output to the "Install.ps1" script and checking the "filelist.txt" file, I found that the "apex" folder and its content (mado_release.apex) are missing from every latest released x64 .7z archive here in the repo (I didn't check the arm64 archives).

The workaround is to copy that missing folder from another source such as a backup archive or via https://store.rg-adguard.net/ (download a matching package for our system using ProductID: 9P3395VX91NR), then extract the missing files required and copy them into the root of the desired WSA release folder from this repo on our system and finally execute "Run.bat" again as per the installation instructions for a successful install at last.

The remedy for a permanent fix is for the missing folder and content to be replaced correctly within the .7z archives and we live happily ever after for a while, hopefully.

Below is the result of my findings and I now have WSA running using this repos solution.

Many thanks

[YT-Advanced]

How about Custom Build ?

And check filelist.txt to see which file is missing

[stanleyyeung]

I'm coming across the same issue with WSA_2311.40000.5.0_arm64_Release-Nightly-GApps-13.0-NoAmazon on a Windows 11 Insider Build. I also tried the WsaSetup.exe in the Custom Build folder and checked the filelist.txt. It seems I'm missing the apex folder.

[YT-Advanced]

I'm coming across the same issue with WSA_2311.40000.5.0_arm64_Release-Nightly-GApps-13.0-NoAmazon on a Windows 11 Insider Build. I also tried the WsaSetup.exe in the Custom Build folder and checked the filelist.txt. It seems I'm missing the apex folder.

Thanks for your information. Can you create an empty apex folder before installing

[TriDefender]

I'm coming across the same issue with WSA_2311.40000.5.0_arm64_Release-Nightly-GApps-13.0-NoAmazon on a Windows 11 Insider Build. I also tried the WsaSetup.exe in the Custom Build folder and checked the filelist.txt. It seems I'm missing the apex folder.

Thanks for your information. Can you create an empty apex folder before installing

I think it misses more than just apex, however the installation was successfull if I removed the filecheck process

[stanleyyeung]

It finally installs. But unfortunately the Google Play Store still doesn't show up on my Start menu after the WSA finishes loading...

[YT-Advanced]

It finally installs. But unfortunately the Google Play Store still doesn't show up on my Start menu after the WSA finishes loading...

You should wait some minute for the initialize of Play Store and other app

[stanleyyeung]

Yes it does load longer this time than usual. But there is still no Google Play Store in my Start menu after it is done and I also cannot connect to the adb at 127.0.0.1:58526.

[YT-Advanced]

Should be fixed with hot fix in the latest releases

Make sure that you have uninstall your current WSA