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.

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 all of the options.  When attempting to apply a skin, it still gives me the error pictured above and sends me to the knowledge base page.  I have tried numerous variations of the rule.  I've tried adding additional executables to the rule.  I've uninstalled and reinstalled WindowBlinds.  I've run it as an administrator.  Nothing changes the result - skins cannot be applied, as they just generate an error and open the webpage. 

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?

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.

Google 'f.lux' ... it's a proggy that auto dims your monitor for lower brightness at night under artificial light [when the intensity is not needed].

I use it....

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 causing the fix to fail.  Such problems are usually rare enough that actually solving them is unrealistic.

Unfortunately, ESET is the antivirus that has best met my needs, as it is one of the only I've tried that hasn't consistently interfered with games and thrown false positives twice a week.

Thanks, and that's a great suggestion.  I've actually used f.lux in the past, but it doesn't really help with the problem.  F.lux adjusts the color of the light as well as its intensity, which is OK for some things, but I do enough stuff that distorted colors are a problem more often than they are a solution.  It is only the bright colors, usually whites, that cause me problems (this reply box, for instance, feels like I'm staring at a light bulb.)  F.lux would ease that a little in the evening, but it would also alter the blues, the reds, the greens - colors that aren't an issue for me at all.

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.