Unable to update to version 7.5.4.0 with winget: "install technology is different from the current version installed"

[michellejazmin]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

1. List available upgrades using winget upgrade.
2. Try to update PowerShell using winget.

Expected behavior

PS>winget upgrade --id Microsoft.PowerShell
Found PowerShell [Microsoft. PowerShell] Version 7.5.4.0
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third—party packages.
Downloading https://github.com/PowerShell/PowerShell/releases/download/v7.5.4/PowerShell-7.5.4-win-x64.msi

Actual behavior

PS>winget upgrade
Name                   Id                   Version Available Source
--------------------------------------------------------------------
PowerShell 7.5.3.0-x64 Microsoft.PowerShell 7.5.3.0 7.5.4.0   winget
1 upgrades available.


PS>winget upgrade --id Microsoft.PowerShell
No installed package found matching input criteria.

PS>winget upgrade powershell
No available upgrade found.
No newer package versions are available from the configured sources.

PS>winget upgrade "PowerShell 7.5.3.0-x64"
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.

Error details

Environment data

Name                           Value
----                           -----
PSVersion                      7.5.3
PSEdition                      Core
GitCommitId                    7.5.3
OS                             Microsoft Windows 10.0.26200
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

No response

[JiggyMcFluff]

Same issue here.

Current version 7.5.3.0 (msi) previously installed by winget. winget show displays same installer types.

Powershell 7.5.3.0

winget show --id Microsoft.Powershell --version 7.5.3.0

Found PowerShell [Microsoft.PowerShell]
Version: 7.5.3.0
Publisher: Microsoft Corporation
Publisher Url: https://github.com/PowerShell/PowerShell/
Publisher Support Url: https://github.com/PowerShell/PowerShell/issues
Author: Microsoft Corporation
Moniker: pwsh
Description:
  PowerShell is a cross-platform (Windows, Linux, and macOS) automation and configuration tool/framework that works well with your existing tools and is optimized for dealing with structured data (e.g. JSON, CSV, XML, etc.), REST APIs, and object models.
  It includes a command-line shell, an associated scripting language and a framework for processing cmdlets.
Homepage: https://microsoft.com/PowerShell
License: MIT
License Url: https://github.com/PowerShell/PowerShell/blob/master/LICENSE.txt
Copyright: Copyright (c) Microsoft Corporation
Copyright Url: https://github.com/PowerShell/PowerShell/blob/master/LICENSE.txt
Release Notes Url: https://github.com/PowerShell/PowerShell/releases/tag/v7.5.3
Documentation:
  Product Documentation: https://learn.microsoft.com/powershell
  FAQ: https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md
Tags:
  command-line
  cross-platform
  open-source
  powershell
  pwsh
  shell
Installer:
  Installer Type: wix
  Installer Url: https://github.com/PowerShell/PowerShell/releases/download/v7.5.3/PowerShell-7.5.3-win-x64.msi
  Installer SHA256: 28e23a6e3a18662b73e6fb267855f31786fb95ec943111de9e9e1338844106b4
  Release Date: 2025-09-10
  Offline Distribution Supported: true

Powershell 7.5.4.0

winget show --id Microsoft.Powershell

Found PowerShell [Microsoft.PowerShell]
Version: 7.5.4.0
Publisher: Microsoft Corporation
Publisher Url: https://github.com/PowerShell/PowerShell/
Publisher Support Url: https://github.com/PowerShell/PowerShell/issues
Author: Microsoft Corporation
Moniker: pwsh
Description:
  PowerShell is a cross-platform (Windows, Linux, and macOS) automation and configuration tool/framework that works well with your existing tools and is optimized for dealing with structured data (e.g. JSON, CSV, XML, etc.), REST APIs, and object models.
  It includes a command-line shell, an associated scripting language and a framework for processing cmdlets.
Homepage: https://microsoft.com/PowerShell
License: MIT
License Url: https://github.com/PowerShell/PowerShell/blob/master/LICENSE.txt
Copyright: Copyright (c) Microsoft Corporation
Copyright Url: https://github.com/PowerShell/PowerShell/blob/master/LICENSE.txt
Release Notes Url: https://github.com/PowerShell/PowerShell/releases/tag/v7.5.4
Documentation:
  Product Documentation: https://learn.microsoft.com/powershell
  FAQ: https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md
Tags:
  command-line
  cross-platform
  open-source
  powershell
  pwsh
  shell
Installer:
  Installer Type: wix
  Installer Url: https://github.com/PowerShell/PowerShell/releases/download/v7.5.4/PowerShell-7.5.4-win-x64.msi
  Installer SHA256: 84a39d39f113f884333686c4df70bc6c517f5b5d3982d88b4a0139f10ebb3fcb
  Release Date: 2025-10-20
  Offline Distribution Supported: true

[VictorCL-CSA-Nebulan]

It is an anomalous behavior that I also hope they can resolve.
By virtue of the update, I tried the following command.

winget install --id Microsoft.PowerShell --source winget --version 7.5.4.0

In my case, as a result I got an "Installation abandoned" message, but the installer continued the process. By the end and after a few minutes I had PowerShell v 7.5.4.0 installed.

It's a temporary solution, but in my case it worked.

[daxian-dbw]

@anamnavi Can you please help check if this is a PowerShell issue or WinGet issue?

[kilasuit]

Ahh I vaguly remember us having a very similar issue previously when the MSIX packages were being listed instead of the MSI's for the PowerShell Packages in the winget-pgks repo.

IIRC what @michellejazmin is seeing here is due the package having actually last been updated via Microsoft Update which I believe would also bring a similar mismatch here as per @bhattumang7 comment in #26332 that mentions

Starting with WinGet CLI v1.12, enhanced installer technology validation causes upgrade failures with the error:
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.

This I belive is due to running winget upgrade as winget returns the PowerShell package name as PowerShell 7.5.3.0-x64 instead of PowerShell then this points to it not having been installed via winget in my experience & is like this one all my devices that have had PowerShell upgraded via Microsoft Update.

@JiggyMcFluff the below from @VictorCL-CSA-Nebulan is close to what I'd recommend

It is an anomalous behavior that I also hope they can resolve. By virtue of the update, I tried the following command.

winget install --id Microsoft.PowerShell --source winget --version 7.5.4.0

In my case, as a result I got an "Installation abandoned" message, but the installer continued the process. By the end and after a few minutes I had PowerShell v 7.5.4.0 installed.

It's a temporary solution, but in my case it worked.

However I'd suggest that instead you run winget install --id Microsoft.PowerShell --source winget --version 7.5.4.0 --uninstall-previous --force as this should then clean up how winget sees things & was the previous fix that I found when this sorta issue came up previously as there were a few issues raised over a few releases in a row that were like this.

However, if you are running the PowerShell.Preview package (7.6.0-preview.4) too then this adds another additional layer of complexity as this is currently showing up via winget as Microsoft.PowerShell & not Microsoft.PowerShell.Preview after it was updated via Microsoft Update.

@anamnavi / @daxian-dbw
I hope all that helps though I'm not sure if that is showing this way for the preview because of it getting closer to an RC release for the Preview package but that would make lots of sense to me & feels like its a mixture of a Microsoft Update metadata & Winget metadata having a clash since Winget Cli v1.12

[anamnavi]

@michellejazmin @JiggyMcFluff had you installed 7.5.3.0 from the Store or from winget?

If the previous version 7.5.3.0 was installed from the store and the new 7.5.4.0 version was installed from winget then the install technology will be different as store supplies msix and winget supplies msi. In this case, I found @kilasuit suggestion to do winget install --id Microsoft.PowerShell --source winget --version 7.5.4.0 --uninstall-previous --force removed the old version with differing install technology and installed the new version succesfully from winget.

The second part of this is regarding the Installation abandoned verbose message. Here I have 7.5.3 installed from winget and then I run winget upgrade --id Microsoft.PowerShell and see the Installation abandoned message as well. However installation completes successfully and when I open a new Powershell session I see 7.5.4.0 is installed. Any insight on why this happens @denelon? Is it because I've got a powershell process running and am trying to upgrade that?

[michellejazmin]

@anamnavi I always update PowerShell via winget as it is the method Microsoft recommends. But this time I was able to update using the MSI from the GitHub Releases. Sadly I hadn't seen your comment until now so I couldn't try using the winget command you provided.