Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 258/260 feeds/APIs · 416/439 docs · checked 22:55 UTC Customize Public modeDiscuss ChangeIntel on Discord

PowerShell installation and servicing on Windows

This page's changes and edits · All guidance changes

Microsoft's edit ·

Fixes #12973 - Document $Profile limitations for MSIX (#12978)

Microsoft's commit message in MicrosoftDocs/PowerShell-Docs · commit aa336f5 · +12 −8 lines · also on GitHub

11 ---
22 description: How to install PowerShell on Windows
3 −ms.date: 04/22/2026
3 +ms.date: 05/01/2026
44 title: Install PowerShell 7 on Windows
55 ---
66 # Install PowerShell 7 on Windows
⋯ 199 unchanged lines
206206 #### Limitations of a MSIX-based installation
207207
208208 Store-based installations are installed for a single user. There is no option to install it for all
209 −users. By default, Microsoft Store packages run in an application sandbox that virtualizes access to
210 −some filesystem and registry locations. Changes to virtualized file and registry locations don't
211 −persist outside of the application sandbox.
209 +users. Microsoft Store packages run in an application sandbox that virtualizes access to some
210 +filesystem and registry locations. Changes to virtualized file and registry locations don't persist
211 +outside of the application sandbox.
212212
213213 Store-based installations don't support PowerShell remoting. The application sandbox blocks all
214214 changes to the application's root folder. Any system-level configuration settings stored in
⋯ 9 unchanged lines
224224 - `Enable-ExperimentalFeature -Scope AllUsers`
225225 - `Set-ExecutionPolicy -Scope LocalMachine`
226226
227 −For more information, see [Understanding how packaged desktop apps run on Windows][06].
227 +For MSIX-based installations, you can't create or modify the all-users profile scripts
228 +`$PROFILE.AllUsersAllHosts` and `$PROFILE.AllUsersCurrentHost` because those profiles must be
229 +stored in `$PSHOME`. Current-user profiles are still supported.
228230
229 −Beginning in PowerShell 7.2, the PowerShell package is now exempt from file and registry
230 −virtualization. Changes to virtualized file and registry locations now persist outside of the
231 −application sandbox. However, changes to the application's root folder are still blocked.
231 +The PowerShell package is exempt from file and registry virtualization. Changes to virtualized file
232 +and registry locations now persist outside of the application sandbox. However, changes to the
233 +application's root folder are still blocked.
234 +
235 +For more information, see [Understanding how packaged desktop apps run on Windows][06].
232236
233237 > [!IMPORTANT]
234238 > You must be running on Windows build 1903 or higher for this exemption to work.
⋯ 132 unchanged lines

Microsoft's Markdown source from MicrosoftDocs/PowerShell-Docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 9 Oct 23:21 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Oct 22:55 UTC · 258 of 260 readable · 256 fully read · documentation 416/439 current