starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Cannot upgrade from v1.12.10393.0 to v1.13.11431.0 with chocolately due to Microsoft.VCLibs.140.00.UWPDesktop #17758

New Issue
Closed
opened 2026-01-31 05:52:31 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 05:52:31 +00:00
Owner
Copy Link

Originally created by @rklec on GitHub (Jun 21, 2022).

Windows Terminal version

1.12.10393.0

Windows build number

10.0.19044.0

Other Software

N/A

Steps to reproduce

choco upgrade -y microsoft-windows-terminal

Expected Behavior

Upgrade suceeds.

Actual Behavior

>  choco upgrade -y vcredist140
Chocolatey v1.1.0
Upgrading the following packages:
vcredist140
By upgrading, you accept licenses for the packages.
vcredist140 v14.32.31326 is the latest version available based on your source(s).

Chocolatey upgraded 0/1 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
> choco upgrade -y microsoft-windows-terminal
Chocolatey v1.1.0
Upgrading the following packages:
microsoft-windows-terminal
By upgrading, you accept licenses for the packages.

You have microsoft-windows-terminal v1.12.10393.0 installed. Version 1.13.11431.0 is available based on your source(s).
Progress: Downloading microsoft-windows-terminal 1.13.11431.0... 100%

microsoft-windows-terminal v1.13.11431.0 [Approved]
microsoft-windows-terminal package files upgrade completed. Performing other installation steps.
Progress: 0% - Processing                                                                                              ERROR: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Deployment failed with HRESULT: 0x80073CF3, Fehler bei Updates des Pakets (Abhängigkeits- oder Konfliktüberprüfung).

Das Paket Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe kann von Windows nicht installiert werden, da es von einem Framework abhängig ist, das nicht gefunden wurde. Stellen Sie das von CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US veröffentlichte Framework Microsoft.VCLibs.140.00.UWPDesktop mit einer neutralen oder x64-Prozessorarchitektur und Mindestversion 14.0.30035.0 zusammen mit dem zu installierenden Paket bereit. Die derzeit installierten Frameworks mit
Das Paket Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe kann von Windows nicht installiert werden, da es von einem Framework abhängig ist, das nicht gefunden wurde. Stellen Sie das von CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US veröffentlichte Framework Microsoft.VCLibs.140.00.UWPDesktop mit einer neutralen oder x64-Prozessorarchitektur und Mindestversion 14.0.30035.0 zusammen mit dem zu installierenden Paket bereit. Die derzeit installierten Frameworks mit dem Namen Microsoft.VCLibs.140.00.UWPDesktop sind: {Microsoft.VCLibs.140.00.UWPDesktop_14.0.27629.0_x64__8wekyb3d8bbwe}

NOTE: For additional information, look for [ActivityId] 59f0e28b-853c-0008-5a62-f4593c85d801 in the Event Log or use the command line Get-AppPackageLog -ActivityID 59f0e28b-853c-0008-5a62-f4593c85d801

The upgrade of microsoft-windows-terminal was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'.
 See log for details.

Chocolatey upgraded 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - microsoft-windows-terminal (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'.
 See log for details.

This looks very similar to https://github.com/microsoft/terminal/issues/3097, however this seems solved long ago and all dependencies should be shipped with the app.

Originally created by @rklec on GitHub (Jun 21, 2022). ### Windows Terminal version 1.12.10393.0 ### Windows build number 10.0.19044.0 ### Other Software N/A ### Steps to reproduce `choco upgrade -y microsoft-windows-terminal` ### Expected Behavior Upgrade suceeds. ### Actual Behavior ``` > choco upgrade -y vcredist140 Chocolatey v1.1.0 Upgrading the following packages: vcredist140 By upgrading, you accept licenses for the packages. vcredist140 v14.32.31326 is the latest version available based on your source(s). Chocolatey upgraded 0/1 packages. See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log). > choco upgrade -y microsoft-windows-terminal Chocolatey v1.1.0 Upgrading the following packages: microsoft-windows-terminal By upgrading, you accept licenses for the packages. You have microsoft-windows-terminal v1.12.10393.0 installed. Version 1.13.11431.0 is available based on your source(s). Progress: Downloading microsoft-windows-terminal 1.13.11431.0... 100% microsoft-windows-terminal v1.13.11431.0 [Approved] microsoft-windows-terminal package files upgrade completed. Performing other installation steps. Progress: 0% - Processing ERROR: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Deployment failed with HRESULT: 0x80073CF3, Fehler bei Updates des Pakets (Abhängigkeits- oder Konfliktüberprüfung). Das Paket Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe kann von Windows nicht installiert werden, da es von einem Framework abhängig ist, das nicht gefunden wurde. Stellen Sie das von CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US veröffentlichte Framework Microsoft.VCLibs.140.00.UWPDesktop mit einer neutralen oder x64-Prozessorarchitektur und Mindestversion 14.0.30035.0 zusammen mit dem zu installierenden Paket bereit. Die derzeit installierten Frameworks mit Das Paket Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe kann von Windows nicht installiert werden, da es von einem Framework abhängig ist, das nicht gefunden wurde. Stellen Sie das von CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US veröffentlichte Framework Microsoft.VCLibs.140.00.UWPDesktop mit einer neutralen oder x64-Prozessorarchitektur und Mindestversion 14.0.30035.0 zusammen mit dem zu installierenden Paket bereit. Die derzeit installierten Frameworks mit dem Namen Microsoft.VCLibs.140.00.UWPDesktop sind: {Microsoft.VCLibs.140.00.UWPDesktop_14.0.27629.0_x64__8wekyb3d8bbwe} NOTE: For additional information, look for [ActivityId] 59f0e28b-853c-0008-5a62-f4593c85d801 in the Event Log or use the command line Get-AppPackageLog -ActivityID 59f0e28b-853c-0008-5a62-f4593c85d801 The upgrade of microsoft-windows-terminal was NOT successful. Error while running 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'. See log for details. Chocolatey upgraded 0/1 packages. 1 packages failed. See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log). Failures - microsoft-windows-terminal (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\microsoft-windows-terminal\tools\chocolateyInstall.ps1'. See log for details. ``` This looks very similar to https://github.com/microsoft/terminal/issues/3097, however this seems solved long ago and all dependencies should be shipped with the app.
claunia added the Needs-TriageIssue-BugResolution-ExternalNeeds-Tag-Fix labels 2026-01-31 05:52:31 +00:00
claunia commented 2026-01-31 05:52:32 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 21, 2022):

Thanks for the report! We don't actually maintain the choco package for the Terminal ourselves (as discussed in #2044). As noted in the README:

If you have any issues when installing/upgrading the package please go to the Windows Terminal package page and follow the Chocolatey triage process

I suspect whoever does maintain the choco package needs to use the Windows 10 versions of the Terminal package, instead of the Windows 11 versions. Sorry about that!

@zadjii-msft commented on GitHub (Jun 21, 2022): Thanks for the report! We don't actually maintain the choco package for the Terminal ourselves (as discussed in #2044). As noted in the README: > If you have any issues when installing/upgrading the package please go to the [Windows Terminal package page](https://chocolatey.org/packages/microsoft-windows-terminal) and follow the [Chocolatey triage process](https://chocolatey.org/docs/package-triage-process) I suspect whoever does maintain the choco package needs to use the Windows 10 versions of the Terminal package, instead of the Windows 11 versions. Sorry about that!
claunia commented 2026-01-31 05:52:32 +00:00
Author
Owner
Copy Link

@rklec commented on GitHub (Jun 21, 2022):

Okay, reported downstream to the maintainer(s) at https://github.com/mkevenaar/chocolatey-packages/issues/136

@rklec commented on GitHub (Jun 21, 2022): Okay, reported downstream to the maintainer(s) at https://github.com/mkevenaar/chocolatey-packages/issues/136
claunia commented 2026-01-31 05:52:32 +00:00
Author
Owner
Copy Link

@theperm commented on GitHub (Jun 21, 2022):

Thanks for the report! We don't actually maintain the choco package for the Terminal ourselves (as discussed in #2044). As noted in the README:

If you have any issues when installing/upgrading the package please go to the Windows Terminal package page and follow the Chocolatey triage process

I suspect whoever does maintain the choco package needs to use the Windows 10 versions of the Terminal package, instead of the Windows 11 versions. Sorry about that!

I checked and its using this file Microsoft.WindowsTerminalPreview_Win10_1.14.1451.0_8wekyb3d8bbwe.msixbundl

@theperm commented on GitHub (Jun 21, 2022): > Thanks for the report! We don't actually maintain the choco package for the Terminal ourselves (as discussed in #2044). As noted in the README: > > > If you have any issues when installing/upgrading the package please go to the [Windows Terminal package page](https://chocolatey.org/packages/microsoft-windows-terminal) and follow the [Chocolatey triage process](https://chocolatey.org/docs/package-triage-process) > > I suspect whoever does maintain the choco package needs to use the Windows 10 versions of the Terminal package, instead of the Windows 11 versions. Sorry about that! I checked and its using this file Microsoft.WindowsTerminalPreview_Win10_1.14.1451.0_8wekyb3d8bbwe.msixbundl
claunia commented 2026-01-31 05:52:33 +00:00
Author
Owner
Copy Link

@rklec commented on GitHub (Feb 6, 2023):

This script here finally made it work: https://github.com/microsoft/terminal/issues/3097#issuecomment-1345242698

More details here: https://github.com/mkevenaar/chocolatey-packages/issues/136#issuecomment-1418874749

@rklec commented on GitHub (Feb 6, 2023): This script here finally made it work: https://github.com/microsoft/terminal/issues/3097#issuecomment-1345242698 More details here: https://github.com/mkevenaar/chocolatey-packages/issues/136#issuecomment-1418874749
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Tag-Fix Needs-Triage Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17758
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?