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

Bug report - Chocolately install fails when attempting to upgrade to 0.4.2382.0 #3591

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

Originally created by @Taubin on GitHub (Aug 27, 2019).

Environment

Microsoft Windows [Version 10.0.18936.1000]
Windows Terminal version (if applicable):  Version: 0.3.2171.0

Any other software?

Steps to reproduce

Run powershell as admin
Run the following command: choco upgrade microsoft-windows-terminal

Expected behavior

I expect Chocolatey to install the latest version of Terminal (0.4.2382.0)

Actual behavior

The installation fails with the following error:

RROR: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Deployment failed with HRESULT: 0x80073CFB, The provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details.

Deployment of package Microsoft.WindowsTerminal_0.3.2171.0_x64__8wekyb3d8bbwe was blocked because the provided package has the same identity as an already-installed package but the contents are different. Increment the version number of the package to be installed, or remove the old package for every user on the system before installing this package.

NOTE: For additional information, look for [ActivityId] a1d00f98-5894-0000-f26c-d5a19458d501 in the Event Log or use the command line Get-AppPackageLog -ActivityID a1d00f98-5894-0000-f26c-d5a19458d501

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.

Full logfile:
https://gist.github.com/Taubin/57643031f49ab624cfe5375d79f7b93e

Originally created by @Taubin on GitHub (Aug 27, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ``` Microsoft Windows [Version 10.0.18936.1000] Windows Terminal version (if applicable): Version: 0.3.2171.0 Any other software? ``` # Steps to reproduce Run powershell as admin Run the following command: choco upgrade microsoft-windows-terminal # Expected behavior I expect Chocolatey to install the latest version of Terminal (0.4.2382.0) # Actual behavior The installation fails with the following error: ``` RROR: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Deployment failed with HRESULT: 0x80073CFB, The provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details. Deployment of package Microsoft.WindowsTerminal_0.3.2171.0_x64__8wekyb3d8bbwe was blocked because the provided package has the same identity as an already-installed package but the contents are different. Increment the version number of the package to be installed, or remove the old package for every user on the system before installing this package. NOTE: For additional information, look for [ActivityId] a1d00f98-5894-0000-f26c-d5a19458d501 in the Event Log or use the command line Get-AppPackageLog -ActivityID a1d00f98-5894-0000-f26c-d5a19458d501 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. ``` Full logfile: https://gist.github.com/Taubin/57643031f49ab624cfe5375d79f7b93e
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-30 23:25:05 +00:00
claunia commented 2026-01-30 23:25:06 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 27, 2019):

/ping @mkevenaar

@DHowett-MSFT commented on GitHub (Aug 27, 2019): /ping @mkevenaar
claunia commented 2026-01-30 23:25:06 +00:00
Author
Owner
Copy Link

@mkevenaar commented on GitHub (Aug 27, 2019):

@taubin this is known and should be resolved with the next release. As a work around you could run Get-AppxPackage -Name Microsoft.WindowsTerminal | Remove-AppxPackage in an elevated powershell. After that, you can install the package as usual.

@DHowett-MSFT thanks for pinging me!

@mkevenaar commented on GitHub (Aug 27, 2019): @taubin this is known and should be resolved with the next release. As a work around you could run ` Get-AppxPackage -Name Microsoft.WindowsTerminal | Remove-AppxPackage` in an elevated powershell. After that, you can install the package as usual. @DHowett-MSFT thanks for pinging me!
claunia commented 2026-01-30 23:25:07 +00:00
Author
Owner
Copy Link

@mkevenaar commented on GitHub (Aug 27, 2019):

Also it seems that the package is not updated yet to the latest release. This
Should be available soon.

@mkevenaar commented on GitHub (Aug 27, 2019): Also it seems that the package is not updated yet to the latest release. This Should be available soon.
claunia commented 2026-01-30 23:25:07 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Aug 29, 2019):

Closing since this is external. The core issue here was that the chocolatey package attempted to install the same (?) or an older (??) version of Terminal over the same (?) or a newer (??) version.

@DHowett-MSFT commented on GitHub (Aug 29, 2019): Closing since this is external. The core issue here was that the chocolatey package attempted to install the same (?) or an older (??) version of Terminal over the same (?) or a newer (??) version.
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 Needs-Tag-Fix 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#3591
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?