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

Can't open settings while installing Visual Studio #8170

New Issue
Closed
opened 2026-01-31 01:22:33 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 01:22:33 +00:00
Owner
Copy Link

Originally created by @MehediH on GitHub (May 15, 2020).

When installing Visual Studio, it sets the IDE as the default application for opening .json files on Windows. As a result, when trying to open the settings from Windows Terminal, Visual Studio throws an error saying it can't be opened. Going into File Explorer and setting Notepad as the default app for opening .json files fixes the issue and the Terminal is able to open the settings.

Expected behavior here would be to have a fallback where the default app for opening .json files does not work, and open it on Notepad instead.

This is not really an issue with Windows Terminal itself, but it could affect the UX where the user may not understand why Windows Terminal is unable to open settings.

screenshot showing Visual Studio error

Originally created by @MehediH on GitHub (May 15, 2020). When installing Visual Studio, it sets the IDE as the default application for opening .json files on Windows. As a result, when trying to open the settings from Windows Terminal, Visual Studio throws an error saying it can't be opened. Going into File Explorer and setting Notepad as the default app for opening .json files fixes the issue and the Terminal is able to open the settings. Expected behavior here would be to have a fallback where the default app for opening .json files does not work, and open it on Notepad instead. This is not really an issue with Windows Terminal itself, but it could affect the UX where the user may not understand why Windows Terminal is unable to open settings. ![screenshot showing Visual Studio error](https://i.imgur.com/qWRWG8q.png)
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 01:22:33 +00:00
claunia commented 2026-01-31 01:22:34 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 15, 2020):

Wow, that's unexpected. Unfortunately, from Terminal's perspective, it has successfully opened the settings file.

It just so happens that the application that said it handled it handled it by popping up a dialog.

Terminal does fall back to Notepad, but when the launched process outright lies to us we can't recover from that ☹️

@DHowett-MSFT commented on GitHub (May 15, 2020): Wow, that's unexpected. Unfortunately, from Terminal's perspective, it _has_ successfully opened the settings file. It just so happens that the application that said it handled it handled it by popping up a dialog. Terminal does fall back to Notepad, but when the launched process outright lies to us we can't recover from that ☹️
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 Issue-Question Needs-Tag-Fix Resolution-Answered
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#8170
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?