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

Bug Report - Error Message while opening preferrences -- Windows Terminal Version: 1.0.1811.0 #9524

New Issue
Closed
opened 2026-01-31 01:56:36 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 01:56:36 +00:00
Owner
Copy Link

Originally created by @gottingerfrank on GitHub (Jul 9, 2020).

Error Message ="Adobe Acrobat cannot open 'settings.json' ... filetype not supported or damaged

Windows Terminal
Version: 1.0.1811.0

Error Message happend when trying to open preferrences of "Windows Terminal" App
Window (clicking on the register of the window).

First thing most people do when they open a terminal app for the first time/new computer/os, is go to preferrences
to change the size/look of fonts, colors, or window size and such ...

Screenshot of original (german language version) error message:

screenshot_WinTerminal1

Originally created by @gottingerfrank on GitHub (Jul 9, 2020). Error Message ="Adobe Acrobat cannot open 'settings.json' ... filetype not supported or damaged Windows Terminal Version: 1.0.1811.0 > **Error Message happend when trying to open preferrences** of "Windows Terminal" App > Window (clicking on the register of the window). First thing most people do when they open a terminal app for the first time/new computer/os, is go to preferrences to change the size/look of fonts, colors, or window size and such ... Screenshot of original (german language version) error message: ![screenshot_WinTerminal1](https://user-images.githubusercontent.com/16911419/87001088-ef3a3780-c1b6-11ea-8d57-64e198853bc4.png)
claunia commented 2026-01-31 01:56:37 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 9, 2020):

The Terminal just tries to open whatever application is set as the default editor for .json files. Apparently, on you machine, that's been set to Adobe Acrobat. If you change that to notepad, or any other text editor, does that fix the issue for you?

@zadjii-msft commented on GitHub (Jul 9, 2020): The Terminal just tries to open whatever application is set as the default editor for `.json` files. Apparently, on you machine, that's been set to Adobe Acrobat. If you change that to notepad, or any other text editor, does that fix the issue for you?
claunia commented 2026-01-31 01:56:37 +00:00
Author
Owner
Copy Link

@JoshuaKGoldberg commented on GitHub (Jul 11, 2020):

This happened for me as well when I switched the default editor for .json files to VS Code. Pressing Ctrl+, made the Windows error bloop sound and showed this error popup for a fraction of a second (I could only get a screenshot using a still from screen recording):

Screenshot of a Visual Studio Code popup with black content instead of text

Switching back to Notepad++ allows settings to open fine.

@JoshuaKGoldberg commented on GitHub (Jul 11, 2020): This happened for me as well when I switched the default editor for `.json` files to VS Code. Pressing <kbd>Ctrl</kbd>+<kbd>,</kbd> made the Windows error bloop sound and showed this error popup for a fraction of a second _(I could only get a screenshot using a still from screen recording)_: ![Screenshot of a Visual Studio Code popup with black content instead of text](https://user-images.githubusercontent.com/3335181/87228611-61a24780-c370-11ea-84f5-490c6cfcbb12.png) Switching back to Notepad++ allows settings to open fine.
claunia commented 2026-01-31 01:56:37 +00:00
Author
Owner
Copy Link

@gottingerfrank commented on GitHub (Jul 11, 2020):

Yes, for some reason I do not know .json was set to open with adobe acrobat. Changed it to my text editor and it was fine.
Guess I was just also expecting a GUI Window. That's why I found it so strange. Works now. Thanks

@gottingerfrank commented on GitHub (Jul 11, 2020): Yes, for some reason I do not know .json was set to open with adobe acrobat. Changed it to my text editor and it was fine. Guess I was just also expecting a GUI Window. That's why I found it so strange. Works now. Thanks
claunia commented 2026-01-31 01:56:38 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 13, 2020):

Thanks for following up!

@zadjii-msft commented on GitHub (Jul 13, 2020): Thanks for following up!
claunia commented 2026-01-31 01:56:38 +00:00
Author
Owner
Copy Link

@JoshuaKGoldberg commented on GitHub (Jul 13, 2020):

@zadjii-msft I think this issue is not resolved. It's reasonable to want VS Code as a default editor for JSON files. It's normally able to open them when prompted by other programs. Would you think this is an issue in Terminal or VS Code?

@JoshuaKGoldberg commented on GitHub (Jul 13, 2020): @zadjii-msft I think this issue is not resolved. It's reasonable to want VS Code as a default editor for JSON files. It's normally able to open them when prompted by other programs. Would you think this is an issue in Terminal or VS Code?
claunia commented 2026-01-31 01:56:38 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 13, 2020):

@JoshuaKGoldberg I'm mainly resolving this since OP's original issue was resolved. I'm not sure why vscode isn't working for you as the default json editor, but I doubt it's Terminal specific. We're simply calling ShellExecute on the settings file, and hoping the system can figure it out:
592c634577/src/cascadia/TerminalApp/TerminalPage.cpp (L1683-L1697)

Does double-clicking a json file in Explorer work to launch VsCode?

@zadjii-msft commented on GitHub (Jul 13, 2020): @JoshuaKGoldberg I'm mainly resolving this since OP's original issue was resolved. I'm not sure why vscode isn't working for you as the default json editor, but I doubt it's Terminal specific. We're simply calling `ShellExecute` on the settings file, and hoping the system can figure it out: https://github.com/microsoft/terminal/blob/592c63457781c9d753ae6648f03c96d998a0080e/src/cascadia/TerminalApp/TerminalPage.cpp#L1683-L1697 Does double-clicking a `json` file in Explorer work to launch VsCode?
claunia commented 2026-01-31 01:56:38 +00:00
Author
Owner
Copy Link

@JoshuaKGoldberg commented on GitHub (Jul 13, 2020):

It does work in Explorer, yes 👍. Both when VS Code isn't yet launched (to start a new window) and when it already is (to open the file in an existing window).

@JoshuaKGoldberg commented on GitHub (Jul 13, 2020): It does work in Explorer, yes :+1:. Both when VS Code isn't yet launched (to start a new window) and when it already is (to open the file in an existing window).
claunia commented 2026-01-31 01:56:38 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 13, 2020):

That's very bizarre. I'd file an issue on the VsCode repo honestly, because they'll be far more equipped to be able to figure out why this isn't working for you than we are 😕

@zadjii-msft commented on GitHub (Jul 13, 2020): That's very bizarre. I'd file an issue on the VsCode repo honestly, because they'll be far more equipped to be able to figure out why this isn't working for you than we are 😕
claunia commented 2026-01-31 01:56:39 +00:00
Author
Owner
Copy Link

@JoshuaKGoldberg commented on GitHub (Jul 13, 2020):

Ok, thanks for the pointers - I appreciate the GitHub issue debugging! ❤️

@JoshuaKGoldberg commented on GitHub (Jul 13, 2020): Ok, thanks for the pointers - I appreciate the GitHub issue debugging! ❤️
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-Attention Needs-Tag-Fix Needs-Triage 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#9524
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?