Severe Groupy 2 Bug: Foreground Game Performance Drops from 200+ FPS to 20–30 FPS
I am reporting a severe compatibility issue caused by Groupy 2.
Stardock Forums
Title
Severe Groupy 2 Bug: Foreground Game Performance Drops from 200+ FPS to 20–30 FPS
Post
I am reporting a severe compatibility issue caused by Groupy 2.
When the Stardock Groupy service is running, VALORANT drops from more than 200 FPS to approximately 20–30 FPS whenever the game window has foreground focus. At the same time, GPU utilization becomes abnormally low.
The behavior is immediately reversible:
Game window focused: 20–30 FPS, low GPU utilization
Click outside the game window: 200+ FPS, normal GPU utilization
Click back into the game: FPS immediately drops to 20–30 again
The problem occurs consistently in fullscreen, borderless fullscreen, and windowed modes. I also tested resolutions ranging from 1024×768 to 2880×1920, with virtually no change in frame rate. This clearly rules out resolution, graphics settings, or insufficient hardware performance.
I spent an entire day troubleshooting this issue, including:
Graphics drivers
Windows graphics settings
Power and performance modes
Game settings
Hardware utilization
Background services
Other installed software
After isolating the services through a clean boot, I confirmed that disabling only the Stardock Groupy service immediately restores normal foreground performance above 200 FPS.
I then added:
VALORANT-Win64-Shipping.exe
to Groupy’s blocked application list. This also resolved the problem while allowing Groupy to remain enabled.
This confirms that Groupy’s interaction with the game window, foreground focus, or rendering process is directly responsible for the performance loss.
This is not a minor compatibility issue or normal software overhead. Groupy reduced foreground performance by nearly 90%, without any warning or indication that it was interfering with another application. Because Groupy is paid software, this level of interference is unacceptable. I purchased it to improve productivity in applications such as Microsoft Word, not to silently cripple unrelated programs and cause an entire day of unnecessary hardware and driver troubleshooting.
The blocked-application rule is currently a workaround, but it is not a proper fix. Users should not have to discover severe performance degradation first and then manually exclude every affected application.
Please investigate:
1. Why Groupy interferes with foreground rendering and GPU utilization.
2. Whether Groupy continues to hook or monitor applications that should not be grouped.
3. Why full-screen and GPU-accelerated applications are not excluded automatically.
4. Whether blocked applications are completely isolated from all Groupy window and focus handling.
Please reproduce and properly address this issue in a future update, and document the fix clearly in the changelog.
