mlgmxyysd / wsapackagingtool Goto Github PK

There is no '.\libraries\WSA.pfx' and always failed to generate the certificate. Any idea on how to fix this issue? Thanks in advance!

PS C:\Work\WSAPackagingTool> .\repack.cmd
Repack - WSAPackagingTool v1.3 By MlgmXyysd
https://github.com/WSA-Community/WSAPackagingTool
*********************************************

[-] Initializing...
[-] Generating certificate...
[-] Checking certificate availability...
[#] Certificate test fail.
[-] Generating certificate...
[-] Checking certificate availability...
[#] Certificate test fail.
[-] Generating certificate...
[-] Checking certificate availability...
[#] Certificate test fail.
[-] Generating certificate...
[-] Checking certificate availability...

My device is currently running the LTSC version of Windows 10 21H2 19044.2311. However, it seems impossible that to install the wsa by merely download the latest package of wsa and modify the version specified in AppxManifest.xml. Is their any old version of wsa package still exists? I guess that it will work since the initial version of wsa might be tested in the preview version of Windows 10 two years ago.
Thanks.

I was noticing that when I would use this install.cmd if the .msixbundle file is in a folder path that has a space in it. The script will fail.
After echoing what was set to the PACKAGE variable if you pass a file
AKA.
C:\mypath\with space\WSA.msixbundle

The Script will only grab the everything up to the space.

C:\mypath\with

Therefore would get caught in your '[#] Error: You need specify a valid Msixbundle package.' only after echoing the PACKAGE variable I noticed that what was happening.

This also gets worse if you add multiple spaces in the path name.
A path with two spaces
C:\my path\with space\WSA.msixbundle

will become
C:\my
path\with
space\WSA.msixbundle

and so on.

I was unable to find a way around this other then removing the spaces. If it is a limitation of the script maybe echo the path or tell the user that they need to remove all spaces from the path.

We can download the WSL2 package from the linke below:
https://github.com/microsoft/WSL/releases/download/1.0.3/Microsoft.WSL_1.0.3.0_x64_ARM64.msixbundle

Is that possible to make a tool like WSL2PackagingTool for WSL2? Thanks in advance!

[fixed] [fixed] [fixed]
Edit: I'm so sorry, apparently I mistaken to delete AppxBlockMap.xml and AppxSignature.p7x for the bundle rather than the WSAx64.
So, the fix is just bring those both files back, and everything is fine :)

I always end up with..
MakeAppx : error: Bundle creation failed.
MakeAppx : error: 0x8051100f - The specified package format is not valid: The zip archive is missing the end of central directory marker.
Eventhough I do absolutely nothing with temp folder, just unpack repack.
I've tried with x64 Libraries, but ended up with the same error message

Is there any chance that this script could be modified so that there could be two installation instances of WSA on a computer, that is, one official unmodified and second which is modified and uses a different Package Family Name. Also, each instance uses its own userdata.vhdx. I don't seek for them to be working at the same time, this is not mandatory. I thought of this because, for example, people always could have the latest WSA without Google services, basically, for trying newest features and a second instance with an older WSA which is a modified version with Google services. Because frequently integrating Google services to each newest WSA build may be unstable and lead to bootloops, this can interfere with daily work.

I followed the video carefully, but when I ran the "install.cmd" , the problem appeared. It always stuck in the loop. I checked the source , I think that here is something wrong :
%PS% Start-Process -Verb runAs -FilePath '"%~0"' -ArgumentList 'am_admin %CMD_LINE%'

My Enviorment is Windows 11 , using tradtion Console.

Thanks!

When I tried this tool after preparing WSA for GApps integration, whenever I try to install it, either with the given installer, Windows Package Installer or Add-AppxPackage, I get the following error:

Merge failure for shared merged PRI file: error 0x80073B0F

The PRI file in question is that of my main locale (but I suppose that's just the first one detected).

Looking around, it seems that that's because "the packaging layout won't create or validate your resources.pri". Could it be that this script doesn't fix any locale that's not english, so there is some kind of mismatch when trying to install other languages?