Page 2 of 2
Re: Microsoft Store template problem
Published: March 26, 2026 - 2:22 PM
by Esberard
I conclude that we'll have to forget about updating apps from the Microsoft Store from now on…

Re: Microsoft Store template problem
Published: March 26, 2026 - 2:32 PM
by sfonteneau
esberard wrote: ↑March 26, 2026 - 2:22 PM
I conclude that we'll have to forget about updating apps from the Microsoft Store from now on…
If it works.
I just modified the code so that the emsixbundle installs in session_setup and not in install.
I'll let you try:
https://srvluti.ad.tranquil.it/wapt-tes ... EPROD.wapt
Simon
Re: Microsoft Store template problem
Published: March 26, 2026 - 2:45 PM
by Esberard
Yes, but that means one installation per user. We can't afford that kind of setup, because we have machines that can have up to 40 different people connecting to them, so that's 40 times the app's profile size, and depending on the app's size, it can quickly become enormous (for example, FileLight, which is 153MB x 40 = 6GB just for that one, and that's multiplied for each app). And don't even get me started on Photos, which is 1.1GB...
Re: Microsoft Store template problem
Published: March 26, 2026 - 4:46 PM
by gadam
Good morning,
We realize that there are not only .emsixbundle but also emsix, eappxbundle and eappx which will all pose the same problem of not working in install for all users.
This forum post at MS indicates the same situation for .eappx for example:
I don't think the eappx package will work with the Add-AppxProvisionedPackagem or DISM. If you wanted to only install the package for the current users you could script the installation by getting each users SID and running something like Add-AppxPackage -Path ./Appfile.eappx -User<SID>
We are currently reworking the package to take into account the different extensions starting with ".e" but we can do nothing regarding installations in session_setup, it is a limitation of Windows.
Sincerely
Gwenaël