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

WindowsTerminal.exe/ wt.exe uses different settings than Windows Terminal App #14036

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

Originally created by @constantin-kuehne on GitHub (May 29, 2021).

Windows Terminal version (or Windows build number)

1.8.1444.0 / 1.8.210524004-release1.8

Other Software

No response

Steps to reproduce

When opening the Windows Terminal App via the Windows Terminal App Icon it uses the settings.json under C:\Users\User\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState while if you open it via the WindowsTerminal.exe/ wt.exe it opens the settings.json under C:\Users\User\AppData\Local\Microsoft\Windows Terminal, therefore if you use the wt command in the "search bar" of the explorer it opens it with the wrong settings.

Is this the intended behavior?

Settings when opening with Windows Terminal App Icon
Screenshot 2021-05-29 020149

Settings when opening with WindowsTerminal.exe/ wt.exe/ wt command in explorer
Screenshot 2021-05-29 020214

Also the version numbers are different based on opening sequence. It is 1.8.1444.0 when opening with Windows Terminal App Icon and 1.8.210524004-release1.8 when opening with the WindowsTerminal.exe/ wt.exe / wt in explorer.

Expected Behavior

The expected behavior would be that they use the same settings.

Actual Behavior

They use different settings.json as stated above.

Originally created by @constantin-kuehne on GitHub (May 29, 2021). ### Windows Terminal version (or Windows build number) 1.8.1444.0 / 1.8.210524004-release1.8 ### Other Software _No response_ ### Steps to reproduce When opening the Windows Terminal App via the Windows Terminal App Icon it uses the settings.json under C:\Users\User\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState while if you open it via the WindowsTerminal.exe/ wt.exe it opens the settings.json under C:\Users\User\AppData\Local\Microsoft\Windows Terminal, therefore if you use the wt command in the "search bar" of the explorer it opens it with the wrong settings. Is this the intended behavior? Settings when opening with Windows Terminal App Icon ![Screenshot 2021-05-29 020149](https://user-images.githubusercontent.com/70445955/120080362-d9787e00-c0b8-11eb-897e-982db0af3caa.png) Settings when opening with WindowsTerminal.exe/ wt.exe/ wt command in explorer ![Screenshot 2021-05-29 020214](https://user-images.githubusercontent.com/70445955/120080382-ef863e80-c0b8-11eb-965f-a188a098a30d.png) Also the version numbers are different based on opening sequence. It is 1.8.1444.0 when opening with Windows Terminal App Icon and 1.8.210524004-release1.8 when opening with the WindowsTerminal.exe/ wt.exe / wt in explorer. ### Expected Behavior The expected behavior would be that they use the same settings. ### Actual Behavior They use different settings.json as stated above.
claunia added the Resolution-Duplicate label 2026-01-31 03:59:04 +00:00
claunia commented 2026-01-31 03:59:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 1, 2021):

If I had to guess, this is because you (or something on your system) changed the permissions on C:\Program Files\WindowsApps. It is critically important to the app platform (which supports all packaged applications on Windows) that the permissions on that folder are not damaged.

See #9452 for more information, as well as remediations.

/dup #9452

@DHowett commented on GitHub (Jun 1, 2021): If I had to guess, this is because you (or something on your system) changed the permissions on `C:\Program Files\WindowsApps`. It is critically important to the app platform (which supports all packaged applications on Windows) that the permissions on that folder are _not damaged._ See #9452 for more information, as well as remediations. /dup #9452
claunia commented 2026-01-31 03:59:06 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 1, 2021):

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 (Jun 1, 2021): 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#14036
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?