TDS (unpack) error: Locked file

Hi , TDS gives this error:

23:44:32 [Locked File] Couldn't open c:\program files\here-tds3\xdynamic\tds.unpk\core10k.exe for read access, file is locked

The problem started when my pc was infected with a trojan,
and both NOD32 and TDS found that one, almost at the same time.
Both complained that the file was locked.
The trojan is removed, but now there are a lot of files,
which give this errors (example above).
It looks to me if TDS has a problem with unpacking files NOW, (same files were scanned without a problem before)

BTW: Process Guard,NOD32 and TDS, SpywareGuard and SpySweeper are active.

Is this a known problem?

Albert

 

Hi unixmagic, If you can you copy & ZIP the file, please send it to submit@diamondcs.com.au it can be analysed.
Can you rename the file to something like core10l.bak ? If you cannot then it is probably being held open by another process, in which case boot into safe mode and try it there.
If you can download AutoStart viewer from here: http://www.diamondcs.com.au/index.php?page=products
Run it and from "Main" select Show services & Show drivers then save to notepad and copy / paste into your next post.

Once posted here we can try and see if there is anything else that is causing a problem.

HTH Pilli

 

Hi Pilli,
The strange thing is that the files that give these kind of problems,
are all files in a 'install' directory.
That is a directory where i keep programs that can be installed directly
from that disk/directory.
So those files should never be locked by an process, other then the virusscanner or so.
And the other thing is that those files are there for months, and never gave me a error like this.

So i rebooted (first time in months) and re-installed TDS-3,
now i am testing ...(renaming etc.)
if the problem is still there i'll send you a exmple of a file wich gave me this kind of error.

Regards,
Albert

 

Imagine the following: NOD32 is proteckting (locking) a detected file, so no othjer scanner can access the file anymore.
Close NOD32 or other scanners themoment while scanning with TDS. This is with all scanners among each other with a resident part. If TDS is just up and not in a scan you can keep it up during scans of other scanners.

The Unp folder is where copies of files are unpacked and should be deleted after that or in a next scan. So what is there can safely be deleted. Note, these are copies so the originals are somewhere on your system in other places.
So you might like to submit what is alarmed on now anyway, as with the many detections recently added it might be possible to refine the databases for that code.

 

Imagine the following: NOD32 is proteckting (locking) a detected file, so no othjer scanner can access the file anymore.
Close NOD32 or other scanners ..

Hi Jooske, this is what caused the problem, after that i've de-installed
the virusscanner, rebooted and the problem was still there.

so, even when no other scanners were active the problem was still there.

No i've reinstalled TDS-3, and the problem is solved, even wih the other
things like the virusscanner running , there is no problem.

Just like it was before the whole thing started.

So for me the problem is solved now ..
===========================

Pilli Thanks for the help, and Jooske 'bedankt ' (Dutch).

eh.. the only thing that is still interr. is what was changed with TDS,
that caused this ?

Albert

 

Albert, have you been infected, crashed badly, anything which could have caused TDS getting corrupted?
(no need to uninstall other scanners of course, only close them temporary!)

 

Jooske wrote: "Albert, have you been infected, crashed badly, anything which could have caused TDS getting corrupted?"

-> No , i feel fine, but my PC had some strange behaviour

Jooske, what happened was, i had a well-known trojan on my pc,
i was expecting that when i downloaded a file from a website.
But to my surprise NOD32 found this directly when i opened a zip-file.
I wanted to know if/how TDS-3 would react when i scanned the same directory.
Because i run TDS-3 for quitte a while now, but my pc was never infected.
Although one of the things i do for my job, is testing/evaluating/compairing programs.

So i disabled the virusscanner and tried to scan with TDS-3,
then i saw the error for the first time.
So, i expected that although NOD32 was closed-down it still had locked the file.
That is not bad ...
But after removing the mentioned trojan file(s) , i started to have problems with scanning the normal (read: no-trojan) files mentioned
earlier.

And now i have re-installed TDS al the problems are gone.

So yes, the situation above (read: NOD32) corrupted TDS for some reason.

And i've been running the mentioned programs, for quitte a long time,
all at the same time, never had a problem.
Probably because my pc was never infected.

Albert