[quote who="sdRohan" reply="144" id="3701146"] I did talk to the lead today and he said to me: '“Going to get this fixed!!!!” I will let you know when I do. [/quote] Followed by: "ffs get off me already!" [e digicons]:D[/e]
[quote who="sedstr" reply="140" id="3700903"] You haven't worked it out yet? Investigate color hot-track, because that appears to be the source of the problem from my investigations. This is really really annoying - I'd be happy to revert to an older version till you get this fixed, in fact, I'd be happier on an older version.
[quote who="sdRohan" reply="128" id="3700296"] All, We have modified the tests a bit and any that installed it should use patch_unregister.cmd, reboot, remove the temp Fences files and start over from here: https://www.dropbox.com/sh/l9t0akw9osrqslt/AABtiljNULpeIiI1tUVrhHOOa?dl=0 The instructions.txt file has been updates so please read it carefully. Looking
[quote who="sdRohan" reply="122" id="3700077"] All, <span st
Dual monitor here too, with a 1980x1080 and 1680x1050 setup... but I though the multi monitor thing was known by the devs? It has been commented through various threads multiple times. Disabling the second monitor on both hardware or software doesnt fix it btw, but maybe some setting on Windows sticks so you have to start clean to really test it.
[quote who="chaospromos" reply="113" id="3698185"] Update, I was able to use MSCONFIG to stop fences from starting on reboot. Just go to your "STARTUP" tab in MSCONFIG, and uncheck Fences. When you reboot, run the Fences 3.03 startup file, and it will install. THIS FIXED MY ISSUE. Stardock, if you are watching, you need to give the Purge \ Reinstallation fix to everyone who has this problem. The issue is your new updated versions,
[quote who="smooreace" reply="79" id="3696694"] out-file : Cannot perform operation because the wildcard path C:\Users\[YOUR did not resolve to a file. At line:1 char:1 + Get-ItemProperty HKLM:\Software\Wow6432Node\Microsoft\Windows\Current ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OpenError: (C:\Users\[YOUR:String) [Out-File], FileNotFoundExcepti
[quote who="neroilo" reply="75" id="3696663"] Sorry, but your list is not sorted alphabetically and there are many spaces between lines. It can be difficult to read. [/quote] The format is irrelevant since its purpose is to be used with the compare command to get a small list of identical software [quote who="elbleins" reply="74" id="3696626"] Maybe this will help. If everyone with the problem creates a list of all installed programs (at least as
It may be worth noting that I ve had this exact same slowdown problem since Windows 7, only then it appeared at random and I could fix it by changing any UI settings on the Fences config screen. Though it may have been caused by a different bug, and yes, Microsoft might be at fault anyway. Thing is, we want some more communication over this problem. 3 months ago I got an email about helping on a more direct look into this bug over remote control with a developer. H
The are no older versions from stardock. If I remember correctly, I found them on filehippo, but personally speaking 3.03 has only very slightly decreased the lag for me, so your mileage may vary. Im still waiting for the remote tests they wanted to run with us to debug performance.
I made a few more tests and it is definitely because of the icon count. I started deleting various kinds of shortcuts and fences, until I just realized that 0 icons = 0 delay, and every new icon I put inside a fence added a very tiny slight delay that eventually starts to mount up. But I still don´t get why is this happening now. Just in case. I revised every windows update (I had none the day it started failing) and new software, and no
For some reason, the icons inside my fences takes at least a second to register a click/double click, which is painful to say the least. Example GIF This has happened to me (very rarely) in the past, but the old trick of changing the Fences "Show Labels" option fixed it. Now its been over 1 week of this, and apparently its not going away.