Strange store apps behavior post 2311 ELM

[Sergio Masone1709161115]

I dont know if its an app layering thing or not, but I have a template of windows 11 that was published using 2311 on nutanix, that was working well, the ELM since a while has been updated, Now every publish i do , all windows store apps are broken, when a user logs on and tries to run calculator for example it will say "cannot launch the app" and that for every windows store app, mysteriously to get them working again i launch the ms store app once in the session, then all apps start working again until next logon, then back to square one again... I don't use store apps all that much so didn't noticed till late this behavior, and the main difference i can see is the one working was published with 2311, broken one 2403, same OS layer version.. Outside of published template, in packaging machine with os layer revisions, everything store apps works just fine, its just when a template is published it acts this way..

 

Anyone else have something similar?

[Sergio Masone1709161115]

23 hours ago, Sergio Masone1709161115 said:

I dont know if its an app layering thing or not, but I have a template of windows 11 that was published using 2311 on nutanix, that was working well, the ELM since a while has been updated, Now every publish i do , all windows store apps are broken, when a user logs on and tries to run calculator for example it will say "cannot launch the app" and that for every windows store app, mysteriously to get them working again i launch the ms store app once in the session, then all apps start working again until next logon, then back to square one again... I don't use store apps all that much so didn't noticed till late this behavior, and the main difference i can see is the one working was published with 2311, broken one 2403, same OS layer version.. Outside of published template, in packaging machine with os layer revisions, everything store apps works just fine, its just when a template is published it acts this way..

 

Anyone else have something similar?

After hours of debugging, looks to be the adobe reader layer that is causing this problem... not sure how, but seems to be an issue for me on windows 11, app layering, and that layer..