Trojan Hunter triggering NOD 32

Seems from this forum Trojan Hunter is commonly used by others.

I use Eset NOD32 as primary virus program but also have malewarebytes, TrojanHunter and Prevx. They seem to all get along except NOD32 and Trojan Hunter.

Not sure if suspected false positives go here, have also sent to support but since its a popular program may be others with the problem:

Here is log entries from ESET NOD32.

12/1/2009 2:01:40 PMReal-time file system protectionfileC:\DOCUME~1\VALUED~1\LOCALS~1\Temp\Appnd.oszddybnWin32/Too lbar.AskSBar potentially unwanted applicationcleaned by deletingAVA-336119\Valued CustomerEvent occurred on a new file created by the application: C:\Program Files\TrojanHunter 5.2\TrojanHunter.exe.

12/1/2009 1:18:22 PMReal-time file system protectionfileC:\DOCUME~1\VALUED~1\LOCALS~1\Temp\Appnd.tvhhtfftWin32/Too lbar.AskSBar potentially unwanted applicationcleaned by deletingAVA-336119\Valued CustomerEvent occurred on a new file created by the application: C:\Program Files\TrojanHunter 5.2\TrojanHunter.exe.

11/28/2009 4:02:16 PMReal-time file system protectionfileC:\DOCUME~1\VALUED~1\LOCALS~1\Temp\Appnd.xummcebeWin32/Too lbar.AskSBar potentially unwanted applicationdeletedAVA-336119\Valued CustomerEvent occurred on a new file created by the application: C:\Program Files\TrojanHunter 5.2\TrojanHunter.exe.

11/28/2009 7:27:16 AMReal-time file system protectionfileC:\DOCUME~1\VALUED~1\LOCALS~1\Temp\Appnd.swhelwieWin32/Too lbar.AskSBar potentially unwanted applicationdeletedAVA-336119\Valued CustomerEvent occurred on a new file created by the application: C:\Program Files\TrojanHunter 5.2\TrojanHunter.exe.

Comments on the TrojanHunter Forum:
During the TH scan, TH is unpacking CABs and other packed files. During the unpack, it stores the files in the TEMP directory. NOD32 is detecting one of the TEMP files as malicious.

Why doesn't NOD32 detect this during its own scan? Because it is not unpacking and thoroughly checking what is in the packed file during its own scan.

Until NOD32 corrects this issue, you may wish to temporarily disable NOD32 during TH's scan. An inconvenience, yes, but that is about the only way to stop it.