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

Terminal output missing (beyond upper left 1/4) - when fullscreen over RDP and disconnect/connect - leave fullscreen usually fixes output #15350

New Issue
Closed
opened 2026-01-31 04:35:55 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 04:35:55 +00:00
Owner
Copy Link

Originally created by @g0t4 on GitHub (Sep 26, 2021).

Windows Terminal version (or Windows build number)

10.0.22000.194, 1.11.2421.0

Other Software

I've tried this with different shells:
PowerShell (desktop edition)
PowerShell (core) 7.1 and 7.2 preview
WSL - Official Ubuntu distro

Doesn't seem to matter what shell is running inside the terminal tab.

My machine is Win 11 (latest build)

I've tested both latest stable Windows Terminal 1.10.2383.0 and Preview 1.11.2421.0

Steps to reproduce

  1. Connect over RDP (haven't tested a local connection) - from a mac in my case
  2. Open Windows Terminal
  3. Enter Fullscreen window size (alt+enter)
  4. (optional) run a command that produces output (beyond just the upper left quadrant of screen)
  5. Disconnect RDP (in my case I use Cmd+W on my Mac)
  6. Connect RDP (right away is fine, no need to wait)
  7. Only top left quadrant of content shows
  • Even new running commands--after RDP reconnect, when only the top left quadrant shows--don't show output beyond top left quadrant
  1. Leave fullscreen and re-enter fullscreen to fix this, sometimes I have to change window size too (after leaving fullscreen and before reentering fullscreen).

This doesn't happen with other window sizes in my experience (ie maximized but not fullscreen doesn't trigger the issue).

Expected Behavior

Windows Terminal Output would remain the same. Like it does when the window is maximized (not fullscreen).

Actual Behavior

Only the top left quadrant shows until I leave/reenter fullscreen (alt+enter).

Before RDP disconnect: (Preview 1.11)
image

After RDP reconnect: (Preview)
image

WSL - After RDP reconnect: (Preview)
image

WSL - After fixing (leave/re-enter fullscreen): (Preview)
image

Stable Windows Terminal build - After RDP reconnect:
image

Originally created by @g0t4 on GitHub (Sep 26, 2021). ### Windows Terminal version (or Windows build number) 10.0.22000.194, 1.11.2421.0 ### Other Software I've tried this with different shells: PowerShell (desktop edition) PowerShell (core) 7.1 and 7.2 preview WSL - Official Ubuntu distro Doesn't seem to matter what shell is running inside the terminal tab. My machine is Win 11 (latest build) I've tested both latest stable Windows Terminal 1.10.2383.0 and Preview 1.11.2421.0 ### Steps to reproduce 1. Connect over RDP (haven't tested a local connection) - from a mac in my case 2. Open Windows Terminal 3. Enter Fullscreen window size (alt+enter) 4. (optional) run a command that produces output (beyond just the upper left quadrant of screen) 5. Disconnect RDP (in my case I use Cmd+W on my Mac) 6. Connect RDP (right away is fine, no need to wait) 7. Only top left quadrant of content shows - Even new running commands--after RDP reconnect, when only the top left quadrant shows--don't show output beyond top left quadrant 8. Leave fullscreen and re-enter fullscreen to fix this, sometimes I have to change window size too (after leaving fullscreen and before reentering fullscreen). This doesn't happen with other window sizes in my experience (ie maximized but not fullscreen doesn't trigger the issue). ### Expected Behavior Windows Terminal Output would remain the same. Like it does when the window is maximized (not fullscreen). ### Actual Behavior Only the top left quadrant shows until I leave/reenter fullscreen (alt+enter). Before RDP disconnect: (Preview 1.11) ![image](https://user-images.githubusercontent.com/180189/134805383-d750de0d-9ed9-4b08-8b43-d775036f76c8.png) After RDP reconnect: (Preview) ![image](https://user-images.githubusercontent.com/180189/134805475-3194fcce-d647-489b-bd78-37f4914627d5.png) WSL - After RDP reconnect: (Preview) ![image](https://user-images.githubusercontent.com/180189/134805510-b830fc19-cd30-40e5-bac1-1be1fbf618d1.png) WSL - After fixing (leave/re-enter fullscreen): (Preview) ![image](https://user-images.githubusercontent.com/180189/134805538-51ab28b6-4f2a-419e-ab46-b07fb39a8980.png) Stable Windows Terminal build - After RDP reconnect: ![image](https://user-images.githubusercontent.com/180189/134805567-3c1d3bbf-479a-4e56-a7f7-54f6f71f3bf2.png)
claunia commented 2026-01-31 04:35:56 +00:00
Author
Owner
Copy Link

@mkke commented on GitHub (Sep 27, 2021):

I have the same effect on my machine, I'm also connecting via RDP from a Mac.
For me it's also happening with windows that aren't full-screen.
Enabling full-screen updates or software rendering makes no difference.
I'm on Windows 10 20H2 19042.1237. Terminal 1.11.2421.0.

@mkke commented on GitHub (Sep 27, 2021): I have the same effect on my machine, I'm also connecting via RDP from a Mac. For me it's also happening with windows that aren't full-screen. Enabling full-screen updates or software rendering makes no difference. I'm on Windows 10 20H2 19042.1237. Terminal 1.11.2421.0.
claunia commented 2026-01-31 04:35:56 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 18, 2021):

This looks terribly similar to #11317, though

This doesn't happen with other window sizes in my experience (ie maximized but not fullscreen doesn't trigger the issue).

Makes me think that this is something different. Out of curiosity, does the machine have a different DPI locally than the machine that you're using to RDP to the Terminal? Seems as though we've messed something up with the DPI updates.

@zadjii-msft commented on GitHub (Oct 18, 2021): This looks terribly similar to #11317, though > This doesn't happen with other window sizes in my experience (ie maximized but not fullscreen doesn't trigger the issue). Makes me think that this is something different. Out of curiosity, does the machine have a different DPI locally than the machine that you're using to RDP to the Terminal? Seems as though we've messed something up with the DPI updates.
claunia commented 2026-01-31 04:35:57 +00:00
Author
Owner
Copy Link

@DanielNesbitt commented on GitHub (Jan 20, 2022):

The issue does seem to be DPI scaling related. I was able to reproduce this just by changing the DPI scaling.

At 150%:
image

At 200%
image

The output that is missing seems to depend on the difference in scaling. I suspect that RDP goes through a DPI switch even if the scaling factor on both machines is the same. In my case, I noticed this problem when using RDP between two Windows 10 machines with 150% scaling.

@DanielNesbitt commented on GitHub (Jan 20, 2022): The issue does seem to be DPI scaling related. I was able to reproduce this just by changing the DPI scaling. At 150%: ![image](https://user-images.githubusercontent.com/377432/150336447-b55be5a9-ce67-49cf-aa9f-d2fa43c386dc.png) At 200% ![image](https://user-images.githubusercontent.com/377432/150336549-80a5700b-2aa3-472a-80ce-0485c0101e30.png) The output that is missing seems to depend on the difference in scaling. I suspect that RDP goes through a DPI switch even if the scaling factor on both machines is the same. In my case, I noticed this problem when using RDP between two Windows 10 machines with 150% scaling.
claunia commented 2026-01-31 04:35:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 17, 2022):

I'm putting this in 1.14 cause it looks like it's just a variation on https://github.com/microsoft/terminal/issues/11317. Any chance you could share your settings.json file? Seemingly, this has to do with certain font sizes & faces, so more data can't hurt.

@zadjii-msft commented on GitHub (Feb 17, 2022): I'm putting this in 1.14 cause it looks like it's just a variation on https://github.com/microsoft/terminal/issues/11317. Any chance you could share your [settings.json file](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#where-can-i-find-the-settings-file)? Seemingly, this has to do with certain font sizes & faces, so more data can't hurt.
claunia commented 2026-01-31 04:35:57 +00:00
Author
Owner
Copy Link

@DanielNesbitt commented on GitHub (Feb 17, 2022):

Here is my profile. I am using a custom font style.

@DanielNesbitt commented on GitHub (Feb 17, 2022): Here is my [profile](https://github.com/microsoft/terminal/files/8089921/settings.txt). I am using a custom font style.
claunia commented 2026-01-31 04:35:57 +00:00
Author
Owner
Copy Link

@g0t4 commented on GitHub (Feb 17, 2022):

"defaults": {

        "bellStyle": "none",
        "closeOnExit": "graceful",
        "colorScheme": "Wes iTerm",
        "font":
        {
            "face": "SauceCodePro NF",
            "size": 26
        },
        "historySize": 99999,
        "useAcrylic": false

    }

I'm using Nerd Font's Sauce Code Pro

https://github.com/ryanoasis/nerd-fonts/releases/download/v2.1.0/SourceCodePro.zip

@g0t4 commented on GitHub (Feb 17, 2022): "defaults": { "bellStyle": "none", "closeOnExit": "graceful", "colorScheme": "Wes iTerm", "font": { "face": "SauceCodePro NF", "size": 26 }, "historySize": 99999, "useAcrylic": false } I'm using Nerd Font's Sauce Code Pro - https://www.nerdfonts.com/font-downloads - https://github.com/ryanoasis/nerd-fonts/releases/download/v2.1.0/SourceCodePro.zip
claunia commented 2026-01-31 04:35:57 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Feb 17, 2022):

(Thanks for all the info!)

I'm gonna tentatively call this a duplicate of #11317 and concentrate our DPI bugs over there. I'm alarmed that this regressed. 😄

@DHowett commented on GitHub (Feb 17, 2022): (Thanks for all the info!) I'm gonna tentatively call this a duplicate of #11317 and concentrate our DPI bugs over there. I'm alarmed that this regressed. :smile:
claunia commented 2026-01-31 04:35:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 18, 2022):

/dup #11317

@zadjii-msft commented on GitHub (Feb 18, 2022): /dup #11317
claunia commented 2026-01-31 04:35:58 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 18, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Feb 18, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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-Rendering Issue-Bug Needs-Tag-Fix Priority-3 Product-Terminal Resolution-Duplicate
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#15350
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?