I'm having exactly the same issue with the latest preview build. I understand that the preview is pre-release software, and thus not supported, but a fix would be greatly appreciated. Thanks, Pete
Installation path is C:\Program Files (x86)\Stardock\Fences\ and not C:\Program Files (x86)\Stardock\Fences3\ Also, there is a misplaced " Either way, I'm activated and Fences is working, so thanks
Using Cmd line activation resolved my issues with Fences 3.01 on the Insider Preview. I am now using the latest 14352 build. The command used in your esupport article needed a change in my case, from "C:\Program Files (x86)\Stardock\Fences3"\SASUpgrade.exe -prodId=2628 -prodName="Fences3" -company="Stardock" -ver="2.90" -email="USER@USER.COM" serial="PRODUCTKEYGOESHERE" to <s
Have you guys at Stardock installed Fences 3.01 on an Insider build to track what's causing the problem with activation and opening the program? If there are modifications to your code required do you have an ETA on when a new version will be pushed out?
I updated to Fences 3.01 and rebooted, but am still unable to open the application, or enter my license key.
I am in the same boat with this one - I had a fences 2 installation which was working as intended. I am running the latest Windows 10 Preview build 14342. I installed Fences 3, and was not prompted for my product key. Now after rebooting, my fences are visible, but I cannot open Fences 3, either from the Start menu, or via 'right-click, Configure Fences'. I then subsequently reinstalled, and then reinstalled again after deleting the Stard