Fences Causing very slow boot

When I'm in the office with my Windows 10 laptop (with Fences latest version), I can boot, login & be working in about a minute.
When I work from home, the system boots & I login but then the system seems to hang for around 10 minutes before I can do anything!
If I disable fences and reboot, I'm up logged in & working within a minute.
If I then enable Fences & reboot....We're back to the 10 minute wait again.

When I work from home, after logging in I usually manually start a VPN. However, this is difficult with the system hung. Even if I auto start the VPN, the system won't accept keyboard input, so I can't login to it.

I suspect that Fences is trying to access the internet using the proxy settings in IE. However, these proxy setting are only valid when I'm in the office or connected via VPN! And I can't connect the VPN because Fences is blocking everything!
It would be nice if the dev team at Stardock are listening & could fix this, even if only to bring the timeout down from 10 minutes to something more sensible.

6,351 views 2 replies
Reply #1 Top

Hello,

Sorry to hear you are having issues.

First, Is your fences the latest version? If its not please get the latest version.

Second, Please try these workaround steps for networked portal fences and see if it help with the speed. https://forums.stardock.com/486084/fences-support-faq#folderportalsempty

Try that and report back.

Thanks.

Basj,

Stardock Community Assistant.

Reply #2 Top

Hi Basj


Thanks for the quick response. I am running Fences 3.0.9.11. I had a look at the link you sent & the problem description looks nothing like the issue I have? I might have found it myself if it did.
I have around 200 items on my desktop, probably up to half of them are links to websites, network shares or items in network shares.
This is why I use Fences|-)  
So for me, the workaround is more painful than the problem. However, to test the issue I did move everything from my desktop into a sub-folder. This did resolve the issue. On moving everything back, with the VPN disconnected it took some minutes before Fences sorted itself out. However, it was quicker than the bootup/login hang and unlike that situation, keyboard & mouse input were accepted. So I could work. 
I think for me, the best workaround until this is resolved will be to have a logout script to disable Fences. Then I can enable after I have logged in & connected.

Regards
Keith30