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

Preview 0.5 asset fails to install (hangs on 'Installing required frameworks 16%') #4038

New Issue
Closed
opened 2026-01-30 23:36:35 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 23:36:35 +00:00
Owner
Copy Link

Originally created by @daldr-ntml on GitHub (Sep 25, 2019).

Originally assigned to: @bitcrazed on GitHub.

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.295]
Windows Terminal version (if applicable): 0.5.2661.0
Any other software? N/A

Steps to reproduce

In https://github.com/microsoft/terminal/issues/2647 I reported that the Github preview asset 0.4 hung when installing behind a company proxy server. This was fixed by manually installing dependency package: VCLibs.140.

Now, on installing Terminal Preview 0.5, using the GitHub release asset, the same problem happens. There is no indication of the missing dependency. This is on the same machine so I assume VCLibs.140 is still present.

image

Originally created by @daldr-ntml on GitHub (Sep 25, 2019). Originally assigned to: @bitcrazed on GitHub. # Environment ``` Windows build number: Microsoft Windows [Version 10.0.18362.295] Windows Terminal version (if applicable): 0.5.2661.0 Any other software? N/A ``` # Steps to reproduce In https://github.com/microsoft/terminal/issues/2647 I reported that the Github preview asset 0.4 hung when installing behind a company proxy server. This was fixed by manually installing dependency package: VCLibs.140. Now, on installing Terminal Preview 0.5, using the GitHub release asset, the same problem happens. There is no indication of the missing dependency. This is on the same machine so I assume VCLibs.140 is still present. ![image](https://user-images.githubusercontent.com/7724321/65578765-5e1f0a80-df6e-11e9-9e48-d0911162f752.png)
claunia added the Issue-BugResolution-ExternalProduct-TerminalArea-Build labels 2026-01-30 23:36:35 +00:00
claunia commented 2026-01-30 23:36:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 25, 2019):

I'm not sure why this thread isn't a dupe of #2647. The original thread is still open, and we haven't resolved the problem, so whatever caused it to be broken is probably still broken for 0.5. I don't think we need another one of these threads for each release...

/dupe #2647

@zadjii-msft commented on GitHub (Sep 25, 2019): _I'm not sure why this thread isn't a dupe of #2647_. The original thread is still open, and we haven't resolved the problem, so whatever caused it to be broken is probably _still_ broken for 0.5. I don't think we need another one of these threads for each release... /dupe #2647
claunia commented 2026-01-30 23:36:36 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 25, 2019):

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 (Sep 25, 2019): 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-30 23:36:36 +00:00
Author
Owner
Copy Link

@daldr-ntml commented on GitHub (Sep 25, 2019):

This issue is different to #2647. #2647 was fixed by manually installing 'C++ Runtime v14 framework package'. That package is already installed on my machine (same machine as was used for #2647) but the 0.5 asset does not install. Therefore it must be failing because of another dependency, which we need to identify.

Therefore I contend that this is not a duplicate. Please reopen.

@daldr-ntml commented on GitHub (Sep 25, 2019): This issue is different to #2647. #2647 was fixed by manually installing 'C++ Runtime v14 framework package'. That package is already installed on my machine (same machine as was used for #2647) but the 0.5 asset does not install. Therefore it must be failing because of another dependency, which we need to identify. Therefore I contend that this is not a duplicate. Please reopen.
claunia commented 2026-01-30 23:36:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 25, 2019):

Sure, assigning @bitcrazed to loop in the appropriate teams.

@zadjii-msft commented on GitHub (Sep 25, 2019): Sure, assigning @bitcrazed to loop in the appropriate teams.
claunia commented 2026-01-30 23:36:36 +00:00
Author
Owner
Copy Link

@daldr-ntml commented on GitHub (Nov 14, 2019):

This problem is still present in 0.6.2951.0. Any chance of a fix please?

@daldr-ntml commented on GitHub (Nov 14, 2019): This problem is still present in 0.6.2951.0. Any chance of a fix please?
claunia commented 2026-01-30 23:36:36 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Nov 15, 2019):

Thanks for reporting @DavidA2014. We're investigating, but as you can see from the appmanifest, Terminal only depends on the VC 140 RTL redist:

  <Dependencies>
    <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.18362.0" MaxVersionTested="10.0.18362.0" />
    <PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.27323.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
    <PackageDependency Name="Microsoft.VCLibs.140.00.UWPDesktop" MinVersion="14.0.27323.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" />
  </Dependencies>

It is possible that:

  1. Your machine's installation engine is in an incomplete/pending/waiting state, perhaps confused by how your employer's proxy blocks traffic and/or and hasn't yet seen the manually installed VC 140 RTL redist
  2. Your admin's may have removed/uninstalled the VC redist behind the scenes

Can you please

  1. Install the redist
  2. Rebooted your machine
  3. (Re) install the Terminal

⚠ If you still see problems, as per the redist's "Details" section, ensure that your VC 140 Desktop redist is installed. :

After installation succeeds: If you look under the folder “C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs” on your machine, you will see the Microsoft.VCLibs.Desktop folder that contain the framework packages for C++ Runtime 14.0.

@bitcrazed commented on GitHub (Nov 15, 2019): Thanks for reporting @DavidA2014. We're investigating, but as you can see from the appmanifest, Terminal only depends on the VC 140 RTL redist: ```xml <Dependencies> <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.18362.0" MaxVersionTested="10.0.18362.0" /> <PackageDependency Name="Microsoft.VCLibs.140.00" MinVersion="14.0.27323.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> <PackageDependency Name="Microsoft.VCLibs.140.00.UWPDesktop" MinVersion="14.0.27323.0" Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" /> </Dependencies> ``` It is possible that: 1. Your machine's installation engine is in an incomplete/pending/waiting state, perhaps confused by how your employer's proxy blocks traffic and/or and hasn't yet seen the manually installed VC 140 RTL redist 1. Your admin's may have removed/uninstalled the VC redist behind the scenes Can you please 1. Install the redist 1. Rebooted your machine 1. (Re) install the Terminal ⚠ If you still see problems, as per [the redist](https://www.microsoft.com/en-us/download/details.aspx?id=53175)'s "Details" section, ensure that your VC 140 Desktop redist is installed. : > After installation succeeds: If you look under the folder “C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs” on your machine, you will see the Microsoft.VCLibs.Desktop folder that contain the framework packages for C++ Runtime 14.0.
claunia commented 2026-01-30 23:36:37 +00:00
Author
Owner
Copy Link

@daldr-ntml commented on GitHub (Nov 15, 2019):

@bitcrazed Thanks for your help. The redist was already installed. I uninstalled Terminal, rebooted and then ran the 0.6 installer again. It succeeded this time.

I'll close this issue now. Could you support an installation log to make it easier to diagnose why the installation fails when the redist is not found?

@daldr-ntml commented on GitHub (Nov 15, 2019): @bitcrazed Thanks for your help. The redist was already installed. I uninstalled Terminal, rebooted and then ran the 0.6 installer again. It succeeded this time. I'll close this issue now. Could you support an installation log to make it easier to diagnose why the installation fails when the redist is not found?
claunia commented 2026-01-30 23:36:37 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Nov 15, 2019):

Good to know, thanks @DavidA2014.

It's quite possible that if your corporate Proxy/Firewall may simply block certain calls/responses/traffic causing your machine's installer's state engine to stall, waiting for a response that never comes. If you do see this again, please let us know and we'll broker a conversation with the installer engine team.

@bitcrazed commented on GitHub (Nov 15, 2019): Good to know, thanks @DavidA2014. It's quite possible that if your corporate Proxy/Firewall may simply block certain calls/responses/traffic causing your machine's installer's state engine to stall, waiting for a response that never comes. If you do see this again, please let us know and we'll broker a conversation with the installer engine team.
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 Area-Build Issue-Bug Product-Terminal 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#4038
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?