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: Green Screen of Death when acessing settings from within console #1477

New Issue
Closed
opened 2026-01-30 22:28:17 +00:00 by claunia · 7 comments
claunia commented 2026-01-30 22:28:17 +00:00
Owner
Copy Link

Originally created by @mrmikeman38 on GitHub (Jun 3, 2019).

Environment

Windows build number: 10.0.18362.145
Windows Terminal version (if applicable):

Steps to reproduce

-Open "Windows Terminal (dev build)"
-Open the dropdown menu
-Select "Settings" from dropdown menu

Expected behavior

"Profiles.json" is opened

Actual behavior

Windows crashes to a Green Screen of Death with stop code APC_INDEX_MISMATCH

No further information presented.

Originally created by @mrmikeman38 on GitHub (Jun 3, 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.145 Windows Terminal version (if applicable): ``` # Steps to reproduce -Open "Windows Terminal (dev build)" -Open the dropdown menu -Select "Settings" from dropdown menu <!-- A description of how to trigger this bug. --> # Expected behavior "Profiles.json" is opened <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior Windows crashes to a Green Screen of Death with stop code APC_INDEX_MISMATCH No further information presented. <!-- What's actually happening? -->
claunia commented 2026-01-30 22:28:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 3, 2019):

Well that's insanely bad. I thought we fixed this with the EnableMouseInPointer thing, but this might be something else.

Actually, thinking on it more, this might be something else entirely. The EnableMouseInPointer thing was for Alt+a causing a GSOD.

@zadjii-msft commented on GitHub (Jun 3, 2019): Well that's insanely bad. I thought we fixed this with the `EnableMouseInPointer` thing, but this might be something else. Actually, thinking on it more, this might be something else entirely. The `EnableMouseInPointer` thing was for `Alt+a` causing a GSOD.
claunia commented 2026-01-30 22:28:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 3, 2019):

For the record, I can't get this to repro locally, so if I could get another verification of this bug report, that'd be appreciated.

@zadjii-msft commented on GitHub (Jun 3, 2019): For the record, I can't get this to repro locally, so if I could get another verification of this bug report, that'd be appreciated.
claunia commented 2026-01-30 22:28:18 +00:00
Author
Owner
Copy Link

@mrmikeman38 commented on GitHub (Jun 4, 2019):

For the record, it might be unrelated but Microsoft Word also causes a GSOD on build 1903.

@mrmikeman38 commented on GitHub (Jun 4, 2019): For the record, it might be unrelated but Microsoft Word also causes a GSOD on build 1903.
claunia commented 2026-01-30 22:28:19 +00:00
Author
Owner
Copy Link

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

@mrmikeman38 Thanks for the report. Would you mind collecting a memory dump (see here for brief instructions on enabling that if it's not already enabled) and e-mailing it to secure@microsoft.com? Mention my name ("Dustin Howett") as somebody who they should route it to.

@DHowett-MSFT commented on GitHub (Jun 4, 2019): @mrmikeman38 Thanks for the report. Would you mind collecting a memory dump (see [here](https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/enabling-a-kernel-mode-dump-file) for brief instructions on enabling that _if_ it's not already enabled) and e-mailing it to secure@microsoft.com? Mention my name ("Dustin Howett") as somebody who they should route it to.
claunia commented 2026-01-30 22:28:19 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 8, 2019):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jun 8, 2019): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-30 22:28:19 +00:00
Author
Owner
Copy Link

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

Is it possible to reopen this because this is still a problem. Just installed.
Winver: 18362.175
Windows Terminal: 0.2.1715.0

@KennethVanMele commented on GitHub (Jun 22, 2019): Is it possible to reopen this because this is still a problem. Just installed. Winver: 18362.175 Windows Terminal: 0.2.1715.0
claunia commented 2026-01-30 22:28:19 +00:00
Author
Owner
Copy Link

@Yoanndp commented on GitHub (Jun 23, 2019):

I can provide information about this, I did exactly the same thing as the owner and I got a bsod.
Information :

New Terminal Informations:
Windows Terminal (Preview)
Version: 0.2.1715.0 (From MS Store)

Computer basic informations:
Windows 10 Pro x64
Version 1903 (Build: 18362.175)

BSOD informations:
Bug Check String:
• APC_INDEX_MISMATCH
Bug Check Code:
• 0x00000001
Caused By Driver:
• ntoskrnl.exe
Caused By Address:
• ntoskrnl.exe+1bc8a0

Here is my full Bsod dump uploaded on WeTransfer.com
https://we.tl/t-X23Ccy1nmA

@Yoanndp commented on GitHub (Jun 23, 2019): I can provide information about this, I did exactly the same thing as the owner and I got a bsod. Information : **New Terminal Informations:** Windows Terminal (Preview) Version: 0.2.1715.0 (From MS Store) **Computer basic informations:** Windows 10 Pro x64 Version 1903 (Build: 18362.175) **BSOD informations:** _Bug Check String:_ • APC_INDEX_MISMATCH _Bug Check Code:_ • 0x00000001 _Caused By Driver:_ • ntoskrnl.exe _Caused By Address:_ • ntoskrnl.exe+1bc8a0 Here is my full Bsod dump uploaded on WeTransfer.com https://we.tl/t-X23Ccy1nmA
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-UserInterface Help Wanted Issue-Bug Needs-Author-Feedback Product-Terminal
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#1477
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?