You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Installed from MS Store, prompted to update to version that is not available in MS Store #19520
- ms store should have the latest version- ms store builds should not show update prompts for versions that are not available on the ms store- if ms store is no longer supported for powershell, that should be made clear in the release notes and on the MS store page
Actual behavior
1. get 'out of date, update now' message2. check MS store for updates3. no updates available even when checking 'get updates'
Error details
No response
Environment data
PS C:\Users\fred>$PSVersionTable
Name Value
---------
PSVersion 7.3.3
PSEdition Core
GitCommitId 7.3.3
OS Microsoft Windows 10.0.19045
Platform Win32NT
PSCompatibleVersions {1.0,2.0,3.0,4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Visuals
PowerShell 7.3.3
A new PowerShell stable release is available: v7.3.4
Upgrade now, or check out the release page at:
https://aka.ms/PowerShell-Release?tag=v7.3.4
PS C:\Users\fred> winget update powershell
A newer version was found, but the install technology is different from the current version installed. Please uninstall the package and install the newer version.
Reacted by Eduard de Jong, magicaton and Guillaume Tousignant
The store always lags behind the release by a few days. There are already issues opened with ideas around changing the way the "update now" message is pushed, so people who deployed via the store aren't told to update until it is ready.
Note that this also applies to the PowerShell extension in Visual Studio Code, which shows you the same kind of message.
Automatic detection that you already have the latest release from the Microsoft Store, but just not from Github, followed by a message which is more specific and a tiny little bit less invasive than the current one, would be helpful.
Especially when the version number difference is so small or when no security related bugfix is involved.
We manually publish to the store and the one person with access was on vacation until today but going forward we will have someone with backup access. Fluke issue, we will try our best to ensure quick publishing going forward
We manually publish to the store and the one person with access was on vacation until today but going forward we will have someone with backup access. Fluke issue, we will try our best to ensure quick publishing going forward
Is this actually fixed, or will it reoccur with the next update?
I think the issue posted here should have been given a different title.
The point is really not the fact that the new version on the Store comes with a little bit of a delay. This can absolutely happen, especially if humans still need to do it. But even automated actions can fail sometimes.
I am very thankful to those developers for their hard work.
The point should really only be the way how the message is written. But maybe different issue would have to be posted about this.
And indeed, if they are going to automate the process, the delay is most likely almost never going to happen anymore, causing the message issue to be very low piority from that moment.
There is another issue open about the message to update appearing prematurely.
AIUI PowerShell's check for "new version" is "what is the latest downloadable via the github link". It really needs to look at something else, and say "what should I be telling people to update to", which should only get updated when the store is ready.
Here is an issue to track automating the process #19528
As for the update message I don't think we would be able to change that easily based on the type of install, Travis Plunk (@TravisEz13) may know better. Additionally we have a delay from our release on GitHub to Microsoft Update that unfortunately is not "work-around-able" 😆 but that would be another case a different update message would be helpful.
AIUI PowerShell's check for "new version" is "what is the latest downloadable via the github link". It really needs to look at something else, and say "what should I be telling people to update to", which should only get updated when the store is ready.
Yea I agree, it would be helpful to make it so the update message is relevant to whatever your specific upgrade is. I will add that to my investigation in issue linked above.
One option would be to completely suppress the upgrade notice if running from MSIX - as, unless the user has explicitly disabled windows services to opt-in to doing updates themselves - it will be automatically updated by windows when possible.
changed the title [-]Powershell v7.3.4 is not in MS store/has no msix[/-][+]Installed from MS Store, prompted to update to version that is not available in MS Store[/+]on Apr 18, 2023
Just on this as we had some other discussions in the Interactive UX WG around some of this recently as this notification is a big bug bear for us all and we get comments on each release discussion as well as multiple issues raised on this each month too.
One option would be to completely suppress the upgrade notice if running from MSIX - as, unless the user has explicitly disabled windows services to opt-in to doing updates themselves - it will be automatically updated by windows when possible.
We have been asked about disabling the Update message before which can be done today with the env var POWERSHELL_UPDATECHECK=0
I don't think this should be set as part of the install process if installed via MSIX generally as you can do that if you wished to as that format can be used just like MSI. It may be possible to do so via installs from the Microsoft store though and is perhaps worth Steven Bucher (@StevenBucher98) adding to his investigations list
Activity
[-]Powershell v7.3.4 is not in MS store[/-][+]Powershell v7.3.4 is not in MS store/has no msix[/+]jhoneill commentedon Apr 16, 2023
The store always lags behind the release by a few days. There are already issues opened with ideas around changing the way the "update now" message is pushed, so people who deployed via the store aren't told to update until it is ready.
eduarddejong commentedon Apr 17, 2023
Note that this also applies to the PowerShell extension in Visual Studio Code, which shows you the same kind of message.
Automatic detection that you already have the latest release from the Microsoft Store, but just not from Github, followed by a message which is more specific and a tiny little bit less invasive than the current one, would be helpful.
Especially when the version number difference is so small or when no security related bugfix is involved.
StevenBucher98 commentedon Apr 17, 2023
Store should be updated now with 7.3.4, thank you for your patience.
fredemmott commentedon Apr 17, 2023
Is this actually fixed, or will it reoccur with the next update?
StevenBucher98 commentedon Apr 17, 2023
We manually publish to the store and the one person with access was on vacation until today but going forward we will have someone with backup access. Fluke issue, we will try our best to ensure quick publishing going forward
ThomasNieto commentedon Apr 17, 2023
Steven Bucher (@StevenBucher98) is there an issue we can track to have that manual process moved to automated CI/CD?
eduarddejong commentedon Apr 18, 2023
I think the issue posted here should have been given a different title.
The point is really not the fact that the new version on the Store comes with a little bit of a delay. This can absolutely happen, especially if humans still need to do it. But even automated actions can fail sometimes.
I am very thankful to those developers for their hard work.
The point should really only be the way how the message is written. But maybe different issue would have to be posted about this.
And indeed, if they are going to automate the process, the delay is most likely almost never going to happen anymore, causing the message issue to be very low piority from that moment.
jhoneill commentedon Apr 18, 2023
There is another issue open about the message to update appearing prematurely.
AIUI PowerShell's check for "new version" is "what is the latest downloadable via the github link". It really needs to look at something else, and say "what should I be telling people to update to", which should only get updated when the store is ready.
StevenBucher98 commentedon Apr 18, 2023
Here is an issue to track automating the process #19528
As for the update message I don't think we would be able to change that easily based on the type of install, Travis Plunk (@TravisEz13) may know better. Additionally we have a delay from our release on GitHub to Microsoft Update that unfortunately is not "work-around-able" 😆 but that would be another case a different update message would be helpful.
Yea I agree, it would be helpful to make it so the update message is relevant to whatever your specific upgrade is. I will add that to my investigation in issue linked above.
fredemmott commentedon Apr 18, 2023
https://learn.microsoft.com/en-us/windows/win32/api/appmodel/nf-appmodel-getcurrentpackagefullname can be used to determine if it's running from an MSIX
One option would be to completely suppress the upgrade notice if running from MSIX - as, unless the user has explicitly disabled windows services to opt-in to doing updates themselves - it will be automatically updated by windows when possible.
[-]Powershell v7.3.4 is not in MS store/has no msix[/-][+]Installed from MS Store, prompted to update to version that is not available in MS Store[/+]kilasuit commentedon Jul 18, 2023
Just on this as we had some other discussions in the Interactive UX WG around some of this recently as this notification is a big bug bear for us all and we get comments on each release discussion as well as multiple issues raised on this each month too.
We have been asked about disabling the Update message before which can be done today with the env var
POWERSHELL_UPDATECHECK=0I don't think this should be set as part of the install process if installed via MSIX generally as you can do that if you wished to as that format can be used just like MSI. It may be possible to do so via installs from the Microsoft store though and is perhaps worth Steven Bucher (@StevenBucher98) adding to his investigations list