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

BSOD When clicking Settings #7830

New Issue
Closed
opened 2026-01-31 01:13:41 +00:00 by claunia · 17 comments
claunia commented 2026-01-31 01:13:41 +00:00
Owner
Copy Link

Originally created by @Zagan202 on GitHub (Apr 30, 2020).

Environment

Windows build number:Microsoft Windows [Version 10.0.18363.778]
Windows Terminal version (if applicable): 0.11.1191.0

Steps to reproduce

Click settings button

Expected behavior

Opens settings.json

Actual behavior

BSOD

Originally created by @Zagan202 on GitHub (Apr 30, 2020). # Environment ```none Windows build number:Microsoft Windows [Version 10.0.18363.778] Windows Terminal version (if applicable): 0.11.1191.0 ``` # Steps to reproduce Click settings button # Expected behavior Opens settings.json # Actual behavior BSOD
claunia added the Needs-TriageNeeds-Tag-FixResolution-No-ReproNeeds-Attention labels 2026-01-31 01:13:41 +00:00
claunia commented 2026-01-31 01:13:42 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 30, 2020):

/feedback

@DHowett-MSFT commented on GitHub (Apr 30, 2020): /feedback
claunia commented 2026-01-31 01:13:42 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 30, 2020):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Apr 30, 2020): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 01:13:42 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 30, 2020):

What was the bug check code?

@DHowett-MSFT commented on GitHub (Apr 30, 2020): What was the bug check code?
claunia commented 2026-01-31 01:13:42 +00:00
Author
Owner
Copy Link

@Zagan202 commented on GitHub (Apr 30, 2020):

I’m unsure where I would find the bug check code.

@Zagan202 commented on GitHub (Apr 30, 2020): I’m unsure where I would find the bug check code.
claunia commented 2026-01-31 01:13:42 +00:00
Author
Owner
Copy Link

@Zagan202 commented on GitHub (Apr 30, 2020):

https://aka.ms/AA8amwr

@Zagan202 commented on GitHub (Apr 30, 2020): https://aka.ms/AA8amwr
claunia commented 2026-01-31 01:13:43 +00:00
Author
Owner
Copy Link

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

Unfortunately, it looks like the feedback system was unable to recover any information about your bugcheck. I hate to ask, but does this happen every time you open Settings?

All Terminal does when you click "Settings" is, effectively, double-click the json file using ShellExecute. I'd be very surprised to learn that that's broken.

If it does reproduce when you click Settings again, there should be a filename and an "error code" on the screen next to the QR code. That would be really quite helpful in figuring out what's up.

@DHowett-MSFT commented on GitHub (May 1, 2020): Unfortunately, it looks like the feedback system was unable to recover any information about your bugcheck. I hate to ask, but does this happen _every_ time you open Settings? All Terminal does when you click "Settings" is, effectively, double-click the `json` file using `ShellExecute`. I'd be very surprised to learn that that's broken. If it _does_ reproduce when you click Settings again, there should be a filename and an "error code" on the screen next to the QR code. That would be really quite helpful in figuring out what's up.
claunia commented 2026-01-31 01:13:43 +00:00
Author
Owner
Copy Link

@Zagan202 commented on GitHub (May 1, 2020):

It does happen every time I click settings.
The BSOD says
Stop code: SYSTEM_SERVICE_EXCEPTION
What failed: Ntfs.sys
This is where the QR code led me
https://support.microsoft.com/en-us/help/14238/windows-10-troubleshoot-blue-screen-errors

@Zagan202 commented on GitHub (May 1, 2020): It does happen every time I click settings. The BSOD says Stop code: SYSTEM_SERVICE_EXCEPTION What failed: Ntfs.sys This is where the QR code led me https://support.microsoft.com/en-us/help/14238/windows-10-troubleshoot-blue-screen-errors
claunia commented 2026-01-31 01:13:43 +00:00
Author
Owner
Copy Link

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

Whoa whoa whoa that's really bad.

If you go into this folder:

%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState

and double-click settings.json

... does it also explode?

I hate to keep asking you to BSOD your computer again and again ☹️

@DHowett-MSFT commented on GitHub (May 1, 2020): Whoa whoa whoa that's _really bad_. If you go into this folder: ``` %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState ``` and double-click settings.json ... does it also explode? I hate to keep asking you to BSOD your computer again and again ☹️
claunia commented 2026-01-31 01:13:44 +00:00
Author
Owner
Copy Link

@Zagan202 commented on GitHub (May 1, 2020):

It does not blow up when I open it directly, which is what I've been doing for the past day or so because of this.

Some extra bit of info, I open JSON files with vscode instead of notepad.

@Zagan202 commented on GitHub (May 1, 2020): It does not blow up when I open it directly, which is what I've been doing for the past day or so because of this. Some extra bit of info, I open JSON files with vscode instead of notepad.
claunia commented 2026-01-31 01:13:44 +00:00
Author
Owner
Copy Link

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

Hmm. What about if you run the command (from cmd, unfortunately):

start %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json

That uses the same API as Terminal does.

@DHowett-MSFT commented on GitHub (May 1, 2020): Hmm. What about if you run the command (from cmd, unfortunately): ``` start %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json ``` That uses the same API as Terminal does.
claunia commented 2026-01-31 01:13:45 +00:00
Author
Owner
Copy Link

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

Judging by it being in ntfs.sys, my first concern would be filesystem corruption. The filesystem driver should never be killing the system under normal circumstances.

Any unusual third-party AV?

@DHowett-MSFT commented on GitHub (May 1, 2020): Judging by it being in _ntfs.sys_, my first concern would be filesystem corruption. The filesystem driver should _never_ be killing the system under normal circumstances. Any unusual third-party AV?
claunia commented 2026-01-31 01:13:45 +00:00
Author
Owner
Copy Link

@Zagan202 commented on GitHub (May 1, 2020):

Running that from cmd seemed to work and I got this output

 [main 2020-05-01T02:54:13.829Z] update#setState idle
(node:22348) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:22348) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:22348) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:22348) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:22348) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:22348) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:5176) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:5176) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more `information`

No unusual third party AV just Avast

@Zagan202 commented on GitHub (May 1, 2020): Running that from cmd seemed to work and I got this output ``` [main 2020-05-01T02:54:13.829Z] update#setState idle (node:22348) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information (node:22348) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information (node:22348) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information (node:22348) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information (node:22348) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information (node:22348) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information (node:5176) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information (node:5176) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more `information` ``` No unusual third party AV just Avast
claunia commented 2026-01-31 01:13:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 1, 2020):

Curious, what's your default editor for json files? VsCode? What version are you running?

This is getting weirder and weirder

@zadjii-msft commented on GitHub (May 1, 2020): Curious, what's your default editor for `json` files? VsCode? What version are you running? This is getting weirder and weirder
claunia commented 2026-01-31 01:13:45 +00:00
Author
Owner
Copy Link

@Zagan202 commented on GitHub (May 2, 2020):

Default editor for json is vscode.
Version of vscode 1.44.2
It is bizarre.

@Zagan202 commented on GitHub (May 2, 2020): Default editor for json is `vscode`. Version of vscode `1.44.2` It is bizarre.
claunia commented 2026-01-31 01:13:46 +00:00
Author
Owner
Copy Link

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

Thanks for bearing with us. I've not been able to find any followup steps here, unfortunately, and it looks like Terminal's holding the ShellExecute API correctly. Im don't think there's a path forward from this project's perspective...

Gonna tentatively resolve this one as "no-repro" since we can't get our hands on it. It looks like a filesystem issue, and perhaps a disk check will restore order. Perhaps it won't. ☹️

@DHowett-MSFT commented on GitHub (May 13, 2020): Thanks for bearing with us. I've not been able to find any followup steps here, unfortunately, and it looks like Terminal's holding the ShellExecute API correctly. Im don't think there's a path forward from this project's perspective... Gonna tentatively resolve this one as "no-repro" since we can't get our hands on it. It looks like a filesystem issue, and perhaps a disk check will restore order. Perhaps it won't. ☹️
claunia commented 2026-01-31 01:13:46 +00:00
Author
Owner
Copy Link

@cobyl commented on GitHub (Sep 20, 2020):

Interesting. Have exactly same situation. How you solve that?

@cobyl commented on GitHub (Sep 20, 2020): Interesting. Have exactly same situation. How you solve that?
claunia commented 2026-01-31 01:13:46 +00:00
Author
Owner
Copy Link

@Zagan202 commented on GitHub (Sep 20, 2020):

Unfortunately I didn't solve it.
What does your BSOD report say btw?

@Zagan202 commented on GitHub (Sep 20, 2020): Unfortunately I didn't solve it. What does your BSOD report say btw?
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-Attention Needs-Tag-Fix Needs-Triage Resolution-No-Repro
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#7830
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?