Unfortunately that does not work for me. The service is there and it's set to auto, but the service does not start on boot.
If I now go to the services and try to start the service manually, it will not start, just errors out.
I have just installed the new beta (2.11), restored everything to normal, and fences appears to crash Windows Explorer, and prevent my start up items loading, so no change there.
I have gone back to my method I stated in an earlier post. Disable the Fences startup items, boot the system, then at any time after that just right click on the desktop and my fences load.
There definitely something that Fences does not like about my system, even though I did a W8 refresh a while back.
I do have another problem which I reported maybe a year ago, but no solution was found via tech support. If I right click on any program shortcut within a fence, select open file location, nothing happens. I have to select 'properties' instead then 'open file location' from the pop up window that appears. But this is off-topic ......
I did quick search on the error below, and a very quick scan of the results says this error relates to Net Framework 1.1, and occurs when trying to Stop a service ....... not starting one. TBH I cannot be bothered to try and track the error down at the moment. It's too hot, and I have other things to do ....