TESTED "x64" security software..

Any task running with a *32 is 32 bit. No matter what directory it resides.

Yes, Vista x64 is supposed to put all fully 64-bit coded programs in /Program files/ and all of the 32-bit coded programs in /Program Files (x86)/ but this isn't always the case. Besides, you can force most installations into any folder you wish.

The bottom line is what you see in Task Manager. If it has a *32, it's 32 bit. If it doesn't, it's 64 bit.

I'm sorry, but I really fail to see the use for this thread except to spread mis-information and confusion.

Just because an AV app written to be 64bit compatible has a process that runs in 32bit mode, doesn't mean you're any less protected or that the scans are only half as fast, so this topic is rather pointless.

It's personal preferrence that is driving this thread, as you've pointed out in another thread that you don't like to see any "*32" processes in your 64bit Os's Task Mgr, but you're trying to make it look like these programs are less than capable in this thread and it's simply not true.
These are fully 64bit capable programs and perform as good as, if not better than in some cases, any of the programs you call "True 64bit". If you have any proof of anything different, please post it and any links to confirmation of the data you provide. Otherwise, I think this thread should be closed myself, or at least unstickied and allowed to fade out.

This is NOT an attack on you Ginter and is not meant to start any problems between us, that's the last thing I try to do on any forums I frequent, but I see this thread as being somewhat unfair to the less savvy users who may believe that their AV or other security app is not securing them properly, even tho it's written for 64bit. They may be inclined to drop a perfectly good, if not superior, security product that they paid for and go and purchase another one for no real reason. Kind of a waste of money and time and I wouldn't like to see that happen to anyone here.

I see every point in this thread and I thank the OP for starting it. It's to show which security applications (AV, firewall and anti-spyware) are true 64-bit applications.

Even though WOW64 helps support 32-bit applications you ideally want to be running 64-bit software on a 64-bit OS. I run 64-bit Crysis (obviously). I run 64-bit VirtualBox as well. You don't seem to understand this at all?

Hi Jon

The problem here is that these are not 32bit applications running in an emulated 32bit environment on a 64bit OS, these are applications written to be fully 64bit compatible that happen to have a process running in 32bit.
The only "Testing" that was done here was to install the AV Program, open Task Mgr, and see if anything related to the AV program listed a process with *32 behind it...that's not testing for AV products in my book, nor in any book I know of.
In another thread here, this OP has actually called any AV product with a 32bit process as "Garbage", without any regard as to how they actually tested on 64bit systems by the world's most respected Independant AV Test labs.

So, what is a "True 64bit application"?
Is it one that uses all the aspects of a 64bit data throughput, or is it one that runs perfectly well under a 64bit environment?
Well, while one might think that an AV product that doesn't list any process as running in 32bit mode, would obviously run it's scans at a much faster rate than one that does, that's simply not true...in fact I would offer here that almost every AV product out today still uses the same scanning engine as their 32bit product does, even those ones who do not list one of their processes as a 32bit one.

So where is the advantage here?
Nowhere, and it's actually detrimental to less security savvy users who may think that Eset's NOD32 may be garbage because it's ekern process is listed as *32 in Task Mgr. Then they just may uninstall what is probably (and easily shown to be such) the top ranked AV product for 64bit Vista, and install something that is nowhere near as secure just because it doesn't have a process with an "*32" behind it in Task Mgr.

To me, and to many others here as well, that's simply not an acceptable reason, it's not "Official" and it's certainly not "Testing" to what would be considered an acceptable level by the Security Industry's standards.
This thread was unstickied so it would fade away for exactly these reasons, let's please let it go from here on.
If you have any hard data to prove otherwise, that any of the listed AV products with a 32bit process listed in Task Mgr offers less protection than one which doesn't because of this, please feel free to start another thread on the subject and we'll go from there.

I installed eTrust Internet Threat Management 8.1 on Vista Business x64.
e Trust Antivirus agent is ok, but Pest Patrol is not supported.

I use eTrust ITM at work. I would never use it at home. Look at Trendmicro's solutions. Avast Pro 4.8 is excellent anti-virus.

Have you used symantec corporate and does it support 64bit?

I have - Symantec Endpoint Security ver 11, which has both 32 bit and 64 bit installers.

*However* I think the installer *itself* may be 32 bit, as the '64bit' installer still tried to install to %ProgramFilesx86%....

I use avast 64bit which links into outlook and I will be downloading comodo firewall tonight, it is now supposed to be 64bit complient.

Be sure not to install the search toolbar / sponsor / whatever it calls itself....