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

Frequent process failures due to GetConsoleScreenBufferInfoEx failing #7844

New Issue
Open
opened 2026-01-31 01:14:06 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 01:14:06 +00:00
Owner
Copy Link

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

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 0.11.1191.0

I'm running PowerShell within the terminal.

Steps to reproduce

Run msbuild.exe or dotnet build.
Resizing the window during the build is not necessary, but may increase the frequency of the failure.

Expected behavior

No errors or build breaks.

Actual behavior

Evidently some processes that are attached to the console and spawned from within the Windows Terminal call GetConsoleScreenBufferInfoEx and it frequently fails with GetConsoleScreenBufferInfoEx->WinError: #6, as shown below:

INFO  00:02:02.377: Targets status: Progress 97.4 %, Pending 1, Ready 0, NotStarted 0, Failed 0, Succeeded 37, FromCache 36, Cache download rate: 0.0 Mbps
INFO  00:02:12.468: Targets status: Progress 97.4 %, Pending 1, Ready 0, NotStarted 0, Failed 0, Succeeded 37, FromCache 36, Cache download rate: 0.0 Mbps
ERROR Command src\env\shell\UIInternal_Checked_X86 (src\env\shell\UIInternal) finished with result Failed, reason: EXEC : error : "GetConsoleScreenBufferInfoEx->WinError: #6"
Log location: \\DESKTOP-CA1DFI9\D$\VS\src\env\shell\UIInternal\Logs\Checked\X86

This causes frequent build breaks. Restarting the build will usually get the build to pass or at least get further along, so I just repeat the build until it finally succeeds.

I've never seen this outside of Windows Terminal.

Originally created by @AArnott on GitHub (Apr 30, 2020). # Environment ```none Windows build number: 10.0.19041.0 Windows Terminal version (if applicable): 0.11.1191.0 ``` I'm running PowerShell within the terminal. # Steps to reproduce Run msbuild.exe or `dotnet build`. Resizing the window during the build is _not_ necessary, but *may* increase the frequency of the failure. # Expected behavior No errors or build breaks. # Actual behavior Evidently some processes that are attached to the console and spawned from within the Windows Terminal call `GetConsoleScreenBufferInfoEx` and it frequently fails with `GetConsoleScreenBufferInfoEx->WinError: #6`, as shown below: ``` INFO 00:02:02.377: Targets status: Progress 97.4 %, Pending 1, Ready 0, NotStarted 0, Failed 0, Succeeded 37, FromCache 36, Cache download rate: 0.0 Mbps INFO 00:02:12.468: Targets status: Progress 97.4 %, Pending 1, Ready 0, NotStarted 0, Failed 0, Succeeded 37, FromCache 36, Cache download rate: 0.0 Mbps ERROR Command src\env\shell\UIInternal_Checked_X86 (src\env\shell\UIInternal) finished with result Failed, reason: EXEC : error : "GetConsoleScreenBufferInfoEx->WinError: #6" Log location: \\DESKTOP-CA1DFI9\D$\VS\src\env\shell\UIInternal\Logs\Checked\X86 ``` This causes *frequent* build breaks. Restarting the build will usually get the build to pass or at least get further along, so I just repeat the build until it finally succeeds. I've never seen this outside of Windows Terminal.
claunia added the Resolution-ExternalNeeds-Tag-FixNeeds-Attention labels 2026-01-31 01:14:06 +00:00
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 Resolution-External
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#7844
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?