Out of interest I created a fresh vanilla install of the build in question on Hyper-V and installed Fences as first thing. There is a problem with this build You can recreate.
Certainly appreciate all your efforts here, c242. As you would suspect, however, a variety of false positives can appear using a VM. That said, I would still like to see why this failed at a later time.
Jonus, we need to be sure you are not performing this on a VM or anything your work might offer as one. We also could not get it to function properly on a VM.
Paul and I both tested this on actual Win10 boxes. We both removed all traces of Fences (install dir, activation files, reg entries).
Video of mine (it's just like Pauls's):
I believe it could be the activation key that is activating but not making the program enabled in some strange way, if that could make sense..
The activation file (License.sig) is stored here:
If it's missing after you activate it, that's a problem.
Stardock Product Lifecycle Manager