SetupAPI logs an error if it detects an unsigned or incorrectly signed driver file prior to committing the file queue. This occurs if the driver does not have a catalog file or if the file’s signature and the corresponding signature in the driver’s catalog file do not match. The following example contains the messages that SetupAPI logs in this case. To correct the error, determine the driver’s catalog file and verify the file’s signature.
@ 12:32:12.370 #I340 Extracted file "blender.dll" from cabinet "Cabinet_File_Path\Cabinet_File_Name.cab" to "C:\WINDOWS\System32\SET62.tmp" (target is "C:\WINDOWS\System32\blender.dll").
@ 12:32:12.390 #I336 Copying file "C:\WINDOWS\System32\SET62.tmp" to "C:\WINDOWS\System32\blender.dll" via temporary file "C:\WINDOWS\System32\SET63.tmp".
@ 12:32:12.410 #E361 An unsigned or incorrectly signed file "C:\WINDOWS\System32\SET62.tmp" will be installed (Policy=Ignore). Error 1168: Element not found.
In the previous example, the #I336 and #E361 messages report that the blender.dll file was either unsigned or incorrectly signed.
Share with your friends: | 
