Repository navigation
PS7-packaged: Server Core cannot register/activate MSIX packages #27610
Description
Activity
Tracked internally; targeting resolution by 27H1/early 27H2.
So after 7.7 is released? Shouldn’t these types of issues be blockers for going MSIX only? I’m very concerned this change is being steamrolled in. It shouldn’t be too late to delay the MSIX only work until 7.8 and continue to work on fixing these problems in the meantime to enable MSIX packages for more scenarios until then.
Reacted by MartinGC94, JAK1047, Thomas Nieto, Ryan Yates, Nicolas Redfern, jantari, Karl Wester-Ebbinghaus, Flavien MICHALECZEK and w3lld0neI'd have to agree with Jordan Borean (@jborean93). If we don't expect a blocker to be resolved until the time frame release of 7.8 then why target it for 7.7? All that will mean is there will be less testers of 7.7 discovering issues and pushing technical debt into the next version.
Just a note I'll add although I'm not sure if it's relevant in the case of MSIX, but I like most administrators do not install Desktop Essentials on Server Core since it goes against Microsoft's best practice for a reduced attack footprint. So any work done should be viewed through the lens of a base Server Core install being compatible and not one with the additional FOD or DE installed.
Reacted by Karl Wester-Ebbinghaus and w3lld0ne
On Windows Server Core, MSIX package registration/activation fails because the MSIX activation stack depends on the AppInfo service, which in turn pulls in UAC — a component not present on Server Core. This blocks installing/running the Store-packaged PowerShell 7 on Server Core editions.
Fix direction: split AppInfo into an MSIX-activation piece and a separate desktop-only (UAC-dependent) piece. Not yet fully scoped.
Tracked internally; targeting resolution by 27H1/early 27H2.