I am facing the same issue. Once I uninstall Fences 3, the issue disappears. I have wiped this program so strongly off my system that even the NSA would be jealous. I deleted all files, dll's and registry keys AND EVEN traces on the disk by wiping them with Gutmann 35 passes through Eraser. But once I reinstall the program, the issue comes back.

So @Support, don't you DARE TELL ME TO REINSTALL THE PROGRAM!

If you need logs I can support you with them. I have also identified it through Process Hacker 2 that it is a specific window in the explorer.exe which isn't being told to be invisible or closed.

Ok so to get this done properly, I've gathered a lot of information for you on this. First: I can set the Window Handle through Process Hacker 2 to be invisible, to see if it is that window which I marked for you in the following screenshot, and I can confirm it is. It also opens up a "explorer.exe" window in my Taskbar which I can close just fine. Anyways, I've gathered screenshots and extensive information about the window, find the information attached below:

https://i.imgur.com/rq0AsU3.png https://i.imgur.com/FuxCM5W.png

Start Address: explorer.exe+0x9c8c0

Stack Thread:
0, ntoskrnl.exe!KeWaitForMutexObject+0x38f0
1, ntoskrnl.exe!KeWaitForMutexObject+0x1787
2, ntoskrnl.exe!KeWaitForMutexObject+0x98f
3, ntoskrnl.exe!KeWaitForMutexObject+0x233
4, ntoskrnl.exe!KeWaitForMultipleObjects+0x45b
5, win32kfull.sys!xxxUpdateInputHangInfo+0x10d7
6, win32kfull.sys!xxxUpdateInputHangInfo+0xca5
7, win32kfull.sys!NtUserWaitMessage+0x48
8, win32k.sys!EngSaveFloatingPointState+0x45a1
9, ntoskrnl.exe!setjmpex+0x7ce8
10, win32u.dll!NtUserWaitMessage+0x14
11, shell32.dll!SHChangeNotifyRegisterThread+0x19c
12, shell32.dll!Ordinal201+0x36
13, explorer.exe+0x4c24e
14, explorer.exe+0x9c846
15, kernel32.dll!BaseThreadInitThunk+0x14
16, ntdll.dll!RtlUserThreadStart+0x21

Windows - Thread:
Class: SysListView32 ; Handle: 0x207c6 ; Thread: explorer.exe (4636): 4640

Window - Properties (SysListView32): General
Thread: explorer.exe (4636): 4640
Rectangle: (0, 0) - (400, 400) [400x400]
Normal rectangle: (0, 0) - (400, 400) [400x400]
Client rectangle: (8, 31) - (392, 392) [384x361]
Instance handle: 0x7ffb1e8b0000
Menu handle: 0x0
User data: 0x0
Unicode: Yes
Window proc: 0x7ffb688d9da0 (comctl32.dll!DSA_Create+0x1880)
Dialog proc: N/A
Dialog control ID: 0

Window - Properties (SysListView32): Styles
Styles: 0x14c02040
WS_BORDER
WS_CLIPSIBLINGS
WS_DLGFRAME
WS_VISIBLE
Extended styles: 0x20000900
WS_EX_WINDOWEDGE

Window - Properties (SysListView32): Class
Name: SysListView32
Atom: 0xc0f4
Styles: 0x4008 (CS_DBLCLKS | CS_GLOBALCLASS)
Instance handle: 0x7ffb68850000
Icon handle: 0x0
Small icon handle: 0x0
Cursor handle: 0x10003
Background brush: 0x6
Menu name: 0x0
Window proc: 0x7ffb688b9630 (comctl32.dll!Ordinal395+0x31f0)

Window - Properties (SysListView32): Properties
Name: UxSubclassInfo ; Value: 0x9093110

If like the OP, how often is 'sometimes' and can it be readily reproduced?  If so, how can it be reproduced?

Also, I would like to know if it still happens under a clean boot of each app:

https://forums.stardock.com/488142/groupy-support-faq#cleanboot

https://forums.stardock.com/486084/fences-support-faq#cleanboot

Sean Drohan
Stardock Support Manager