Too many trains of thought here.  I'll start over.

It is my assumption that the very first installation of STARDOCK FENCES on any box with the win10 OS (including the latest Preview) would work as it should.

The error is hidden somewhere in what remains on the box (cleaning or not) when the program is re-installed: re-written/written-over.  I speak from my own experience only.  I made many attempts to install/uninstall/re-install STARDOCK FENCES over the last 2 Insider previews.  It was not until I manually scoured every last shred (and some were hard to find) of STARDOCK that I achieved success...through multiple re-boots too!

Consider too, where is the info (file?) on your box that is prompting the error message?  If you are, indeed, doing a "clean" install, how does the program "remember"?

A Windows Explorer problem?  If this error information is a result/comes with/caused by your new "clean" installation, then the program is interacting incorrectly with something ALREADY ON YOUR BOX.

Finally, remember, error messages are only as accurate as the programmer who compiled them.  They are not always a reflection of what actually IS, but what most nearly represents the true error 'recipe'.  They are not unique/error specific messages sent to you in real time from a cognizant source.  

That's the best I can do.  Good luck everyone.

Kevin

APOLOGIES

Despite my faultless logic (tongue in cheek), STARDOCK FENCES does NOT work as intended with Windows IP build 14936.  I apologize for my previous posts insisting it did.

Kevin

Upgraded to Build 14942.rs_prerelease and fences are working properly.

I am having the same problem with 14936.  After the update, Fences fails to launch.  It wants to, says that it should be enabled,  Windows tells me that FENCES.EXE is running when I try to reinstall, but it's not visible in the Task Manager.   I will wait (as patiently as I can) for an update or patch from StarDock.  I love Fences.

Also do NOT re-install MalwareBytes after upgrading to build 14942. You'll just get BSODs all over again.

MalwareBytes are looking in to issue (as of 10 October, 2016) so hopefully a resolution on that soon.

In the meantimes Fences 3.03 Beta is running happily!

Quoting ZubaZ,

reply 1

We are aware of this and will be looking into it.

Insider builds are a mixed blessing.  

I use the insider builds on my phone, but there's no way I'd run them on my desktops, too many issues with 3rd-party programs and such.  Nope, I'm not in a hurry to get new Win 10 features before regular users, no siree.  Given the issues with Windows Update and peoples machines getting borked, I'd rather wait until things have been tried and tested properly, and even then I'm not sure I want it all.  I just want to use my machines as regular PCs, so I pass on anything to do with the Store and the 'apps'.  They are just a clutter I have little or no use for.... including Cortana, something I once looked forward to but have disabled.  I managed without it before and I still do.