Everything takes a long time to load

Windows 11 24H2

Fences 5.88

 

On the previous version (I think it was 5.86), when I used the hotkey for "Show Fences (toggle)", the shortcut I double clicked would open inmediately; after the latest update, when I double click a shortcut, this isn't the behavior any more, I have to wait for a few seconds for it to open or click "outside" of the fences for it to start loading. 

 

I searched the settings for a new one in case this was optional but I didn't find one. Is this a known bug? If not, could you help me roll back to the previous version? I don't want to use "press and hold", "toggle" works just fine for me but with the previous behavior.

 

Thanks in advance.

22,098 views 27 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Need to know your Windows 11 24H2 OS Build number. Please use Windows own Winver.exe to get this number.

Thank you,
Basj,
Stardock Community Assistant.

Reply #3 Top

Thank you, I can reproduce this issue, I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant



Reply #4 Top

I've had the same issue.  Not sure that I tried 5.86.  But reverting to 5.04 allowed double-clicking shortcuts to launch quickly again.

Reply #5 Top

Meanwhile, could you please share the previous version installer so I can work normally? I also noticed an extreme lag when dragging a file from a portal to any window. Thanks in advance. 

Reply #6 Top

I don't have links to share older versions. Perhaps Support have it. Please wait for Support to reply.

Thank you,

Basj,
Stardock Community Assistant

Reply #7 Top

I seldom do this, but if you right click on a shortcut, do you see a delay then as well?  I did.  But I didn't care because I just never do that.

I'm assuming this problem is not widespread since I've only seen a few post here about it.

Reply #8 Top

Reference video: reproduced issue on peek launch delay.

Thank you,

Basj,
Stardock Community Assistant

Reply #10 Top

I wasn't able to track down the randomness, but that video does show exactly what I was experiencing - before I went back to 5.04.  Most times it would take that long to launch a program.  But sometimes it would launch quickly. 

I guess I need to re-install in a VM, see if I can repro there.  If I can, I'll just follow the beta releases in that VM until it gets fixed.

Reply #11 Top

Thanks for the feedback everyone, we have an out-of-band build that we believe will resolve this issue. As with all of our other out-of-band builds, this has not received the same level of review prior to shipping as a traditional beta release for us - so please do no install on any critical infrastructure.

That being said, in our quick testing, it resolved the issue as we expected but please know that the changelog may not reflect this newest change.

Download: Fences 5 Build 5.8.9.1

If you do install this build, please let us know if it resolves the issue.

+1 Loading…
Reply #12 Top

Ok, got a Windows BSOD - unrelated to Fences - but since I had to reboot, I took the opportunity to install the update above.  No difference - UNLESS I don't use Peek.  I never paid much attention previously to whether I was using Peek or just revealing the icons via desktop click and launching from there.  I suppose I've been using Peek all this time.

Via Peek - same old delay, every time.

Click on desktop to reveal hidden Fences, double click any program - instant launch.

Here's a demo - https://app.screencast.com/Kj3cDSUAINvzR

Also, to be clear, since I didn't do this in the video.  I just finished repeatedly launching that app via desktop click then double-click.  Launches fast every time.  Then tried 5 times with peek, slow to launch EVERY time. 

Reply #13 Top

Quoting IrwinMFletch, reply 12

Ok, got a Windows BSOD - unrelated to Fences - but since I had to reboot, I took the opportunity to install the update above.  No difference - UNLESS I don't use Peek.  I never paid much attention previously to whether I was using Peek or just revealing the icons via desktop click and launching from there.  I suppose I've been using Peek all this time.

Via Peek - same old delay, every time.

Click on desktop to reveal hidden Fences, double click any program - instant launch.

Here's a demo - https://app.screencast.com/Kj3cDSUAINvzR

Also, to be clear, since I didn't do this in the video.  I just finished repeatedly launching that app via desktop click then double-click.  Launches fast every time.  Then tried 5 times with peek, slow to launch EVERY time. 

Please try purge and reinstall steps as mention here : [Link]. Just make sure to redownload the latest version from your account page. Reboot after the purge. Reinstall and reboot again after the installation. Retest and report back here.

Thank you,
Basj,
Stardock Community Assistant.

Reply #14 Top

Hi.

The issues (slow response to open and lag when trying to drag files from portals) were solved with the link shared here (I did purge before because I saw the other comment). I used the one shared here, on the download site, there is a beta that has a 181 build (the one shared here was 180) but I dit not mess with that, I just used the one shared by BradSams.

Reply #15 Top

Quoting sanmarcha, reply 14

Hi.

The issues (slow response to open and lag when trying to drag files from portals) were solved with the link shared here (I did purge before because I saw the other comment). I used the one shared here, on the download site, there is a beta that has a 181 build (the one shared here was 180) but I dit not mess with that, I just used the one shared by BradSams.

The purge and reinstall steps was for IrwinMFletch. Great to hear your issue was resolved, just as a note, I believe, the j181 build is the latest version, should also work. Appreciate your taking time to report back.

Thank you,

Basj,
Stardock Community Assistant

Reply #16 Top

The issue is gone after installing the Beta version. Thank you very much! 

Reply #17 Top

Quoting Cyber1e, reply 16

The issue is gone after installing the Beta version. Thank you very much! 

Great, thank you for reporting back.

Thank you,

Basj,
Stardock Community Assistant

Reply #18 Top

Glad to hear it's fixed.  But now, V6 is tempting me - LOL.  Think I'll put that in a VM for now and next time I have to reboot I'll do the purge and install the latest v5 on the main box.  Can I assume v5 is OUT of Beta and 5.89 has the 'fix'?

Reply #19 Top

Correct! v5.89 has the Peek performance fix, and is the current release version for v5

+1 Loading…
Reply #20 Top

Quoting basj, reply 15

I believe, the j181 build is the latest version

Where can I find that version?  All the links here give me j180.

Reply #21 Top

Maybe it does not matter, none of the installers work at the moment

 

Reply #22 Top

Quoting IrwinMFletch, reply 21

Maybe it does not matter, none of the installers work at the moment

 


Hello,
Sorry to hear you still having issues. It the setup not responding from the same system that was working before? (reply#4)

Thank you,
Basj,
Stardock Community Assistant.

Reply #23 Top

Yes, same system.  I even let Fences itself download the update - same behavior.  This worked before because I'd installed the 180 beta earlier only to find that the issue with lag was fixed in 181 - which I can not find.  So I assumed the installers are trying to connect to some server that's down.

Reply #24 Top

Quoting IrwinMFletch, reply 23

Yes, same system.  I even let Fences itself download the update - same behavior.  This worked before because I'd installed the 180 beta earlier only to find that the issue with lag was fixed in 181 - which I can not find.  So I assumed the installers are trying to connect to some server that's down.

If you have Windows Pro version, please test install in Windows Sandbox and see if the same issue appear while in there: https://support.stardock.com/space/SHC/1416560645/Testing+Fences+in+Sandbox

Thank you,

Basj,
Stardock Community Assistant

Reply #25 Top

Worked in a VM, I probably just need to reboot or follow those removal instructions you shared earlier.  I'm almost at the point to reverting to some shareware I used for years.