Slow startup
Stardock Forums
Hi Stardock,
Fences 2.13
When I start my PC with Fences, the PC is very slow to startup and I get an almost blank screen before fences "snap in". If I uninstal Fences the PC start very quickly. I have googled the problem and it seems others have this problem too.
My OS: WIN 7 64 Bit
Please advice
Best Regards
Hey MikeLookz,
Please download the following file: http://sd.stardock.com/Support/FencesLoadSvc.bat
Once the file is downloaded, please right click it, then select "Run as administrator".
Note: This file assumes Fences is installed into the typical install folder.
If successful, the file should report that a scheduled task was created.
Once that has completed, please perform a restart of your computer, and Fences should load after a short delay.
If it does not, I'd like to gather some information from your PC about a potential cause and request that you open a ticket.
Please see the following article for information on placing a ticket:
Thank you!
Hello kin3tix
Same problem on one of my laptops with windows 8.1. I use on two laptops the payed version of Fences 2.13. One has the same problem as Mikelookz. A very long boottime with a blank desktop (only background). It seems that Fences.exe is the last utility which is activated. Utilities like Dropbox and Qsync (from Qnap NAS) are allready working for some time before my Desktop shows up. Very annoying because I can't do anything before my Desktop is there. The other laptop starts relatively fast, but my Desktop is cluttered with Icons until I left-click once somewhere on my Desktop. Then the icons 'seek' quickly there appropriate place.
I want to trie 'FencesLoadSvc.bat'. I see it creates a task which starts 10 seconds after logon. Doesn't that 'bite' the allready configured startup of fences.exe which I see in the startup items of Windows Taskmanager? Should I disable that startup item in Taskmanager? Why a delay of 10 seconds? Doesn't that slow down the boot time of my laptop?
Hello lklaverstijn,
Having the task scheduled on top of the already existing startup item will not cause any issues, however, it will cause the Fences configuration window to load when called for the second time. Therefore, I would indeed recommend disabling the startup simply for the sake of testing that task.
Regarding the time delay set in the task, it is just a base value we found to be appropriate for the average computer and can certainly be adjusted if you feel it is too long or not long enough. To clarify however, the task is not delaying the startup process in any way, rather it is being triggered by logging onto your system and after 10 seconds have passed, your system will run the task. As a result, this should not result in any delays in your boot time.
If the task does not help, please create a ticket so we can look into this issue further. Please see the following article for information on placing a ticket:
Welcome Guest! Please take the time to register with us.