wbload.dll
Detected as W32 Trojan
Friday, June 22, 2007 by gavin63 | Discussion: Stardock Support General
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
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
 |
|
Page 2 of 2 | |
|
|---|
Katrinakat
Reply #22 Saturday, June 23, 2007 1:26 PM
I just got the same results from AVG, which scans every day. In my case, however, the suspect files were on Drive D, which has recently been demoted from being my main hard drive--because there seemed to be a virus that no one could isolate. Oddly enough, the original symptoms were these: When I went online, a virus warning would pop up, window blinds would unload, and the internet would be disconnected.
WB seems to be working fine on the new drive, and that pesky "trojan" was not detected there.
Reply #22 Saturday, June 23, 2007 1:26 PM
I just got the same results from AVG, which scans every day. In my case, however, the suspect files were on Drive D, which has recently been demoted from being my main hard drive--because there seemed to be a virus that no one could isolate. Oddly enough, the original symptoms were these: When I went online, a virus warning would pop up, window blinds would unload, and the internet would be disconnected.
WB seems to be working fine on the new drive, and that pesky "trojan" was not detected there.
Ladysarajane
Reply #23 Saturday, June 23, 2007 2:33 PM
Reply #23 Saturday, June 23, 2007 2:33 PM
AVG has the new dat file for the day. I am updating and rescanning my computer now to see if it picks it up.
[email protected]
Reply #24 Saturday, June 23, 2007 3:01 PM
Reply #24 Saturday, June 23, 2007 3:01 PM
As of the 269.9.6/863 6/23/2007 11:08 am AVG update, it was still incorrectly detecting it. I've emailed them again this afternoon. And F-Secure for good measure. The latest Kaspersky updates seem sorted.
Ladysarajane
Reply #25 Saturday, June 23, 2007 4:47 PM
I used that update and it did not detect it this time.
Ummm....seems like my computer cannot find that file. It is strange that Windowblinds is still working for me. Any suggestions on what I should do?
PS...I do have the file wbload64.dll
Reply #25 Saturday, June 23, 2007 4:47 PM
As of the 269.9.6/863 6/23/2007 11:08 am AVG update, it was still incorrectly detecting it. I've emailed them again this afternoon. And F-Secure for good measure. The latest Kaspersky updates seem sorted.
I used that update and it did not detect it this time.
Ummm....seems like my computer cannot find that file. It is strange that Windowblinds is still working for me. Any suggestions on what I should do?
PS...I do have the file wbload64.dll
nukemdomis
Reply #26 Saturday, June 23, 2007 10:02 PM
Reply #26 Saturday, June 23, 2007 10:02 PM
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.
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.
Neil Banfield
Reply #27 Sunday, June 24, 2007 5:34 AM
Reply #27 Sunday, June 24, 2007 5:34 AM
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.
Ladysarajane
Reply #28 Sunday, June 24, 2007 12:46 PM
Reply #28 Sunday, June 24, 2007 12:46 PM
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.
I am surprised that my windowblinds is still working, but any search I do, cannot find the wbload.dll file.
JediJosh
Reply #29 Sunday, June 24, 2007 12:55 PM
Reply #29 Sunday, June 24, 2007 12:55 PM
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.
Neil, any idea why? All the suggestions I have read about don't help.
WeatherBound
Reply #30 Sunday, June 24, 2007 2:49 PM
Reply #30 Sunday, June 24, 2007 2:49 PM
Avg newest update has finally corrected the false positive problem as of 2/24/2007.
nukemdomis
Reply #31 Sunday, June 24, 2007 5:28 PM
Reply #31 Sunday, June 24, 2007 5:28 PM
That's odd. My setup automatically grabs any available update (if any) before running a scan.
WeatherBound
Reply #32 Sunday, June 24, 2007 6:33 PM
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 #32 Sunday, June 24, 2007 6:33 PM
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.
jlesica
Reply #33 Tuesday, June 26, 2007 5:46 PM
Reply #33 Tuesday, June 26, 2007 5:46 PM
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.
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.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
|
|
Page 2 of 2 | |
|
|---|
Reply #21 Saturday, June 23, 2007 10:58 AM
I anxiously await the new update from AVG.
My AVG also auto deleted the file instead of giving me the option, but I don't know if it really did, because WB seems to working fine for me so far.
Thank you for keeping us informed.