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

[0.5.2762.0] Cannot install MSIXBundle #4489

New Issue
Closed
opened 2026-01-30 23:48:57 +00:00 by claunia · 9 comments
claunia commented 2026-01-30 23:48:57 +00:00
Owner
Copy Link

Originally created by @tebeco on GitHub (Oct 16, 2019).

Environment

Windows build number: Microsoft Windows NT 10.0.18362.0
Windows Terminal version: Microsoft.WindowsTerminal_0.5.2762.0_8wekyb3d8bbwe.msixbundle
vc_uwpdesktop.140.exe (installed and repaired, in doubt)

Steps to reproduce

Not sure if this will work but it's similar to the config here

  • Create a VM with OS version 10.0.18362.0
  • install vc_uwpdesktop.140.exe
  • Download the msixbundle
  • Cut the network (to simulate the Dumb firewall corp rules)
  • Manually run the MsixBundle (see screenshot at the end)

Expected behavior

Best idea would be a to have both :

  • a full offline installer package (no pre-requisite like C++140...)
  • Same MsixBundle as today (but with way more info when issue occurs)

I was expecting to have a link on the missing dependency installer, an error code, a log file, an event in event viewer, anyting telling me detailed informations on what's not detected / missing.
As you can see in the screenshot, it's impossible to understand what's missing (no product name, no logs, no linked file)

Actual behavior

App Installer failed to install package dependencies. Ask the developer for package.

image

After i changed my proxy for a more "relax" one, the error changed to this :
image

App Installer failed to install package dependencies. Ask the developer for Microsoft.VCLibs.140.00.UWPDesktop package.

Is that supposed to be this one ?
image

Originally created by @tebeco on GitHub (Oct 16, 2019). # Environment ```none Windows build number: Microsoft Windows NT 10.0.18362.0 Windows Terminal version: Microsoft.WindowsTerminal_0.5.2762.0_8wekyb3d8bbwe.msixbundle vc_uwpdesktop.140.exe (installed and repaired, in doubt) ``` # Steps to reproduce Not sure if this will work but it's similar to the config here * Create a VM with OS version `10.0.18362.0` * install `vc_uwpdesktop.140.exe` * Download the msixbundle * Cut the network (to simulate the Dumb firewall corp rules) * Manually run the `MsixBundle` (see screenshot at the end) # Expected behavior Best idea would be a to have both : * a full offline installer package (no pre-requisite like C++140...) * Same MsixBundle as today (but with way more info when issue occurs) I was expecting to have a link on the missing dependency installer, an error code, a log file, an event in event viewer, anyting telling me detailed informations on what's not detected / missing. As you can see in the screenshot, it's impossible to understand what's missing (no product name, no logs, no linked file) # Actual behavior App Installer failed to install package dependencies. Ask the developer for package. ![image](https://user-images.githubusercontent.com/2266487/66901772-9f4f8b00-efff-11e9-9043-f531ec43bed3.png) After i changed my proxy for a more "relax" one, the error changed to this : ![image](https://user-images.githubusercontent.com/2266487/66906588-42a49e00-f008-11e9-8d6f-b151dfded41f.png) > App Installer failed to install package dependencies. Ask the developer for Microsoft.VCLibs.140.00.UWPDesktop package. Is that supposed to be this one ? ![image](https://user-images.githubusercontent.com/2266487/66906701-6a940180-f008-11e9-83ab-13f433e83a11.png)
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-30 23:48:58 +00:00
claunia commented 2026-01-30 23:48:59 +00:00
Author
Owner
Copy Link

@ludovicalarcon commented on GitHub (Oct 16, 2019):

I’m struggling with the same issue

@ludovicalarcon commented on GitHub (Oct 16, 2019): I’m struggling with the same issue
claunia commented 2026-01-30 23:48:59 +00:00
Author
Owner
Copy Link

@EmTschi commented on GitHub (Oct 16, 2019):

No access to the Windows Store?
look here: #3097

@EmTschi commented on GitHub (Oct 16, 2019): No access to the Windows Store? look here: #3097
claunia commented 2026-01-30 23:48:59 +00:00
Author
Owner
Copy Link

@tebeco commented on GitHub (Oct 16, 2019):

neat ! i'll take a look at it
sorry for the dup'

is it a good idea to set add a bloc in the MD so that it's not in an issue ?
or is that supposed to be fixed later on ? (a full offline bundle would fix it ?)

do you want me to close this ticket ? or do i test it before closing ?

@tebeco commented on GitHub (Oct 16, 2019): neat ! i'll take a look at it sorry for the dup' is it a good idea to set add a bloc in the MD so that it's not in an issue ? or is that supposed to be fixed later on ? (a full offline bundle would fix it ?) do you want me to close this ticket ? or do i test it before closing ?
claunia commented 2026-01-30 23:48:59 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 16, 2019):

We'll work on producing a full offline bundle. Thanks!

@DHowett-MSFT commented on GitHub (Oct 16, 2019): We'll work on producing a full offline bundle. Thanks!
claunia commented 2026-01-30 23:49:00 +00:00
Author
Owner
Copy Link

@RafneQ commented on GitHub (Oct 23, 2019):

The discussion continues in the new thread: https://github.com/microsoft/terminal/issues/1386

@RafneQ commented on GitHub (Oct 23, 2019): The discussion continues in the new thread: https://github.com/microsoft/terminal/issues/1386
claunia commented 2026-01-30 23:49:00 +00:00
Author
Owner
Copy Link

@iftkharhussain commented on GitHub (Apr 8, 2020):

I’m struggling with the same issue

@iftkharhussain commented on GitHub (Apr 8, 2020): I’m struggling with the same issue
claunia commented 2026-01-30 23:49:01 +00:00
Author
Owner
Copy Link

@rubyFeedback commented on GitHub (Aug 28, 2020):

Same here. WindowsTerminal came only with a MSIXBundle.

I am used to .exe and .msi - no clue yet what to do with MSIXBundle extensions .... tried to
double click, then got the above error message and another message stating this does
not work on my desktop machine. So now I am left in the dark. :(

@rubyFeedback commented on GitHub (Aug 28, 2020): Same here. WindowsTerminal came only with a MSIXBundle. I am used to .exe and .msi - no clue yet what to do with MSIXBundle extensions .... tried to double click, then got the above error message and another message stating this does not work on my desktop machine. So now I am left in the dark. :(
claunia commented 2026-01-30 23:49:01 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 28, 2020):

and another message stating this does not work on my desktop machine. So now I am left in the dark. :(

What was the error message exactly?

I'm pretty sure we've been shipping the VCLibs with the terminal package for the last couple releases, so you shouldn't be getting this exact error message any longer.

See also #6010

@zadjii-msft commented on GitHub (Aug 28, 2020): > and another message stating this does not work on my desktop machine. So now I am left in the dark. :( What was the error message _exactly_? I'm pretty sure we've been shipping the VCLibs with the terminal package for the last couple releases, so you shouldn't be getting this _exact_ error message any longer. See also #6010
claunia commented 2026-01-30 23:49:02 +00:00
Author
Owner
Copy Link

@MickBadran commented on GitHub (Nov 2, 2020):

and another message stating this does not work on my desktop machine. So now I am left in the dark. :(

What was the error message exactly?

I'm pretty sure we've been shipping the VCLibs with the terminal package for the last couple releases, so you shouldn't be getting this exact error message any longer.

See also #6010

The exact error message is

"The app didn't start."

image

Let me know how you go - I also renamed to .zip and tried to run either the x86 or x64 package on their own. No go.

@MickBadran commented on GitHub (Nov 2, 2020): > > and another message stating this does not work on my desktop machine. So now I am left in the dark. :( > > What was the error message _exactly_? > > I'm pretty sure we've been shipping the VCLibs with the terminal package for the last couple releases, so you shouldn't be getting this _exact_ error message any longer. > > See also #6010 The exact error message is "**The app didn't start.**" ![image](https://user-images.githubusercontent.com/10069146/97819377-43d06800-1cfc-11eb-99b9-7f679eaad8c3.png) Let me know how you go - I also renamed to .zip and tried to run either the x86 or x64 package on their own. No go.
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 Needs-Triage
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#4489
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?