wrong link

@FaffeF I updated the link @BlackV shared

wrong link

Ah apologies for that, thanks @kilasuit

Thanks for bringing these over — these are exactly the right questions and we want to address them directly.

To set honest expectations for the community call: we won't have complete answers to all of these yet. What we can do is walk through what we know today, be clear about what's still being worked out, and make sure these specific scenarios are on the record as things we're actively tracking.

A few things I can say now: PowerShell 7.6 LTS retains MSI for its full supported lifecycle — nothing is changing for current deployments. The transition is happening in the 7.7 preview cycle specifically so we have time to work through exactly these scenarios before it matters.

Server Core, enterprise deployment, session configuration, and Windows Update behavior are all on our list. We'll cover what we can in the call and be straight about what we're still figuring out.

@doctordns — I appreciate you raising this directly, so let me be equally direct.

The early announcement was intentional — we wanted to surface real-world scenarios and concerns before 7.7 ships, not after. That's the feedback we're looking for, and threads like this one are exactly why we do it early.

To be clear on scope: PowerShell 7.6 LTS is unaffected. This is a 7.7 and beyond conversation. MSI isn't disappearing from under anyone today.

MSIX is the modern Windows packaging model — this is a platform direction, not a PowerShell team decision made in isolation. There are teams at Microsoft actively working to close the remaining MSIX scenario gaps. That work is happening because of concerns like the ones raised here. The direction is set.

What the community shapes is how this transition happens — the tooling, the timeline, the scenario coverage. That's where your input is genuinely valuable and what I want to hear about on May 21st.