starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Window is not cleared #22922

New Issue
Closed
opened 2026-01-31 08:27:18 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:27:18 +00:00
Owner
Copy Link

Originally created by @ygoe on GitHub (Feb 14, 2025).

Windows Terminal version

1.21.3231.0

Windows build number

10.0.22631.4602

Other Software

No response

Steps to reproduce

  1. Set Terminal as the default terminal app in Windows 11
  2. Run a console application from Visual Studio
  3. Don't close the temrinal tab
  4. Run your app from VS again

Expected Behavior

Normal rendering of output in an empty window.

Actual Behavior

Most of the time, when starting your app from VS, the terminal window is cleared and the new app output is shown.

Sometimes, and then often in a row, the old content remains visible in the terminal and the new output is "printed over it". Any content that isn't written by the new app output remains there. This is completely unreadable.

The only solution is then to stop the app, close the terminal tab or window, and run the app again to have it print its output in a clean window.

Originally created by @ygoe on GitHub (Feb 14, 2025). ### Windows Terminal version 1.21.3231.0 ### Windows build number 10.0.22631.4602 ### Other Software _No response_ ### Steps to reproduce 1. Set Terminal as the default terminal app in Windows 11 2. Run a console application from Visual Studio 3. Don't close the temrinal tab 4. Run your app from VS again ### Expected Behavior Normal rendering of output in an empty window. ### Actual Behavior Most of the time, when starting your app from VS, the terminal window is cleared and the new app output is shown. Sometimes, and then often in a row, the old content remains visible in the terminal and the new output is "printed over it". Any content that isn't written by the new app output remains there. This is completely unreadable. The only solution is then to stop the app, close the terminal tab or window, and run the app again to have it print its output in a clean window.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:27:19 +00:00
claunia commented 2026-01-31 08:27:20 +00:00
Author
Owner
Copy Link

@similar-issues-ai[bot] commented on GitHub (Feb 14, 2025):

We've found some similar issues:

  • #15768 , similarity score: 81%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@similar-issues-ai[bot] commented on GitHub (Feb 14, 2025): We've found some similar issues: - #15768 , similarity score: 81% If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue. > Note: You can give me feedback by 👍 or 👎 this comment.
claunia commented 2026-01-31 08:27:20 +00:00
Author
Owner
Copy Link

@ygoe commented on GitHub (Feb 14, 2025):

Looks like the same, but it's closed and forgotten, so we need a new issue for the open bug.

@ygoe commented on GitHub (Feb 14, 2025): Looks like the same, but it's closed and forgotten, so we need a new issue for the open bug.
claunia commented 2026-01-31 08:27:20 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 14, 2025):

Visual Studio tries to reuse the same console window for debugging sessions. This is a bug in their debug session broker. You may need to file a bug on their Developer Community forum.

Terminal is not in charge of session reuse.

@DHowett commented on GitHub (Feb 14, 2025): Visual Studio tries to reuse the same console window for debugging sessions. This is a bug in their debug session broker. You may need to file a bug on their Developer Community forum. Terminal is not in charge of session reuse.
claunia commented 2026-01-31 08:27:21 +00:00
Author
Owner
Copy Link

@ygoe commented on GitHub (Feb 14, 2025):

I've never seen this bug before switching to Windows Terminal. Is the bug in Visual Studio only applying to this terminal host app?

@ygoe commented on GitHub (Feb 14, 2025): I've never seen this bug before switching to Windows Terminal. Is the bug in Visual Studio only applying to this terminal host app?
claunia commented 2026-01-31 08:27:21 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 26, 2025):

I think it may be! Sorry!

@DHowett commented on GitHub (Mar 26, 2025): I think it may be! Sorry!
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-Bug Needs-Triage
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#22922
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?