impossible-to-move white boxes drawn all over taskbar and on desktop, outside of windows terminal #20062

Open
opened 2026-01-31 07:02:14 +00:00 by claunia · 13 comments
Owner

Originally created by @ClaireCJS on GitHub (Jun 10, 2023).

Windows Terminal version

1.16.10261.0

Windows build number

10.0.19045.2965

Other Software

  • running 4 monitors, 3 1080p + 1 VGA

  • verified that the bug still works regardless of whether DisplayFusion window manager is running

Steps to reproduce

Open multiple tabs.

Expected Behavior

Widows Terminal only draws inside of its own windows

Actual Behavior

View it on youtube -> https://youtu.be/UfArtJ9bbB8

  1. Windows Terminal draws a white box at the upper left of my primary monitor that is there at all times

  2. Windows Terminal draws several white rectangles behind the taskbar (not visible when the taskbar is visible). Approximately one per tab.

  3. The white rectangles behind the taskbar can be made to disappear and reappear by minimizing instances of windows terminal (easier to reproduce and view when done on another monitor). I will make a youtube video of this.
    picture

  4. Typically, the white square-ish rectangle on the upper left of the primary monitor is drawn if the console windows are not minimized, and white wide rectangles in the taskbar are drawn if the console windows are minimized.

[![video]
(https://img.youtube.com/vi/UfArtJ9bbB8/maxresdefault.jpg)]
(https://www.youtube.com/watch?v=UfArtJ9bbB8)

Originally created by @ClaireCJS on GitHub (Jun 10, 2023). ### Windows Terminal version 1.16.10261.0 ### Windows build number 10.0.19045.2965 ### Other Software * running 4 monitors, 3 1080p + 1 VGA * verified that the bug still works regardless of whether DisplayFusion window manager is running ### Steps to reproduce Open multiple tabs. ### Expected Behavior Widows Terminal only draws inside of its own windows ### Actual Behavior View it on youtube -> https://youtu.be/UfArtJ9bbB8 1) Windows Terminal draws a white box at the upper left of my primary monitor that is there at all times 2) Windows Terminal draws several white rectangles behind the taskbar (not visible when the taskbar is visible). Approximately one per tab. 3) The white rectangles behind the taskbar can be made to disappear and reappear by minimizing instances of windows terminal (easier to reproduce and view when done on another monitor). I will make a youtube video of this. ![picture](https://github.com/microsoft/terminal/assets/789591/8687699b-8796-4964-aebd-70d2ec159597) 4) Typically, the white square-ish rectangle on the upper left of the primary monitor is drawn if the console windows **are not** minimized, and white wide rectangles in the taskbar are drawn if the console windows **are** minimized. [![video] (https://img.youtube.com/vi/UfArtJ9bbB8/maxresdefault.jpg)] (https://www.youtube.com/watch?v=UfArtJ9bbB8)
claunia added the Issue-BugProduct-TerminalArea-Windowing labels 2026-01-31 07:02:14 +00:00
Author
Owner

@lhecker commented on GitHub (Jun 12, 2023):

I wonder if this is the hidden DesktopWindowXamlSource window. And it does look somewhat similar to #15219. Have you ever used tools like Process Explorer or System Informer before? Would you be able to tell us what Window Class that is?

@lhecker commented on GitHub (Jun 12, 2023): I wonder if this is the hidden DesktopWindowXamlSource window. And it does look somewhat similar to #15219. Have you ever used tools like Process Explorer or System Informer before? Would you be able to tell us what Window Class that is?
Author
Owner

@ClaireCJS commented on GitHub (Jun 12, 2023):

I wonder if this is the hidden DesktopWindowXamlSource window. And it does look somewhat similar to #15219. Have you ever used tools like Process Explorer or System Informer before? Would you be able to tell us what Window Class that is?

I use process explorer regularly, but i don't think process explorer gives a tool to identify window classes.

Okay. Just got back from figuring out how to identify window classes. Spyxx.exe sure doesn't seem available in my visual studio installation, but i found something called WinSpy++ that has similar functionality.

@ClaireCJS commented on GitHub (Jun 12, 2023): > I wonder if this is the hidden DesktopWindowXamlSource window. And it does look somewhat similar to #15219. Have you ever used tools like Process Explorer or System Informer before? Would you be able to tell us what Window Class that is? I use process explorer regularly, but i don't think process explorer gives a tool to identify window classes. Okay. Just got back from figuring out how to identify window classes. Spyxx.exe sure doesn't seem available in *my* visual studio installation, but i found something called WinSpy++ that has similar functionality.
Author
Owner

@ClaireCJS commented on GitHub (Jun 12, 2023):

And the result is.... WinSpy++ cannot pick up the window class even when I set 'hidden windows'. It just identifies as explorer.exe

And maybe that's true. Maybe explorer is doing this somehow, but it's absolutely because of and in response to Windows Terminal

Here's the info from the upper-left square:
image
image
image
image
image
image

@ClaireCJS commented on GitHub (Jun 12, 2023): And the result is.... WinSpy++ cannot pick up the window class even when I set 'hidden windows'. It just identifies as explorer.exe And maybe that's true. Maybe explorer is doing this somehow, but it's absolutely because of and in response to Windows Terminal Here's the info from the upper-left square: ![image](https://github.com/microsoft/terminal/assets/789591/57b845ed-7e23-4e6b-a14a-99790742ace6) ![image](https://github.com/microsoft/terminal/assets/789591/18619626-fef3-473b-86a5-57c5cd702911) ![image](https://github.com/microsoft/terminal/assets/789591/ca183eb2-ae80-45ed-bdec-1130d8848410) ![image](https://github.com/microsoft/terminal/assets/789591/f71b5f04-3afe-4a8b-9026-174f7241d6cc) ![image](https://github.com/microsoft/terminal/assets/789591/f5043ae2-f6ab-4d3f-b57b-10f3fe6a5121) ![image](https://github.com/microsoft/terminal/assets/789591/79c30bcb-248d-4d38-8cf0-a7c2b1ebd24c)
Author
Owner

@ClaireCJS commented on GitHub (Jun 12, 2023):

I really would love this to be fixed. I use command line almost exclusively for everything since the 1980s, and I rely on transparency becasue I'm often typing about something that's behind my window. But I have to turn transparency completely off to not have these rectangles everywhere.

@ClaireCJS commented on GitHub (Jun 12, 2023): I really would love this to be fixed. I use command line almost exclusively for everything since the 1980s, and I rely on transparency becasue I'm often typing about something that's behind my window. But I have to turn transparency completely off to not have these rectangles everywhere.
Author
Owner

@DHowett commented on GitHub (Jun 12, 2023):

Are you using some software like "Mica for Everyone"? As well, you definitely seem to have at least one thing running that manipulates all windows on the system (judging by the five additional caption buttons in all of your screenshots 😉).

We're not necessarily incompatible with those things, but they have caused us windowing headaches in the past.

@DHowett commented on GitHub (Jun 12, 2023): Are you using some software like "Mica for Everyone"? As well, you definitely seem to have at least one thing running that manipulates all windows on the system (judging by the five additional caption buttons in all of your screenshots 😉). We're not necessarily incompatible with those things, but they have caused us windowing headaches in the past.
Author
Owner

@ClaireCJS commented on GitHub (Jun 12, 2023):

Are you using some software like "Mica for Everyone"? As well, you definitely seem to have at least one thing running that manipulates all windows on the system (judging by the five additional caption buttons in all of your screenshots 😉).

We're not necessarily incompatible with those things, but they have caused us windowing headaches in the past.

I guess you missed the part in the initial report where I already mentioned that this behavior happens even when DisplayFusion is not running.

That's literally the first thing I checked, but yea, DisplayFusion has never caused anything like this in all my years of using it anyway. No idea what "mica for everyone" is.

@ClaireCJS commented on GitHub (Jun 12, 2023): > Are you using some software like "Mica for Everyone"? As well, you definitely seem to have at least one thing running that manipulates all windows on the system (judging by the five additional caption buttons in all of your screenshots 😉). > > We're not necessarily incompatible with those things, but they have caused us windowing headaches in the past. I guess you missed the part in the initial report where I already mentioned that this behavior happens even when DisplayFusion is not running. That's literally the first thing I checked, but yea, DisplayFusion has never caused anything like this in all my years of using it anyway. No idea what "mica for everyone" is.
Author
Owner

@DHowett commented on GitHub (Jun 12, 2023):

I guess you missed the part in the initial report where I already mentioned that this behavior happens even when DisplayFusion is not running.

I sure did!

Interesting. The only other time we've seen reports of this was when M4E was installed 😄

@DHowett commented on GitHub (Jun 12, 2023): > I guess you missed the part in the initial report where I already mentioned that this behavior happens even when DisplayFusion is not running. I sure did! Interesting. The only other time we've seen reports of this was when M4E was installed :smile:
Author
Owner

@ClaireCJS commented on GitHub (Jun 12, 2023):

Well, here's all the process names I'm running. I don't really want to just go willy nilly killing things and seeing what happens, but if there are any suspects that one may think could be the cause I'd certainly be willing to kill the process and see if the behavior continues.

ps|awk "{print $2}"|sort|uniq [i'm running windows, i swear :)]

AdjustService
ApCent
ApplicationFrameHost
armsvc
audiodg
ChatGPT
chrome
ChsIME
com.docker
com.docker.backend
com.docker.build
com.docker.dev-envs
com.docker.extensions
com.docker.proxy
CompPkgSrv
conhost
Cortana
crashpad_handler
csrss
ctfmon
dasHost
DbxSvc
DisplayFusion
DisplayFusionHookApp32
DisplayFusionHookApp64
DisplayFusionService
dllhost
Docker
docker
Dropbox
DropboxUpdate
dwm
editplus
ensserver
Everything
explorer
FileWatcher
fontdrvhost
GCloud
GoogleCrashHandler
GoogleCrashHandler64
GoogleDriveFS
IPROSetMonitor
javaw
jusched
laclient
Last.fm
LogiBolt
LogiOptions
LogiOptionsMgr
LogiOverlay
logi_crashpad_handler
LsaIso
lsass
Memory
Microsoft.Photos
MiniLyrics
msdtc
msedge
msedgewebview2
MsMpEng
msrdc
NisSrv
nvcontainer
NVDisplay.Container
NVIDIA
of
OfficeClickToRun
ONENOTEM
OpenConsole
opera
opera_crashreporter
PhoneExperienceHost
procexp
procexp64
Registry
RGBFusion
RPMDaemon
RtkAudUService64
rundll32
RuntimeBroker
SearchApp
SearchIndexer
Secure
SecurityHealthService
SecurityHealthSystray
services
SgrmBroker
ShellExperienceHost
sihost
smss
spoolsv
sqlwriter
StartMenuExperienceHost
svchost
System
SystemSettings
taskhostw
tcc
TeamViewer_Service
TextInputHost
UserOOBEBroker
uTorrent
utorrentie
Video.UI
vmcompute
vmmem
vmms
vmwp
vpnkit-bridge
winamp
WindowsTerminal
wininit
winlogon
wlanext
WmiPrvSE
wsl
wslhost
wslrelay
wslservice
WUDFHost
WzPreloader
XMouseButtonControl
System

@ClaireCJS commented on GitHub (Jun 12, 2023): Well, here's all the process names I'm running. I don't really want to just go willy nilly killing things and seeing what happens, but if there are any suspects that one may think could be the cause I'd certainly be willing to kill the process and see if the behavior continues. ``` ps|awk "{print $2}"|sort|uniq [i'm running windows, i swear :)] AdjustService ApCent ApplicationFrameHost armsvc audiodg ChatGPT chrome ChsIME com.docker com.docker.backend com.docker.build com.docker.dev-envs com.docker.extensions com.docker.proxy CompPkgSrv conhost Cortana crashpad_handler csrss ctfmon dasHost DbxSvc DisplayFusion DisplayFusionHookApp32 DisplayFusionHookApp64 DisplayFusionService dllhost Docker docker Dropbox DropboxUpdate dwm editplus ensserver Everything explorer FileWatcher fontdrvhost GCloud GoogleCrashHandler GoogleCrashHandler64 GoogleDriveFS IPROSetMonitor javaw jusched laclient Last.fm LogiBolt LogiOptions LogiOptionsMgr LogiOverlay logi_crashpad_handler LsaIso lsass Memory Microsoft.Photos MiniLyrics msdtc msedge msedgewebview2 MsMpEng msrdc NisSrv nvcontainer NVDisplay.Container NVIDIA of OfficeClickToRun ONENOTEM OpenConsole opera opera_crashreporter PhoneExperienceHost procexp procexp64 Registry RGBFusion RPMDaemon RtkAudUService64 rundll32 RuntimeBroker SearchApp SearchIndexer Secure SecurityHealthService SecurityHealthSystray services SgrmBroker ShellExperienceHost sihost smss spoolsv sqlwriter StartMenuExperienceHost svchost System SystemSettings taskhostw tcc TeamViewer_Service TextInputHost UserOOBEBroker uTorrent utorrentie Video.UI vmcompute vmmem vmms vmwp vpnkit-bridge winamp WindowsTerminal wininit winlogon wlanext WmiPrvSE wsl wslhost wslrelay wslservice WUDFHost WzPreloader XMouseButtonControl System ```
Author
Owner

@ClaireCJS commented on GitHub (Jun 12, 2023):

Interesting. The only other time we've seen reports of this was when M4E was installed 😄

Oh that's very interesting. I can see why you suggested that, then!

So this has only been seen before with a program causing it.

Now I'm eyeing all my program suspiciously.
But they never did this when I used command lines in other containers. (daily, for 35 yrs)

@ClaireCJS commented on GitHub (Jun 12, 2023): > Interesting. The only other time we've seen reports of this was when M4E was installed 😄 Oh that's very interesting. I can see why you suggested that, then! So this has only been seen before with a program causing it. Now I'm eyeing all my program suspiciously. But they never did this when I used command lines in other containers. (daily, for 35 yrs)
Author
Owner

@ClaireCJS commented on GitHub (Jun 16, 2023):

MAJOR UPDATE
I've isolated the behavior further.

These boxes are drawn if I start windows terminal directly.

These boxes are not drawn if I start windows terminal indirectly.

Clarification of terminology:

"Directly" = Start menu -> open windows terminal.

Windows terminal has "Default Terminal Application" set to "Windows Terminal" and "When Terminal Starts" is set to "Open a tab with the default profile", and my default profile is TCC, my preferred command line.

"Indirectly" = I start TCC.exe, which then opens up in windows terminal thanks to me setting it as the default terminal application.

Oh wow, there's a cute little shield on the upper left? I've never seen that until today because it's always been drawn over with a white box:
image


Suffice to say - I feel like Windows Terminal should behave the same when started via the start menu, than when indirectly started as a side-effect of being the default terminal application.

But at the same time - It doesn't do this with CMD.EXE, just with TCC.EXE, so I do wonder what is special about TCC that breaks Windows Terminal, but only when Windows Terminal is launched directly, not when launched indirectly.

@ClaireCJS commented on GitHub (Jun 16, 2023): **MAJOR UPDATE** I've isolated the behavior further. These boxes are drawn if I start windows terminal directly. These boxes are not drawn if I start windows terminal indirectly. Clarification of terminology: "Directly" = Start menu -> open windows terminal. Windows terminal has "Default Terminal Application" set to "Windows Terminal" and "When Terminal Starts" is set to "Open a tab with the default profile", and my default profile is TCC, my preferred command line. "Indirectly" = I start TCC.exe, which then opens up in windows terminal thanks to me setting it as the default terminal application. Oh wow, there's a cute little shield on the upper left? I've never seen that until today because it's always been drawn over with a white box: ![image](https://github.com/microsoft/terminal/assets/789591/0bcddc9e-fbd3-410a-b2dd-41c887bd458a) ------------------ Suffice to say - I feel like Windows Terminal should behave the same when started via the start menu, than when indirectly started as a side-effect of being the default terminal application. But at the same time - It doesn't do this with CMD.EXE, just with TCC.EXE, so I do wonder what is special about TCC that breaks Windows Terminal, but only when Windows Terminal is launched directly, not when launched indirectly.
Author
Owner

@ClaireCJS commented on GitHub (Jun 16, 2023):

Update:

Actually, the white square in the upper right is still there, when launching indirectly (i.e. not starting windows terminal first).

But the rectangles on the taskbar are only there when launching directly.

@ClaireCJS commented on GitHub (Jun 16, 2023): Update: Actually, the white square in the upper right is still there, when launching indirectly (i.e. not starting windows terminal first). But the rectangles on the taskbar are only there when launching directly.
Author
Owner

@zadjii-msft commented on GitHub (Sep 20, 2023):

Moving comments from #15786. The issue in this thread is probably, most certainly, unique to TCC in the Terminal. (a reminder to scroll the quoted text, cause gifs get cut off)

what the fuck

minimized-phwnd

okay, so there's a good chance the PseudoConsoleWindow is moving there when it's minimized. why tho


Here's an idea though: if you go into WinSpy++, then hit More >>, you should be able to find a cmd.exe (or tcc.exe or whatever the shell is), with a pseudoconsolewindow underneath it (after double-clicking). Hit the Autoupdate button, and see how that window reacts to the Terminal restoring and being minimized. The Flash button is also helpful for ID'ing where on the screen a window should be (it will flash the bounds of a window even if the window isn't visible).
Once you've got a lock on the right pseudoconsolewindow, share those screenshots?

Well, it's kind of hard to share the screen of the flash function flashing, but basically...

image

  1. Flashing the entire TCC flashes a square with the size and placement that is approximately the default size and placement TCC comes up with, when it starts on my screen. And it always starts on the same monitor, even if my taskbar shortcuts are on different monitors. TCC before Windows Terminal when launched directly did not behave that way.

I'm starting to think Windows Terminal and multiple monitors and moving TCC to a different monitor somehow is causing some sort of disconnect where TCC might have leftover aspects of its windows in the original monitor from where it was moved from (and originally opened into) (i.e. primary monitor).

  1. Flashing 002416B0 TCC.EXE "TCC:c658" captured the upper-left square and about 3 more square's width to the right. Small rectangle.
  2. Flashing 07442Dc2 PsuedoConsoleWindow captured the upper-left square and a few pixels to the left of it.
  3. Flashing Default IME - i see nothing

I'm staring to think this is specific to how Windows Terminal interacts with TCC when TCC is moved to another monitor. I have thought it behaved strange, but not quite been able to put my finger on it.


Oh, it's definitely TCC+Windows Terminal specific. I think it was phrased that way on it's own issue but then my issue got merged/mentioned into this issue since they're the same thing with apparently two different causes.

But yea, to answer your question, it doesn't happen with powershell tabs

but it also doesn't happen when TCC is run without windows terminal

I suspect TCC is doing something weird and nonstandard and Windows Terminal isn't detecting something it meant to detect correctly. It's kind of been the broad pattern.

@zadjii-msft commented on GitHub (Sep 20, 2023): Moving comments from #15786. The issue in this thread is probably, most certainly, unique to TCC in the Terminal. (a reminder to scroll the quoted text, cause gifs get cut off) > what the fuck > > ![minimized-phwnd](https://user-images.githubusercontent.com/18356694/269365231-dfbf8193-ad60-4567-a387-97ccbdf43327.gif) > > okay, so there's a good chance the `PseudoConsoleWindow` is moving there when it's minimized. _why tho_ --------------- > > Here's an idea though: if you go into WinSpy++, then hit `More >>`, you should be able to find a `cmd.exe` (or `tcc.exe` or whatever the shell is), with a pseudoconsolewindow underneath it (after double-clicking). Hit the Autoupdate button, and see how _that_ window reacts to the Terminal restoring and being minimized. The Flash button is also helpful for ID'ing where on the screen a window should be (it will flash the bounds of a window even if the window isn't visible). > > Once you've got a lock on the right pseudoconsolewindow, share those screenshots? > > Well, it's kind of hard to share the screen of the flash function flashing, but basically... > > ![image](https://user-images.githubusercontent.com/789591/269397720-7b2dabd8-3878-4da3-a3c8-5d13a4414188.png) > > 1. Flashing the entire TCC flashes a square with the size and placement that is approximately the default size and placement TCC comes up with, when it starts on my screen. And it always starts on the same monitor, even if my taskbar shortcuts are on different monitors. TCC before Windows Terminal when launched directly did not behave that way. > > I'm starting to think Windows Terminal and multiple monitors and moving TCC to a different monitor somehow is causing some sort of disconnect where TCC might have leftover aspects of its windows in the original monitor from where it was moved from (and originally opened into) (i.e. primary monitor). > > 2. Flashing 002416B0 TCC.EXE "TCC:c658" captured the upper-left square and about 3 more square's width to the right. Small rectangle. > 3. Flashing 07442Dc2 PsuedoConsoleWindow captured the upper-left square and a few pixels to the left of it. > 4. Flashing Default IME - i see nothing > > I'm staring to think this is specific to how Windows Terminal interacts with TCC when TCC is moved to another monitor. I have thought it behaved strange, but not quite been able to put my finger on it. ------------ > Oh, it's definitely TCC+Windows Terminal specific. I think it was phrased that way on it's own issue but then my issue got merged/mentioned into this issue since they're the same thing with apparently two different causes. > > But yea, to answer your question, it doesn't happen with powershell tabs > > but it also doesn't happen when TCC is run without windows terminal > > I suspect TCC is doing something weird and nonstandard and Windows Terminal isn't detecting something it meant to detect correctly. It's kind of been the broad pattern.
Author
Owner

@zadjii-msft commented on GitHub (Sep 20, 2023):

Oh well this might explain it:

[3:05 PM] Mike
maybe related: why might the OS not yeet the window to -32000,-32000 when it gets minimized? That's seemingly only happening to the PseudoConsoleWindow's, with or without that change. And that's sus to me

[3:21 PM] Evan
Oooh, it's because it's owned. Owned windows by default would be 'parked' in bottom right corner instead of -32000.

I believe you could have the fake window handle wm_getminmaxinfo and set ptMin to -32000.

That might at least help, by moving the conpty hwnd into space where it belongs.


edit:
Uh,

WM_GETMINMAXINFO doesn't seem to ever fire for our owned, popup window
Doing a SetWindowPlacement with flags = WPF_SETMINPOSITION and .x and .y set to -32000 in WM_CREATE didn't seem to do the right thing either, and instead got sent to (-1,-1) - (159,27) - 160x28

we'll need something else it might seem.

@zadjii-msft commented on GitHub (Sep 20, 2023): Oh well this might explain it: > [3:05 PM] Mike > maybe related: why might the OS not yeet the window to -32000,-32000 when it gets minimized? That's seemingly only happening to the PseudoConsoleWindow's, with or without that change. And that's sus to me > [3:21 PM] Evan > Oooh, it's because it's owned. Owned windows by default would be 'parked' in bottom right corner instead of -32000. > > I believe you could have the fake window handle wm_getminmaxinfo and set ptMin to -32000. That might at least help, by moving the conpty hwnd into _space_ where it belongs. ---- edit: Uh, `WM_GETMINMAXINFO` doesn't seem to ever fire for our owned, popup window Doing a `SetWindowPlacement` with `flags = WPF_SETMINPOSITION` and `.x` and `.y` set to -`32000` in `WM_CREATE` didn't seem to do the right thing either, and instead got sent to `(-1,-1) - (159,27) - 160x28` we'll need something else it might seem.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20062