avast! 4.6.603 Final released!

If you're running Windows 2000 or XP you don't have to configure anything. Just set Normal or High Sensitivity and you're ready

 

I'm trying the Pro version, and this problem still occurs

I redownloaded the English Pro version, selected the Change process, and restarted my system.

I restarted, and I see the C:\Windows\System32 window open, and I checked the start-up value, and it was blank (the same as the first time).

 

Can you check the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem for a value NtfsDisable8dot3NameCreation. Does it exist? If so, what value does it have?

Thanks
Vlk

 

It exists, and it has a value of:

0x00000001

Thanks for your prompt responses ^_^

 

Geez, who put it there?!?! This is the cause of the problem.
Delete the value, restart the machine, and retry the Repair process in avast.
This will solve the problem.

 

All fixed!

Thanks for your help!

Why did that registry value cause this problem?

 

Is this versions detection rates comparable with nod32? The previous version failed pretty badly according to the vb! results...
If it is as good, I may consider getting it for one of my pcs.

mtia
#
Toby.

 

no my cpu has wins 98

 

hi
can i ask a question
i noticed that avast new version opens a lot of files on wxp! ( for example clicking on a directory scan tons of exe & dll)
but not in w2k
why?
can i avoid this in wxp?