starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Error "The specified user does not have a valid profile" after updating to 0.8 #5946

New Issue
Closed
opened 2026-01-31 00:26:10 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 00:26:10 +00:00
Owner
Copy Link

Originally created by @RoguePointer80 on GitHub (Jan 15, 2020).

Originally assigned to: @DHowett-MSFT on GitHub.

Environment

Microsoft Windows [Version 10.0.18363.535]
Windows Terminal version (if applicable): 0.8

Steps to reproduce

Turn on the computer in the morning. Let Microsoft Store do its updates.
Windows Terminal now at v0.8.
Click on the pinned icon on the taskbar (I use it every day all day, so I pinned it there)
The program does not start, instead a dialog is presented with the path to the main executable and the error message "The specified user does not have a valid profile.

I then made a backup of my profiles.json file, deleted it (expecting it to be created fresh), restart the app; same behaviour.
I then went to Add Remove Programs, uninstalled Windows Terminal. Then re-install it from the Windows Store; same behaviour.

Expected behavior

When I click on the icon, the program starts.

Actual behavior

image

Originally created by @RoguePointer80 on GitHub (Jan 15, 2020). Originally assigned to: @DHowett-MSFT on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Microsoft Windows [Version 10.0.18363.535] Windows Terminal version (if applicable): 0.8 # Steps to reproduce Turn on the computer in the morning. Let Microsoft Store do its updates. Windows Terminal now at v0.8. Click on the pinned icon on the taskbar (I use it every day all day, so I pinned it there) The program does not start, instead a dialog is presented with the path to the main executable and the error message "The specified user does not have a valid profile. I then made a backup of my profiles.json file, deleted it (expecting it to be created fresh), restart the app; same behaviour. I then went to Add Remove Programs, uninstalled Windows Terminal. Then re-install it from the Windows Store; same behaviour. # Expected behavior When I click on the icon, the program starts. # Actual behavior <!-- What's actually happening? --> ![image](https://user-images.githubusercontent.com/30326057/72438060-123cdf00-3772-11ea-8de6-d9430bd52f4e.png)
claunia added the Needs-Tag-FixProduct-TerminalSeverity-Crash labels 2026-01-31 00:26:10 +00:00
claunia commented 2026-01-31 00:26:11 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 23, 2020):

We have not been able to reproduce this issue. If you reboot the computer, does it help?

@DHowett-MSFT commented on GitHub (Jan 23, 2020): We have not been able to reproduce this issue. If you reboot the computer, does it help?
claunia commented 2026-01-31 00:26:11 +00:00
Author
Owner
Copy Link

@RoguePointer80 commented on GitHub (Jan 27, 2020):

Somehow, rebooting the computer fixed the issue. I hate when it does that.
Not much to work with; I guess you can close this issue, maybe it wasn't related to Terminal after all. (strange that the rest of my programs worked).

@RoguePointer80 commented on GitHub (Jan 27, 2020): Somehow, rebooting the computer fixed the issue. I hate when it does that. Not much to work with; I guess you can close this issue, maybe it wasn't related to Terminal after all. (strange that the rest of my programs worked).
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-Tag-Fix Product-Terminal 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#5946
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?