4.3.1Loading Class Installers and Co-Installers: Verbose Logging
The following example illustrates what the loading-class-installers subsection looks like for a Blender device—if the most verbose logging level is set. By reviewing these messages in the SetupAPI log file, you can determine whether the correct installers are loaded.
#-148 Loading coinstaller modules for "Blender_Device_Description".
@ 10:18:56.718 #V132 File "Blender_CoInstaller_File_Path\Blender_CoInstaller_File_Name.dll" (key "Blender_CoInstaller_File_Name.dll") is signed in catalog "Blender_Catalog_File_Path\Blender_Catalog_File_Name.cat".
@ 10:18:56.718 #V146 Using exported function "Blender_CoInstaller_Exported_Function_Name" in module "Blender_CoInstaller_File_Path\Blender_CoInstaller_File_Name.dll".
In this previous example, the #148 message indicates that SetupAPI is loading a co-installer. The #V132 and #V146 messages specify the particular co-installer, indicate that it is signed, and specify its entry point.
Note
Do not attempt to update a co-installer that is currently in use with another version of the co-installer that has the same name. For information about how to correctly update co-installers, see the “Updating Driver Files” section in the Windows DDK documentation.
Share with your friends: | 
