Greybird3339

Unfortunately, this issue was enough of a problem to make Fences unusable for me. Along with the fact that this issue has been going on through multiple iterations without a solution, while support keeps me spinning my wheels - well, I need an app I can use, and I cannot use Fences. It's been enough that I've given up on Stardock entirely, and have found an alternative for Fences. I have gone from having nearly every aspect of my system customized by SD to only h

I don't own Fences 5. I could check the free trial, but I still wouldn't own Fences 5, so that wouldn't help.

[quote who="basj" reply="1" id="3915304"] Hello, Sorry to hear you are having issues. Have you tried review this thread and try some of suggestion discussed in there? : https://forums.stardock.com/512027 . Also, try Fences 5, there is report where Multimonitor issue resolved in this version. Thanks Basj, Stardock Community Assistant. [/quote] As far as I can tell, there are n

I've been struggling with Fences (4.21) for a while. Ever since I added a second monitor (same resolution and refresh rate), I've had a range of issues. Windows 10, fully updated, and yeah - I've tried reinstalling Fences from scratch. Individual fences frequently move from one monitor to another after a reboot. Anything added to the primary desktop (saved, extracted, etc) gets moved onto the secondary monitor. Today I decided to move

I'm having exactly the same issue, and as far as I can see, nobody has ever come up with a solution. Multiple fences on multiple 'pages' keep getting moved. It's causing serious problems, since it keeps putting fences from multiple monitors on top of each other, making it really, really difficult to select them to get them back where they belong. Is there an actual solution to this, or better yet, a way to get direct customer support?

I don't expect any software to be perfect, but if I'm paying an active subscription, and am expected to re-subscribe, I expect the basic functions to work.

I just rebooted my system six times in a row, wondering just how many updates there were, only to find out that it was installing the same update over, and over, and over. This is not a 'please ignore' . It is causing multiple people time and headaches. This is a 'fix the software.'

That's a shame. I will just have to stick with Windows native options for now.

I want a little color, and all of the 'Dark' themes tend to be... heavy. But I'm also photosensitive, and make heavy use of Windows native dark mode. I've found quite a few skins I actually like, but they all replace explorer/etc backgrounds with bright white. Is there any way to get WB to respect Windows settings on this?

I could, possibly, but it comes with the unfortunate side effect of putting ESET permanently into 'alert' mode, which has the effect of making it impossible to tell when a real alert is present. I'm going to keep fiddling with it on my own. I will post here if I come upon any solutions.

Thanks, Neil. I wasn't assigning blame - with so much software and variability in PCs, there will be times when there are simply incompatibilities. I can promise you that the instructions were followed (and WB was removed and reinstalled multiple times, into different directories and on different drives to try and eliminate that issue), which is why I said "at least on my system." I'm guessing that there is some other piece of software, driver, or hardware that is ca

I'm updating this just in case anyone else has the problem. There is nothing worse than googling your problem, finding a discussion about it, and then finding that the answer never got posted. Unfortunately, after some back and forth with Stardock, it seems that there currently is no solution to this problem. WindowBlinds 10 is simply incompatible with ESET NOD32 Antivirus, at least on my system. Hopefully there will be an update at some point in the future

IZR-265-37962 I've already heard back from the help desk and replied. I just wanted to make sure I wasn't submitting two support requests for one issue.

Thanks again for the timely update. I've always been happy working with Stardock. I tried the new instructions and get the same result. WindowBlinds sees ESET and tells me to change settings, never letting me actually apply a skin. I already contacted Stardock via the email link on the KB page earlier. Should I submit a ticket as well?

Thanks for checking. Two problems. First, there is a step missing between 7 and 8. After you name a rule and set it to 'allow', you have to pick from a number of options for how you want the rule to work. Having no knowledge of how WB works under the hood, there is no means by which to determine which options to pick. To try and get it working, though (I've had WB since WindowBlinds 2, and miss having it), I selected

The instructions on the knowledge base article refer to interface elements that don't exist or have been moved. If I've read correctly, the new process for excluding items from HIPS seems to be much more complex, and requires certain details about what the exclusion is to allow and not allow rather than just a 'one size fits all' exclusion. I've got no idea which of the options apply to WindowBlinds.

I am trying to use WB 10 on my Windows 10 system. It installed fine, but when I try to apply a skin, I get a popup, below. Closing the popup links me to this knowledge base article . The problem is that the knowledge base article is three years old, and the instructions have nothi