![]() |
|
#1
|
|||
|
|||
|
It seems to scan my hard drives fine but once it gets to my external hard drive it gets stuck the recycle bin on it.
The funny thing is the recycle bin is empty from what i can see. Well i tried scanning it again for 12 hours last night, when i came back today i got a popup of 3 infiltrations which i set to delete, but the scanner had gotten stuck scanning the recycle bin again, and i have no idea if ESET has managed to delete those files properly...actually those files still seem to be there so i guess not... |
|
#2
|
||||
|
||||
|
i would copy external hard drive content to internal drive (nod32 will scan while copying) and then format the external drive
|
|
#3
|
|||
|
|||
|
Why? .
|
|
#4
|
||||
|
||||
|
because its infected
|
|
#5
|
|||
|
|||
|
So why cant ESET scan it?
|
|
#6
|
||||
|
||||
|
dunno, try to scan it in safe mode or use ESET RescueCD
|
|
#7
|
|||
|
|||
|
Tried scanning it in safemode but it doesnt seem to remove anything. At the end of the scan the command prompt window simply closes. I get no options whatsoever.
|
|
#8
|
||||
|
||||
|
Quote:
use parameters |
|
#9
|
||||
|
||||
|
Enable the "Log all files" option in the ThreatSense engine parameters, so you can be able to see the progress more detailed.
this is because you probably have many files on your PC (yes, including the archived files!). |
|
#10
|
|||
|
|||
|
When running in safemode it seems to automatically use the command line "auto" so im not sure if that helps....
|
|
#11
|
|||
|
|||
|
BUMP can i get a official response on why ESET cannot scan my removable drive?
|
|
#12
|
|||
|
|||
|
Download Procdump, disable self-defense and restart the computer. Reproduce the problem. Create a dump of ekrn.exe by running "procdump -ma ekrn.exe" and supply the dump to ESET for perusal.
|
|
#13
|
|||
|
|||
|
Here you go. This one seems to have hanged while trying to scan a .jpg file on my E drive(internal hard disk).
For some reason the forum doesnt allow uploading of procdump files so... -http://www.mediafire.com/?7tftrf8676vjnyf- |
|
#14
|
|||
|
|||
|
bump .
|
|
#15
|
|||
|
|||
|
You posted it in Friday's noon and now is Monday evening. The first work day of this week is tomorrow so please bear with us and give the developers time to have a look at the dump.
|
|
#16
|
|||
|
|||
|
Hmm, any news so far?
|
|
#17
|
|||
|
|||
|
The dump showed that D:\SC2\rzr-scii.iso was being scanned at the moment you generated it. ISO files can be very large and scanning them may take even an hour or more, depending on the type and number of files inside. The scan was run with older modules while newer ones were already used by ekrn (perhaps you updated while the scan was running).
If the problem occurs when scanning G: drive, make sure no other scans are running concurently. We'd also need to know if all on-demand scanner logs are in the finished state and none of them is in progress when you observe problems with "hanging". Also create a Procmon log from the moment the problem occurs which should shed more light as to what operations are actually being performed. Last edited by Marcos : November 18th, 2010 at 09:11 AM. |
|
#18
|
|||
|
|||
|
Quote:
What do you mean by this? |
|
#19
|
|||
|
|||
|
Quote:
|
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|