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

Windows Terminal scroll back isn't working in Windows 10 #15968

New Issue
Closed
opened 2026-01-31 04:53:37 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 04:53:37 +00:00
Owner
Copy Link

Originally created by @jerryasher on GitHub (Nov 26, 2021).

Windows Terminal version

1.11.2921.0

Windows build number

10.0.19044.1348

Other Software

No response

Steps to reproduce

  1. Open a new windows terminal with a shell (powershell, cmd.exe, ubuntu, yori)
  2. fill the terminal window with many more lines than the window can display, (dir or ls of a very large directory)
  3. using the mouse wheel, scroll back (up), or ctrl-shift-home or ctrl-shift-up or ctrl-shift-pgup

Expected Behavior

The terminal should scroll through the earlier lines, display them, and keeping them displayed until there is "typing" at which point the scroll should snap back to the newest command prompt awaiting input

Actual Behavior

I have Windows Terminal running on both Windows 10 and Windows 11, with identical settings.json (modulo any changes I've made this evening as I try to pinpoint this issue) The behavior I am seeing only occurs on Windows 10, Windows 11 behaves as expected.

Testing with any of the following shells

  • Powershell Core
  • CMD.exe
  • Yori
  • Ubuntu

When I

  • fill the terminal window with many more lines than would be visible, (dir or ls of a very large directory)
  • use the mouse wheel to scroll back (up) through the earlier lines of output

I can see the window scrolling its contents, but as soon as soon as I stop scrolling, the window snaps back to the bottom, the newest lines of output, the line with the newest command prompt.

This is with

  • scroll to input white typing on
  • scroll bars visible or hidden
  • seemingly regardless of history size

This seems similar to #11771

Originally created by @jerryasher on GitHub (Nov 26, 2021). ### Windows Terminal version 1.11.2921.0 ### Windows build number 10.0.19044.1348 ### Other Software _No response_ ### Steps to reproduce 1. Open a new windows terminal with a shell (powershell, cmd.exe, ubuntu, yori) 2. fill the terminal window with many more lines than the window can display, (`dir` or `ls` of a very large directory) 3. using the mouse wheel, scroll back (up), or ctrl-shift-home or ctrl-shift-up or ctrl-shift-pgup ### Expected Behavior The terminal should scroll through the earlier lines, display them, and keeping them displayed until there is "typing" at which point the scroll should snap back to the newest command prompt awaiting input ### Actual Behavior I have Windows Terminal running on both Windows 10 and Windows 11, with identical `settings.json` (modulo any changes I've made this evening as I try to pinpoint this issue) The behavior I am seeing only occurs on Windows 10, Windows 11 behaves as expected. Testing with any of the following shells + Powershell Core + CMD.exe + Yori + Ubuntu When I + fill the terminal window with many more lines than would be visible, (`dir` or `ls` of a very large directory) + use the mouse wheel to scroll back (up) through the earlier lines of output I can see the window scrolling its contents, but as soon as soon as I stop scrolling, the window snaps back to the bottom, the newest lines of output, the line with the newest command prompt. This is with + scroll to input white typing on + scroll bars visible or hidden + seemingly regardless of history size This seems similar to #11771
claunia commented 2026-01-31 04:53:38 +00:00
Author
Owner
Copy Link

@jerryasher commented on GitHub (Nov 26, 2021):

My settings are here: settings.json

@jerryasher commented on GitHub (Nov 26, 2021): My settings are here: [settings.json](https://github.com/microsoft/terminal/files/7606904/settings.json.txt)
claunia commented 2026-01-31 04:53:38 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 29, 2021):

I can see the window scrolling its contents, but as soon as soon as I stop scrolling, the window snaps back to the bottom, the newest lines of output, the line with the newest command prompt.

Curious. Sounds like some sort of other dead key is coming through and causing us to snap back down. Throwing "snapOnInput": false in the defaults should fix that, but you've already got that set for the Yori profile...

Can you try reproing this with the debug tap to get a trace of all the input and output. Once the bug starts occurring, send us a screenshot and we might be able to figure out what the Terminal thinks it's getting here.

@zadjii-msft commented on GitHub (Nov 29, 2021): > I can see the window scrolling its contents, but as soon as soon as I stop scrolling, the window snaps back to the bottom, the newest lines of output, the line with the newest command prompt. Curious. Sounds like some sort of other dead key is coming through and causing us to snap back down. Throwing `"snapOnInput": false` in the defaults _should_ fix that, but you've already got that set for the Yori profile... Can you try reproing this with the [debug tap](https://github.com/microsoft/terminal/wiki/Enabling-the-debug-tap) to get a trace of all the input and output. Once the bug starts occurring, send us a screenshot and we might be able to figure out what the Terminal thinks it's getting here.
claunia commented 2026-01-31 04:53:39 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 3, 2021):

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 (Dec 3, 2021): 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**.
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-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#15968
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?