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

Terminal not working when installed from .msixbundle file in a Microsoft Store disabled computer #19055

New Issue
Closed
opened 2026-01-31 06:32:32 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:32:32 +00:00
Owner
Copy Link

Originally created by @atlasfoo on GitHub (Dec 12, 2022).

Hello. I'm having lots of trouble trying to install Windows Terminal in a work organization computer with several network and configuration restrictions, including to have disabled the Microsoft Store and the winget command.

Because of this, we usually install the app via the release distributed .msixbundle file, doing this graphically (double clicking the file and clicking install in the installing wizard), it installs correctly but when we try to open it, results in the following error message:

image

If we do the installation via the Add-AppxPackage command, and try to open the installed terminal, it never opens nor shows any kind of feedback, it only shows the icon in the start menu like it's trying to download something from the store (that we can't use).

image (21)

We follow the instructions on this site, that shows how to install Terminal on Windows Server (without Store and winget), we follow all the steps including the installation of the VCLibs, but the installation only works on machines that have the winget command enabled. I've looked for this error in google and in the issues of this repo but all references to old versions of Windows Terminal.

Computer Specifications:

  • Windows 10 Pro for Workstations 22H2
  • Network/Internet connection via organizational proxy
  • Microsoft Store not usable (blocked by network policy)
  • winget command disabled (deleted by network policy)
  • There is not any chance to use the Store and the winget command in this computer
Originally created by @atlasfoo on GitHub (Dec 12, 2022). Hello. I'm having lots of trouble trying to install Windows Terminal in a work organization computer with several network and configuration restrictions, including to have disabled the Microsoft Store and the `winget` command. Because of this, we usually install the app via the release distributed `.msixbundle` file, doing this graphically (double clicking the file and clicking install in the installing wizard), it installs correctly but when we try to open it, results in the following error message: ![image](https://user-images.githubusercontent.com/25232701/207148796-34b4b5d6-49d3-4597-bc90-97b99ddd1353.png) If we do the installation via the `Add-AppxPackage` command, and try to open the installed terminal, it never opens nor shows any kind of feedback, it only shows the icon in the start menu like it's trying to download something from the store (that we can't use). ![image (21)](https://user-images.githubusercontent.com/25232701/207155937-0e1564ff-7212-45de-8b77-e0777dc99a73.png) We follow the instructions on this [site](https://4sysops.com/archives/install-windows-terminal-without-the-store-on-windows-server/), that shows how to install Terminal on Windows Server (without Store and winget), we follow all the steps including the installation of the VCLibs, but the installation only works on machines that have the winget command enabled. I've looked for this error in google and in the issues of this repo but all references to old versions of Windows Terminal. Computer Specifications: - Windows 10 Pro for Workstations 22H2 - Network/Internet connection via organizational proxy - Microsoft Store not usable (blocked by network policy) - winget command disabled (deleted by network policy) - There is not any chance to use the Store and the winget command in this computer
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 06:32:32 +00:00
claunia commented 2026-01-31 06:32:33 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 12, 2022):

Thanks for the report! For full offline deployment, you'll want to use the "preinstallation kit" that is mentioned in the release notes. It contains an offline provisioning license.

@DHowett commented on GitHub (Dec 12, 2022): Thanks for the report! For full offline deployment, you'll want to use the "preinstallation kit" that is mentioned in the release notes. It contains an offline provisioning license.
claunia commented 2026-01-31 06:32:33 +00:00
Author
Owner
Copy Link

@atlasfoo commented on GitHub (Dec 13, 2022):

Excuse my ignorance, but how can I use the provisioning license for the installation to work? :(

I tried to find something about it in the docs btw.

@atlasfoo commented on GitHub (Dec 13, 2022): Excuse my ignorance, but how can I use the provisioning license for the installation to work? :( I tried to find something about it in the docs btw.
claunia commented 2026-01-31 06:32:33 +00:00
Author
Owner
Copy Link

@miles-smiles commented on GitHub (Feb 8, 2025):

Not sure why this issue was closed. According to the documentation on this page the preinstallation kit seems to be for a different use case and assumes access to the Microsoft store. When I install using the msix bundle, the installation seems to complete but launching the terminal fails.

I'm getting an error message that says: “Windows cannot access C:\Program Files\WindowsApps\Microsoft…\WindowsTerminal.exe”. Sure enough there's no C:\Program Files\WindowsApps directory.

Is there another way around this problem for machines that don't have network access?

@miles-smiles commented on GitHub (Feb 8, 2025): Not sure why this issue was closed. According to the documentation on [this page](https://learn.microsoft.com/en-us/windows/terminal/distributions) the preinstallation kit seems to be for a different use case and assumes access to the Microsoft store. When I install using the msix bundle, the installation seems to complete but launching the terminal fails. I'm getting an error message that says: “Windows cannot access C:\Program Files\WindowsApps\Microsoft…\WindowsTerminal.exe”. Sure enough there's no C:\Program Files\WindowsApps directory. Is there another way around this problem for machines that don't have network access?
claunia commented 2026-01-31 06:32:34 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 13, 2025):

Not sure how I missed your request, atlasfoo! Sorry about that.

You should be able to provision Terminal for offline use using Add-AppxProvisionedPackage (rather than Add-AppxPackage) plus the contents of the preinstallation kit. You'll need to pass the path to the main package, the dependency packages, and the license XML file.

@DHowett commented on GitHub (Feb 13, 2025): Not sure how I missed your request, atlasfoo! Sorry about that. You should be able to provision Terminal for offline use using `Add-AppxProvisionedPackage` (rather than `Add-AppxPackage`) plus the contents of the preinstallation kit. You'll need to pass the path to the main package, the dependency packages, and the license XML file.
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 Issue-Question Needs-Tag-Fix Resolution-Answered
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#19055
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?