Threaten found by Eset Nod32

I've been using WindowBlinds and the rest of Stardock customizing software for just over 5 years and have never had any problems.  I would say that what you are seeing is a false positive.

Well, just trying to help out here, but I know the first question anyone at Stardock will ask is are you using a purchased legal copy of Windowblinds, and if so to please post the "About Windowblinds" system information here for them to see.

This file is a part of Window Blinds!!! Just add it to the list of ESET exclusions and you will never see this message...

Yes but It's weird that Nod32 thinks it's a trojan, no ?

Maybe my protection is to high ?

Usually it is wbsrv.dll that gets detected as a false positive.

Assuming you downloaded the software direct from Stardock / Download.com (if the Trial) it should be something you can safely ignore.

I first have download it as a trial from Stardock.com, and then I downloaded it from Impulse, without deleting the trial version...

Some AV packages seem rather too keen to say something is bad.  Perhaps because they want to be seen to be doing things.

When we get reports of such issues we report it to them and eventually they sort it out.

BTW virustotal.com is a great place to see what other AV packages think of the file.

I tried with the version in the WB7 release and none of the AV packages detected it as a virus.

Fichier 4C10DAA935EB71BBD8A20A11E85723009BE28211.dll reçu le 2009.11.18 07:07:53 (UTC)
Situation actuelle: terminé

on the english side of things,... same thing's happening to me. Have been a subscriber for a number of years and would expect to see this issue with other virus software , but not eset.. .thought they were more on top of things...

Anyone have the path and file I need to insert into exclusions?  It wants me to reboot so it can "clean" the files... and honestly... would rather not have that happen as it will really mess with my computer.

Ok. I just have completly remove Windowblinds, but not Impulse, and reinstall it propelly using Impulse.

I have no more threaten message when I reboot. Hope it will stop...

Thx all

Hmmm... Where have you installed WindowBlinds? You'll find this file here... 

The path must be: WB INSTALLED DIRECTORY \ wblind.dll

By the way, I saw the same message a few days ago. Two clicks in the ESET settings and it doesn't touch my WindowBlinds!

cool, I already have it set to ignore wba when it's doing full scan because it's already checked it when it gets dl'd , so  I will hunt down the path and see if that makes a difference.

Been afraid to reboot because if it removes that dll it'll screw with the software.

ok vad, here's the thing, I'm finding wblind2.dll and wblindp.dll, no plain ol wblind.dll ... any further suggestions as to which is causing the issue?

ok, I just had it exclude all stardock folders/files  cross fingers... (trust ya'll explicitly to protect my investment in your product)

When we get reports of issues like this, this site is the first place I go.  Every time so far it has come back clean or with only the offending engine reporting a threat. 

This is actually one of the first things I do when installing new AV software on a machine.  So much of what our software does quite frankly looks like changes that viruses might make (how many spyware apps change your wallpaper?  WindowBlinds does that!) and alot of these paranoid heuristic engines would rather be safe than sorry.

That would suggest the AV app deleted the file.

You may need to restore it from the AV app if you can, or reinstall WB.

This has now been addressed.  Make sure you have virus definitions that are version 4621 or higher.  You may need to verify WindowBlinds through Impulse, or uninstall/reinstall, but after that, you should be good to go.

I had exactly (only in english) the same NOD problem this morning as the OP.  All software is legit and updated to latest versions.  It might be due to the newest updated definitions from Eset?  I just excluded it and no more problems.

angus1949: What version of the definitions database do you have?

These false-positives happen so frequently with Stardock's proggies that you wonder just how often one or other of the AV proggies is 'getting it wrong' with some other program out there.

You would 'think' that once a product flagged a false-positive the AV company would set an automatic exclusion - one that wasn't lost/circumvented by the very next AV update.

It's one thing for an AV to be cautious....quite another to interfere/disable/break a legitimate [and clean] product.