The "repack.cmd" cannot put x64 architecture into the msixbundle. about wsapackagingtool HOT 16 CLOSED

Great news! I just did fresh install of Windows 10 (yes, 10 not 11) 32-bit in Hyper-V. And guess what repack.cmd did its job without any errors. Now both ARM64 and x64 modified msixes are now included in msixbundle. :)

from wsapackagingtool.

Great news! I just did fresh install of Windows 10 (yes, 10 not 11) 32-bit in Hyper-V. And guess what repack.cmd did its job without any errors. Now both ARM64 and x64 modified msixes are now included in msixbundle. :)

There is another possibility. For compatibility reasons, the built-in toolset is 32-bit, which cannot access too large byte-addressable memory (4GiB max). Replacing it with the corresponding architecture may solve the problem.
https://github.com/WSA-Community/WSAPackagingTool/tree/master/libraries#info

from wsapackagingtool.

Maybe I should add a judgment on whether the packaging is successful or not.

it is very important in a program, hopefully in the future there will be

from wsapackagingtool.

Out of memory, upgrade your computer hardware or kill some background programs

I have the same issue here, however my PC has 32GB RAM and while the repack.cmd was running, I saw that system and programs were using only less than half of the memory. I runned this tool also on another PC with 16GB RAM and the same issue as well. I even did fresh install of Windows 11 in VM, but no luck. A few times it succeeds, but mostly with ARM64 package not x64.

from wsapackagingtool.

It may be at the top. Or check the repack output. Msix may fail to pack

from wsapackagingtool.

No. I'm sorry the picture can't reflect my problem completely. I checked several times，but in vain.

from wsapackagingtool.

You can try to record the log output of repack. I suspect x64 has problems in the msix packaging process

from wsapackagingtool.

OK，I will try it later.

from wsapackagingtool.

Processing "\?\C:\WSAPackagingTool-master\temp\WsaPackage_1.8.32836.0_x64_Release-Nightly.msix_ext\WsaSettingsBroker\WsaSettingsBroker.exe" as a payload file. Its path in the package will be "WsaSettingsBroker\WsaSettingsBroker.exe".
Processing "\?\C:\WSAPackagingTool-master\temp\WsaPackage_1.8.32836.0_x64_Release-Nightly.msix_ext\wslcore.dll" as a payload file. Its path in the package will be "wslcore.dll".
Processing "\?\C:\WSAPackagingTool-master\temp\WsaPackage_1.8.32836.0_x64_Release-Nightly.msix_ext\wsldeps.dll" as a payload file. Its path in the package will be "wsldeps.dll".
Processing "\?\C:\WSAPackagingTool-master\temp\WsaPackage_1.8.32836.0_x64_Release-Nightly.msix_ext\wsldevicehost.dll" as a payload file. Its path in the package will be "wsldevicehost.dll".
Processing "\?\C:\WSAPackagingTool-master\temp\WsaPackage_1.8.32836.0_x64_Release-Nightly.msix_ext\wslhost.exe" as a payload file. Its path in the package will be "wslhost.exe".
MakeAppx : error: Package creation failed.
MakeAppx : error: 0x8007000e - Not enough memory resources are available to complete this operation.

from wsapackagingtool.

from wsapackagingtool.

this is the log

from wsapackagingtool.

Out of memory, upgrade your computer hardware or kill some background programs

from wsapackagingtool.

ohh thats the problem, thank you

from wsapackagingtool.

It has nothing to do with this tool. Maybe I should add a judgment on whether the packaging is successful or not.

from wsapackagingtool.

There is another possibility. For compatibility reasons, the built-in toolset is 32-bit, which cannot access too large byte-addressable memory (4GiB max). Replacing it with the corresponding architecture may solve the problem. https://github.com/WSA-Community/WSAPackagingTool/tree/master/libraries#info

Yes, your guess is right. I replaced the files in the "library" directory with "x64" architecture files. Now, it's working correctly. To help others, I will upload the files into a new directory called "library_64" soon.

Thanks all of you!

from wsapackagingtool.

multi architecture support is planned
https://github.com/WSA-Community/WSAPackagingTool#to-dos

from wsapackagingtool.