MS update my Windows 10 to new evaluation copy: Build 14915.rs_prerelease.160826-1902 since I on the fast ring. Now Fences will not running because of error telling me "Windows Explorer don't shutdown correctly. Go to my desktop and click on restart Fences" When I click on restart Fences then my system starts to lockup and couple minutes later I get my OS back but still no Fences. I tried to reload Fences and again no working Fences. Right now my Fences are turn off until Stardock fixes the bug in Fences to work with new release.
I reinstalled the 3.03 beta to test it. Duh!. And I had purged ALL stardock files and folders and registry items first. I have no other Stardock products installed.
Since Fences works on two other machines with 14936 installed, it really makes no sense that removing files and registry items could be the cause of the problem.
Obviously alkolkin means that it had no effect on Fences working.
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
May I suggest that if you have not contacted support, you should do so.
We do not know if, like the previous "broken" insider build this one will be fixed by MS but we are interested in collecting data to see if we can manage these issues that they introduce better.
https://esupport.stardock.com/index.php?/default_import/Tickets/Submit
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.
It has started working again (version 3.03 beta) under Windows 10 Insider Build 14942...
I guess your install didn't get stuck at 81% then. I think 14942 is one of their less good builds (other than no longer breaking Fences)
Upgraded to Build 14942.rs_prerelease and fences are working properly.
I had to un-install MalwareBytes first. Appears this was the issue preventing the build from installing.
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!
Works on the newly released build 14946 too.
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.
There are many great features available to you once you register, including:
Sign in or Create Account
