If you do not have any Symantec product, delete the driver from there. This is why we can’t get rid from NAV so easy…
The Registry “corrupted” keys by NAV are:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\VirtualDeviceDrivers
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\VirtualDeviceDrivers
If the avast! driver was not listed here you would not be protected under DOS (cmd window). The symptoms of this were:
a) into a cmd window it was forbidden to use DOS programs (16-bits). The user just get the prompt after the command and nothing happens, e.g.:
C:\pkunzip -n *.zip {enter}
C:
By the way, with the WinZip Command Line the same effect were noted. This application is the command line version of WinZip 9.0 (www.winzip.com)
b) the cmd window just not ‘change’ its name with the command. For example, In AutoIt 2.64 scripts (the best macro maker for Windows, thanks to Jonathan Bennett), sending a ‘Run’ command to cmd windows (e.g.: Run, C:\pkzip.exe -n .zip or RunWait, %COMSPEC% /C copy c:\.zip a:\, hide), the cmd window remains with the title C:\Windows\System32\cmd.exe). The commands (programs) are not executed!
As I said, I do recommend the freeware Registrar Lite to browse the Registry. It’s a Freeware!
The solution is manually editing these Registry keys (corrupted by Symantec products or RNAV2003: see rnav_log.txt which is generated by the application):
A Registry key must have this format: string,0,string,0,string,0,…,0,0
But in my case it looks some idiotic program did:
string,0,0,string,0,string,0,0
You may have to export the key in the file, remove one zero from the first double zeros.
Be sure the strings end with double zeros.
Then import it back and reboot.
You should then see there the record for <avast directory>\aswMonVd.dll similar to this:
Key name: HKLM\SYSTEM\ControlSet001\Control\VirtualDeviceDrivers
Value name: VDD
Type: REG_MULTI_SZ
Type number: 00000007
Text: <avast directory>\aswMonVd.dll
There must be the aswMonVD.dll in your avast directory too.
For me, this adventure was enough and works. Good luck and pray!
If you don´t believe me, try eicar test from DOS (cmd window). See either DOS under XP / NAV. Good luck. 