Thanks for the reply. I tried the quickscan as you suggested, although it did pick up on a problem that avast hadn’t pickedup on(not automatically refreshing)it didn’t detect the mdstriat.dll. So I’ll try the thorough scan. Hopefully when I waken up tomorrow I’ll be pleasantly surprised.
Btw the sceduling for bootscan is blanked out with me so I presume(unless there’s a way around it)that this option is offlimits for me.
Unfortunately the anti-malware program didn’t even detect it. The strange thing is when I try to search the directory it says that it doesn’t exist, but Avast does detect it and everytime it gives the same error message when I try to move it to chest.
This is the directory:
C:\Windows\Installer\1777e10.msi\Cabs.w34.cab\MDstriat.dll
Does anybody have any suggestions on how to get round this problem or even to the extent I should be worried about the malignancy of it?
Also I just noticed the Avast scanner has 19/1 as my last scan and I’ve been scanning regularly ???
OK, guys. I’m brand new to this forum, but need help just the same. I’m not running Avast but AVG free. Maybe should be on their forum. Will go there if needed. I’m getting a different error, actually a “threat detected”: “downloader.generic9.AUJP”, located in the same file (system32\MDstrait.dll). AVG can’t “heal” it. Dunno where to go from here. Found this forum using Google. ANY help will be appreciated. My notification just started today, February 17, 2010.
I doubt the anti-malware would find it as it is within two different archives and avast has unpacked both of them where they haven’t.
The problem is the file can’t be extracted from deep within the archives without probable corruption of the archive file. So your only option it to manually remove the complete archive, C:\Windows\Installer\1777e10.msi which contains the other archive Cabs.w34.cab and detected file MDstriat.dll.
Thanks that seemed to help…I’m not sure what that installer was(hopefully I haven’t thrown out the baby with the bathwater :-), or how it got there, does make me think twice about leaving the pc on when I’m not using it though
The installer is either inert (e.g. hasn’t been run) in which case there is no problem as it wouldn’t be essential, or if it had been run that file would likely to be installed somewhere, possibly in the system32 folder. In which case avast would have found this in multiple locations and not just inside the two archive files.
If no one else has access to it no problem leaving it on, but you may want to take extra precautions. Some firewalls allow the user to block all outbound connections, so when you are away nothing can get out. If others have access, ensure that they are all required to log on and that you can have a log off user all you have to do is log on when you come back.
DD26 back with you guys. That file FYI, IS in system32. I’ve been putzing around with it all day. FINALLY got some satisfaction. AVG Free finally removed it “as a power user” whatever that means, but it’s GONE. I also have a “Windows.old” folder and looked there to copy and paste a clean copy of that file into my active/operational system32 folder thinking it’s a necessary system file … no luck, it’s not in the “old” folder. I have to believe the exact filename (MDstriat.dll) is the actual culprit and is the one that needs to be removed. Having said that, my computer has HAD it removed and seems to be working normally once again. If you Avast guys can remove it “as a power user”, I suggest giving that a try … seems to have worked for me.
I am using Windows Vista Home Premium (SP2). I got scary message about Trojan Horse MDstriat.dll from Avg Free, followed the path of DD6, removed as power user. It worked. Thanks.