t$m files

[mudsharky]

That explains how I could have search engine log entries appearing inside these files... I have copies of those files released (by Yahoo, was it?) for research usage. They are huge. I wonder why AVG would choke on them and cause a reboot though! To further test this, I have shut off the sched scanning of my PC and should therefore not see anymore of these files appear.

(I'll know in a week when I get back home from a short holiday and turn my machine back on.)
Thx
RG

[MarkA]

I also decided to turn off the AVG scheduled scan to see what would happen.

No new t$m files!

I would say this is pretty good evidence that AVG is having a problem with it's scheduled scan.

Mark

[Staff]

I was confident of it on your last post and added .T$M to the FILExt database as being AVG-related and pointing to this thread. I've seen several searches for that file extension in the logs and have been following this thread closely because of that. You've helped more people than just the few participating here. Thank you.

[MarkA]

Grisoft support is working with me to try to resolve this problem.

I have a couple questions for everyone that has experienced this problem. Hopefully your answers will help us locate the source of this problem. If you have the problem with t$m files, can you please post responses to these questions:

1. Which version of Windows are you running, and which service pack?
2. Do you have AVG setup to scan ALL file types (not just infectable files?)
3. When you have a t$m file left over that is NOT 0 bytes in size: Is the drive that contains your TEMP directory full?

Thanks!

I'll post any new significant information, and of course, the final resolution to the problem.

Mark

[mudsharky]

Running w2k sp4
AVG setup to scan ALL file types
The drive that contains my TEMP directory has plenty of room.

[MarkA]

I'm writing to report that this issue has been resolved by Grisoft.

The problem had to do with the way AVG handles files that are locked. When a locked file (or archive (.zip)) is encountered, AVG will make a copy of the file in the TEMP directory. AVG then scans the copied file that is in the temp directory. There was a problem with this process, but only when run from a scheduled scan.

If the problem comes up again I would suggest contacting Grisoft.

Mark

[Staff]

Thank you for posting the results and for following up with the necessary legwork. I'll annotate the database accordingly.

[mudsharky]

Originally Posted by MarkA

I'm writing to report that this issue has been resolved by Grisoft.

The problem had to do with the way AVG handles files that are locked. When a locked file ...

If the problem comes up again I would suggest contacting Grisoft.

Mark

The problem here has NOT been solved! If scanning is enabled these files are still created and the PC still reboots itself. I suppoe I must contact them and work with them hoping they fix it or I'll have to switch to another product.

[mudsharky]

Originally Posted by mudsharky

The problem here has NOT been solved! ... I suppoe I must contact them and work with them hoping they fix it or I'll have to switch to another product.

Nevermind. They will not entertain any support requests from me as I am not a registered user.

[Staff]

Uninstall the software and then download and install the latest version. If they've fixed the software that should solve the problem.