Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[0.5.2762.0] Cannot install MSIXBundle #3219

Closed
tebeco opened this issue Oct 16, 2019 · 9 comments
Closed

[0.5.2762.0] Cannot install MSIXBundle #3219

tebeco opened this issue Oct 16, 2019 · 9 comments
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@tebeco
Copy link

tebeco commented 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

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 16, 2019
@ludovicalarcon
Copy link

I’m struggling with the same issue

@EmTschi
Copy link

EmTschi commented Oct 16, 2019

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

@tebeco
Copy link
Author

tebeco commented 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 ?

@DHowett-MSFT
Copy link
Contributor

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

@RafneQ
Copy link

RafneQ commented Oct 23, 2019

The discussion continues in the new thread: #1386

@iftkharhussain
Copy link

I’m struggling with the same issue

@rubyFeedback
Copy link

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. :(

@zadjii-msft
Copy link
Member

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

@MickBadran
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

9 participants