search

microsoft / PowerToys

Windows system utilities to maximize productivity
MIT License
106.98k stars 6.31k forks source link

FancyZones does no work correctly with Remote Desktop Connection Windows #9040

Open Scimitar21 opened 3 years ago

Scimitar21 commented 3 years ago

ℹ Computer information

📝 Provide detailed reproduction steps (if any)

If you have a virtual desktop opened via Remote Desktop Connection (old preinstalled version not the app from the Microsoft Store) and put it in a fancyzone it stays there. But if you then go on fullscreen in this window and then you minimize it again, it is not minimized correctly into the assigned fancy zone but is larger and outside the zone. If you then go back to fullscreen in this windows and minimize again the window changes its shape completely (almost fullscreen). In previous versions of Fancy Zones you could do this without any problems. This was very useful to have local and remote desktop side by side on one screen.

This error only happens with Remote Desktop Connection-windows, with all other windows / programs it works perfectly fine.

I installed older versions of Powertoys but problem stayed with me. Happened first around November and I always hoped the next update of PowerToys would fix it.

Could not find anybody else having this problem, so i am sorry if you already know about this.

Thanks!

✔️ Expected result

_Window of Remote Desktop Connection that is assigned to a fancyzone stays in the zone after being maximized and then minimized again.

❌ Actual result

_Window jumps out of assigned FancyZone

📷 Screenshots

Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form

enricogior commented 3 years ago

@Scimitar21 which PowerToys version was working?

Scimitar21 commented 3 years ago

As mentioned above: I installed various older versions of Powertoys but problem stayed with me. Happened first around November. But i now figured that in Windows something must have generally changed in an update around November regarding the window adjustment of the RDP-window, as the RDP-window shows this strange behaviour also when i do not use powertoys. Thus, I don't know if it is fixable by Fancy Zones or if this is more a Windows 10 issue.

mcdonamw commented 3 years ago

I have a similar issue. I RDP to a desktop running FancyZones from my laptop using mRemoteNG as a max-sized window (not fullscreen). Whenever my systems auto-lock due to inactivity, after I log in again all my windows are rearranged and are no longer tied to the fancyzones.

This even occurs if I simply resize my mRemoteNG window (often accidentally) and return it back to the original size. Each time this happens RDP goes through a "reconnect" process to resize the desktop and all my windows are thrown out of whack. Would be great if something could be done about this to lock windows to a specific zone at specific resolutions.

DHobart commented 3 years ago

As mentioned above: I installed various older versions of Powertoys but problem stayed with me. Happened first around November. But i now figured that in Windows something must have generally changed in an update around November regarding the window adjustment of the RDP-window, as the RDP-window shows this strange behaviour also when i do not use powertoys. Thus, I don't know if it is fixable by Fancy Zones or if this is more a Windows 10 issue.

I actually installed PowerToys specifically for fancy zones to wrangle RDP sessions that were randomly resizing themselves after maximizing and restoring. Turns out they cannot be contained.

Just a hunch that this is related to this issue: [EDIT 10/05/2021: This link no longer works as they have apparently deleted their user voice forum. I'll leave it here as reference in case they restore the data to some new platform (maybe windows integrated feedback)] https://remotedesktop.uservoice.com/forums/266795-remote-desktop-services/suggestions/41740267-rdp-window-growing-toggling-between-fullscreen-an

If that is the case it would be nice to get some more support behind that fix request. I literally drag multiple RDP sessions back into their zone 10+ times a day to keep them organized.

yuyoyuppe commented 3 years ago

Could be possibly solved by https://github.com/microsoft/PowerToys/pull/11776

JayValkyr commented 3 years ago

Same issue here. I have PowerToys both on, my home workstation and my remote work desktop. Using RDP in full screen mode. Fancy zones on the remote desktop work perfectly until the connection goes down. Whenever I need to initiate a new connection, all the windows are all over the place and need to be assigned to their zones. It's not a huge issue, but somewhat time consuming. As I have multiple windows open on the remote desktop and Ultra Wide screen.

franky920920 commented 2 years ago

@Scimitar21, @JayValkyr, @mcdonamw Cloud you check if this is still an issue on the latest version (v0.47) of PowerToys? This cloud be resolved by #11776.

DHobart commented 2 years ago

@Scimitar21, @JayValkyr, @mcdonamw Cloud you check if this is still an issue on the latest version (v0.47) of PowerToys? This cloud be resolved by #11776.

I just tested with the latest version (v0.47.0) and the windows still seem to pop out of their zones and gradually increase in size as you subsequently maximize and restore down.

JayValkyr commented 2 years ago

@Scimitar21, @JayValkyr, @mcdonamw Cloud you check if this is still an issue on the latest version (v0.47) of PowerToys? This cloud be resolved by #11776.

I think it was better in v0,45. The windows were aligning back to their "previous" zones when reconnecting with RDP. But since v0.47 it seems the grid layout is always defaulted to Priority Grid. The windows do align to that, but you need to switch the layout every single time (edit: seems to be #13664).

franky920920 commented 2 years ago

@JayValkyr Yes, that is a known issue now. Tracking in #13625

ghost commented 2 years ago

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.

Ayanmullick commented 2 years ago

https://github.com/microsoft/PowerToys/issues/13625#issuecomment-942988941

@JayValkyr , The RDP full screen issue isn't yet resolved for me even with the latest version. While maximizing an RDP window it still goes outside its zone and takes the whole screen.

JayValkyr commented 2 years ago

#13625 (comment)

@JayValkyr , The RDP full screen issue isn't yet resolved for me even with the latest version. While maximizing an RDP window it still goes outside its zone and takes the whole screen.

That's a different issue. I have the same if running RDP inside a zone. But this particular issue, which was fixed in .1 was related to zones (layout) reverting back to Priority Grid when reconnecting to a workstation running PowerToys.

Ayanmullick commented 2 years ago

#13625 (comment)

@JayValkyr , The RDP full screen issue isn't yet resolved for me even with the latest version. While maximizing an RDP window it still goes outside its zone and takes the whole screen.

That's a different issue. I have the same if running RDP inside a zone. But this particular issue, which was fixed in .1 was related to zones (layout) reverting back to Priority Grid when reconnecting to a workstation running PowerToys.

Ok, so this issue isn't fixed yet right?

image

JayValkyr commented 2 years ago

#13625 (comment)

@JayValkyr , The RDP full screen issue isn't yet resolved for me even with the latest version. While maximizing an RDP window it still goes outside its zone and takes the whole screen.

That's a different issue. I have the same if running RDP inside a zone. But this particular issue, which was fixed in .1 was related to zones (layout) reverting back to Priority Grid when reconnecting to a workstation running PowerToys.

Ok, so this issue isn't fixed yet right?

image

Yeah, seems i'm mixing it up. But yes, that issue isn't fixed.

ghost commented 2 years ago

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.

Ayanmullick commented 2 years ago

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.

@JayValkyr, is the bot configured to close this without resolution?

ghost commented 2 years ago

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.

bclrk commented 2 years ago

This is still a problem. Adding a comment so that hopefully it gets some attention

viceice commented 2 years ago

Pretty annoying to see this, just got a DQHD display, so i need to split the panel. Found the nice powertoys and need to see that RDP app are not working with FancyZones. 😕

viceice commented 2 years ago

Please vote up issue (below issue description) with 👍 to hopefully get higher prio.

catbears commented 1 year ago

Similar problem here: on the main machine power toys is running and switching Esc and Caps lock keys for me.

On the remote machine both things are happening (Vim switches modes and caps lock is turned on at the same time). So if I work remote, I have to turn power toys off, then turn them on again when I work local.

Simon-Sandrew commented 1 year ago

still an issue^

guntern commented 1 month ago

Could it be, that there are two things discussed in this issue, or do I have a misunderstanding? The two topics I read:

  1. a problem with the RDP window itself with the FancyZones on the local machine.
  2. a problem with windows inside a RDP session with the FancyZones on the remote machine. (e.g. described in #22396 )

My reading is, that topic 1 is the original idea of this issue. And thus, #22396 would actually not be a duplicate of this one.