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

Cannot run terminal when Windows Store is not available #9787

New Issue
Closed
opened 2026-01-31 02:03:46 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 02:03:46 +00:00
Owner
Copy Link

Originally created by @CobusKruger on GitHub (Jul 23, 2020).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): v1.1.2021.0

Steps to reproduce

On my domain-joined PC, Windows Store apps are disabled. So I downloaded the latest release from here: https://github.com/microsoft/terminal/releases/download/v1.1.2021.0/Microsoft.WindowsTerminal_1.1.2021.0_8wekyb3d8bbwe.msixbundle

I then double-click the file to install it, and installation goes through as expected. In the Start menu I now have an icon for Windows Terminal. I click that to launch the app.

Expected behavior

I expect Windows Terminal to open.

Actual behavior

I get an error:
image

I verified that the file exists. The text about it being a network location is non-sensical, as it is on my laptop hard drive. The error code (0x800704cf) is the same as I get when trying to sign into a Windows Store app, then with the message "You will need the Internet for this." Internet access is working fine, I'm not connected to a VPN, and I don't have a proxy specified.

Windows Firewall is also turned off, but I do have Cylance installed.

Originally created by @CobusKruger on GitHub (Jul 23, 2020). <!-- 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: 10.0.18363.0 Windows Terminal version (if applicable): v1.1.2021.0 ``` # Steps to reproduce On my domain-joined PC, Windows Store apps are disabled. So I downloaded the latest release from here: https://github.com/microsoft/terminal/releases/download/v1.1.2021.0/Microsoft.WindowsTerminal_1.1.2021.0_8wekyb3d8bbwe.msixbundle I then double-click the file to install it, and installation goes through as expected. In the Start menu I now have an icon for Windows Terminal. I click that to launch the app. # Expected behavior I expect Windows Terminal to open. # Actual behavior I get an error: ![image](https://user-images.githubusercontent.com/10893522/88284482-c608c380-cced-11ea-8ca0-6f536aae0076.png) I verified that the file exists. The text about it being a network location is non-sensical, as it is on my laptop hard drive. The error code (0x800704cf) is the same as I get when trying to sign into a Windows Store app, then with the message "You will need the Internet for this." Internet access is working fine, I'm not connected to a VPN, and I don't have a proxy specified. Windows Firewall is also turned off, but I do have Cylance installed.
claunia added the Resolution-Duplicate label 2026-01-31 02:03:46 +00:00
claunia commented 2026-01-31 02:03:47 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Jul 23, 2020):

This is a dupe and what's really need is to get the diagnostic data you can generate from Feedback Hub. It's a known issue issue and is the same on a host with no Internet with Windows Firewall enabled and Defender as the only A/V (that's still domain joined). You can work around this by changing .msixbundle to .zip and extract. Then take the relevant CascadiaPackage msix (arm/x86/x64) and change that to .zip as well. Extract it. Open the folder. You'll find WindowsTerminal.exe inside. Some things will not work as intended with this method ( you can't have it launch at log in for example) but for the most part everything works.

@WSLUser commented on GitHub (Jul 23, 2020): This is a dupe and what's really need is to get the diagnostic data you can generate from Feedback Hub. It's a known issue issue and is the same on a host with no Internet with Windows Firewall enabled and Defender as the only A/V (that's still domain joined). You can work around this by changing .msixbundle to .zip and extract. Then take the relevant CascadiaPackage msix (arm/x86/x64) and change that to .zip as well. Extract it. Open the folder. You'll find WindowsTerminal.exe inside. Some things will not work as intended with this method ( you can't have it launch at log in for example) but for the most part everything works.
claunia commented 2026-01-31 02:03:47 +00:00
Author
Owner
Copy Link

@CobusKruger commented on GitHub (Jul 23, 2020):

@WSLUser I would love to give you the diagnostic data from Feedback hub, but that gets the same error code 0x800704cf when I try to sign in. I looked at the data in Documents\FeedbackHub, but there's a lot of stuff in there. If you can point me to where I can find the diagnostics to attach, I will.

Meanwhile, thank you very much for the workaround.

@CobusKruger commented on GitHub (Jul 23, 2020): @WSLUser I would love to give you the diagnostic data from Feedback hub, but that gets the same error code 0x800704cf when I try to sign in. I looked at the data in Documents\FeedbackHub, but there's a lot of stuff in there. If you can point me to where I can find the diagnostics to attach, I will. Meanwhile, thank you very much for the workaround.
claunia commented 2026-01-31 02:03:47 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Jul 23, 2020):

It doesn't go to me. I'm not with MS. Have you installed Feedback Hub? If so, try opening it. If not, see if you can remove your host from the domain and disable the group policy. My money is on something in group policy but which setting causes this is a mystery. Then install/sign in with proper creds (don't use your personal unless that's your company policy) Feedback Hub. Tell it to remember login (in Windows settings). Add machine back to domain. Reapply group policy. Try opening Feedback Hub. If it works and you have it connected to Internet then look for Windows Terminal and submit feedback. You should have option to record the issue. Choose it. Attempt to re-open Terminal from Start Menu and press ok with error. End the data gathering in Feedback Hub and click submit. A URL should appear for you for the data dump. Paste that URL here.

@WSLUser commented on GitHub (Jul 23, 2020): It doesn't go to me. I'm not with MS. Have you installed Feedback Hub? If so, try opening it. If not, see if you can remove your host from the domain and disable the group policy. My money is on something in group policy but which setting causes this is a mystery. Then install/sign in with proper creds (don't use your personal unless that's your company policy) Feedback Hub. Tell it to remember login (in Windows settings). Add machine back to domain. Reapply group policy. Try opening Feedback Hub. If it works and you have it connected to Internet then look for Windows Terminal and submit feedback. You should have option to record the issue. Choose it. Attempt to re-open Terminal from Start Menu and press ok with error. End the data gathering in Feedback Hub and click submit. A URL should appear for you for the data dump. Paste that URL here.
claunia commented 2026-01-31 02:03:48 +00:00
Author
Owner
Copy Link

@CobusKruger commented on GitHub (Jul 23, 2020):

Thanks for the explanation, but I'm pretty sure that removing and re-adding the machine to the domain isn't going to happen, based on previous experience with our infrastructure team. So for the moment, I'll use the workaround. Thanks again.

@CobusKruger commented on GitHub (Jul 23, 2020): Thanks for the explanation, but I'm pretty sure that removing and re-adding the machine to the domain isn't going to happen, based on previous experience with our infrastructure team. So for the moment, I'll use the workaround. Thanks again.
claunia commented 2026-01-31 02:03:48 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 24, 2020):

Thanks for the report! I'm going to accumulate this with the rest of /dup #1386 😄

@DHowett commented on GitHub (Jul 24, 2020): Thanks for the report! I'm going to accumulate this with the rest of /dup #1386 :smile:
claunia commented 2026-01-31 02:03:48 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 24, 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 (Jul 24, 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!
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 Resolution-Duplicate
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#9787
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?