Article ID: 954070 - Last Review: July 1, 2008 - Revision: 1.0 Message in the Digital Signer field in Device Manager after you install a signed driver on a Windows Vista-based computer: "Not digitally signed"On This PageSYMPTOMSConsider the following scenario:
CAUSEThis problem occurs if the developer uses a customer-defined GUID for a class name that is selected from a Microsoft-defined list of classes (such as BLUETOOTH)
in the .inf file. Note If "Not digitally signed" is displayed in the Digital Signer field in the device properties in Device Manager, this may not be caused by the same issue that is described in the "Symptoms" section. Instead, your driver may not have been signed by the software publisher. If this is the case, you may be able to obtain a signed driver from the software publisher. For more information about signed drivers in Windows Vista and about the steps to take if you do not have a signed driver, visit the following Microsoft Web site: http://windowshelp.microsoft.com/Windows/en-US/help/5622d7d6-531b-4e76-be48-0059d38339c41033.mspx
(http://windowshelp.microsoft.com/Windows/en-US/help/5622d7d6-531b-4e76-be48-0059d38339c41033.mspx)
WORKAROUNDTo work around this issue, use one of the following methods, as appropriate for your situation. Workarounds for end-usersMethod 1If "Not digitally signed” is displayed in the Digital Signer field in Device Manager because of the issue that is described in the "Cause" section, use the Update Driver command in Device Manager to update the driver. To do this, follow these steps:
Method 2Install the driver before you connect the hardware device to the computer.Workaround for driver developersIf "Not digitally signed” is displayed in the Digital Signer field in Device Manager because of the issue that is described in the "Cause" section, change the .inf file to use the Microsoft-assigned GUID for the Microsoft-defined class name. For example, if the Microsoft-defined class name of BLUETOOTH is used, use the already defined GUID for BLUETOOTH, and then re-sign the driver.STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about drivers, visit the following Microsoft Web site: http://windowshelp.microsoft.com/Windows/en-US/Help/703e99fd-96a7-4063-98ee-fce4a7539a251033.mspx
(http://windowshelp.microsoft.com/Windows/en-US/Help/703e99fd-96a7-4063-98ee-fce4a7539a251033.mspx)
For more information about how to update a driver for hardware that is not working correctly, visit the following Microsoft Web site: http://windowshelp.microsoft.com/Windows/en-US/Help/b3c6477e-1111-4b9f-a52a-fffdc51e9c901033.mspx
(http://windowshelp.microsoft.com/Windows/en-US/Help/b3c6477e-1111-4b9f-a52a-fffdc51e9c901033.mspx)
APPLIES TO
| Article Translations
|
Back to the top


