Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

PowerShell 7 Upgrade MSI Setting Bug

Ouverte
  • Quelque chose ne va pas ?
#67 0 commentaires 2 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
1/5
Temps estimé
Moins d'une heure
Accessibilité débutants
8/100
Type d'issue
Documentation
Clarté
À clarifier
Activité
À l'abandon
Stack technique
shell
Domaine
release

Piste de recherche

This is a known-issue announcement with no file, test or entry point to change in this repository. The fix it describes is in PowerShell/PowerShell pull request #20420, which is referenced but not linked here. Nothing here is a clear task for a newcomer, so a useful next step is to ask a maintainer whether this notice still needs updating.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Previously, there was a bug in the PowerShell 7 MSI installer that did not remember modified installation settings after upgrading via WinGet and therefore subsequent updates reset the settings to their defaults. This only affects users after upgrading using WinGet, which performs a non-interactive installation of the MSI package. This affects any PowerShell 7 version upgraded via WinGet.

Who is affects 

Anyone who downloads a PowerShell 7.x .MSI package from GitHub, changes a setting in the MSI GUI options (opting out of telemetry for example) and then upgrades to a newer version non-interactively. 

What settings are affected

If you have modified the settings for any of the following MSI settings these may not have been saved if you have upgraded via WinGet since setting them:

  • ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL  
  • ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL  
  • ENABLE_PSREMOTING  
  • REGISTER_MANIFEST  
  • ADD_PATH
  • DISABLE_TELEMETRY  
  • INSTALLFOLDER 
Actions 
Telemetry

If you disabled telemetry during a previous installation, you need to disable it again after an upgrade installation. To opt out of telemetry, set the POWERSHELL_TELEMETRY_OPTOUT environment variable to True for your system. You can set this value by running the following command in an elevated PowerShell session.

[Environment]::SetEnvironmentVariable(POWERSHELL_TELEMETRY_OPTOUT, 'True', 'Machine') 

PowerShell collects minimal telemetry that is anonymized before it is sent to Microsoft. For more information about telemetry, see about_Telemetry.

All other settings

If you need to upgrade PowerShell using Winget run the upgrade command with the --interactive option: 

winget upgrade Microsoft.PowerShell --interactive 

This option runs the installer interactively so you can change the necessary settings.  

Upcoming fixes 

This behavior is fixed in the PowerShell 7.5.0-preview.3 release. After installing this version, the MSI installer package saves the settings you chose. When you install a new MSI package released after 7.5.0-preview.3, the Windows Installer will use the saved settings. For a detailed description of the fix, see Pull Request #20420 .

Langage dominant
Aucune donnée de langage
Étoiles
20
Forks
8
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de PowerShell/Announcements

Toutes les issues de PowerShell/Announcements

Issues similaires

Plus d'issues Release

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.