“The driver software you are installing has not been
properly signed with authenticode technology. Therefore,
Windows cannot tell if the software has been modified
since it was published. The publisher’s identity cannot
be verified because of a problem:
The parameter is incorrect”


Resolution is to set Key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Non-Driver Signing\Policy to 00.

“The driver software you are installing has not been
properly signed with authenticode technology. Therefore,
Windows cannot tell if the software has been modified
since it was published. The publisher’s identity cannot
be verified because of a problem:
The parameter is incorrect”


UPDATE:  You probably need to edit this via Group Policy instead  — this is an example of the group policy for kernel mode drivers for printers:



1. Open Group Policy Management and open the Default Domain Controllers
policy. NOT the default domain policy.
2. Double-click Administrative Templates, and then double-click Printers.
3. Right-click Disallow installation of printers using kernel mode drivers,
and then click Properties.
4. In the Setting tab, click Disabled, and then click OK.

Explanation of the ‘Disallow installation of printers using kernel mode
drivers’

Determines whether printers using kernel-mode drivers may be installed on
the local computer.  Kernel-mode drivers have access to system-wide memory,
and therefore poorly-written kernel-mode drivers can cause stop errors.


 

 

3 Responses to Inplace upgrade from SBS2k to 2k3 and get an error regarding driver not signed?

  1. Karen Christian says:

    We’ve seen lots of these notifications during a clean install (swing migration) and have had to answer ‘Yes’ to continue after each. Is this a result of the particular media being used? We have not experienced this in the past. It is present when using CD1 and CD2. The source of this media was MS from the Sweet Success Program (for retail SBS2K3 Premium). Checking other servers using SBS2K, SBS2K3 clean install and SBS2K3 inplace upgrade show the value as 00 as noted above.

    Thanks for posting this. It is somewhat comforting to see we are not the only ones to come across this oddity.

  2. We had exactly this on a SBS 2000 to SBS 2003 upgrade. The registry change stopped this.

    Thanks forthe info

  3. Krop says:

    Upgraded to server2k3 enterprise and had this problem, the key change fixed it, thanks very much!