Invalid Device Driver VDD

[Al Grotheer]

When I open the "command" window I get the following gripe.

16 bit MS-DOS subsystem

C\WINNT\sys32\command.com\SYSTEM\current control
set\control\virtual device driver VDD

VDD format in registry is invalid.

Choose close or ignore.

If I choose close the window closes. If I choose ignore I
can proceed with using the window. (I do run 32 bit.) Is
this important? How do I get rid of this?

Thanks,

Al Grotheer

 

[Marty List]

- Open the Registry using REGEDT32.EXE (not regedit.exe)

- Go to this key:
HKLM\System\CurrentControlSet\Control\VirtualDeviceDrivers\

- Find this value:
VDD

- Make sure it is a reg type "REG_MULTI_SZ", not "REG_SZ"


If the type is correct, you may have aproblem with the data. See if it
points to any files that don't exist. If you can't find anything wrong, try
looking at this value on another machine with similar software installed.

If all else fails you could export the key so you have a backup, and then
delete just the VDD value. This will get rid of the error message, but it
may break something else. If you recognize the file that is being
referenced, try deleting the value & then reinstalling that application.

 

[Marty List]

Did you try deleting it and re-creating it? Sometimes what the GUI shows
you as "blank" may not actually be blank. Make sure you recreate it as type
"REG_MULTI_SZ".

 

[Al Grotheer]

When I open the \VirtualDeviceDrivers\ window there is
litterally nothing there. There is no VDD or any other
value. I called up the edit screen and put in VDD with
the REG_MULTI_SZ, but then it wanted a key. I had none.

 

[charles]

When I open the \VirtualDeviceDrivers\ window there is
litterally nothing there. There is no VDD or any other
value. I called up the edit screen and put in VDD with
the REG_MULTI_SZ, but then it wanted a key. I had none.

It has happened to me that it showed blank like you describe in regedt32 but
when I looked at it using regedit it showed right. I could delete the false
string from there.

The VDD error hasn't happened here in a while but recurred recently again after
updating some Symantec Norton programs. Does anyone know why this happens? In my
case it has always been (but not necessarily) after a Norton update.