Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: PowerShell/PowerShell
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: a17f176
Choose a base ref
...
head repository: PowerShell/PowerShell
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 0a6a8d5
Choose a head ref
  • 1 commit
  • 1 file changed
  • 2 contributors

Commits on Mar 19, 2026

  1. feat: enable per-user MSI installation for PowerShell 

    - Remove InstallScope="perMachine" from Package; add ALLUSERS property
  (default "1" = per-machine, set ALLUSERS="" for per-user install)
- Default INSTALLFOLDER to [LocalAppDataFolder]PowerShell for per-user
- Change all PREVIOUS_* RegistrySearch Root HKLM→HKMU so saved settings
  are read from the right hive on upgrade
- Change SaveInstallerProperties Root HKLM→HKMU for same reason
- Add AND ALLUSERS="1" to custom actions (RegisterManifest,
  EnablePSRemoting, EnableMU) so they are skipped for per-user installs
- Split Telemetry/DisableTelemetry/SetPath into machine (System="yes",
  HKLM, ALLUSERS="1") and user (System="no", HKCU, ALLUSERS="") variants
- Add ALLUSERS="1" condition to MURegistryEntries, RegistryEntries, AppPath
- Add RegistryEntriesPerUser (HKCU) so per-user installs are detectable
- Add new per-user component refs to Feature element

Co-authored-by: TravisEz13 <10873629+TravisEz13@users.noreply.github.com>
    @TravisEz13
    Copilot and TravisEz13 committed Mar 19, 2026
    Configuration menu
    Copy the full SHA
    0a6a8d5 View commit details
    Browse the repository at this point in the history
Loading