gavin63 gavin63

wbload.dll

▼

wbload.dll

Detected as W32 Trojan

from WinCustomize Forums
Hi there

I am running Zone Alarm Firewall with Antivirus and for some reason it detected wbload.dll in my system32 folder as a trojan and quarantined it. I have restored the file back as it is a dll process to load Window Blinds

Anyone else had this problem at all and is there a work around
18,614 views 33 replies
Reply #26 from Stardock Forums Top
AVG also found wbload to be be a Trojan. While searching I found this post and decided to post a screenshot of the detection.



AVG reported the file as Trojan horse Generic5.ajz and right now I have no clue what to think. Here's another screen shot showing the final results as part of a small post over at The Vault forums.
Reply #27 from WinCustomize Forums Top

As I have already explained, AVG is flagging this file incorrectly.  They have been contacted about this and hopefully they will correct this in their definition updates soon.

The AV companies should check their definitions a little more carefully before releasing them.

Ashes of the Singularity II
Reply #28 from Stardock Forums Top
Neil, should I uninstall Windowblinds and reinstall it or how should I replace the missing wbload.dll file? Is there anyway I can just replace it?

I am surprised that my windowblinds is still working, but any search I do, cannot find the wbload.dll file.
Reply #29 from Stardock Forums Top
I had the same problem when I first installed WB 5.51. AVG saw wbload.dll as a virus so I hit ignore, disabled AVG and reinstalled WindowBlinds and AVG hasn't picked it up as a virus since. Although I still cannot get WindowBlinds to work on my Windows Vista Premium system. I still get the Reboot message every time I attempt to access it.

Neil, any idea why? All the suggestions I have read about don't help.

Reply #30 from WinCustomize Forums Top
Avg newest update has finally corrected the false positive problem as of 2/24/2007.
Reply #32 from WinCustomize Forums Top
That's odd. My setup automatically grabs any available update (if any) before running a scan.


Try doing it yourself. I just did it this morning and it gave me an update. I then scanned the same files and everything came out good.
Reply #33 from WinCustomize Forums Top
A few days ago I had a detection of Trojan.Win32.Agent.es in the wise_post.exe file in the \stardock\object desktop\windowblinds path using Zonealarm SS 7 (kaspersky engine). The file was quarantined, but after updating my definitions, restoring the file and doing a new scan, the file shows up clean. I submitted the file to the virusscan.jotti.com site and the file was again reported as clean.

Did anyone else have this trouble? I'm just trying to be thorough because no one had mentioned wise_post.exe and I did not have a problem with wbload.dll. I'm guessing false positive, but want to be sure.