I am getting this error message regularly, I think whenever I want to
install a new device.

System\CurrentControlSet\Control\Virtual DeviceDrivers VDD Virtual
DeviceDriver format in the registry is invalid Choose "Close" to
terminate the application

---

Request for Question Clarification by sublime1-ga on 08 Feb 2003 10:16 PST

stevensong...

What operating system are you using?
In Windows 2000, the registry entry for VDD is here:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers]
There should be a string value 'VDD', type 'REG_MULTI_SZ', with
a hex value '00 00 00 00', which will look like this:
'0000   00 00 00 00         ....'

I suspect it will be similar for other Windows operating systems.

If you are not *very* comfortable viewing and editing the
registry, you may not want to try this, since creating an
error in the registry can produce severe problems (much like
you now describe). There is really no reason to be intimidated
as long as you don't make any changes, intentional or otherwise,
to the registry. If you feel comfortable, then go to 'Start'
--> 'Run', type 'regedit' and hit 'Enter'. Then navigate the
registry tree to the location given above and note what is 
currently there under the 'VDD' entry, especially noting any
differences from what I have described above.

Please come back here and report what you have found, along
with your operating system. If what you find is corrupted,
I or another researcher will probably be able to tell. 
Additionally, if the entry seems corrupted, a researcher
running the same Operating System as you will be able to
export a valid entry and upload it to an area where you 
will be able to download it as a '.reg' file, say, 'VDD.reg'.
Once you've downloaded it to your computer, you can just
right-click on it and select 'merge'. This should repair
the corrupted entry in your registry.

sublime1-ga

---

Request for Question Clarification by sublime1-ga on 08 Feb 2003 10:22 PST

stevensong...

I neglected to mention that, in order to view the
(anticipated) hex 'value' of the 'VDD' 'REG_MULTI_SZ'
entry, under 'VirtualDevice Drivers', you will need
to double-click on that entry, titled 'VDD', under
the 'Name' column, on the right of the registry viewer.

---

Clarification of Question by stevensong-ga on 08 Feb 2003 11:56 PST

Thanks for responding

I am running Windows 2000 Professional 

I have looked at the file you suggested and, under value data, the
line that starts 0000 is followed by 43 00 3A 00 5C 00 50 00 C.:.\.P.

Under 0000, the next lines are 0010, 0018, 0020, 0028, 0030, 0038,
0040

Am I looking in the correct place?

Regards

stevensong

stevensong...

Of course, I can't verify that you're looking in the correct
place...all I can do is point you to the location that I gave
you and assume you are clicking on the 'VDD' entry I referred
to. 

I believe that this is the case, however, so I will point you
to a site where this error, and its resolution, are discussed:

"Issue Details: "System\CurrentControlSet\Control\
 VirtualDeviceDriver.VDD. Virtual Device Driver Format in the
 Registry is invalid. Choose 'Close' to terminate the application."
 Resolution: This error is caused due to an unknown problem that
 exists in the Registry. Clicking on Ignore is a temporary solution
 that should allow the Backpack software to install. The permanent
 solution is to fix your Registry by performing the following:

"WARNING: Using the Registry Editor incorrectly can cause serious,
 system-wide problems that may require you to reinstall Windows
 2000 to correct them. Micro Solutions, Inc. and Microsoft cannot
 guarantee that any problems resulting from the use of the Registry
 Editor can be solved. Micro Solutions has tested the following
 procedure in-house and it has fixed the error in question. However,
 making changes to the Registry should be done at your own risk.
 Micro Solutions recommends that all Registry modifications be
 performed by an experienced Windows 2000 professional!"
http://www.micro-solutions.com/tech_support/issues/341any.html

What follows are instructions for using regedt32, a 32-bit version
of regedit, to delete the current 'VDD' key and replace it with
a new one. This can only be done with regedt32, since only that
version of regedit allows the creation of a 'REG_MULTI_SZ' type
key.

What I will suggest is a simpler way, which is, as I said earlier,
to download a VDD.reg file, which I have uploaded here:
http://www.lucidmatrix.com/uploads/VDD.reg

Just download this file to a directory which you will be able to
locate in Windows Explorer and then right-click on it and select
'merge'. Then reboot and try the installation which was giving
you trouble before. You should have no problems.

To be on the safe side, however, I strongly recommend that you
back up your current settings. You can do this in the same way
that I created the VDD.reg file:

Go to 'Start' -> 'Run', type 'regedit' and hit 'Enter'. Then
navigate the registry tree to the location:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers]
Left-click once on the 'VDD' key (so it is highlighted), and 
go to the MenuBar, up top, and select 'Registry' -> 'Export
Registry File'. Name it VDDold.reg, and save it to a location
you can find again.

Should my solution not solve your problem, you can access 
VDDold.reg, right-click on it and select 'merge', and your
registry will return to the way it currently is. If I've
solved your problem, you can later delete this file.


Please do not rate this answer until you are satisfied that
the answer cannot be improved upon by means of a dialog
established through the "Request for Clarification" process.

sublime1-ga


Searches done, via Google:

"VDD Virtual Device Driver format in the registry is invalid"
://www.google.com/search?q=%22VDD+Virtual+Device+Driver+format+in+the+registry+is+invalid%22

I am new to this but, given that the answer seems to have sorted me
out, I can only rate it as perfect. Thanks veryu much and I will
certainly be using you again (although hopefully not too soon since
that will tend to imply I have another problem