Bug of Groupy2 in the virtual desktop of Win11 system

Testing System: Win Professional Edition 23h2

Test background: Set the grouping rule of Groupy to group Edge processes together

Bug: In Win11 system, Groupy will group Edge windows from different virtual desktops together. This situation does not occur under the Win10 system.

3,647 views 7 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Need more information.

  1. Windows 11 full version number and OS Build number. Please use Winver.exe.
  2. Windows 10 full version number and OS Build number. Please use Winver.exe.
  3. Screenshot of that Grouping rule that group Edge processes together.

added: I have made a short video in testing your issue. But, unless I misunderstood your issue, the issue do not appear in my system.

Thank you.
Basj,
Stardock Community Assistant.

Reply #2 Top

This is an operation under Win11. When switching Edge browsers, the virtual desktop will also be displayed and switched

The steps are as follows:

1. Create an Edge window under virtual desktop 1;

2. Create a window for Edge on virtual desktop 2;

3. Groupy will merge the Edge windows from the two different virtual desktops above;

When switching between two merged Edge windows, the virtual desktop will also change accordingly.

Reply #3 Top

This is an operation under Win10, and switching to the Edge browser will not cause any changes to the virtual desktop.

Reply #5 Top

I have checked here on Win11 and cannot reproduce it either.

We need full version information on Groupy and Windows 11 please (build number for Win11).

Also what method have you used to explorer windows to open together?  A custom rule, or using the option in the groupy bar menu to always group edge windows together?

Reply #6 Top

Hello, thank you very much for your reply:

It uses custom rules, and the configuration of the rules and system information are already provided on the 4th floor

Reply #7 Top

Please try removing that custom rule and use the method I use on my video. See if the issue still appear if you use that method.

Thank you,

Basj,
Stardock Community Assistant