Removing the PowerShell Update Notification #27060
Replies: 7 comments 5 replies
-
|
I [personally] have not relied on that notification and cannot think of any workflows that do. Others may certainly differ with valid reasons! |
Beta Was this translation helpful? Give feedback.
-
|
Set environment variable: |
Beta Was this translation helpful? Give feedback.
-
|
Over the last year, for health reasons, i've not been paying detailed attention to releases. So I find the message useful. Im usually pretty impatient, so whenever I see the message, I can either wait for WU, or just run I find this feature convenient and helpful. There is a workaround if needed. I'm not in favour of removing this. |
Beta Was this translation helpful? Give feedback.
-
|
some way of checking PowerShell updates is useful. not specifically the check that is notifying about new version when PowerShell session starts, but more generally a way to check, is my PowerShell up-to-date or there are newer versions available. |
Beta Was this translation helpful? Give feedback.
-
There already is, it should be down to "what mechanism did I use to install PowerShell?". PowerShell itself should not care what version it is, whether any other versions exist, how it was installed, where it came from, or why a user chose any particular version. It should just be the version it is and get on with being PowerShell. If you installed with winget, then use winget to check and update. If you installed with yum, or apt then use those tools. I run my own fork where I removed AMSI, Telemetry and Version checking because I simply don't want those features and I don't want them activating without my knowledge. They can't if I have physically removed the code. |
Beta Was this translation helpful? Give feedback.
-
Winget is not available on Windows Server 2016 (or 2019). So, I still need something else. |
Beta Was this translation helpful? Give feedback.
-
If you did not use winget, then what did you use to get pwsh installed? If you used Windows PowerShell, Invoke-WebRequest and misexec then you still have those tools. |
Beta Was this translation helpful? Give feedback.
-
|
I have written several books that focus on using PowerShell on Windows Server. I use VM farm of around 15 HyperV VMs. I install PowerShell on those hosts, using |
Beta Was this translation helpful? Give feedback.
-
|
Ironically the script you mentioned is not listed at Install PowerShell 7 on Windows You also have the problem that PowerShell cannot update itself while running, so you would still need to run that script using Windows PowerShell. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I know that the installation script is not mentioned in the documentation. Sadly. It is a very simple way to install and uldate powershell, particularly on Windows server. As mentioned, on my workstation, I have a function that shortcuts the script invocation. The function kicks off an msi based installation quietly then exits to avoid the issue you raise. It works, and avoids having to wait while 3rd part power toys get updated with the latest |
Beta Was this translation helpful? Give feedback.
-
|
You should not be updating versions in production systems based on a Pavlovian response to having seen a new version being released. A new version should only go into production after it has been tested on internal systems first, and then scheduled into production in a managed manner. |
Beta Was this translation helpful? Give feedback.
-
|
Another benefit of using this script is that it simplifies side by side installation of released and preview releases. You could probably work out how to do it using developer power toys, but the script is far simpler. And it works as soon as the update is pushed to Github (weeks or days faster). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
PowerShell currently includes an update notification that informs users when a newer version of PowerShell is available. This feature was originally introduced to help users discover new releases, particularly for installations that are not managed through package managers or automatic update mechanisms.
Over time, the ecosystem around PowerShell distribution has evolved. Many users now install and maintain PowerShell through channels such as package managers, operating system updates, or enterprise management tooling, where update awareness and lifecycle management may already be handled outside of the shell itself. Given these changes, we are evaluating whether the built-in update notification continues to provide sufficient value relative to its complexity and potential for confusion in managed environments.
This discussion is focused specifically on the possibility of removing the update notification feature entirely, rather than modifying or redesigning its behavior.
If the update notification were removed from PowerShell, what concerns or impacts would you anticipate in your environments or workflows?
Beta Was this translation helpful? Give feedback.
All reactions