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

Cannot install Windows terminal - dependencies to VCLibs #6401

New Issue
Closed
opened 2026-01-31 00:37:39 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 00:37:39 +00:00
Owner
Copy Link

Originally created by @4integration on GitHub (Feb 13, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.628]

Any other software?

Steps to reproduce

Tried installing Windows Terminal both via msixbundle and Chocolatey but both fails based on the dependency check to Microsoft.VCLibs.140.00 but have it installed.

Running the install via an elevated PowerShell.
Do not have access to Windows Store due to corporate policies.

image

Expected behavior

To get Windows Terminal installed

Actual behavior

With Chocolatey

PS C:\Users\myuser\Downloads> choco install microsoft-windows-terminal
Chocolatey v0.10.15
Installing the following packages:
microsoft-windows-terminal
By installing you accept licenses for the packages.
Progress: Downloading microsoft-windows-terminal 0.8.10261.0... 100%

microsoft-windows-terminal v0.8.10261.0 [Approved]
microsoft-windows-terminal package files install completed. Performing other installation steps.
The package microsoft-windows-terminal wants to run 'chocolateyinstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation
Do you want to run the script?([Y]es/[A]ll - yes to all/[N]o/[P]rint): Y

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, Package failed updates, dependency or conflict validation.

Windows cannot install package Microsoft.WindowsTerminal_0.8.10261.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.27323.0, along with this package to install. The frameworks with name "Microsoft.VCLibs.140.00" currently installed are: {Microsoft.VCLibs.140
Windows cannot install package Microsoft.WindowsTerminal_0.8.10261.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.27323.0, along with this package to install. The frameworks with name "Microsoft.VCLibs.140.00" currently installed are: {Microsoft.VCLibs.140.00_14.0.25426.0_x64__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.25426.0_x86__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.26706.0_x64__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.26706.0_x86__8wekyb3d8bbwe}

NOTE: For additional information, look for [ActivityId] c0ce159a-e239-0004-04de-cec039e2d501 in the Event Log or use the command line Get-AppPackageLog -ActivityID c0ce159a-e239-0004-04de-cec039e2d501

The install 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 installed 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.
PS C:\Users\myuser\Downloads>

Detailed log: chocolatey-windows-terminal.log

With msixbundle

PS C:\Users\myuser\Downloads> Add-AppPackage -path ".\Microsoft.WindowsTerminal_0.8.10261.0_8wekyb3d8bbwe.msixbundle"
Add-AppPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation.
Windows cannot install package Microsoft.WindowsTerminal_0.8.10261.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00" published by "CN=Microsoft Corporation, O=Microsoft Corpora
tion, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.27323.0, along with this package to install. The frameworks with name "Microsoft.VCLibs.140.00" currently installed are: {Microsoft.VCLibs.140
Windows cannot install package Microsoft.WindowsTerminal_0.8.10261.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00" published by "CN=Microsoft Corporation, O=Microsoft Corpora
tion, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.27323.0, along with this package to install. The frameworks with name "Microsoft.VCLibs.140.00" currently installed are: {Microsoft.VCLibs.140.00_14.0.25426.0
_x64__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.25426.0_x86__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.26706.0_x64__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.26706.0_x86__8wekyb3d8bbwe}
NOTE: For additional information, look for [ActivityId] c0ce159a-e239-0002-48ad-cec039e2d501 in the Event Log or use the command line Get-AppPackageLog -ActivityID c0ce159a-e239-0002-48ad-cec039e2d501
At line:1 char:1
+ Add-AppPackage -path ".\Microsoft.WindowsTerminal_0.8.10261.0_8wekyb3 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (C:\Users\dfc086...bbwe.msixbundle:String) [Add-AppxPackage], IOException
    + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand
Originally created by @4integration on GitHub (Feb 13, 2020). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18363.628] Any other software? ``` # Steps to reproduce Tried installing Windows Terminal both via msixbundle and Chocolatey but both fails based on the dependency check to Microsoft.VCLibs.140.00 but have it installed. Running the install via an **elevated** PowerShell. Do **not** have access to Windows Store due to corporate policies. ![image](https://user-images.githubusercontent.com/11057350/74413742-49b9ac80-4e40-11ea-950d-a699a3ba98f9.png) # Expected behavior To get Windows Terminal installed # Actual behavior ## With Chocolatey ``` PS C:\Users\myuser\Downloads> choco install microsoft-windows-terminal Chocolatey v0.10.15 Installing the following packages: microsoft-windows-terminal By installing you accept licenses for the packages. Progress: Downloading microsoft-windows-terminal 0.8.10261.0... 100% microsoft-windows-terminal v0.8.10261.0 [Approved] microsoft-windows-terminal package files install completed. Performing other installation steps. The package microsoft-windows-terminal wants to run 'chocolateyinstall.ps1'. Note: If you don't run this script, the installation will fail. Note: To confirm automatically next time, use '-y' or consider: choco feature enable -n allowGlobalConfirmation Do you want to run the script?([Y]es/[A]ll - yes to all/[N]o/[P]rint): Y 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, Package failed updates, dependency or conflict validation. Windows cannot install package Microsoft.WindowsTerminal_0.8.10261.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.27323.0, along with this package to install. The frameworks with name "Microsoft.VCLibs.140.00" currently installed are: {Microsoft.VCLibs.140 Windows cannot install package Microsoft.WindowsTerminal_0.8.10261.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.27323.0, along with this package to install. The frameworks with name "Microsoft.VCLibs.140.00" currently installed are: {Microsoft.VCLibs.140.00_14.0.25426.0_x64__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.25426.0_x86__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.26706.0_x64__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.26706.0_x86__8wekyb3d8bbwe} NOTE: For additional information, look for [ActivityId] c0ce159a-e239-0004-04de-cec039e2d501 in the Event Log or use the command line Get-AppPackageLog -ActivityID c0ce159a-e239-0004-04de-cec039e2d501 The install 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 installed 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. PS C:\Users\myuser\Downloads> ``` **Detailed log**: [chocolatey-windows-terminal.log](https://github.com/microsoft/terminal/files/4197226/chocolatey-windows-terminal.log) ## With msixbundle ``` PS C:\Users\myuser\Downloads> Add-AppPackage -path ".\Microsoft.WindowsTerminal_0.8.10261.0_8wekyb3d8bbwe.msixbundle" Add-AppPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation. Windows cannot install package Microsoft.WindowsTerminal_0.8.10261.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00" published by "CN=Microsoft Corporation, O=Microsoft Corpora tion, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.27323.0, along with this package to install. The frameworks with name "Microsoft.VCLibs.140.00" currently installed are: {Microsoft.VCLibs.140 Windows cannot install package Microsoft.WindowsTerminal_0.8.10261.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.VCLibs.140.00" published by "CN=Microsoft Corporation, O=Microsoft Corpora tion, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 14.0.27323.0, along with this package to install. The frameworks with name "Microsoft.VCLibs.140.00" currently installed are: {Microsoft.VCLibs.140.00_14.0.25426.0 _x64__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.25426.0_x86__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.26706.0_x64__8wekyb3d8bbwe Microsoft.VCLibs.140.00_14.0.26706.0_x86__8wekyb3d8bbwe} NOTE: For additional information, look for [ActivityId] c0ce159a-e239-0002-48ad-cec039e2d501 in the Event Log or use the command line Get-AppPackageLog -ActivityID c0ce159a-e239-0002-48ad-cec039e2d501 At line:1 char:1 + Add-AppPackage -path ".\Microsoft.WindowsTerminal_0.8.10261.0_8wekyb3 ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : WriteError: (C:\Users\dfc086...bbwe.msixbundle:String) [Add-AppxPackage], IOException + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand ```
claunia added the Resolution-Duplicate label 2026-01-31 00:37:39 +00:00
claunia commented 2026-01-31 00:37:40 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 14, 2020):

Thanks for the good report here! We're tracking issues with the VCLibs in /dup #3097

@DHowett-MSFT commented on GitHub (Feb 14, 2020): Thanks for the good report here! We're tracking issues with the VCLibs in /dup #3097
claunia commented 2026-01-31 00:37:40 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 14, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Feb 14, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 00:37:40 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 14, 2020):

(It only mentions one of them, but we must fix both.)

@DHowett-MSFT commented on GitHub (Feb 14, 2020): (It only mentions one of them, but we must fix both.)
claunia commented 2026-01-31 00:37:40 +00:00
Author
Owner
Copy Link

@4integration commented on GitHub (Mar 18, 2020):

Tested with version 0.10.761.0 - same issues

@4integration commented on GitHub (Mar 18, 2020): Tested with version 0.10.761.0 - same issues
claunia commented 2026-01-31 00:37:40 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 18, 2020):

Given that we have not changed the libraries we depend on, this should come as no surprise.

@DHowett-MSFT commented on GitHub (Mar 18, 2020): Given that we have not changed the libraries we depend on, this should come as no surprise.
claunia commented 2026-01-31 00:37:41 +00:00
Author
Owner
Copy Link

@4integration commented on GitHub (Mar 18, 2020):

Maybe no surprise for you having insights in the dependencies but for me as enterprise user as just want to install and use the wanted Windows Terminal on our current Win10 machines.

Eventually we will get Mac or Linux as development environments ....

@4integration commented on GitHub (Mar 18, 2020): Maybe no surprise for you having insights in the dependencies but for me as enterprise user as just want to install and use the wanted Windows Terminal on our current Win10 machines. Eventually we will get Mac or Linux as development environments ....
claunia commented 2026-01-31 00:37:41 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 18, 2020):

Sorry, my comment was meant as a joke. I'll make sure that we update one of the connected threads here when we resolve our dependency issues.

@DHowett-MSFT commented on GitHub (Mar 18, 2020): Sorry, my comment was meant as a joke. I'll make sure that we update one of the connected threads here when we resolve our dependency issues.
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 Resolution-Duplicate
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#6401
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?