Title bar buttons aren't working (PowerToys)

[Ronkiro]

Environment

Windows build number: 10.0.18362.295
Windows Terminal version (if applicable): 0.6.2951.0

Any other software?

Steps to reproduce

Open terminal and click on close/minimize/maximize/edit environment.

Expected behavior

It should work

Actual behavior

It shows weird cursor and doesn't work.

Printscreen

[zadjii-msft]

This is super weird. I bet it has to do with our WM_NCHITTEST code in NonClientIslandWindow. If I had to go out on a limb, it's almost as if the entire titlebar area is being treated as HTTOP, which would cause the area to be treated as the "top drag region".

Unfortunately, I can't really repro this myself :/

@Ronkiro if you click and drag while the mouse is like that, does it resize the window? If so, that would probably confirm my suspicion. Also, does it act like that for the entire height of the titlebar area?

---

P.S.

protip: you can actually just paste images directly into the input box on github, and it'll automatically uplod them to github and embed them inline. It's pretty neat

[Ronkiro]

@zadjii-msft
I tried adding the image but it was failing... It was creating github's link but it was a wrong link lol i think i was missing something.

Back to the terminal, holding click doesn't resizes window. But, when moving to the non-button area of the title bar (The middle area) the cursor goes to default one again.

Still in the default cursor, i can't click close/minimize/etc. ALT+F4 works though.
Testing a bit, i also noticed that i cannot do any mouse actions in terminal (Like marking a text, right clicking to paste/open menu, etc). But shortcuts like CTRL+V works. The only exceptions are double clicking the middle area (it maximizes the screen properly) and resizing the window.

Also, the image the cursor sticks with is the last one i hovered. I mean, if i move to the "Resize left" area and then move to title bar, the mouse will be with the "Resize left" icon.

[JohnFNovak]

I also had this issue (Microsoft Windows [Version 10.0.18362.418]), but restarting the machine fixed it.

[DHowett-MSFT]

@Ronkiro Does restarting fix it for you? @JohnFNovak indicates that it may. 😄

[Ronkiro]

Nope @DHowett-MSFT. I mean, i already had restarted many times until i really create the issue here, but it didn't help.

Also noting that it's an enterprise W10, not sure if this can help anyhow.

[LuanVSO]

this happens to me randomly too, exiting powertoys process seems to fix it.
in a related problem trying to drag the wt window with shift pressed freeze the window in place
but it start moving when you release the shift key

[Ronkiro]

Seems related to PowerToys for me too, exiting also fixed.

[zadjii-msft]

Excellent to hear. Summoning @crutkas if he's got any ideas on the matter

[crutkas]

What version of PowerToys are you on

[crutkas]

I'm trying to repo this but can't. I'm on PowerToys 0.14.1 and here are my steps to reproduce. You may need to share your FancyZone settings.

We do stuff with shift to make you aware we're going to snap to your zones.

My system info currently:

• PowerToys 0.14.1
• Terminal: 0.7.3451.0
• Win10: 18363.535, Version 1909

1. Launch power toys.
2. Launch Terminal.
3. click minimize, maximize (they all work)
4. added PowerShell tab
5. Added Cmd Tab
6. Remove new PowerShell tab with X
7. Hold Shift and go to FancyZone zone

[Ronkiro]

Win10: Ver 1903, build 18362.295 (Enterprise)
PowerToys: 0.11.0

I also have "Use new zone editting experience" enabled, not sure if this has any relationships.

BTW, i can't reproduce the problem again now. Would be good if anyone that also had the problem could keep helping with info. But i didn't change any of the versions, just did the workaround fix.

[LuanVSO]

powertoys 0.14.1
win10 insider slow ring : 2004, build 19041.1
wt:0.7.3451.0

the bug happened when i was collecting the version of wt,
it also seen to affect the power toys settings
i connected a display and moving wt window to it made the buttons work
though only on the 2nd display
used the step recorder to capture it:
powertoys bug.zip
powertoys bug 2.zip

[enricogior]

@DHowett
I meant pure Win32, no XAML, the only thing I've found so far that can be a potential entry point for the problem is described in
microsoft/PowerToys#5944 (comment)
I suggested to build a debug version of Terminal to monitor that class name to verify if the Steps recorder is correctly identifying the UI element as child of the Terminal process, it would confirm that there is an injection of the class object from outside.

[aharpervc]

This has now happened to me as well, but actually a hybrid of this and #4448 where I can't type nor can I click on title bar buttons or scroll or use any UI element (I can resize the window, though). This has happened more than once.

• I am using PowerToys v0.20.1
• I am not using the shortcut guide
• resizing and snapping the windows (win+arrow) works
• clicking into the window (titlebar, tab bar, min/max/exit) doesn't work
• typing into the window has no effect
• the shell is powershell (and then running wsl inside that), and the process tree is still alive
• I am running 150% DPI scaling, but I only have 1 monitor plugged in
• I started the app yesterday, and the computer has slept/woken since then. I only noticed the problem after waking the computer
• I started a second instance of the terminal app, and it works fine

[enricogior]

@aharpervc

I am not using the shortcut guide

Is Shortcut Guide turned off in the PowerToys settings or simply you are not invoking it?

[aharpervc]

It's turned off:

[enricogior]

@aharpervc
thank you.

That seems to exclude the possibility that the bug is caused directly by Shortcut Guide, since it's not running and therefore it can't be what is injecting the PToyD2DPopup class in the Terminal process.

[crutkas]

@aharpervc what graphic chipset are you running? NVidia?

[aharpervc]

@aharpervc what graphic chipset are you running? NVidia?

AMD Radeon Pro 560

[jimmyff]

I was also experiencing this issue (Cannot interact with Power Shell window bar other than drag it around). Restarting windows & killing the 'Windows Terminal' app in the task manager do not fix it for me.

Power toys version 0.19.1
Windows 10 Pro 19042.541

I just opened Power Toys to check if my shortcut guide was enabled as suggested above but I couldn't interact with that UI either. I then killed the 'Powertoys runner' process using task manager and it fixed both issues for now at least.

[chr1573r]

Good thing I found this thread on Google!
After updating to Windows 10 feature release 2004 last week, I could not click anywhere on the titlebar of the Windows Terminal App (neither tab controls or minimize/maximize/close).
Was not possible to select text in the terminal window either.
Problem disappeared immediately when closing Power Toys in the tray 👍

[girlandhercode]

In my case, this happens to both Windows Terminal (Version: 1.4.3243.0) and Windows Terminal Preview (Version: 1.5.3242.0) whether or not PowerToys (Version: 0.25.0) is running. My Windows 10 version is 1909 and OS Build is 18363.1198.

This is probably useless information, but using WindowSpy (Autohotkey inspection component), I've noticed there is a difference between the class name/instance number (ClassNN in WindowSpy) of the controls involved.

When I can interact with the mouse hovering over the New Tab button or any of the minimize/maximize etc buttons:

ClassNN:  Windows.UI.Composition.DesktopWindowContentBridge1
Text:	  DesktopWindowXamlSource

---

When I can not interact with the mouse on these controls this changes to:

ClassNN: Windows.UI.Core.CoreWindow1
Text:        DesktopWindowXamlSource

[zadjii-msft]

For future readers: there's plenty more investigation that's been done in #6120. My last working theory was that toggling the "Shortcut Guide" off should fix this.

There were also the related:

• [KBM] long pressing the Win key while remapping a key results in no mouse input PowerToys#4360
• Shortcut Guide not appearing PowerToys#3833
• Shortcut not working PowerToys#3250
• Sometimes ShortcutGuide doesn't work suddenly. PowerToys#3090

[enricogior]

@zadjii-msft
the main issue in the PowerToys repo to track this weird bug is microsoft/PowerToys#5944

[zadjii-msft]

Is anyone still seeing this? There's been a decent number of PowerToys and Terminal releases since this was filed, but there hasn't been any reports in quite some time. Seems like this was potentially fixed.

[ghost]

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.

[mcdonamw]

I just found this as I just experienced this issue with Terminal, though some of the reported symptoms above are not existent on mine. Note: This is the first time I've ever seen this issue.

I CANNOT click on anything in the Terminal window except the minimize, maximize, and close buttons. No tab or titlebar.
I CANNOT highlight/paste using left click anywhere in the window (Powershell 7 is the only window open, as is default).
I CAN left click/drag the terminal window around the screen.
I CAN maximize/restore window via double click on titlebar.
I CAN right click the titlebar and context menu comes up and is functional.
PowerToys Settings app is also affected in the same way. PowerToys v0.58.0.

[zadjii-msft]

note to future self: mcdonamw figured their issue out over in microsoft/PowerToys#5944 just by seemingly rebooting PowerToys

[b-hayes]

Im having the same issues as @mcdonamw and I do not use power toys. Can only type comamnds and close the terminal nothing elseworks.

[DHowett]

@b-hayes hmm, do you happen to have more than one monitor? Can you remember whether Terminal was on the primary display or not? If not, was it to the left?

[b-hayes]

I was using RDP which changes the display to match the remote client. I RDP in from two other machines so the display can change 3 times in a single day. I rebooted the system and the problem hasn't come back again so 🤷🏼‍♂️