starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

fullscreen not working on all displays #5189

New Issue
Closed
opened 2026-01-31 00:07:05 +00:00 by claunia · 17 comments
claunia commented 2026-01-31 00:07:05 +00:00
Owner
Copy Link

Originally created by @kort3x on GitHub (Nov 26, 2019).

Originally assigned to: @DHowett-MSFT on GitHub.

Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 0.7.3291.0

Steps to reproduce

Entering fullscreen only works on two of my three monitors.
On the third one terminal just maximizes and shows nothing but black/gray and a bright white titlebar.

image

Originally created by @kort3x on GitHub (Nov 26, 2019). Originally assigned to: @DHowett-MSFT on GitHub. <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- 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. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. 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.0 Windows Terminal version (if applicable): 0.7.3291.0 ``` # Steps to reproduce Entering fullscreen only works on two of my three monitors. On the third one terminal just maximizes and shows nothing but black/gray and a bright white titlebar. ![image](https://user-images.githubusercontent.com/13918530/69661858-73eea000-1083-11ea-83f2-b90d8a3783a4.png)
claunia commented 2026-01-31 00:07:07 +00:00
Author
Owner
Copy Link

@ramsay-vibes commented on GitHub (Nov 26, 2019):

My machine has two identical monitors, but fullscreen only works on the primary monitor. Fullscreen on monitor 2 fails per the screenshot above.

@ramsay-vibes commented on GitHub (Nov 26, 2019): My machine has two identical monitors, but _fullscreen_ only works on the primary monitor. Fullscreen on monitor 2 fails per the screenshot above.
claunia commented 2026-01-31 00:07:08 +00:00
Author
Owner
Copy Link

@kort3x commented on GitHub (Nov 26, 2019):

I have three identical monitors.
Two of them connected with DisplayPort and one DVI.
The secondary DP craps out when entering fullscreen.

Reminds me of an issue over at PowerToys:
https://github.com/microsoft/PowerToys/issues/611

@kort3x commented on GitHub (Nov 26, 2019): I have three identical monitors. Two of them connected with DisplayPort and one DVI. The secondary DP craps out when entering fullscreen. Reminds me of an issue over at PowerToys: https://github.com/microsoft/PowerToys/issues/611
claunia commented 2026-01-31 00:07:08 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 26, 2019):

Are those displays connected to different display adapters, or to the same one? What's your graphics hardware situation?

@DHowett-MSFT commented on GitHub (Nov 26, 2019): Are those displays connected to different display adapters, or to the same one? What's your graphics hardware situation?
claunia commented 2026-01-31 00:07:09 +00:00
Author
Owner
Copy Link

@kort3x commented on GitHub (Nov 26, 2019):

GPU:

Videoprocessor : GeForce GTX 1050 Ti
Videomodedescription : 1920 x 1200 x 4294967296 colors
DriverDate : 05.09.2019 02:00:00
DriverVersion : 26.21.14.3630

Monitors:

All connected to same GPU

GetSystemMetrics = 3
GetMonitorInfo OK
EnumDisplayDevices OK:
DeviceID = \?\DISPLAY#GSM59B4#5&e062d6f&0&UID4353#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
DeviceKey = \Registry\Machine\System\CurrentControlSet\Control\Class{4d36e96e-e325-11ce-bfc1-08002be10318}\0010
DeviceName = \.\DISPLAY1\Monitor0
DeviceString = Generic PnP Monitor
GetMonitorInfo OK
EnumDisplayDevices OK:
DeviceID = \?\DISPLAY#GSM59B4#5&e062d6f&0&UID4356#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
DeviceKey = \Registry\Machine\System\CurrentControlSet\Control\Class{4d36e96e-e325-11ce-bfc1-08002be10318}\0012
DeviceName = \.\DISPLAY2\Monitor0
DeviceString = Generic PnP Monitor
GetMonitorInfo OK
EnumDisplayDevices OK:
DeviceID = \?\DISPLAY#GSM59B4#5&e062d6f&0&UID4355#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
DeviceKey = \Registry\Machine\System\CurrentControlSet\Control\Class{4d36e96e-e325-11ce-bfc1-08002be10318}\0011
DeviceName = \.\DISPLAY3\Monitor0
DeviceString = Generic PnP Monitor
EnumDisplayMonitors OK

WMI report:
Active: 1
WeekOfManufacture: 9
InstanceName: DISPLAY\GSM59B4\5&e062d6f&0&UID4353_0
YearOfManufacture: 2016
ManufacturerName: 71 83 77 0 0 0 0 0 0 0 0 0 0 0 0 0
ProductCodeID: 53 57 66 52 0 0 0 0 0 0 0 0 0 0 0 0
SerialNumberID: 54 48 57 78 84 83 85 52 88 56 54 50 0 0 0 0
UserFriendlyName: 50 52 69 66 50 51 0 0 0 0 0 0 0

Active: 1
WeekOfManufacture: 9
InstanceName: DISPLAY\GSM59B4\5&e062d6f&0&UID4356_0
YearOfManufacture: 2016
ManufacturerName: 71 83 77 0 0 0 0 0 0 0 0 0 0 0 0 0
ProductCodeID: 53 57 66 52 0 0 0 0 0 0 0 0 0 0 0 0
SerialNumberID: 54 48 57 78 84 90 78 55 51 54 48 53 0 0 0 0
UserFriendlyName: 50 52 69 66 50 51 0 0 0 0 0 0 0

Active: 1
WeekOfManufacture: 9
InstanceName: DISPLAY\GSM59B4\5&e062d6f&0&UID4355_0
YearOfManufacture: 2016
ManufacturerName: 71 83 77 0 0 0 0 0 0 0 0 0 0 0 0 0
ProductCodeID: 53 57 66 52 0 0 0 0 0 0 0 0 0 0 0 0
SerialNumberID: 54 48 57 78 84 74 74 52 88 56 50 56 0 0 0 0
UserFriendlyName: 50 52 69 66 50 51 0 0 0 0 0 0 0

@kort3x commented on GitHub (Nov 26, 2019): ### GPU: Videoprocessor : GeForce GTX 1050 Ti Videomodedescription : 1920 x 1200 x 4294967296 colors DriverDate : 05.09.2019 02:00:00 DriverVersion : 26.21.14.3630 ### Monitors: All connected to same GPU GetSystemMetrics = 3 GetMonitorInfo OK EnumDisplayDevices OK: DeviceID = \\?\DISPLAY#GSM59B4#5&e062d6f&0&UID4353#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} DeviceKey = \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0010 DeviceName = \\.\DISPLAY1\Monitor0 DeviceString = Generic PnP Monitor GetMonitorInfo OK EnumDisplayDevices OK: DeviceID = \\?\DISPLAY#GSM59B4#5&e062d6f&0&UID4356#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} DeviceKey = \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0012 DeviceName = \\.\DISPLAY2\Monitor0 DeviceString = Generic PnP Monitor GetMonitorInfo OK EnumDisplayDevices OK: DeviceID = \\?\DISPLAY#GSM59B4#5&e062d6f&0&UID4355#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7} DeviceKey = \Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0011 DeviceName = \\.\DISPLAY3\Monitor0 DeviceString = Generic PnP Monitor EnumDisplayMonitors OK WMI report: Active: 1 WeekOfManufacture: 9 InstanceName: DISPLAY\GSM59B4\5&e062d6f&0&UID4353_0 YearOfManufacture: 2016 ManufacturerName: 71 83 77 0 0 0 0 0 0 0 0 0 0 0 0 0 ProductCodeID: 53 57 66 52 0 0 0 0 0 0 0 0 0 0 0 0 SerialNumberID: 54 48 57 78 84 83 85 52 88 56 54 50 0 0 0 0 UserFriendlyName: 50 52 69 66 50 51 0 0 0 0 0 0 0 Active: 1 WeekOfManufacture: 9 InstanceName: DISPLAY\GSM59B4\5&e062d6f&0&UID4356_0 YearOfManufacture: 2016 ManufacturerName: 71 83 77 0 0 0 0 0 0 0 0 0 0 0 0 0 ProductCodeID: 53 57 66 52 0 0 0 0 0 0 0 0 0 0 0 0 SerialNumberID: 54 48 57 78 84 90 78 55 51 54 48 53 0 0 0 0 UserFriendlyName: 50 52 69 66 50 51 0 0 0 0 0 0 0 Active: 1 WeekOfManufacture: 9 InstanceName: DISPLAY\GSM59B4\5&e062d6f&0&UID4355_0 YearOfManufacture: 2016 ManufacturerName: 71 83 77 0 0 0 0 0 0 0 0 0 0 0 0 0 ProductCodeID: 53 57 66 52 0 0 0 0 0 0 0 0 0 0 0 0 SerialNumberID: 54 48 57 78 84 74 74 52 88 56 50 56 0 0 0 0 UserFriendlyName: 50 52 69 66 50 51 0 0 0 0 0 0 0
claunia commented 2026-01-31 00:07:09 +00:00
Author
Owner
Copy Link

@ramsay-vibes commented on GitHub (Nov 26, 2019):

Both of my monitors are connected to separate DPs. Both monitors using NVIDIA GeForce GTX 1060 6GB GPU. Both monitors using native resolution (1920 x 1080).

@ramsay-vibes commented on GitHub (Nov 26, 2019): Both of my monitors are connected to separate DPs. Both monitors using NVIDIA GeForce GTX 1060 6GB GPU. Both monitors using native resolution (1920 x 1080).
claunia commented 2026-01-31 00:07:09 +00:00
Author
Owner
Copy Link

@BundyB commented on GitHub (Nov 26, 2019):

I'm seeing this on one of my monitors, plus different behaviour on a second.

The two 2560x1440 panels (one of which is primary) fullscreen fine.
The 2560x1600 panel to the right of primary displays like the screenshot above.
The 1920x1080 panel fullscreens perfectly to the top half of the display, with the bottom half matching the screenshot.

All panels are DP off the same AMD FirePro W5100.

@BundyB commented on GitHub (Nov 26, 2019): I'm seeing this on one of my monitors, plus different behaviour on a second. The two 2560x1440 panels (one of which is primary) fullscreen fine. The 2560x1600 panel to the right of primary displays like the screenshot above. The 1920x1080 panel fullscreens perfectly to the top half of the display, with the bottom half matching the screenshot. All panels are DP off the same AMD FirePro W5100.
claunia commented 2026-01-31 00:07:10 +00:00
Author
Owner
Copy Link

@Aarklendoia commented on GitHub (Nov 27, 2019):

Same problem for me. I have an nVidia NV300 (one connector for two DVI monitor). The display shows a strip on the left but the rest is entirely grey (dark theme).

image

@Aarklendoia commented on GitHub (Nov 27, 2019): Same problem for me. I have an nVidia NV300 (one connector for two DVI monitor). The display shows a strip on the left but the rest is entirely grey (dark theme). ![image](https://user-images.githubusercontent.com/1765298/69724685-af897880-111c-11ea-9cde-b588b8976017.png)
claunia commented 2026-01-31 00:07:10 +00:00
Author
Owner
Copy Link

@LuanVSO commented on GitHub (Nov 27, 2019):

similar to https://github.com/microsoft/terminal/issues/3710#issuecomment-559074329
but with more cols.

hardware: laptop
second screen conected via hdmi to intel graphic adapter.
primary screen also register as conected to intel graphic adapter.

main screen resolution(left):1366X768
secondary screen resolution(right):1920X1080

image

@LuanVSO commented on GitHub (Nov 27, 2019): similar to https://github.com/microsoft/terminal/issues/3710#issuecomment-559074329 but with more cols. hardware: laptop second screen conected via hdmi to intel graphic adapter. primary screen also register as conected to intel graphic adapter. main screen resolution(left):1366X768 secondary screen resolution(right):1920X1080 ![image](https://user-images.githubusercontent.com/43626415/69742345-64229a80-111b-11ea-8303-dc56a5459ff6.png)
claunia commented 2026-01-31 00:07:10 +00:00
Author
Owner
Copy Link

@moswald commented on GitHub (Nov 27, 2019):

I have three identical monitors, and full screen behaves differently on each. On my center (primary) monitor it works fine. On my right monitor, the terminals are only sized about 20px wide (see Aarklendoia's screenshot above), but the app does take up the whole monitor. On my left monitor, the app takes up the whole monitor, but now the terminals are sized larger than the app. I'm using panes, and what happens is my right-most pane is pushed offscreen, while my center and left panes are visible and look somewhat normal.

@moswald commented on GitHub (Nov 27, 2019): I have three identical monitors, and full screen behaves differently on each. On my center (primary) monitor it works fine. On my right monitor, the terminals are only sized about 20px wide (see Aarklendoia's screenshot above), but the app does take up the whole monitor. On my left monitor, the app takes up the whole monitor, but now the terminals are sized larger than the app. I'm using panes, and what happens is my right-most pane is pushed offscreen, while my center and left panes are visible and look somewhat normal.
claunia commented 2026-01-31 00:07:10 +00:00
Author
Owner
Copy Link

@SkyTrix commented on GitHub (Nov 28, 2019):

I have a laptop with one external monitor connected through DVI. When my laptop screen is set as the main display in display settings, full screen works on both screens. However, when I set the external monitor as the main display, fullscreen only works on the external monitor and on my laptop it shows similar results as image from OP. None of the displays are scaled (100%). I hope this helps.

@SkyTrix commented on GitHub (Nov 28, 2019): I have a laptop with one external monitor connected through DVI. When my laptop screen is set as the main display in display settings, full screen works on both screens. However, when I set the external monitor as the main display, fullscreen only works on the external monitor and on my laptop it shows similar results as image from OP. None of the displays are scaled (100%). I hope this helps.
claunia commented 2026-01-31 00:07:11 +00:00
Author
Owner
Copy Link

@LoZeno commented on GitHub (Nov 28, 2019):

My setup:

Windows build number: 10.0.18363
Windows Terminal version (if applicable): 0.7.3291.0

Laptop with 4k display with 150% scaling on an Nvidia GeForce GTX 950M GPU;
Two external monitors: 1080p display with 100% scaling connected through an HP 3005pr USB 3.0 dock.

On the main (integrated) monitor, fullscreen works perfectly; on the two external monitors, fullscreen looks like this:

Annotation 2019-11-28 092009

@LoZeno commented on GitHub (Nov 28, 2019): My setup: Windows build number: 10.0.18363 Windows Terminal version (if applicable): 0.7.3291.0 Laptop with 4k display with 150% scaling on an Nvidia GeForce GTX 950M GPU; Two external monitors: 1080p display with 100% scaling connected through an HP 3005pr USB 3.0 dock. On the main (integrated) monitor, fullscreen works perfectly; on the two external monitors, fullscreen looks like this: ![Annotation 2019-11-28 092009](https://user-images.githubusercontent.com/3267561/69796264-97b9ff00-11c5-11ea-9f0f-566ea10ce0cd.png)
claunia commented 2026-01-31 00:07:11 +00:00
Author
Owner
Copy Link

@hoshinomahiro commented on GitHub (Dec 2, 2019):

Environment:
Windows Insider Preview 19025
Windows Terminal 0.7.3291.0

I have two same screens, and Alt+Enter works well in each screen if I don't move terminal from
the first screen to the second. Once I move it, I will get the this bug!

@hoshinomahiro commented on GitHub (Dec 2, 2019): Environment: Windows Insider Preview 19025 Windows Terminal 0.7.3291.0 I have two same screens, and `Alt+Enter` works well in each screen if I don't move terminal from the first screen to the second. Once I move it, I will get the this bug!
claunia commented 2026-01-31 00:07:11 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 2, 2019):

Assigning myself as followup to test whether the in-PR fix helps this.

@DHowett-MSFT commented on GitHub (Dec 2, 2019): Assigning myself as followup to test whether the in-PR fix helps this.
claunia commented 2026-01-31 00:07:12 +00:00
Author
Owner
Copy Link

@Elevate08 commented on GitHub (Dec 16, 2019):

I'm having this happen on my Laptop, 2 displays connected via Docking Station over USB-C work fine. The 3rd via HDMI from Laptop results in the full screen bug reported here.

@Elevate08 commented on GitHub (Dec 16, 2019): I'm having this happen on my Laptop, 2 displays connected via Docking Station over USB-C work fine. The 3rd via HDMI from Laptop results in the full screen bug reported here.
claunia commented 2026-01-31 00:07:12 +00:00
Author
Owner
Copy Link

@ajaykumarkannan commented on GitHub (Dec 18, 2019):

I'm seeing the same issue. I have two identify monitors but the second one (the one where the failure occurs) is in rotated by 90 degrees.

@ajaykumarkannan commented on GitHub (Dec 18, 2019): I'm seeing the same issue. I have two identify monitors but the second one (the one where the failure occurs) is in rotated by 90 degrees.
claunia commented 2026-01-31 00:07:12 +00:00
Author
Owner
Copy Link

@ramsay-vibes commented on GitHub (Jan 17, 2020):

FWIW, this started working for me after upgrade to WT 0.8 on both machines where I previously experienced the issue.

@ramsay-vibes commented on GitHub (Jan 17, 2020): FWIW, this started working for me after upgrade to WT 0.8 on both machines where I previously experienced the issue.
claunia commented 2026-01-31 00:07:12 +00:00
Author
Owner
Copy Link

@kort3x commented on GitHub (Feb 15, 2020):

works for me now.

Thanks!

@kort3x commented on GitHub (Feb 15, 2020): works for me now. Thanks!
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 Issue-Bug Needs-Tag-Fix Priority-1 Product-Terminal Resolution-No-Repro
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#5189
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?