Windowblinds7 (XP) + Nod32 = Wblind.dll infected

from WinCustomize Forums

 

Well I have just updated my windowblinds last night .. and when I started my system this evening ... NOD32 all of the sudden blipped that Wblind.dll is infected with Win32/Genetik trojan :| tried to uninstall/re-download+reinstall routine but the same results :|

11/19/2009 3:20:33 AM    Startup scanner    file    C:\PROGRA~1\Stardock\OBJECT~1\WINDOW~1\wblind.dll    probably a variant of Win32/Genetik

 

I wonder if someone else can explain or having the same results :|

 

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
Your machine supports per pixel borders on WindowBlinds skins.

(Plug and Play Monitor) 1 is attached to NVIDIA GeForce 6200

Wblind.dll File missing - Please reinsta20
Wbsrv.dll 2009/08/29 04:21:18
SevenConfig.exe 2009/11/12 21:16:53
Wbload.exe 2009/11/06 22:44:12
Wbhelp.dll 2009/07/30 01:11:07
Wbui.dll 2009/07/30 01:11:05
Tray.dll 2009/10/21 19:13:19
Screen.exe 2009/11/07 22:39:26


thanks and regards

BX

12,840 views 6 replies
Reply #1 from WinCustomize Forums Top

Basically NOD32 has incorrectly guessed that wblind.dll is some sort of bad file.

This is known as a false positive.

We will be contacting NOD to ask them to correct their app.

For now you should be ok to ignore this error, though you will need to restore wblind.dll and tell NOD to ignore this file.

Chances are the issue wasn't you updating, but NOD32 having some sort of file update.

Reply #2 from Stardock Forums Top

If you're in the US I say fight it, wblind.dll is innocent till proven guilty. :grin:

CursorFX - Customize your Windows cursor
Reply #3 from WinCustomize Forums Top

Quoting ChuckCS, reply 2
If you're in the US I say fight it, wblind.dll is innocent till proven guilty.
End of ChuckCS's quote

If only AV apps worked like that!

They seem to assume guilt and inform the user the file IS bad (not might be, but IS). 

Reply #4 from WinCustomize Forums Top

I got the same nod32 warning on both my home and work computers, and ended up uninstalling and reinstalling on both computers after I mistakenly had nod32 "fix and remove" the "Genetik Trojan variant."  What a pain in the butt, ESET!!

Windowblinds 7 is now working beautifully on both computers.

Reply #5 from Stardock Forums Top

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.

Reply #6 from Stardock Forums Top

Make sure you have virus definitions that are version 4621 or higher.
End of quote

We worked with Eset today to resolve the false positive, and this was the database version that should address it.  Update to this or later.