Stardock Forums
With the Groupy 1.51.1 release, we are creating this thread so that users can report any observed issues.
Thank you for your interest and any time you put into making Groupy 1 a better product.
Sean Drohan
Stardock Support Manager
Known issues
While we appreciate all feedback, please remember that we offer no official support for beta \ preview \ developer channel versions of Windows. If you report issues while in any of those early release channels, you should not expect them to be addressed unless it still exists in a retail version of Windows.
I just updated to this latest version and now my main display screen is glitching with all apps, including just at the login home screen on the bootup home page. I use a samsung 43" 4K TV for central display, main PC screen for left display and a Dell monitor for right display. Is there any way to roll back updating? This is very hard to work with. It really only glitches in the current window I am using but it's pretty bad. I manually accepted the update and installed it before this issue started so it is the only thing I have done differently today before this issue started occuring.
Please try this, uninstall Groupy, reboot immediately, re-download latest version directly from your account page: https://store.stardock.com/myaccount/products. Install it, reboot immediately again. Retest it and report back.
Thank you,
Basj,
Stardock Community Assistant
I finally got it corrected last night. I initially tried to uninstall Groupy. I tested it and was still having the issues, so I reinstalled Groupy and was still having problems. In the end I ended up having to uninstall my GPU driver software (Nvidia GTX 1080 GPU) and reinstall it but of course that did not go smoothly and I ended up having to get a 3rd party app to completely uninstall the plug ins for it before I could actually reinstall the GPU software and driver and now I'm finally back up and everything is normal. I think that last update somehow corrupted my GPU driver. It's the only explanation I can think of.
Great, really glad to hear your resolved it.
Thank you,
Basj,
Stardock Community Assistant
If you mean Groupy 'corrupted' your GPU driver - that is inconceivable.
Sean Drohan
Stardock Product Lifecycle Manager
Ok "Vizzini", I don't have a CS degree so instead of being petty or smug why don't you explain what happened. I worked 4 hours, no issues. Closed out of some apps, saw a Groupy update I'd been ignoring for days, ran it, computer re-boots and all of a sudden, my external displays are glitching out of control. Reboot = no help, shut down = no help. Uninstall last thing I used which was Groupy. Restarted = no help. Reinstalled Groupy = no help. Looked up forums on why only external displays are glitching to the point I can't use any of my apps efficiently, all of them point to GPU software or driver since it is a 'display issue' now. Tried a bunch of recommended troubleshooting for that = no help. Only thing that helped in the end was a complete uninstall and reinstall of the GPU software and driver. 4 hours later my boss is pissed because I'm behind schedule but at least I can work again. So please, tell me why I had no issues until I ran your update because I would personally love to know, and it would be a lot more helpful than just trying to belittle me.
'Belittle' you? I do not know how you made that leap, but perhaps my brevity played a part - something I will try to remedy now.
My point was that there is nothing inherent to how Groupy is installed, uninstalled, functions, or is used that would cause a GPU driver to be corrupted - that 'correlation does not imply causation'. What I perhaps should have been more mindful of, and I apologize for neglecting, is that it is not uncommon for clients to observe their forensics in such a way.
In the end, while all the events you detailed may have indeed followed, the odds Groupy played any role in it are near absolute zero.
That said, I am pleased it it now working for you, cwgraham66, and thank you for your patronage.
Sean Drohan
Stardock Product Lifecycle Manager
Huh, I don't think you can help it. Even that response with the hyperlink was somehow a little condescending and patronizing. I can't just chalk it up to coincidence at this point though. If I had clicked remind me later, or whatever the "not now" button is on the update window, like I had been doing for a while, I wouldn't have had any problems that day. In fact, it's the only problem I've had on this laptop since I bought it seven years ago. Yes, that's old for a laptop but it's still pretty powerful by today's standards so I can't say for sure that your update caused it entirely by itself, but I can say if I had not run the update, I wouldn't have had to deal with that.
That said I do like Groupy, it's fairly handy for apps that don't auto stack, but I love Fences so thank you for that one, it might be the best desktop organizer I've ever seen.
The most likely reason it showed up after the Groupy update is because that forces a reboot.
Typically something got broken some time before but it does not show up until the next reboot and then not unreasonably a user blames the last thing they did which in this case is a Groupy update.
It could even be a Windows update that was pending that was incompatible with that driver.
Sean is right that installing a Groupy update should have no impact on your graphics drivers unless there is a hard drive fault or some other hardware glitch happening.
I can't rule that out either at this point. Although I do shut this one down nightly or shutdown and update if applicable. My last windows update in my history was on the 15th, so 6 days prior to the issue but I do have other software that update constantly so I can't rule out anything else but none of them should affect the GPU software either...so who knows. The uninstall/ reinstall of the Nvidia software fixed whatever it was, but I can't tell you exactly what I was seeing. I'll try to Dropbox a short video I recorded on my phone of the sign in page after the 5th or so reboot I tried. You can see some glitching. I did not get one of me trying to use a window on my desktop after. It would only occur in the active window or when dragging a window and it was much worse. I don't know what it was or care anymore at this point since it works as it should again but if other people have similar issues, maybe this will help.
Welcome Guest! Please take the time to register with us.