Installer issue using msix #6335

Closed
opened 2026-01-31 00:36:00 +00:00 by claunia · 12 comments
Owner

Originally created by @gbargsley on GitHub (Feb 7, 2020).

Environment

Windows build number: Microsoft Windows NT 10.0.18363.0
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Running latest msix installer and progress stops at 16% and no further info displayed.

Expected behavior

Actual behavior

Originally created by @gbargsley on GitHub (Feb 7, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 ```none Windows build number: Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Running latest msix installer and progress stops at 16% and no further info displayed. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 00:36:00 +00:00
Author
Owner

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

This is probably actually a /dupe of #3097

@DHowett-MSFT commented on GitHub (Feb 7, 2020): This is probably actually a /dupe of #3097
Author
Owner

@ghost commented on GitHub (Feb 7, 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 7, 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!
Author
Owner

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

Since it looks like (from your comment on 3097) this isn't a correct resolution, I'm going to reopen this bug for now.

Is there anything else interesting about your environment? Are you isolated from the Windows Store? Can you run the following (from powershell?)

PS> Get-AppxPackage Microsoft.VCLibs.140.00.UWPDesktop

Are you using any third-party antivirus/quarantine software?

@DHowett-MSFT commented on GitHub (Feb 7, 2020): Since it looks like (from your comment on 3097) this _isn't_ a correct resolution, I'm going to reopen this bug for now. Is there anything else interesting about your environment? Are you isolated from the Windows Store? Can you run the following (from powershell?) ``` PS> Get-AppxPackage Microsoft.VCLibs.140.00.UWPDesktop ``` Are you using any third-party antivirus/quarantine software?
Author
Owner

@gbargsley commented on GitHub (Feb 7, 2020):

Ok, I am on a corporate security protected laptop. I run the msix with my administrator account and also the install to UWDesktop. Our policy block MS App store, so that is why I am using the msix.

We use McAfee and CylanceProtect and possible some other security prevention software.

I ran the code you suggested and nothing happened. I also ran a get-apppackagelog after trying with choco but get same reference to dll and framework.
output.txt

@gbargsley commented on GitHub (Feb 7, 2020): Ok, I am on a corporate security protected laptop. I run the msix with my administrator account and also the install to UWDesktop. Our policy block MS App store, so that is why I am using the msix. We use McAfee and CylanceProtect and possible some other security prevention software. I ran the code you suggested and nothing happened. I also ran a get-apppackagelog after trying with choco but get same reference to dll and framework. [output.txt](https://github.com/microsoft/terminal/files/4173048/output.txt)
Author
Owner

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

Thanks for this!

based on these lines;

2/7/2020 1:24:04 PM       628          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.UWPDesktop" 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.UWPDesktop" currently installed
                                       are: {Microsoft.VCLibs.140.00.UWPDesktop_14.0.26905.0_x64__8wekyb3d8bbwe}

and

PS C:\Users\admin_gb> Get-AppxPackage Microsoft.VCLibs.140.00.UWPDesktop
PS C:\Users\admin_gb> Get-AppxPackage Microsoft.VCLibs.140.00.UWPDesktop

that UWPDesktop package never actually got installed. There's this redistributable .exe, but after it's installed it puts a few appx files on disk that unfortunately need to be manually installed. It's not the best situation, which is why we're tracking #3097 and a discussion with the team that owns that redistributable.

@DHowett-MSFT commented on GitHub (Feb 7, 2020): Thanks for this! based on these lines; ``` 2/7/2020 1:24:04 PM 628 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.UWPDesktop" 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.UWPDesktop" currently installed are: {Microsoft.VCLibs.140.00.UWPDesktop_14.0.26905.0_x64__8wekyb3d8bbwe} ``` and ``` PS C:\Users\admin_gb> Get-AppxPackage Microsoft.VCLibs.140.00.UWPDesktop PS C:\Users\admin_gb> Get-AppxPackage Microsoft.VCLibs.140.00.UWPDesktop ``` that UWPDesktop package never actually got installed. There's this redistributable `.exe`, but after it's installed it puts a few appx files on disk that _unfortunately_ need to be manually installed. It's not the best situation, which is why we're tracking #3097 and a discussion with the team that _owns_ that redistributable.
Author
Owner

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

I just tried an install from "C:\program files (x86)\microsoft sdks\Windows Kits\10\ExtensionSDKs\Microsoft.VCLibs.Desktop\14.0\Appx\Retail\x64\Microsoft.VCLibs.x64.14.00.Desktop.appx" -- it looks like that did give me the right/expected version...

@DHowett-MSFT commented on GitHub (Feb 7, 2020): I just tried an install from `"C:\program files (x86)\microsoft sdks\Windows Kits\10\ExtensionSDKs\Microsoft.VCLibs.Desktop\14.0\Appx\Retail\x64\Microsoft.VCLibs.x64.14.00.Desktop.appx"` -- it looks like that did give me the right/expected version...
Author
Owner

@gbargsley commented on GitHub (Feb 7, 2020):

I see this when running the appx you point to. But I cannot enable the sideload because I cannot figure out how to open settings as an admin account to make the change.

image

@gbargsley commented on GitHub (Feb 7, 2020): I see this when running the appx you point to. But I cannot enable the sideload because I cannot figure out how to open settings as an admin account to make the change. ![image](https://user-images.githubusercontent.com/169602/74069618-6c713e80-49c4-11ea-843c-8306d5e0a4cb.png)
Author
Owner

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

I actually don't know how to install that package if you need to enable sideloading. I thought you needed to enable sideloading to install Terminal using MSIX as well ...

That said: for now it will suffice to unzip the x64 part of Windows Terminal (the msixbundle is just a zip file) and use WindowsTerminal.exe. We're investigating alternative deployment mechanisms that'll be more appropriate for enterprise users in #1386.

Since sideloading applications isn't allowed on your machine, and we're at our heart a sideloadable application, I.. don't see how I can really avoid resolving this bug as "duplicate" and "can't fix" ☹️

@DHowett-MSFT commented on GitHub (Feb 10, 2020): I actually don't know how to install that package if you need to enable sideloading. I thought you needed to enable sideloading to install Terminal using MSIX as well ... That said: for now it will suffice to unzip the x64 part of Windows Terminal (the msixbundle is just a zip file) and use WindowsTerminal.exe. We're investigating alternative deployment mechanisms that'll be more appropriate for enterprise users in #1386. Since sideloading applications isn't allowed on your machine, and we're at our heart a sideloadable application, I.. don't see how I can really avoid resolving this bug as "duplicate" and "can't fix" ☹️
Author
Owner

@gbargsley commented on GitHub (Feb 10, 2020):

That worked. I was able to open WindowsTerminal.exe after extracting the CascadiaPackage_0.8.10261.0_x64.msix package.

Thanks

@gbargsley commented on GitHub (Feb 10, 2020): That worked. I was able to open WindowsTerminal.exe after extracting the CascadiaPackage_0.8.10261.0_x64.msix package. Thanks
Author
Owner

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

Thanks for letting me know. Since it does look like a sideloading/distribution issue, I am going to instead call it a /dupe of #1386: we know we need to improve the story here, and this is just another piece of evidence.

@DHowett-MSFT commented on GitHub (Feb 13, 2020): Thanks for letting me know. Since it does look like a sideloading/distribution issue, I am going to instead call it a /dupe of #1386: we know we need to improve the story here, and this is just another piece of evidence.
Author
Owner

@ghost commented on GitHub (Feb 13, 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 13, 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!
Author
Owner

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

or now it will suffice to unzip the x64 part of Windows Terminal (the msixbundle is just a zip file) and use WindowsTerminal.exe.

@DHowett I would like to point out (I can file a bug for this if needed) that following these steps prevents Windows Terminal from detecting the presence of PS Core. I can enter pwsh from Windows Powershell but I preferably would like to see it still auto-detect it. I know v9 added better Powershell support but not sure if that would include this particular "install" method.

@WSLUser commented on GitHub (Feb 14, 2020): > or now it will suffice to unzip the x64 part of Windows Terminal (the msixbundle is just a zip file) and use WindowsTerminal.exe. @DHowett I would like to point out (I can file a bug for this if needed) that following these steps prevents Windows Terminal from detecting the presence of PS Core. I can enter `pwsh` from Windows Powershell but I preferably would like to see it still auto-detect it. I know v9 added better Powershell support but not sure if that would include this particular "install" method.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6335