On 5/19/2009, Hagen Patzke wrote:
This is what I remember from my WinXP and Vista USB install tests:
The “Driver” entry in Device Manager will not be updated -
nor will the
device name as displayed in device manager - if you don’t remove a
device class completely from the Windows installation (*) but just
update the driver (using a newer INF file).
On 5/20/2009 2:57 AM, Michal Vodicka wrote:
Sorry, that’s not right. This entry is updated after successful driver
update. Nothing needs to be removed. You’re right it may not be the same
version as the current binary (which can be changed) but it is the
version from INF from the last driver installed correct way via DM or
Setup API. I just have a pleasure to work with this API from the hell
and this part seems to work correctly (at least at XP SP3 and Win7).
Thanks for the info, Michal - I remember pulling some hair out when
testing in 2006/2007: updating the version number (DriverVer) in the INF
file did not always help, also my new device name was not always
displayed, if a device class entry with the same ClassGUID already
existed before, also the device icon was not updated (Vista only).
The information was always correctly updated on a fresh install - only
when updating an existing driver I noticed the described behaviour.
Hmmm… for device name and icon, this MSDN entry seems to back my memory:
http://msdn.microsoft.com/en-us/library/ms794537.aspx
“Because the system processes a ClassInstall32 section only if a class
is not already installed, you cannot use a ClassInstall32 section to
reinstall or change the settings for a class that is already installed.”
[Guess what’s in the ClassInstall32 section? The AddReg directive for
driver name and icon. :-)]
Next possibility I’ll have to re-check that DriverVer updates the driver
version displayed on the first device manager info page.