PDA

View Full Version : Lots of locked files. Should I be worried?


Chippy
May 15th, 2005, 12:45 PM
I was just surfing looking for a Nora Jones midi file, when I think I may have come across a trojan. Java fired up and Firefox locked up on me, but I could hear the disk thrashing away, which worried me. NOD reported nothing.

So I shutdown and rebooted and two strange things happening. First, Explorer shut itself down with a DEP error. Its never done that before. Also, if I do a full NOD32 scan, I get all these locked files:

http://www.wilderssecurity.com/supportfiles/locked-files-p459682.gif

NOD has never shown that before. The only locked file I have ever seen was pagefile.sys! So I rebooted and tried again. This time, Explorer is OK, but I still get all these locked files.

I am concerned that perhaps something nasty is "lurking" in the locked files.

Questions: Should I be worried? Why all the locked files? What should I do?

Thanks in advance for any help and advice.

Chip

snowbound
May 15th, 2005, 01:01 PM
The (file locked)[4] is normal. I get that when i scan too.

http://www.wilderssecurity.com/showthread.php?t=55865



snowbound

Matt_Smi
May 15th, 2005, 01:15 PM
I also get those, I actually recognize some in your screenshot. I get more than that too; there are also files in my Ad-Aware and Spybot folder that are locked. They are normal and nothing to worry about, and from what I understand malware cannot get in there.

Chippy
May 15th, 2005, 01:20 PM
Thanks guys.

Strange thing is though - why didn't I get these locked file errors before?

Chip

Matt_Smi
May 15th, 2005, 01:25 PM
When I first got NOD and ran a scan with "stock" settings I only got like two of these, but after I changed to "extra" settings I got a ton more. Did you change any settings in the program?

Chippy
May 15th, 2005, 02:12 PM
{QUOTE-> When I first got NOD and ran a scan with "stock" settings I only got like two of these, but after I changed to "extra" settings I got a ton more. Did you change any settings in the program? <-QUOTE}

I dunno - I can't recall doing so. What do you mean by "extra" settings?

Thanks

Chip

snowbound
May 15th, 2005, 02:16 PM
{QUOTE-> I dunno - I can't recall doing so. What do you mean by "extra" settings?

Thanks

Chip <-QUOTE}

http://www.wilderssecurity.com/showthread.php?t=37509


snowbound

Matt_Smi
May 15th, 2005, 02:22 PM
See the "extra settings for NOD32" sticky at the top of this forum. They are just settings to make NOD more efficient.

alglove
May 15th, 2005, 11:07 PM
By the way, almost all of those locked files (*.dat, *.dat.LOG, and C:\Windows\system32\config\* pertain to the Windows registry. The reason they are locked is because Windows is busy using the registry. This is totally normal.

The other file, MountPointManagerRemoteDatabase, has something to do with the NTFS file system.

rumpstah
May 15th, 2005, 11:30 PM
Only if you have one like this.

Holden4th
May 18th, 2005, 04:55 AM
{QUOTE-> Only if you have one like this. <-QUOTE}

what if you scan insafe mode? Do some of the locked files not appear because they aren't being used by the computer when safe mode is activated?

alglove
May 18th, 2005, 03:16 PM
That is correct, Holden4th.

jayt
May 18th, 2005, 05:22 PM
It would still seem that there should be some way to exclude scanning all these locked and password protected files (without using some arcane switch or going into safe mode to scan). Many other AVs have such a feature. Even the free ones like antivir has such a feature. Is it not possible?

jayt
May 19th, 2005, 11:37 AM
bumpup

Stephanos G.
May 19th, 2005, 11:41 AM
I guess not at the moment ;D

Blackspear
May 19th, 2005, 04:59 PM
From memory, it is to do with having "Scan All Files" ticked in the Nod32 scanner setup.

You could always add to the Future Changes to Nod32 thread, that a tick box be added to not display the locked files unless infected.

Cheers ;D

alglove
May 19th, 2005, 06:13 PM
But how can you know if a file is infected, when the file is locked and therefore not available for scanning?

jayt
May 19th, 2005, 08:22 PM
{QUOTE-> From memory, it is to do with having "Scan All Files" ticked in the Nod32 scanner setup. <-QUOTE}

Thank you Blackspear. :) Unticking "scan all files" does do the trick. And I agree with alglove, what is the point in scanning a file if it is locked or password protected?
I guess my only question now is: does unticking the "scan all files" leave me less protected?

windstrings
May 22nd, 2005, 05:38 PM
It always scanned them before... with your old configuration you just didn't have the "scroll files" ticked.