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

Unable to open settings (profiles.json): ShellExecute in LaunchSettings returns ERROR_ACCESS_DENIED #1835

New Issue
Closed
opened 2026-01-30 22:39:08 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 22:39:08 +00:00
Owner
Copy Link

Originally created by @brettfo on GitHub (Jun 22, 2019).

Environment

Windows build number: 10.0.18362.175 (1903)
Windows Terminal version (if applicable): 0.2.1715.0

Any other software? No

Steps to reproduce

Open the settings file, either through the UI or via Ctrl+,

Expected behavior

The settings file to open.

Actual behavior

Nothing visible happens.

I built and debugged locally from the 0.2.1715.0 sources (66cb7c4b58) and found that ShellExecute in LaunchSettings was returning 5 (ERROR_ACCESS_DENIED according to winerror.h, line 265). The value of settingsPath was properly formed (C:\Users\brettfo\AppData\Local\Packages\WindowsTerminalDev_<some-garbage-characters>\RoamingState\profiles.json) and the file exists on disk with the expected contents.

I also found the settings file corresponding to the app installed from the Store at C:\Users\brettfo\AppData\Local\Packages\Microsoft.WindowsTerminal_<some-garbage-characters>\RoamingState\profiles.json which is also correct and changed settings are appropriately reflected in the app.

Originally created by @brettfo on GitHub (Jun 22, 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: 10.0.18362.175 (1903) Windows Terminal version (if applicable): 0.2.1715.0 Any other software? No ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Open the settings file, either through the UI or via Ctrl+, # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The settings file to open. # Actual behavior <!-- What's actually happening? --> Nothing visible happens. I built and debugged locally from the 0.2.1715.0 sources (66cb7c4b58b0e41ffaeb952ef27f1a8c67e90db8) and found that [ShellExecute in LaunchSettings](https://github.com/microsoft/terminal/blob/66cb7c4b58b0e41ffaeb952ef27f1a8c67e90db8/src/cascadia/TerminalApp/App.cpp#L440) was returning 5 (ERROR_ACCESS_DENIED according to winerror.h, line 265). The value of `settingsPath` was properly formed (`C:\Users\brettfo\AppData\Local\Packages\WindowsTerminalDev_<some-garbage-characters>\RoamingState\profiles.json`) and the file exists on disk with the expected contents. I also found the settings file corresponding to the app installed from the Store at `C:\Users\brettfo\AppData\Local\Packages\Microsoft.WindowsTerminal_<some-garbage-characters>\RoamingState\profiles.json` which is also correct and changed settings are appropriately reflected in the app.
claunia added the Area-SettingsIssue-BugResolution-DuplicateProduct-Terminal labels 2026-01-30 22:39:08 +00:00
claunia commented 2026-01-30 22:39:09 +00:00
Author
Owner
Copy Link

@mithunshanbhag commented on GitHub (Jun 22, 2019):

I too am facing the same issue. Please take a look at the attached screen capture gif below.

Some additional details:

  1. Windows Terminal (preview) version 0.2.1715.0. Downloaded from the Microsoft Store.
  2. This issue also repro'es for me when I build the windows terminal's github sources locally and launch the CascadiaPackage.
  3. The issue still repro'es even if I run the terminal as an elevated admin.
  4. Window Insider Build: 10.0.18922.1000 (fast-ring)
  5. I'm running Windows 10 on Macbook Air (4 proc, 8 GB RAM).
  6. As a workaround, I'm able to tweak the profile.json file manually and configure the settings.

Please let me know if I can provide any additional details.

microsoft-terminal-issue

@mithunshanbhag commented on GitHub (Jun 22, 2019): I too am facing the same issue. Please take a look at the attached screen capture gif below. Some additional details: 1. Windows Terminal (preview) version 0.2.1715.0. Downloaded from the Microsoft Store. 2. This issue also repro'es for me when I build the windows terminal's github sources locally and launch the CascadiaPackage. 3. The issue still repro'es even if I run the terminal as an elevated admin. 4. Window Insider Build: 10.0.18922.1000 (fast-ring) 5. I'm running Windows 10 on Macbook Air (4 proc, 8 GB RAM). 6. As a workaround, I'm able to tweak the profile.json file manually and configure the settings. Please let me know if I can provide any additional details. ![microsoft-terminal-issue](https://user-images.githubusercontent.com/2327905/59960789-33469580-94eb-11e9-8db0-469cbf6d7d72.gif)
claunia commented 2026-01-30 22:39:09 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 24, 2019):

I accidentally made #1460 the master issue for this, so.. here goes!

@DHowett-MSFT commented on GitHub (Jun 24, 2019): I accidentally made #1460 the master issue for this, so.. here goes!
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 Area-Settings Issue-Bug Product-Terminal 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#1835
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?