Anyway, when I asked you to do the purge and reinstall in reply #9. Did you do the full steps or just uninstall and reinstall? Please note that with purge it will cleanup all traces of Fences from your system and when you reinstall it will be just like a new install.
Please try it and report back.
But just in-case you already have it done.
I did your version of the purge uninstalled and also used Revo Uninstaller to delete other traces of it.
It certainly seems that the uninstall was clean because the issue did disappear for two weeks - it would have reared its head again immediately if it was the same install or running on the residue of the last install; least that's what seems logical.
just to clarify. That your problem is that your task buttons no longer work for switching apps. It randomly stuck to one apps.
I'm not sure what you mean by task buttons...
What are task buttons? Anyway no... as seen in the video, switching apps via keyboard works perfectly fine; in fact it is the only method of switching apps that actually works. As you can see in the video (though I couldn't find a setting to show the mouse while recording), whenever focus is lost (reverted to OBS) on the program I ALT-TAB'd to, that moment is when I used a button on the mouse.
You should also see, however, that the program focus got stuck to responded, and it seems that Fences can specifically choose sub-windows and objects rather than just the simple ones that you can control with the taskbar. You might notice as I tried to demonstrate, that it was focussed on the middle portion of OBS, the part that was actually the recording output and no other buttons within the window would work. Right clicking in that area was made obvious, and like I mentioned when the screen moved, those were click + drags that were successful.
This bug renders my computer completely useless if I do not have a keyboard.
And how do you get out of the stuck situation? Restart? or it usually slowly resolve themselves?
Usually what I would do to get out of it, as mentioned in the OP:
This problem can be temporarily alleviated when ending the explorer.exe process (at least, for the most part), because Fences injects dlls into it. Next, when explorer is off and considering rundll32 is still running, the problem persists EXCEPT when I specfically ALT+TAB to Task Manager and click that window. Once this happens, normal focus is restored to the screen until a few seconds after I activate explorer.exe again through Task Manager.
Though it escapes me as to why this method doesn't seem to have quite as much effect anymore. I have resorted to a custom program my friend built for me that blocks Windows shutdown from fully completing, so that I can tell Windows to shut down and have it close most programs down. This seems to fix the problem for a short amount of time, and that's the fix I used to record the bug for you, and as you can see after I opened those windows, the bug appeared. Don't read too far into that though - it's not just a specific program that causes Fences to go haywire. This'll happen no matter what windows I open.
Restarting the computer also seems to fix the problem for a while.
Next steps is to try the cleanboot steps to iron out if there is conflicting apps. https://forums.stardock.com/486084/fences-support-faq#cleanboot
Mind, as for conflicting issues it seems that explorer.exe is just that specifically because of this being fixed when the process is killed.
I don't think there is any specific program that is causing Fences to run faulty, it seems more along the lines of a malfunction, mishandling of focus context when dealing with multiple windows.
I would love to do the clean boot procedure for you but I don't think the problem will come about right away, which means I'd need to use an empty account for quite a while and I haven't got the time just now. Perhaps in the coming weeks or months I will find the time, however this seems to be steps to concluding that my Windows account is specifically in conflict with Fences, and I must remind you that my old installation of Windows Home also saw this problem. I would posit that it is hardly the operating system version or local installation of the account that is the problem.