copy and past your information again, copy everything on the system information tab.

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 ATI Radeon HD 4870  

Wblind.dll      File missing - Please reinsta20
Wbsrv.dll      2009/10/07 15:35:18
SevenConfig.exe      2009/11/12 11:16:53
Wbload.exe      2009/11/06 12:44:12
Wbhelp.dll      2009/10/07 15:35:07
Wbui.dll      2009/10/07 15:35:05
Tray.dll           2009/10/21 09:13:19
Screen.exe      2009/11/07 12:39:26

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 3 Build 2600
OS Manufacturer Microsoft Corporation
System Name xxxxxxxxxxx

System Manufacturer System manufacturer
System Model System Product Name
System Type X86-based PC
Processor x86 Family 16 Model 4 Stepping 2 AuthenticAMD ~3013 Mhz
BIOS Version/Date Phoenix Technologies, LTD ASUS M2N32-SLI DELUXE ACPI BIOS Revision 2208, 09/07/2009
SMBIOS Version 2.4
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale Canada
Hardware Abstraction Layer Version = "5.1.2600.5512 (xpsp.080413-2111)"
User Name TOOTHFAERIE\Zoo
Time Zone Eastern Standard Time
Total Physical Memory 4,096.00 MB
Available Physical Memory 2.30 GB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 10.72 GB
Page File C:\pagefile.sys

Driver Packaging Version 8.65-090813a-087735C-ATI 
Catalyst™ Version 09.9 
Provider ATI Technologies Inc. 
2D Driver Version 6.14.10.6999 
2D Driver File Path System/CurrentControlSet/Control/Video/{0548CAB0-2FA5-471C-92AC-C363841B6054}/0000 
Direct3D Version 6.14.10.0697 
OpenGL Version 6.14.10.8918 
Catalyst™ Control Center Version 2009.0813.2131.36817 
AIW/VIVO WDM Driver Version 6.14.10.6326 
AIW/VIVO WDM SP Driver Version 6.14.10.6238 
AIW/VIVO WDM NSP Driver Version 6.14.10.6326 
AV Stream (T200) Driver Version 6.14.10.1064 

What version of WindowBlinds do you have loaded?

So butt ugly in fact, even a proctologist would turn away feelng nauseous.

Seriously now, could it be when NOD32 is reactivated it is getting a false positive and quarantining/deletng the wblindll???

Just a thought! 

I find it strange that...

yet....

Seems a contradicton in terms to me.

I also have NOD32. Make sure your settings are NOT set to automatically submit suspicious files to Eset. My NOD32 wants to submit that file about 100 times a day. I just keep telling it not to.

I can't seem to find a way to convince it that this file is okay, though.

Seems more and more like NOD32 is misbehaving, doesn't it!  Don't have it myself, so I don't know, but is there a whitelist option that you can use to tell NOD32 to ignore wblind.dll?  If so, it may resolve your problem.

Please update your definitions.

NOD32 should not be incorrectly detecting that file is bad now.

If you have the latest definitions please let us know so we can get them to sort it again.

My definitions are updated, this is not NOD. The first time NOD did it i set it to  restore and exclude the dll .WB7 ran fine after that till i did the windows update. 3 updates were installed, nothing particularly special.

18/11/2009 5:33:33 PM Startup scanner file C:\PROGRA~1\Stardock\OBJECT~1\WINDOW~1\wblind.dll probably a variant of Win32/Genetik trojan cleaned by deleting (after the next restart) - quarantined  

This has not shown up in the log files or quarantine after the 18 of november so NOD is not the culprit My Definitions are :

2009-11-26 15:27

Update 4639 (20091126)

Yes thats the ticket, send me teh dll. Ok i installed wb on one of my spare rigs, it installed fine , copied over the .dll to my machine, rebooted it where the dll was missing again after reboot??? no matter. copied it again, loaded up sevenconfig.exe and clicked on my skin and it applied.

I have no idea where the gd .dll is going and what is deleting it but its there now :

WindowBlinds version : WindowBlinds 7.0 (build 80 x86)

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 ATI Radeon HD 4870  

Wblind.dll      2009/11/18 13:37:20
Wbsrv.dll      2009/10/07 15:35:18
SevenConfig.exe      2009/11/12 11:16:53
Wbload.exe      2009/11/06 12:44:12
Wbhelp.dll      2009/10/07 15:35:07
Wbui.dll      2009/10/07 15:35:05
Tray.dll           2009/10/21 09:13:19
Screen.exe      2009/11/07 12:39:26

I still maintain it is NOT NOD, its not in the logs and i dont have NOD set up to send stuff  for analysis without asking but i would llike to know where the dll is going still.

Thanks all

s

NOD will be what took the dll out.  Remember once the dll has been 'detected' it will have been deleted and you would have needed to reinstall WindowBlinds to fix it.

Due to the nature of Wblind.dll, it is likely NOD set it to be deleted on next reboot.  Would that have been when you installed the latest Windows updates by any chance?

Yes Neil, i think that is what happened then. I dont see any settings for NOD  to delete it and as i said i did set it to exclude from future scans and restore it but the bit was set anyway?. Doesnt quite explain why it deleted it on the second reboot  and why i couldnt reinstall wb7  4 + times and why NODs action of deleting  is not in the logs. I have checked NODs exclusions and wblind.dll is there alright :

C:\PROGRA~1\Stardock\OBJECT~1\WINDOW~1\wblind.dll

I did edit that to  make sure it pointed to the current dll so I hope we are covered now frakkity frak frak

 I will reboot right now just to see what happens. bleh

Hmm gone again. well time to contact Eset.

Thanks again

s

Have you tried setting it's attributes to read only?

Try reinstalling the dll and then redo the NOD exclusion.

zoobabe...I had a similar issue with a game file that Kaspersky claimed was 'bad'...and deleted it...no matter whether it was in 'exclusions' or not.

Nothing I did would make Kaspersky let me use it.

My bet is...your only solution will be to uninstall NOD TOTALLY....including settings and exclusions and sig files.....replace your wblind.dll and finally reinstall NOD....;)

...with the latest definitions...;)

ugh. You know its less work to just keep copying the dll back into the folder, heck i could just write a script to do it for me every time I reboot, which is not often btw. I'll wait to see what Eset  or Neil says, i put in a ticket to Eset. I thought about changing the atributes of the dll but not sure how that would affect it,

Thanks all

s