Cannot install apps

[avi12]

Brief description of your issue

Installing an app results in an error:

Found GitHub CLI [GitHub.cli]
An unexpected error occurred while executing the command:
Unsupported ManifestVersion: 1.0.0
0x8a150007 : Cannot process manifest. The manifest version is higher than supported. Please update the client.

Steps to reproduce

winget install github.cli

Expected behavior

Being able to install the app.

Actual behavior

Getting the error above.

Environment

[winget --info]
Windows Package Manager v0.2.10191 Preview
Windows: Windows.Desktop v10.0.19042.870
Package: Microsoft.DesktopAppInstaller v1.11.10191.0

Additional software
PowerShell (admin): 5.1.19041.868
Windows Terminal: 1.6.10571.0

Please update the client.
this tells you what to do. install the latest .appxbundle from release or update through store.

[avi12]

@ecovio1 I did both. The bug still exists.

[aagz]

v0.1.41331 works fine.

@ecovio1 Now I installed the latest version of .appxbundle.

v0.2.10191:

PS C:\soft> winget install -e --id 7zip.7zip
Найдено 7Zip [7zip.7zip]
При выполнении команды произошла непредвиденная ошибка:
Unsupported ManifestVersion: 1.0.0
0x8a150007 : Cannot process manifest. The manifest version is higher than supported. Please update the client.
PS C:\soft> winget show 7zip
Найдено 7Zip [7zip.7zip]
При выполнении команды произошла непредвиденная ошибка:
Unsupported ManifestVersion: 1.0.0
0x8a150007 : Cannot process manifest. The manifest version is higher than supported. Please update the client.
PS C:\soft>

[jedieaston]

The new version of the client (v0.2.10771) is still marked as "pre-release" in GitHub, so here is the direct link: https://github.com/microsoft/winget-cli/releases/tag/v-0.2.10771-preview.

After installing this you should be able to use the new manifests.

[denelon]

Easton Pillay (@jedieaston) thanks for pointing that out. Generally, I try to remove the "pre-release" label after the package is published to the store. I was thinking once we announce 1.0 I will only remove the "pre-release" mark from versions that have shipped to stable Windows 10. Are there any unintended consequences of doing that? Maybe I should just "edit" the release notes when a version is shipped in the future.

[jedieaston]

I can't think of any, editing the release notes when the build hits the store and keeping the latest release marked latest would be the best move so people can know there's a manual update available to fix bugs.

What would be even better is if we could do winget upgrade --all and have winget upgraded, but I just tried that with a local manifest and since winget has to close to complete the upgrade, it just kind of stops (the upgrade completes successfully, but the progress bar stops at 21% since that's when the old version of winget is closed and there is never a message that install failed or succeeded). I don't know a great solution to that, other than having another copy of winget somewhere that is only used for bootstrapping winget, but it's a use case to think about.

[denelon]

We also get restarted if you upgrade PowerShell (the shell you are using) or Terminal (the terminal you are using).

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

[ltomuta]

Ok, so there is something fishy here.
I have the latest version of the client installed via the store but somehow it still reports itself to be v0.2.2941 instead of 1.whatever.

Why and how to fix this?

I tried uninstalling the app using

Get-AppXPackage Microsoft.DesktopAppInstaller | Remove-AppXPackage

and this seems to work. But after I install it again from the store, the problem remains the same.