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 open after downloading from Microsoft Store #2515

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

Originally created by @llinfeng on GitHub (Jul 3, 2019).

Environment

Windows build number:  [Version 10.0.18362.175]
Windows Terminal version: latest on Windows Store.

Any other software: set WSL as the default profile.

Steps to reproduce

Simply clicking the Launch button will give the following error message:
image

More details:

As I experimented with the Windows Terminal, I have installed it on all my Windows PCs that are running the latest build. 3 out of 4 are performing well. It is only one machine that kept complaining about the "profile". Yet, it is a bit confusing, as:

  • One Surface Pro does not sync with all others;
  • Yet, the other 3 seem to sync their settings;

Expected behavior

Expect the Windows Terminal to open up.

Actual behavior

Repeatedly, I see the following error message:
image

Question:

  1. I notice that the setting for Windows Terminal shall sync across all machines. This feels like magic, but also insecure: can I ask Windows Terminal to source some Dropbox directory, for the profiles.json file?
  2. As an App on Windows Store, is it normal to have all other copies installed on other PCs deleted when I delete the app from one machine? As I was trying to uninstall and re-install Windows Terminal on the machine that cannot launch it (as reported), I noticed that other machines have also deleted their copies of Windows Terminal.
Originally created by @llinfeng on GitHub (Jul 3, 2019). <!-- 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. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [Version 10.0.18362.175] Windows Terminal version: latest on Windows Store. Any other software: set WSL as the default profile. ``` # Steps to reproduce Simply clicking the Launch button will give the following error message: ![image](https://user-images.githubusercontent.com/5890407/60587852-76163200-9d63-11e9-8b1f-9273f4273050.png) ## More details: As I experimented with the Windows Terminal, I have installed it on all my Windows PCs that are running the latest build. 3 out of 4 are performing well. It is only one machine that kept complaining about the "profile". Yet, it is a bit confusing, as: * One Surface Pro does not sync with all others; * Yet, the other 3 seem to sync their settings; # Expected behavior Expect the Windows Terminal to open up. # Actual behavior Repeatedly, I see the following error message: ![image](https://user-images.githubusercontent.com/5890407/60588481-0dc85000-9d65-11e9-8d8c-30395dd1de0d.png) # Question: 1. I notice that the setting for Windows Terminal shall sync across all machines. This feels like magic, but also insecure: can I ask Windows Terminal to source some Dropbox directory, for the `profiles.json` file? 2. As an App on Windows Store, is it normal to have all other copies installed on other PCs deleted when I delete the app from one machine? As I was trying to uninstall and re-install Windows Terminal on the machine that cannot launch it (as reported), I noticed that other machines have also deleted their copies of Windows Terminal.
claunia added the Resolution-ExternalNeeds-Tag-FixNeeds-AttentionSeverity-Crash labels 2026-01-30 22:57:13 +00:00
claunia commented 2026-01-30 22:57:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 3, 2019):

I don't believe we're showing that dialog, so any text about your "profile" isn't actually referring to the profiles in your settings file, this is something closer to the OS I believe.

Is there anything that's particularly different about the setup of the non-working machine? Are you not an admin on that machine, but admin on the others?

Are there any events in Event Viewer that look correlated with this crash? I've never seen this dialog before so I'm really at a loss for what might be causing it.

@zadjii-msft commented on GitHub (Jul 3, 2019): I don't believe we're showing that dialog, so any text about your "profile" isn't actually referring to the profiles in your settings file, this is something closer to the OS I believe. Is there anything that's particularly different about the setup of the non-working machine? Are you not an admin on that machine, but admin on the others? Are there any events in Event Viewer that look correlated with this crash? I've never seen this dialog before so I'm really at a loss for what might be causing it.
claunia commented 2026-01-30 22:57:14 +00:00
Author
Owner
Copy Link

@llinfeng commented on GitHub (Jul 3, 2019):

I would not consider the buggy machine to be any different from all the others. I am Admin to all these machines and I have been following the following steps to guarantee a stable username, say xxx, when I was setting up Windows OS.

  • Choose to go with Offline account when setting up Windows;
  • Name myself as xxx Lastname, and Windows was happily picking up xxx as the username
  • Once the system loads, I use my Microsoft account to log into the Windows store.

The buggy machine should be the first machine that I installed Windows Terminal (Preview) onto: I found its setting file as C:\Users\Username\AppData\Local\Packages\Microsoft.WindowsTerminal_8[xxxxxxxxxx]\RoamingState\profiles.json and have been reusing this path on other machines. All other machines are liking the setting file, and the buggy machien liked the setting file as well.

RE: "profile" as my Microsoft account?

One more thing that I notice: the buggy machine (I named it as "AW") may have some trouble with Windows Store? Here goes the screenshot of devices that I have linked to Microsoft account, T1, T2 and Surface had no trouble launching, and AW does have an issue. It appears that AW is the oldest machine on this list??

image

Question about the setting file

Does the path stay stable? And, can I appoint a Dropbox location for source-ing?

@llinfeng commented on GitHub (Jul 3, 2019): I would not consider the buggy machine to be any different from all the others. I am Admin to all these machines and I have been following the following steps to guarantee a stable username, say `xxx`, when I was setting up Windows OS. * Choose to go with Offline account when setting up Windows; * Name myself as `xxx Lastname`, and Windows was happily picking up `xxx` as the username * Once the system loads, I use my Microsoft account to log into the Windows store. The buggy machine should be the first machine that I installed Windows Terminal (Preview) onto: I found its setting file as `C:\Users\Username\AppData\Local\Packages\Microsoft.WindowsTerminal_8[xxxxxxxxxx]\RoamingState\profiles.json` and have been reusing this path on other machines. All other machines are liking the setting file, and the buggy machien liked the setting file as well. ## RE: "profile" as my Microsoft account? One more thing that I notice: the buggy machine (I named it as "AW") may have some trouble with Windows Store? Here goes the screenshot of devices that I have linked to Microsoft account, T1, T2 and Surface had no trouble launching, and AW does have an issue. It appears that AW is the oldest machine on this list?? ![image](https://user-images.githubusercontent.com/5890407/60595200-884c9c00-9d74-11e9-9642-eb6c5e53df10.png) ## Question about the setting file Does the path stay stable? And, can I appoint a Dropbox location for `source`-ing?
claunia commented 2026-01-30 22:57:14 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Jul 3, 2019):

This sounds like #1770 might help mitigate your issues in the near term.

@miniksa commented on GitHub (Jul 3, 2019): This sounds like #1770 might help mitigate your issues in the near term.
claunia commented 2026-01-30 22:57:15 +00:00
Author
Owner
Copy Link

@AlvinKuruvilla commented on GitHub (Jul 4, 2019):

Ok so I am having a sort of similar issue where I downloaded the preview from the Microsoft store but now I cannot open the new terminal. It seems like it doesn't exist and I can't even install it again because the store sats I already own it. Also, I don't think its an issue with system requirements as I am up to the May 2019 version, is there a requirement I am missing or is this a bug, and how do I fix it
Any answers would be appreciated

@AlvinKuruvilla commented on GitHub (Jul 4, 2019): Ok so I am having a sort of similar issue where I downloaded the preview from the Microsoft store but now I cannot open the new terminal. It seems like it doesn't exist and I can't even install it again because the store sats I already own it. Also, I don't think its an issue with system requirements as I am up to the May 2019 version, is there a requirement I am missing or is this a bug, and how do I fix it Any answers would be appreciated
claunia commented 2026-01-30 22:57:15 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 8, 2019):

Alright, this one is definitely outside our wheelhouse. Would you mind filing feedback in the Feedback Hub, category Developer Platform > App Deployment, and sharing a link here? Thanks.

@DHowett-MSFT commented on GitHub (Jul 8, 2019): Alright, this one is definitely outside our wheelhouse. Would you mind filing feedback in the Feedback Hub, category Developer Platform > App Deployment, and sharing a link here? Thanks.
claunia commented 2026-01-30 22:57:15 +00:00
Author
Owner
Copy Link

@llinfeng commented on GitHub (Jul 9, 2019):

I am closing this ticket as it is not restricted to the Windows Terminal (Preview). Across the board on the faulty desktop machine, I receive the same error message from all Windows Store Apps. This is a Windows OS problem and may or may not be addressed in future Windows updates.

Will be interested to learn any fix to the issue without having the Windows 10 system re-installed.

@llinfeng commented on GitHub (Jul 9, 2019): I am closing this ticket as it is not restricted to the Windows Terminal (Preview). Across the board on the faulty desktop machine, I receive the same error message from all Windows Store Apps. [This is a Windows OS problem and may or may not be addressed in future Windows updates.](https://techcommunity.microsoft.com/t5/Windows-10/quot-The-specified-user-does-not-have-a-valid-profile-quot-error/td-p/193455) Will be interested to learn any fix to the issue without having the Windows 10 system re-installed.
claunia commented 2026-01-30 22:57:15 +00:00
Author
Owner
Copy Link

@llinfeng commented on GitHub (Jul 12, 2019):

I can open all Windows Store Apps on the buggy machine for now. I think a certain Windows Update has solved the problem. Thankfully, I don't need to redo my OS to fix the launching bug.

@llinfeng commented on GitHub (Jul 12, 2019): I can open all Windows Store Apps on the buggy machine for now. I think a certain Windows Update has solved the problem. Thankfully, I don't need to redo my OS to fix the launching bug.
claunia commented 2026-01-30 22:57:15 +00:00
Author
Owner
Copy Link

@llinfeng commented on GitHub (Aug 10, 2019):

Update pre the recent Windows Update to OS Build 18362.10005 ==> I encountered the same error message when attempting to launch Windows Terminal. Performing a "in-place upgrade" solved the issue temoprarily, but the fix did not last two system reboots. Identical problem occured for X410 as well.

As things were working with oldre OS Build 18362.239, here goes how to revert the OS build (not the "Version"):
image
image
image
In the last step, look for the most recently installed "Upgrade for Microsoft Windows" that matches the time-tag and uninstall it. It takes a while and will restart the PC. Though this is actually a "downgrade", I staill saw a "Windows Updates 30% ..." blue window there.

Note, per my specific fix, I also performed one round of "in-place upgrade" in the beginning (as advised by the Support team). If directly reverting to the previous build did not work, please consider performing such "in-place upgrade".

@llinfeng commented on GitHub (Aug 10, 2019): Update pre the recent Windows Update to OS Build `18362.10005` ==> I encountered the same error message when attempting to launch Windows Terminal. Performing a "in-place upgrade" solved the issue temoprarily, but the fix did not last two system reboots. Identical problem occured for X410 as well. As things were working with oldre OS Build `18362.239`, here goes how to revert the OS build (not the "Version"): ![image](https://user-images.githubusercontent.com/5890407/62817417-31b94700-bb04-11e9-818a-65c56a060551.png) ![image](https://user-images.githubusercontent.com/5890407/62817422-4564ad80-bb04-11e9-974a-508274c5fdb4.png) ![image](https://user-images.githubusercontent.com/5890407/62817424-51506f80-bb04-11e9-9054-aef715403f20.png) In the last step, look for the most recently installed "Upgrade for Microsoft Windows" that matches the time-tag and uninstall it. It takes a while and will restart the PC. Though this is actually a "downgrade", I staill saw a "Windows Updates 30% ..." blue window there. Note, per my specific fix, I also performed one round of "in-place upgrade" in the beginning (as advised by the Support team). If directly reverting to the previous build did not work, please consider performing such "in-place upgrade".
claunia commented 2026-01-30 22:57:15 +00:00
Author
Owner
Copy Link

@llinfeng commented on GitHub (Aug 10, 2019):

Note, I still cannot open Windows Terminal through the Start menu after the "fix". I find the following locations for the executables helpful ==> things do get launched properly when calling the executables alone. And, it did not appear to be a need to cut/copy and paste the entire folder to some other locations.

  • For Windows Terminal: c:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.3.2171.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
  • For X410: c:\Program Files\WindowsApps\ChoungNetworksUS.X410_2.6.0.0_x64__vvzc8y2tzcnsr\X410\X410.exe

I tried to schedule X410 for "start on startup" via the Task scheduler. Feeding the absolute address for the X410.exe into the Action tab when configuring the scheduled task got things launched properly. Yet, adding a new string-item to the following registry item did not help launch X410: Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run. Same error was raised.

Also, the executables in the shell:AppsFolder (run in Run window) also did not work (for both Windows Terminal and X410).

  • They won't work by themselves:
    image
  • Nor will a shortcut work:
    image
@llinfeng commented on GitHub (Aug 10, 2019): Note, I still cannot open Windows Terminal through the Start menu after the "fix". I find the following locations for the executables helpful ==> things do get launched properly when calling the executables alone. And, it did not appear to be a need to cut/copy and paste the entire folder to some other locations. * For Windows Terminal: `c:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.3.2171.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe` * For X410: `c:\Program Files\WindowsApps\ChoungNetworksUS.X410_2.6.0.0_x64__vvzc8y2tzcnsr\X410\X410.exe` I tried to schedule X410 for "start on startup" via the Task scheduler. Feeding the absolute address for the `X410.exe` into the Action tab when configuring the scheduled task got things launched properly. Yet, adding a new string-item to the following registry item did not help launch X410: `Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run`. Same error was raised. Also, the executables in the `shell:AppsFolder` (run in Run window) also did not work (for both Windows Terminal and X410). * They won't work by themselves: ![image](https://user-images.githubusercontent.com/5890407/62817609-75618000-bb07-11e9-877e-424ae818f73d.png) * Nor will a shortcut work: ![image](https://user-images.githubusercontent.com/5890407/62817590-477c3b80-bb07-11e9-8e3e-403ef23204c1.png)
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-Attention Needs-Tag-Fix Resolution-External Severity-Crash
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#2515
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?