Driver installation failed, Error 39, Vista 64 bit
Locked
12
12
 
|
Hello,
I have sucessfully installed LibUsbK on XP (32 bit) and Windows 7 (32 and 64 bit) and Vista (32 bit) but failed on Vista 64 bit. Unfortunally it is a customer PC in greece and I have no access to the unit. He tried to follow my installation instruction and the result is an "Error 39" (unable to start the driver, or something is missing). The platform is Intel (4 cores) and Vista 64 Ultimate. The device is listed in the device manager, but marked with an yellow excalamation mark. He was able to install the driver on a different XP pc, just to be sure that everything is in place. Any ideas? Best regards Ekkehard |
Re: Driver installation failed, Error 39, Vista 64 bit
|
On Tue, Dec 20, 2011 at 3:59 PM, Ekkehard
<[hidden email]> wrote: > Hello, > I have successfully installed LibUsbK on XP (32 bit) and Windows 7 (32 and 64 > bit) and Vista (32 bit) but failed on Vista 64 bit. > Unfortunately it is a customer PC in greece and I have no access to the unit. > He tried to follow my installation instruction and the result is an "Error > 39" (unable to start the driver, or something is missing). The platform is > Intel (4 cores) and Vista 64 Ultimate. > The device is listed in the device manager, but marked with an yellow > exclamation mark. > He was able to install the driver on a different XP pc, just to be sure that > everything is in place. > > Any ideas? You can ask the customer to install the debug version of the driver and use Debugview to check if that can give some hints. http://code.google.com/p/usb-travis/downloads/list libusbK-3.0.5.1-setup-chk.exe or libusbK-3.0.5.1-bin-chk.7z DebugView: http://technet.microsoft.com/en-us/sysinternals/bb896647 BTW, this may well be a device problem.Have the customer tried the device under Vista or Windows 7? -- Xiaofan ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
|
I will try the debug version.
The device is ok, it runs (with LibUsbK), under XP 32 bit, Vista 32 bit, Windows 7 32 bit and Windows 7 64 bit. Best regards Ekkehard |
Re: Driver installation failed, Error 39, Vista 64 bit
|
Also, please have try to obtain the C:\Windows\inf\setupapi.dev.log from
the customer's machine, at it may offer some insight as to why Windows cannot start the driver. Each of the driver installation steps are logged there, so if the problem was with the installation, you should see a detailed error there. Regards, /Pete ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
|
Thanks Pete, this is a nice idea! I just checked this file(s) on my PCs - very informative!
As soon as I have the clients file with more detailed information, I will post again. Greets Ekkehard |
|
In reply to this post by Xiaofan Chen
On 12/20/2011 1:19 AM, Xiaofan Chen wrote:
> On Tue, Dec 20, 2011 at 3:59 PM, Ekkehard > <[hidden email]> wrote: >> Hello, >> I have successfully installed LibUsbK on XP (32 bit) and Windows 7 (32 and 64 >> bit) and Vista (32 bit) but failed on Vista 64 bit. >> Unfortunately it is a customer PC in greece and I have no access to the unit. >> He tried to follow my installation instruction and the result is an "Error >> 39" (unable to start the driver, or something is missing). The platform is >> Intel (4 cores) and Vista 64 Ultimate. >> The device is listed in the device manager, but marked with an yellow >> exclamation mark. >> He was able to install the driver on a different XP pc, just to be sure that >> everything is in place. >> >> Any ideas? I have just tested libusbK on Vista 64bit and everything is working correctly on my machine. I'm using the CYStream firmware. > You can ask the customer to install the debug version of the driver and > use Debugview to check if that can give some hints. > http://code.google.com/p/usb-travis/downloads/list > libusbK-3.0.5.1-setup-chk.exe > or libusbK-3.0.5.1-bin-chk.7z > It may simplify things to give the customer the 64bit libusbK.sys and have him copy it to Windows\System32\Drivers manually. > DebugView: http://technet.microsoft.com/en-us/sysinternals/bb896647 > > BTW, this may well be a device problem.Have the customer tried > the device under Vista or Windows 7? > I suspect one of the following two scenarios is causing this problem: 1) The device is drawing more power than the host has to offer. 2) The device is consuming more bandwidth than the host has to offer. Maybe you can ask the customer to disconnect *all* other USB devices. Regards, Travis ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
Re: Driver installation failed, Error 39, Vista 64 bit
|
|
On Tue, Dec 20, 2011 at 8:11 PM, Travis <[hidden email]> wrote:
> I suspect one of the following two scenarios is causing this problem: > 1) The device is drawing more power than the host has to offer. > 2) The device is consuming more bandwidth than the host has to offer. > > Maybe you can ask the customer to disconnect *all* other USB devices. > Usually the above two will result in Code 10 but not Code 39 error. Reference: Explanation of error codes generated by Device Managerhttp://support.microsoft.com/kb/310123 (Says XP, but should work for Vista and Win7). -- Xiaofan ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
|
Some more light in the dark. I was able to get the file "setupapi.dev.log" from the target machine.
It shows problems regarding the signature of the driver files. I created the setup on a Windows 7 (64 bit) machine. On Windows 7 (64 bit) it runs smooth. On XP it shows initially "unsigned" but does not prompt for "really sure to install unsigned driver" (and works) On Vista (32 bit) it comes up with a red unsigned driver alert, but let the user decide and continue (and works) On Vista (64 bit), same as Vista (32 bit) but dont work. It seems to me that the signature check in Vista is different from Windows 7 and blocks from running Best regards Ekkehard {_SCAN_FILE_QUEUE} flq: ScanQ flags=620 flq: SPQ_SCAN_PRUNE_COPY_QUEUE flq: SPQ_SCAN_FILE_COMPARISON flq: SPQ_SCAN_ACTIVATE_DRP flq: ScanQ number of copy nodes=5 flq: File 'C:\Windows\system32\drivers\libusbK.sys' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem95.CAT'. flq: {SPFILENOTIFY_CABINETINFO} flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)} flq: {SPFILENOTIFY_FILEEXTRACTED} flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)} ! sig: VerifyTrustFailed for C:\Windows\system32\drivers\libusbK.sys. ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. cpy: DrpSetRegFileProt 'C:\Windows\system32\drivers\libusbK.sys' Status=0 Class=OEM Legacy flq: File 'C:\Windows\system32\libusbK.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem95.CAT'. ! sig: VerifyTrustFailed for C:\Windows\system32\libusbK.dll. ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. cpy: DrpSetRegFileProt 'C:\Windows\system32\libusbK.dll' Status=0 Class=OEM Legacy flq: File 'C:\Windows\system32\libusb0.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem95.CAT'. ! sig: VerifyTrustFailed for C:\Windows\system32\libusb0.dll. ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. cpy: DrpSetRegFileProt 'C:\Windows\system32\libusb0.dll' Status=0 Class=OEM Legacy flq: File 'C:\Windows\syswow64\libusbK.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem95.CAT'. ! sig: VerifyTrustFailed for C:\Windows\syswow64\libusbK.dll. ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. cpy: DrpSetRegFileProt 'C:\Windows\syswow64\libusbK.dll' Status=0 Class=OEM Legacy flq: File 'C:\Windows\syswow64\libusb0.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem95.CAT'. ! sig: VerifyTrustFailed for C:\Windows\syswow64\libusb0.dll. ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. cpy: DrpSetRegFileProt 'C:\Windows\syswow64\libusb0.dll' Status=0 Class=OEM Legacy flq: ScanQ action=200 DoPruning=32 flq: ScanQ end Validity flags=620 CopyNodes=0 dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)} and a bit later Device not started: Device has problem: 0x27: CM_PROB_DRIVER_FAILED_LOAD. |
Re: Driver installation failed, Error 39, Vista 64 bit
|
|
On Wed, Dec 21, 2011 at 4:27 PM, Ekkehard
<[hidden email]> wrote: > Some more light in the dark. I was able to get the file "setupapi.dev.log" > from the target machine. > It shows problems regarding the signature of the driver files. > I created the setup on a Windows 7 (64 bit) machine. > On Windows 7 (64 bit) it runs smooth. > On XP it shows initially "unsigned" but does not prompt for "really sure to > install unsigned driver" (and works) > On Vista (32 bit) it comes up with a red unsigned driver alert, but let the > user decide and continue (and works) > On Vista (64 bit), same as Vista (32 bit) but dont work. > It seems to me that the signature check in Vista is different from Windows 7 > and blocks from running You may want to check if that Vista 64bit machine has been set up to block unsigned driver package? Take note libusbk.sys has been signed but the whole drive package is not (since that is for your specific VID/PID). Another thing to try, what if you remove the cat file from both the driver package and from the inf file? -- Xiaofan ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
Re: Driver installation failed, Error 39, Vista 64 bit
|
|
On Wed, Dec 21, 2011 at 4:47 PM, Xiaofan Chen <[hidden email]> wrote:
> You may want to check if that Vista 64bit machine has been set up > to block unsigned driver package? Take note libusbk.sys has > been signed but the whole drive package is not (since that is for > your specific VID/PID). > > Another thing to try, what if you remove the cat file from both the driver > package and from the inf file? Yet another thing to try: use Zadig to install libusbK to see if that helps. You can set log level to "debug" to show more information. http://sourceforge.net/projects/libwdi/files/zadig/ -- Xiaofan ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
|
On 12/21/2011 12:52 AM, Xiaofan Chen wrote:
> On Wed, Dec 21, 2011 at 4:47 PM, Xiaofan Chen<[hidden email]> wrote: >> You may want to check if that Vista 64bit machine has been set up >> to block unsigned driver package? I'm not sure this is even possible. An invalid .cat file should cause windows to display the signed driver warning prompt. I cannot find any policy settings that change this behavior is Vista or 7. Did you have something specific in mind? >> Take note libusbk.sys has >> been signed but the whole drive package is not (since that is for >> your specific VID/PID). >> >> Another thing to try, what if you remove the cat file from both the driver >> package and from the inf file? > Yet another thing to try: use Zadig to install libusbK to see if that helps. > You can set log level to "debug" to show more information. > http://sourceforge.net/projects/libwdi/files/zadig/ > It looks like he did use Zadig to create the package because it seems to have a valid cat file. I can reproduce these same errors by creating a package with Zadig on one machine and installing it on another: ! sig: Verifying file against specific (valid) catalog failed! (0x800b0109) ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. I think this error is generated because the .cat file was signed with a machine specific certificate when it was created which is not trusted on the install PC. Although, in the end it still works on my Vista 64 machine after displaying the unsigned driver warning so this problem alone should not cause it to fail. I have 3 complete setupapi.dev.log files from successful vista 64 installations. Each is slightly different because of how the package was created and installed. I can post them if it will help with the analysis. It would also help if you could post your complete log from the "Section start" to the "Section end". e.g. [Device Install Log] OS Version = 6.0.6002 Service Pack = 2.0 Suite = 0x0300 ProductType = 1 Architecture = amd64 [BeginLog] >>> [Device Install (Hardware initiated) - USB\VID_04B4&PID_1003\5&199183a1&0&6] >>> Section start 2011/12/21 06:32:25.876 ..do not snip.. <<< Section end 2011/12/21 06:32:25.985 <<< [Exit status: FAILURE(0xe0000203)] >>> [Device Install (DiShowUpdateDevice) - USB\VID_04B4&PID_1003\5&199183A1&0&6] >>> Section start 2011/12/21 06:32:38.335 ..do not snip.. <<< Section end 2011/12/21 06:33:04.411 <<< [Exit status: SUCCESS] Regards, Travis ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
|
Hi Travis,
below the except from the log file. All parts with xxx-xxx are the overwritten orignal product and company name and inf file name, the rest is still in place. The installer was generated with the inf file generator from the libusbk SDK on a Windows 7 64bit machine. I changed a bit regarding the Device class and Guid. The generated cat file is accepted by the Windows 7 machine and also from XP Best regards Ekkehard Changes in the inf file [Version] Class = "<changed>" ClassGuid = <changed> Provider ="<changed>" [LUsbK_Class_AddReg] HKR,,,0, "<changed>" HKR,,Icon,,-19 Long version from the installer log [Device Install Log] OS Version = 6.0.6001 Service Pack = 1.0 Suite = 0x0100 ProductType = 1 Architecture = amd64 [BeginLog] >>> [Device Install (DiShowUpdateDevice) - USB\VID_16D0&PID_0405\10000000] >>> Section start 2011/12/18 15:57:09.848 cmd: "C:\Windows\system32\mmc.exe" "C:\Windows\System32\devmgmt.msc" /S dvi: {DIF_UPDATEDRIVER_UI} 15:57:09.850 dvi: No class installer for 'xxxxx-xx-xxxxxxx' dvi: No CoInstallers found dvi: Default installer: Enter 15:57:09.861 dvi: Default installer: Exit dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 15:57:09.864 ndv: {Update Driver Software Wizard for USB\VID_16D0&PID_0405\10000000} dvi: Set selected driver complete. dvi: {DIF_SELECTDEVICE} 15:57:17.119 dvi: No class installer for 'xxxxx-xx-xxxxxxx' dvi: {DIF_SELECTDEVICE - exit(0xe000020e)} 15:57:17.127 ui : Prompting user for disk... ui : DPROMPT result = 0 dvi: {DIF_SELECTDEVICE} 15:57:33.378 dvi: No class installer for 'xxxxx-xx-xxxxxxx' dvi: {DIF_SELECTDEVICE - exit(0xe000020e)} 15:57:33.386 inf: {SetupCopyOEMInf: c:\program files (x86)\<path to driver>\xxxxx-xx_xxxxxxx.inf} 15:57:44.593 inf: Opened INF: 'c:\program files (x86)\<path to driver>\xxxxx-xx_xxxxxxx.inf' ([strings] <src = normal>) inf: Opened INF: 'c:\program files (x86)\<path to driver>\xxxxx-xx_xxxxxxx.inf' ([strings] <src = normal>) ! inf: Package was already in store: skipping Driver Store add inf: {SetupCopyOEMInf exit (0x00000000)} 15:57:45.189 inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' ([strings] <src=drvstore>) dvi: Selected driver installs from section [LUsbK_Device] in 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf'. dvi: Set selected driver complete. dvi: {Plug and Play Service: Device Install for USB\VID_16D0&PID_0405\10000000} ump: Creating Install Process: DrvInst.exe 15:57:45.233 ndv: Infpath=C:\Windows\INF\oem95.inf ndv: DriverNodeName=xxxxx-xx_xxxxxxx.inf:LUsbK_DeviceGroup.NTAMD64:LUsbK_Device:3.0.4.0:usb\vid_16d0&pid_0405 ndv: DriverStorepath=C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf ndv: Building driver list from driver node strong name... inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' ([strings] <src=drvstore>) dvi: Selected driver installs from section [LUsbK_Device] in 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf'. dvi: Set selected driver complete. ndv: {Core Device Install} inf: Opened PNF: 'C:\Windows\INF\oem95.inf' ([strings] <src=oempath>) pol: Device installation is subject to policy dvi: {DIF_ALLOW_INSTALL} 15:57:46.543 dvi: No class installer for 'xxxxx-xx-xxxxxxx' dvi: No CoInstallers found dvi: Default installer: Enter 15:57:46.548 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 15:57:46.552 ndv: Installing files... dvi: {DIF_INSTALLDEVICEFILES} 15:57:46.556 dvi: No class installer for 'xxxxx-xx-xxxxxxx' dvi: Default installer: Enter 15:57:46.559 dvi: {Install FILES} inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' ([strings] <src=drvstore>) inf: {Install Inf Section [LUsbK_Device.NTAMD64]} inf: CopyFiles=libusb_files_sys,libusb_files_dll,libusb_files_dll_syswow64 (xxxxx-xx_xxxxxxx.inf line 130) cpy: Open PnpLockdownPolicy: Err=2. This is OK. Use LockDownPolicyDefault flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' flq: SourceSection: [sourcedisksfiles.amd64] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusbK.sys' flq: TargetDirectory- 'C:\Windows\system32\drivers' flq: TargetFilename - 'libusbK.sys' flq: SourceDesc - 'xxxxx-xx-xxxxxxx Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' flq: SourceSection: [sourcedisksfiles.amd64] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusbK.dll' flq: TargetDirectory- 'C:\Windows\system32' flq: TargetFilename - 'libusbK.dll' flq: SourceDesc - 'xxxxx-xx-xxxxxxx Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' flq: SourceSection: [sourcedisksfiles.amd64] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00010000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusb0.dll' flq: TargetDirectory- 'C:\Windows\system32' flq: TargetFilename - 'libusb0.dll' flq: SourceDesc - 'xxxxx-xx-xxxxxxx Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' flq: SourceSection: [sourcedisksfiles.amd64] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusbK_x86.dll' flq: TargetDirectory- 'C:\Windows\syswow64' flq: TargetFilename - 'libusbK.dll' flq: SourceDesc - 'xxxxx-xx-xxxxxxx Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' flq: SourceSection: [sourcedisksfiles.amd64] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00010000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusb0_x86.dll' flq: TargetDirectory- 'C:\Windows\syswow64' flq: TargetFilename - 'libusb0.dll' flq: SourceDesc - 'xxxxx-xx-xxxxxxx Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} inf: {Install Inf Section [LUsbK_Device.NTAMD64] exit (0x00000000)} dvi: Processing co-installer registration section [LUsbK_Device.NTAMD64.CoInstallers]. inf: {Install Inf Section [LUsbK_Device.NTAMD64.CoInstallers]} inf: No (Copy/Ren/Del)Files directives found inf: {Install Inf Section [LUsbK_Device.NTAMD64.CoInstallers] exit (0x00000000)} dvi: Co-installers registered. dvi: {Install INTERFACES} dvi: Installing section [LUsbK_Device.NTAMD64.Interfaces] dvi: {Install INTERFACES exit 00000000} dvi: {Install FILES exit (0x00000000)} dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 15:57:46.737 ndv: Pruning file queue... dvi: {_SCAN_FILE_QUEUE} flq: ScanQ flags=620 flq: SPQ_SCAN_PRUNE_COPY_QUEUE flq: SPQ_SCAN_FILE_COMPARISON flq: SPQ_SCAN_ACTIVATE_DRP flq: ScanQ number of copy nodes=5 flq: File 'C:\Windows\system32\drivers\libusbK.sys' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem95.CAT'. flq: {SPFILENOTIFY_CABINETINFO} flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)} flq: {SPFILENOTIFY_FILEEXTRACTED} flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)} ! sig: VerifyTrustFailed for C:\Windows\system32\drivers\libusbK.sys. ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. cpy: DrpSetRegFileProt 'C:\Windows\system32\drivers\libusbK.sys' Status=0 Class=OEM Legacy flq: File 'C:\Windows\system32\libusbK.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem95.CAT'. ! sig: VerifyTrustFailed for C:\Windows\system32\libusbK.dll. ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. cpy: DrpSetRegFileProt 'C:\Windows\system32\libusbK.dll' Status=0 Class=OEM Legacy flq: File 'C:\Windows\system32\libusb0.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem95.CAT'. ! sig: VerifyTrustFailed for C:\Windows\system32\libusb0.dll. ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. cpy: DrpSetRegFileProt 'C:\Windows\system32\libusb0.dll' Status=0 Class=OEM Legacy flq: File 'C:\Windows\syswow64\libusbK.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem95.CAT'. ! sig: VerifyTrustFailed for C:\Windows\syswow64\libusbK.dll. ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. cpy: DrpSetRegFileProt 'C:\Windows\syswow64\libusbK.dll' Status=0 Class=OEM Legacy flq: File 'C:\Windows\syswow64\libusb0.dll' pruned from copy. sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem95.CAT'. ! sig: VerifyTrustFailed for C:\Windows\syswow64\libusb0.dll. ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. cpy: DrpSetRegFileProt 'C:\Windows\syswow64\libusb0.dll' Status=0 Class=OEM Legacy flq: ScanQ action=200 DoPruning=32 flq: ScanQ end Validity flags=620 CopyNodes=0 dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)} ndv: Committing file queue... flq: {_COMMIT_FILE_QUEUE} flq: CommitQ DelNodes=0 RenNodes=0 BackNodes=0 CopyNodes=0 flq: {_COMMIT_FILE_QUEUE exit(0x00000000)} ndv: Registering CoInstallers... dvi: {DIF_REGISTER_COINSTALLERS} 15:57:47.960 dvi: No class installer for 'xxxxx-xx-xxxxxxx' dvi: Default installer: Enter 15:57:47.966 inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' ([strings] <src=drvstore>) inf: {Install Inf Section [LUsbK_Device.NTAMD64.CoInstallers]} inf: {Install Inf Section [LUsbK_Device.NTAMD64.CoInstallers] exit (0x00000000)} dvi: Co-installers registered. dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 15:57:47.981 ndv: Installing interfaces... dvi: {DIF_INSTALLINTERFACES} 15:57:47.985 dvi: No class installer for 'xxxxx-xx-xxxxxxx' dvi: No CoInstallers found dvi: Default installer: Enter 15:57:47.991 dvi: {Install INTERFACES} inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' ([strings] <src=drvstore>) dvi: Installing section [LUsbK_Device.NTAMD64.Interfaces] dvi: {Install INTERFACES exit 00000000} dvi: Default installer: Exit dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 15:57:48.004 ndv: Installing device... dvi: {DIF_INSTALLDEVICE} 15:57:48.008 dvi: No class installer for 'xxxxx-xx-xxxxxxx' dvi: Default installer: Enter 15:57:48.011 dvi: {Install DEVICE} inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' ([strings] <src=drvstore>) dvi: Processing Registry/Property directives... inf: {Install Inf Section [LUsbK_Device.NTAMD64]} inf: {Install Inf Section [LUsbK_Device.NTAMD64] exit (0x00000000)} inf: {Install Inf Section [LUsbK_Device.NTAMD64.Hw]} inf: AddReg=LUsbK_Device_HW_AddReg (xxxxx-xx_xxxxxxx.inf line 53) inf: HKR,,DeviceInterfaceGUIDs,0x10000,{209E3602-3693-46CE-9267-76CA8AC7DE67} (xxxxx-xx_xxxxxxx.inf line 56) inf: {Install Inf Section [LUsbK_Device.NTAMD64.Hw] exit (0x00000000)} dvi: {Writing Device Properties} dvi: Provider name=xxxxxxx. dvi: DriverDate 09/29/2011 dvi: DriverVersion=3.0.4.0 dvi: Class name=xxxxxxxxxxx dvi: Manufacturer=xxxxxx dvi: Matching DeviceID=usb\vid_16d0&pid_0405 dvi: Strong Name=oem95.inf:LUsbK_DeviceGroup.NTAMD64:LUsbK_Device:3.0.4.0:usb\vid_16d0&pid_0405 dvi: {Writing Device Properties - Complete} inf: {Install Inf Section [LUsbK_Device.NTAMD64.Services]} inf: Addservice=libusbK,2,LUsbK_AddService (xxxxx-xx_xxxxxxx.inf line 63) inf: ServiceType=1 (xxxxx-xx_xxxxxxx.inf line 67) inf: StartType=3 (xxxxx-xx_xxxxxxx.inf line 68) inf: ErrorControl=1 (xxxxx-xx_xxxxxxx.inf line 69) inf: ServiceBinary=C:\Windows\system32\DRIVERS\libusbK.sys (xxxxx-xx_xxxxxxx.inf line 70) inf: DisplayName="libusbK USB Driver 09/29/2011 - 3.0.4.0" (xxxxx-xx_xxxxxxx.inf line 66) dvi: Add Service: Modified existing service 'libusbK'. inf: AddReg=LUsbK_Driver_AddReg (xxxxx-xx_xxxxxxx.inf line 71) inf: HKR,Parameters,DebugLevel,0x10001,4 (xxxxx-xx_xxxxxxx.inf line 77) inf: {Install Inf Section [LUsbK_Device.NTAMD64.Services] exit(0x00000000)} dvi: {Install DEVICE exit (0x00000000)} dvi: Writing common driver property settings. dvi: DriverDescription=xxxxx-xx-xxxxxxx dvi: DeviceDisplayName=xxxxx-xx-xxxxxxx dvi: Install Device: Restarting device. 15:57:48.679 dvi: Install Device: Restarting device completed. 15:57:49.048 !!! dvi: Device not started: Device has problem: 0x27: CM_PROB_DRIVER_FAILED_LOAD. dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 15:57:49.056 dvi: {Build Driver List} 15:57:49.059 dvi: Processing a single INF: 'C:\Windows\INF\oem95.inf' inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf' ([strings] <src=drvstore>) dvi: Created Driver Node: dvi: HardwareID - USB\VID_16D0&PID_0405 dvi: InfName - C:\Windows\System32\DriverStore\FileRepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf dvi: DevDesc - xxxxx-xx-xxxxxxx dvi: DrvDesc - xxxxx-xx-xxxxxxx dvi: Provider - xxxxxxx. dvi: Mfg - xxxxxxxx dvi: ModelsSec - LUsbK_DeviceGroup.NTAMD64 dvi: InstallSec - LUsbK_Device dvi: ActualSec - LUsbK_Device.NTAMD64 dvi: Rank - 0x80ff0001 dvi: Signer - dvi: Signer Score - Not digitally signed dvi: DrvDate - 09/29/2011 dvi: Version - 3.0.4.0 dvi: {Build Driver List - exit(0x00000000)} 15:57:49.102 dvi: {DIF_SELECTBESTCOMPATDRV} 15:57:49.104 dvi: No class installer for 'xxxxx-xx-xxxxxxx' dvi: Default installer: Enter 15:57:49.108 dvi: {Select Best Driver} dvi: Selected driver installs from section [LUsbK_Device] in 'c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf'. dvi: Set selected driver complete. dvi: Selected: dvi: Description - [xxxxx-xx-xxxxxxx] dvi: InfFile - [c:\windows\system32\driverstore\filerepository\xxxxx-xx_xxxxxxx.inf_cfcbcc44\xxxxx-xx_xxxxxxx.inf] dvi: Section - [LUsbK_Device] dvi: Signer - [] dvi: Rank - [0x80ff0001] dvi: {Select Best Driver - exit(0x00000000)} dvi: Default installer: Exit dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 15:57:49.130 dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 15:57:49.132 dvi: No class installer for 'xxxxx-xx-xxxxxxx' dvi: Default installer: Enter 15:57:49.135 dvi: Default installer: Exit dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 15:57:49.139 ndv: Device install status=0x00000000 ndv: Performing device install final cleanup... ! ndv: Queueing up error report since device has a PnP problem... ndv: {Core Device Install - exit(0x00000000)} ump: Server install process exited with code 0x00000000 15:57:54.368 ump: {Plug and Play Service: Device Install exit(00000000)} dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 15:57:54.390 dvi: No class installer for 'xxxxx-xx-xxxxxxx' dvi: No CoInstallers found dvi: Default installer: Enter 15:57:54.396 dvi: Default installer: Exit dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 15:57:54.400 ndv: {Update Driver Software Wizard exit(00000000)} <<< Section end 2011/12/18 15:57:56.110 <<< [Exit status: SUCCESS] |
|
|
On 12/21/2011 1:14 PM, Ekkehard wrote:
> Hi Travis, > below the except from the log file. All parts with xxx-xxx are the > overwritten orignal product and company name and inf file name, the rest is > still in place. > > The installer was generated with the inf file generator from the libusbk SDK > on a Windows 7 64bit machine. Hmm.. the libusbK InfWizard does not generate a .cat file and it seems that you have one. ;) sig: Using catalog 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem95.CAT'. ! sig: VerifyTrustFailed for C:\Windows\system32\drivers\libusbK.sys. ! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. > I changed a bit regarding the Device class and > Guid. The generated cat file is accepted by the Windows 7 machine and also > from XP One thing I notice is this line: ! inf: Package was already in store: skipping Driver Store add I believe this means it is using a driver package that already exists in the driver store; not the one you specified. You can remove these with the 'pnputil' command line tool. This tool requires admin privs. List: pnputil -e Remove: pnputil -f -d oemXX.inf If possible, install service pack 2. There is a blurb in the WDK release notes that states Vista can have problems with WinUSB, but presumably this was fixed in SP1. (WinUSB and libusbK or both KMDF based) http://msdn.microsoft.com/en-us/windows/hardware/gg487438 Below, I've posted a vista 64 log that was successful. The package was created with the libusbK SDK on WIndows 7 and installed on a Vista machine. Regards Travis [Device Install Log] OS Version = 6.0.6002 Service Pack = 2.0 Suite = 0x0300 ProductType = 1 Architecture = amd64 [BeginLog] >>> [Device Install (Hardware initiated) - USB\VID_04B4&PID_1003\5&199183a1&0&6] >>> Section start 2011/12/21 06:32:25.876 ump: Creating Install Process: DrvInst.exe 06:32:25.891 ndv: Retrieving device info... ndv: Setting device parameters... ndv: Building driver list... dvi: {Build Driver List} 06:32:25.891 dvi: Searching for hardware ID(s): dvi: usb\vid_04b4&pid_1003&rev_0000 dvi: usb\vid_04b4&pid_1003 dvi: Searching for compatible ID(s): dvi: usb\class_ff&subclass_00&prot_00 dvi: usb\class_ff&subclass_00 dvi: usb\class_ff dvi: Enumerating INFs from path list 'C:\Windows\INF' inf: Searched 0 potential matches in published INF directory inf: Searched 29 INFs in directory: 'C:\Windows\INF' dvi: {Build Driver List - exit(0x00000000)} 06:32:25.985 ndv: Selecting best match... dvi: {DIF_SELECTBESTCOMPATDRV} 06:32:25.985 dvi: No class installer for 'CY-Stream' dvi: No CoInstallers found dvi: Default installer: Enter 06:32:25.985 dvi: {Select Best Driver} ! dvi: Selecting driver failed(0xe0000228) dvi: {Select Best Driver - exit(0xe0000228)} ! dvi: Default installer: failed! ! dvi: Error 0xe0000228: There are no compatible drivers for this device. dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 06:32:25.985 ndv: {Core Device Install} ndv: Device install status=0xe0000203 ndv: Performing device install final cleanup... ! ndv: Queueing up error report since device installation failed... ndv: {Core Device Install - exit(0xe0000203)} ump: Server install process exited with code 0xe0000203 06:32:25.985 <<< Section end 2011/12/21 06:32:25.985 <<< [Exit status: FAILURE(0xe0000203)] >>> [Device Install (DiShowUpdateDevice) - USB\VID_04B4&PID_1003\5&199183A1&0&6] >>> Section start 2011/12/21 06:32:38.335 cmd: "C:\Windows\system32\mmc.exe" "C:\Windows\System32\devmgmt.msc" /S dvi: {DIF_UPDATEDRIVER_UI} 06:32:38.335 dvi: No class installer for 'CY-Stream' dvi: No CoInstallers found dvi: Default installer: Enter 06:32:38.335 dvi: Default installer: Exit dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 06:32:38.335 ndv: {Update Driver Software Wizard for USB\VID_04B4&PID_1003\5&199183A1&0&6} inf: Opened INF: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' ([strings]<src = normal>) inf: {SetupCopyOEMInf: \\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf} 06:32:51.595 inf: Opened INF: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' ([strings]<src = normal>) dvi: {Staging Package To Driver Store - phase 1} sto: Inf Path = \\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf sto: Flags = 0 sto: Processor Architecture = 9 inf: Opened INF: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' ([strings]<src = normal>) sto: Copying driver package. Inf = \\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf, Destination = C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339} inf: Opened INF: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' ([strings]<src = normal>) flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - '\\travis-pc\usb_driver\inf-wizard\cy-stream' flq: SourceFilename - 'cy-stream.inf' flq: TargetDirectory- 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}' flq: {FILE_QUEUE_COPY exit(0x00000000)} inf: Opened INF: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' ([strings]<src = normal>) flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - '\\travis-pc\usb_driver\inf-wizard\cy-stream' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusb0.dll' flq: TargetDirectory- 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64' flq: SourceDesc - 'CY-Stream Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - '\\travis-pc\usb_driver\inf-wizard\cy-stream' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusbk.dll' flq: TargetDirectory- 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64' flq: SourceDesc - 'CY-Stream Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - '\\travis-pc\usb_driver\inf-wizard\cy-stream' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusbk.sys' flq: TargetDirectory- 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64' flq: SourceDesc - 'CY-Stream Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - '\\travis-pc\usb_driver\inf-wizard\cy-stream' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusb0_x86.dll' flq: TargetDirectory- 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64' flq: SourceDesc - 'CY-Stream Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - '\\travis-pc\usb_driver\inf-wizard\cy-stream' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusbk_x86.dll' flq: TargetDirectory- 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64' flq: SourceDesc - 'CY-Stream Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: {_commit_file_queue} flq: {SPFILENOTIFY_STARTQUEUE} flq: {SPFILENOTIFY_STARTQUEUE - returned 0x00000001} flq: {_commit_copy_subqueue} flq: subqueue count=6 flq: {SPFILENOTIFY_STARTSUBQUEUE} flq: {SPFILENOTIFY_STARTSUBQUEUE - returned 0x00000001} flq: source media: flq: SourcePath - [\\travis-pc\usb_driver\inf-wizard\cy-stream] flq: SourceFile - [cy-stream.inf] flq: Flags - 0x00000000 flq: {_commit_copyfile} flq: {SPFILENOTIFY_STARTCOPY} flq: {SPFILENOTIFY_STARTCOPY - returned 0x00000001} flq: CopyFile: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' flq: to: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\SET9BE1.tmp' flq: MoveFile: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\SET9BE1.tmp' flq: to: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\cy-stream.inf' flq: {SPFILENOTIFY_ENDCOPY} flq: {SPFILENOTIFY_ENDCOPY - returned 0x00000000} flq: {_commit_copyfile exit OK} flq: source media: flq: Description - [CY-Stream Install Disk] flq: SourcePath - [\\travis-pc\usb_driver\inf-wizard\cy-stream\amd64] flq: SourceFile - [libusb0.dll] flq: Flags - 0x00000000 flq: {_commit_copyfile} flq: {SPFILENOTIFY_STARTCOPY} flq: {SPFILENOTIFY_STARTCOPY - returned 0x00000001} flq: CopyFile: '\\travis-pc\usb_driver\inf-wizard\cy-stream\amd64\libusb0.dll' flq: to: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\SET9BF2.tmp' flq: MoveFile: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\SET9BF2.tmp' flq: to: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\libusb0.dll' flq: {SPFILENOTIFY_ENDCOPY} flq: {SPFILENOTIFY_ENDCOPY - returned 0x00000000} flq: {_commit_copyfile exit OK} flq: {_commit_copyfile} flq: {SPFILENOTIFY_STARTCOPY} flq: {SPFILENOTIFY_STARTCOPY - returned 0x00000001} flq: CopyFile: '\\travis-pc\usb_driver\inf-wizard\cy-stream\amd64\libusbk.dll' flq: to: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\SET9C12.tmp' flq: MoveFile: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\SET9C12.tmp' flq: to: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\libusbk.dll' flq: {SPFILENOTIFY_ENDCOPY} flq: {SPFILENOTIFY_ENDCOPY - returned 0x00000000} flq: {_commit_copyfile exit OK} flq: {_commit_copyfile} flq: {SPFILENOTIFY_STARTCOPY} flq: {SPFILENOTIFY_STARTCOPY - returned 0x00000001} flq: CopyFile: '\\travis-pc\usb_driver\inf-wizard\cy-stream\amd64\libusbk.sys' flq: to: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\SET9C42.tmp' flq: MoveFile: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\SET9C42.tmp' flq: to: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\libusbk.sys' flq: {SPFILENOTIFY_ENDCOPY} flq: {SPFILENOTIFY_ENDCOPY - returned 0x00000000} flq: {_commit_copyfile exit OK} flq: {_commit_copyfile} flq: {SPFILENOTIFY_STARTCOPY} flq: {SPFILENOTIFY_STARTCOPY - returned 0x00000001} flq: CopyFile: '\\travis-pc\usb_driver\inf-wizard\cy-stream\amd64\libusb0_x86.dll' flq: to: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\SET9C52.tmp' flq: MoveFile: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\SET9C52.tmp' flq: to: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\libusb0_x86.dll' flq: {SPFILENOTIFY_ENDCOPY} flq: {SPFILENOTIFY_ENDCOPY - returned 0x00000000} flq: {_commit_copyfile exit OK} flq: {_commit_copyfile} flq: {SPFILENOTIFY_STARTCOPY} flq: {SPFILENOTIFY_STARTCOPY - returned 0x00000001} flq: CopyFile: '\\travis-pc\usb_driver\inf-wizard\cy-stream\amd64\libusbk_x86.dll' flq: to: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\SET9C73.tmp' flq: MoveFile: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\SET9C73.tmp' flq: to: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\amd64\libusbk_x86.dll' flq: {SPFILENOTIFY_ENDCOPY} flq: {SPFILENOTIFY_ENDCOPY - returned 0x00000000} flq: {_commit_copyfile exit OK} flq: {SPFILENOTIFY_ENDSUBQUEUE} flq: {SPFILENOTIFY_ENDSUBQUEUE - returned 0x00000000} flq: {_commit_copy_subqueue exit OK} flq: {SPFILENOTIFY_ENDQUEUE} flq: {SPFILENOTIFY_ENDQUEUE - returned 0x00000000} flq: {_commit_file_queue exit OK} sto: Driver Package successfully copied to C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339} inf: Opened INF: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\cy-stream.inf' ([strings]<src = normal>) pol: {Driver package policy check} 06:32:51.814 pol: {Driver package policy check - exit(0x00000000)} 06:32:51.814 dvi: Staging Package To Driver Store - phase 2 inf: Opened INF: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: 'C:\Users\Travis\{fec379cc-e6ab-4fc7-9a80-3f8692e0c339}\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: 'C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: 'C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package\cy-stream.inf' ([strings]<src = normal>) ! sto: The Driver Package does not contain a catalog file, but user wants to install anyway. inf: Opened INF: 'C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: 'C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: 'C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: 'C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package\cy-stream.inf' ([strings]<src = normal>) sto: Machine Name = sto: File Repository = C:\Windows\system32\DriverStore\FileRepository sto: Repository = C:\Windows\system32\DriverStore\Repository sto: Inf Path = C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package\cy-stream.inf sto: Architecture = amd64 sto: PackageRoot = C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package sto: Search Path = C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package;C:\Windows\INF sto: Flags = 0 sto: Package Hash = FEBC806F6E18B46B sto: Signer Score = 0xff000000 sto: Digital Signer = sto: Setting system restore point. inf: Opened INF: 'C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package\cy-stream.inf' ([strings]<src = normal>) inf: Opened INF: 'C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package\cy-stream.inf' ([strings]<src = normal>) ! cmi: File::CopyFileUsingSymbolicLink(C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package\CY-Stream.cat, \\?\C:\Windows\system32\DriverStore\FileRepository\cy-stream.inf_8a68470b\CY- ! cmi: CopyFile from C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package\CY-Stream.cat to \\?\C:\Windows\system32\DriverStore\FileRepository\cy-stream.inf_8a68470b\CY-Stream.cat faile ! cmi: CopyFile(source=C:\Windows\system32\DriverStore\Temp\{5cdaa3b7-e0e1-483e-ad07-1161b35cc180}\Package\CY-Stream.cat, destination=\\?\C:\Windows\system32\DriverStore\FileRepository\cy-stream.inf_8a68470b\CY-Stre idb: Registered 'cy-stream.inf' to driver store path 'cy-stream.inf_8a68470b' idb: Published 'cy-stream.inf_8a68470b\cy-stream.inf' to 'C:\Windows\INF\oem6.inf' sto: Commiting system restore point. sto: {Staging Package To Driver Store - phase 2 exit(00000000)} sto: {Staging Package To Driver Store - phase 1 exit(00000000)} inf: Driver Store location: C:\Windows\system32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.inf inf: Published Inf Path: C:\Windows\INF\oem6.inf inf: Opened INF: '\\travis-pc\usb_driver\inf-wizard\cy-stream\cy-stream.inf' ([strings]<src = normal>) inf: Installing Catalog \\travis-pc\usb_driver\inf-wizard\cy-stream\CY-Stream.cat as: oem6.CAT ! inf: Failed to Catalog - error ignored ! inf: Error 2: The system cannot find the file specified. inf: OEM source media location: \\travis-pc\usb_driver\inf-wizard\cy-stream\ inf: {SetupCopyOEMInf exit (0x00000000)} 06:32:59.770 dvi: Searching for hardware ID(s): dvi: usb\vid_04b4&pid_1003&rev_0000 dvi: usb\vid_04b4&pid_1003 dvi: Searching for compatible ID(s): dvi: usb\class_ff&subclass_00&prot_00 dvi: usb\class_ff&subclass_00 dvi: usb\class_ff inf: Opened INF: 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.inf' ([strings]<src=drvstore>) sig: {_VERIFY_FILE_SIGNATURE} 06:32:59.770 sig: Key = cy-stream.inf sig: FilePath = C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.inf sig: Catalog = C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\CY-Stream.cat ! sig: Verifying file against specific (valid) catalog failed! (0x00000057) ! sig: Error 87: The parameter is incorrect. sig: {_VERIFY_FILE_SIGNATURE exit(0x00000057)} 06:32:59.770 sig: {_VERIFY_FILE_SIGNATURE} 06:32:59.770 sig: Key = cy-stream.inf sig: FilePath = C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.inf sig: Catalog = C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\CY-Stream.cat ! sig: Verifying file against specific Authenticode(tm) catalog failed! (0x80092003) ! sig: Error 0x80092003: An error occurred while reading or writing to a file. sig: {_VERIFY_FILE_SIGNATURE exit(0x80092003)} 06:32:59.770 dvi: Selected driver installs from section [LUsbK_Device] in 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf'. dvi: Class GUID of device changed to: {ecfb0cfd-74c4-4f52-bbf7-343461cd72ac}. dvi: Set selected driver complete. dvi: {Plug and Play Service: Device Install for USB\VID_04B4&PID_1003\5&199183A1&0&6} ump: Creating Install Process: DrvInst.exe 06:32:59.785 ndv: Infpath=C:\Windows\INF\oem6.inf ndv: DriverNodeName=cy-stream.inf:LUsbK_DeviceGroup.NTAMD64:LUsbK_Device:3.0.5.1:usb\vid_04b4&pid_1003 ndv: DriverStorepath=C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.inf ndv: Building driver list from driver node strong name... dvi: Searching for hardware ID(s): dvi: usb\vid_04b4&pid_1003&rev_0000 dvi: usb\vid_04b4&pid_1003 dvi: Searching for compatible ID(s): dvi: usb\class_ff&subclass_00&prot_00 dvi: usb\class_ff&subclass_00 dvi: usb\class_ff inf: Opened INF: 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.inf' ([strings]<src=drvstore>) inf: Saved PNF: 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.PNF' (Language = 0409) sig: {_VERIFY_FILE_SIGNATURE} 06:32:59.817 sig: Key = cy-stream.inf sig: FilePath = C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.inf sig: Catalog = C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\CY-Stream.cat ! sig: Verifying file against specific (valid) catalog failed! (0x00000057) ! sig: Error 87: The parameter is incorrect. sig: {_VERIFY_FILE_SIGNATURE exit(0x00000057)} 06:32:59.832 sig: {_VERIFY_FILE_SIGNATURE} 06:32:59.832 sig: Key = cy-stream.inf sig: FilePath = C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.inf sig: Catalog = C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\CY-Stream.cat ! sig: Verifying file against specific Authenticode(tm) catalog failed! (0x80092003) ! sig: Error 0x80092003: An error occurred while reading or writing to a file. sig: {_VERIFY_FILE_SIGNATURE exit(0x80092003)} 06:32:59.832 dvi: Selected driver installs from section [LUsbK_Device] in 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf'. dvi: Class GUID of device changed to: {ecfb0cfd-74c4-4f52-bbf7-343461cd72ac}. dvi: Set selected driver complete. ndv: {Core Device Install} inf: Opened INF: 'C:\Windows\INF\oem6.inf' ([strings]<src=oempath>) inf: Saved PNF: 'C:\Windows\INF\oem6.PNF' (Language = 0409) pol: Device installation is subject to policy dvi: {DIF_ALLOW_INSTALL} 06:32:59.848 dvi: No class installer for 'CY-Stream' dvi: No CoInstallers found dvi: Default installer: Enter 06:32:59.848 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 06:32:59.848 ndv: Installing files... dvi: {DIF_INSTALLDEVICEFILES} 06:32:59.848 dvi: No class installer for 'CY-Stream' dvi: Default installer: Enter 06:32:59.848 dvi: {Install FILES} inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' ([strings]<src=drvstore>) inf: {Install Inf Section [LUsbK_Device.NTAMD64]} inf: CopyFiles=libusb_files_sys,libusb_files_dll,libusb_files_dll_syswow64 (cy-stream.inf line 130) cpy: Open PnpLockdownPolicy: Err=2. This is OK. Use LockDownPolicyDefault flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' flq: SourceSection: [sourcedisksfiles.amd64] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusbK.sys' flq: TargetDirectory- 'C:\Windows\system32\drivers' flq: TargetFilename - 'libusbK.sys' flq: SourceDesc - 'CY-Stream Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' flq: SourceSection: [sourcedisksfiles.amd64] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusbK.dll' flq: TargetDirectory- 'C:\Windows\system32' flq: TargetFilename - 'libusbK.dll' flq: SourceDesc - 'CY-Stream Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' flq: SourceSection: [sourcedisksfiles.amd64] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00010000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusb0.dll' flq: TargetDirectory- 'C:\Windows\system32' flq: TargetFilename - 'libusb0.dll' flq: SourceDesc - 'CY-Stream Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' flq: SourceSection: [sourcedisksfiles.amd64] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00000000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusbK_x86.dll' flq: TargetDirectory- 'C:\Windows\syswow64' flq: TargetFilename - 'libusbK.dll' flq: SourceDesc - 'CY-Stream Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} flq: QueueSingleCopy... flq: Inf : 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' flq: SourceInf: 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' flq: SourceSection: [sourcedisksfiles.amd64] flq: Source root path based on SourceInf flq: SourceRootPath: 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b' flq: {FILE_QUEUE_COPY} flq: CopyStyle - 0x00010000 flq: SourceRootPath - 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b' flq: SourcePath - '\amd64' flq: SourceFilename - 'libusb0_x86.dll' flq: TargetDirectory- 'C:\Windows\syswow64' flq: TargetFilename - 'libusb0.dll' flq: SourceDesc - 'CY-Stream Install Disk' flq: {FILE_QUEUE_COPY exit(0x00000000)} inf: {Install Inf Section [LUsbK_Device.NTAMD64] exit (0x00000000)} dvi: Processing co-installer registration section [LUsbK_Device.NTAMD64.CoInstallers]. inf: {Install Inf Section [LUsbK_Device.NTAMD64.CoInstallers]} inf: No (Copy/Ren/Del)Files directives found inf: {Install Inf Section [LUsbK_Device.NTAMD64.CoInstallers] exit (0x00000000)} dvi: Co-installers registered. dvi: {Install INTERFACES} dvi: Installing section [LUsbK_Device.NTAMD64.Interfaces] dvi: {Install INTERFACES exit 00000000} dvi: {Install FILES exit (0x00000000)} dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 06:32:59.863 ndv: Pruning file queue... dvi: {_SCAN_FILE_QUEUE} flq: ScanQ flags=620 flq: SPQ_SCAN_PRUNE_COPY_QUEUE flq: SPQ_SCAN_FILE_COMPARISON flq: SPQ_SCAN_ACTIVATE_DRP flq: ScanQ number of copy nodes=5 flq: File 'C:\Windows\system32\libusb0.dll' pruned from copy. cpy: DrpSetRegFileProt 'C:\Windows\system32\libusb0.dll' Status=0 Class=OEM Legacy flq: File 'C:\Windows\syswow64\libusb0.dll' pruned from copy. cpy: DrpSetRegFileProt 'C:\Windows\syswow64\libusb0.dll' Status=0 Class=OEM Legacy flq: ScanQ action=200 DoPruning=32 flq: ScanQ end Validity flags=620 CopyNodes=3 dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)} ndv: Committing file queue... flq: {_COMMIT_FILE_QUEUE} flq: CommitQ DelNodes=0 RenNodes=0 BackNodes=0 CopyNodes=3 flq: {SPFILENOTIFY_STARTQUEUE} flq: {SPFILENOTIFY_STARTQUEUE - exit(0x00000001)} flq: {SPFILENOTIFY_STARTSUBQUEUE} flq: {SPFILENOTIFY_STARTSUBQUEUE - exit(0x00000001)} flq: SPFILENOTIFY_NEEDMEDIA: flq: Description - [CY-Stream Install Disk] flq: SourcePath - [C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\amd64] flq: SourceFile - [libusbK.sys] flq: Flags - 0x00000000 flq: {SPFILENOTIFY_NEEDMEDIA} flq: {SPFILENOTIFY_NEEDMEDIA - exit(0x00000001)} flq: {SPFILENOTIFY_STARTCOPY} ndv: Saving LastKnownGood file C:\Windows\system32\drivers\libusbK.sys (copy) flq: {SPFILENOTIFY_STARTCOPY - exit(0x00000001)} cpy: CopyFile: 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\amd64\libusbK.sys' cpy: to: 'C:\Windows\system32\drivers\SETBC24.tmp' cpy: CopyFile Drp is active cpy: Source File 'C:\Windows\system32\drivers\SETBC24.tmp' is NOT signed NT5 Crypto. cpy: DrpGetFileProt Status=0 dwClass=5 cpy: MoveFile: 'C:\Windows\system32\drivers\SETBC24.tmp' cpy: to: 'C:\Windows\system32\drivers\libusbK.sys' cpy: DrpSetRegFileProt 'C:\Windows\system32\drivers\libusbK.sys' Status=0 Class=OEM Legacy flq: {SPFILENOTIFY_ENDCOPY} flq: {SPFILENOTIFY_ENDCOPY - exit(0x00000001)} flq: {SPFILENOTIFY_STARTCOPY} ndv: Saving LastKnownGood file C:\Windows\system32\libusbK.dll (copy) flq: {SPFILENOTIFY_STARTCOPY - exit(0x00000001)} cpy: CopyFile: 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\amd64\libusbK.dll' cpy: to: 'C:\Windows\system32\SETBC44.tmp' cpy: CopyFile Drp is active cpy: Source File 'C:\Windows\system32\SETBC44.tmp' is NOT signed NT5 Crypto. cpy: DrpGetFileProt Status=0 dwClass=5 cpy: MoveFile: 'C:\Windows\system32\SETBC44.tmp' cpy: to: 'C:\Windows\system32\libusbK.dll' cpy: DrpSetRegFileProt 'C:\Windows\system32\libusbK.dll' Status=0 Class=OEM Legacy flq: {SPFILENOTIFY_ENDCOPY} flq: {SPFILENOTIFY_ENDCOPY - exit(0x00000001)} flq: {SPFILENOTIFY_STARTCOPY} ndv: Saving LastKnownGood file C:\Windows\syswow64\libusbK.dll (copy) flq: {SPFILENOTIFY_STARTCOPY - exit(0x00000001)} cpy: CopyFile: 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\amd64\libusbK_x86.dll' cpy: to: 'C:\Windows\syswow64\SETBC65.tmp' cpy: CopyFile Drp is active cpy: Source File 'C:\Windows\syswow64\SETBC65.tmp' is NOT signed NT5 Crypto. cpy: DrpGetFileProt Status=0 dwClass=5 cpy: MoveFile: 'C:\Windows\syswow64\SETBC65.tmp' cpy: to: 'C:\Windows\syswow64\libusbK.dll' cpy: DrpSetRegFileProt 'C:\Windows\syswow64\libusbK.dll' Status=0 Class=OEM Legacy flq: {SPFILENOTIFY_ENDCOPY} flq: {SPFILENOTIFY_ENDCOPY - exit(0x00000001)} flq: {SPFILENOTIFY_ENDSUBQUEUE} flq: {SPFILENOTIFY_ENDSUBQUEUE - exit(0x00000001)} flq: {SPFILENOTIFY_ENDQUEUE} flq: {SPFILENOTIFY_ENDQUEUE - exit(0x00000001)} flq: {_COMMIT_FILE_QUEUE exit(0x00000000)} ndv: Registering CoInstallers... dvi: {DIF_REGISTER_COINSTALLERS} 06:33:00.004 dvi: No class installer for 'CY-Stream' dvi: Default installer: Enter 06:33:00.004 inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' ([strings]<src=drvstore>) inf: {Install Inf Section [LUsbK_Device.NTAMD64.CoInstallers]} inf: {Install Inf Section [LUsbK_Device.NTAMD64.CoInstallers] exit (0x00000000)} dvi: Co-installers registered. dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 06:33:00.004 ndv: Installing interfaces... dvi: {DIF_INSTALLINTERFACES} 06:33:00.004 dvi: No class installer for 'CY-Stream' dvi: No CoInstallers found dvi: Default installer: Enter 06:33:00.004 dvi: {Install INTERFACES} inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' ([strings]<src=drvstore>) dvi: Installing section [LUsbK_Device.NTAMD64.Interfaces] dvi: {Install INTERFACES exit 00000000} dvi: Default installer: Exit dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 06:33:00.004 ndv: Installing device... dvi: {DIF_INSTALLDEVICE} 06:33:00.004 dvi: No class installer for 'CY-Stream' dvi: Default installer: Enter 06:33:00.004 dvi: {Install DEVICE} inf: Opened PNF: 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf' ([strings]<src=drvstore>) dvi: Processing Registry/Property directives... inf: {Install Inf Section [LUsbK_Device.NTAMD64]} inf: {Install Inf Section [LUsbK_Device.NTAMD64] exit (0x00000000)} inf: {Install Inf Section [LUsbK_Device.NTAMD64.Hw]} inf: AddReg=LUsbK_Device_HW_AddReg (cy-stream.inf line 53) inf: HKR,,DeviceInterfaceGUIDs,0x10000,{DB27858E-9063-A2AB-5B05-7414D7547D54} (cy-stream.inf line 56) inf: {Install Inf Section [LUsbK_Device.NTAMD64.Hw] exit (0x00000000)} dvi: {Writing Device Properties} dvi: Provider name=libusbK dvi: DriverDate 12/04/2011 dvi: DriverVersion=3.0.5.1 dvi: Class name=libusbk devices dvi: Manufacturer=Cypress Semiconductor Corp. dvi: Matching DeviceID=usb\vid_04b4&pid_1003 dvi: Strong Name=oem6.inf:LUsbK_DeviceGroup.NTAMD64:LUsbK_Device:3.0.5.1:usb\vid_04b4&pid_1003 dvi: {Writing Device Properties - Complete} inf: {Install Inf Section [LUsbK_Device.NTAMD64.Services]} inf: Addservice=libusbK,2,LUsbK_AddService (cy-stream.inf line 63) inf: ServiceType=1 (cy-stream.inf line 67) inf: StartType=3 (cy-stream.inf line 68) inf: ErrorControl=1 (cy-stream.inf line 69) inf: ServiceBinary=C:\Windows\system32\DRIVERS\libusbK.sys (cy-stream.inf line 70) inf: DisplayName="libusbK USB Driver 12/04/2011 - 3.0.5.1" (cy-stream.inf line 66) dvi: Add Service: Modified existing service 'libusbK'. inf: AddReg=LUsbK_Driver_AddReg (cy-stream.inf line 71) inf: HKR,Parameters,DebugLevel,0x10001,4 (cy-stream.inf line 77) inf: {Install Inf Section [LUsbK_Device.NTAMD64.Services] exit(0x00000000)} dvi: {Install DEVICE exit (0x00000000)} dvi: Writing common driver property settings. dvi: DriverDescription=CY-Stream dvi: DeviceDisplayName=CY-Stream dvi: {Restarting Devices} 06:33:00.675 dvi: Restart: USB\VID_04B4&PID_1003\5&199183A1&0&6 dvi: Restart complete. dvi: {Restarting Devices exit} 06:33:01.018 dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 06:33:01.018 dvi: {Build Driver List} 06:33:01.018 dvi: Searching for hardware ID(s): dvi: usb\vid_04b4&pid_1003&rev_0000 dvi: usb\vid_04b4&pid_1003 dvi: Searching for compatible ID(s): dvi: usb\class_ff&subclass_00&prot_00 dvi: usb\class_ff&subclass_00 dvi: usb\class_ff dvi: Processing a single INF: 'C:\Windows\INF\oem6.inf' inf: Opened PNF: 'C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.inf' ([strings]<src=drvstore>) sig: {_VERIFY_FILE_SIGNATURE} 06:33:01.033 sig: Key = cy-stream.inf sig: FilePath = C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.inf sig: Catalog = C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\CY-Stream.cat ! sig: Verifying file against specific (valid) catalog failed! (0x00000057) ! sig: Error 87: The parameter is incorrect. sig: {_VERIFY_FILE_SIGNATURE exit(0x00000057)} 06:33:01.033 sig: {_VERIFY_FILE_SIGNATURE} 06:33:01.033 sig: Key = cy-stream.inf sig: FilePath = C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.inf sig: Catalog = C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\CY-Stream.cat ! sig: Verifying file against specific Authenticode(tm) catalog failed! (0x80092003) ! sig: Error 0x80092003: An error occurred while reading or writing to a file. sig: {_VERIFY_FILE_SIGNATURE exit(0x80092003)} 06:33:01.033 dvi: Created Driver Node: dvi: HardwareID - USB\VID_04B4&PID_1003 dvi: InfName - C:\Windows\System32\DriverStore\FileRepository\cy-stream.inf_8a68470b\cy-stream.inf dvi: DevDesc - CY-Stream dvi: DrvDesc - CY-Stream dvi: Provider - libusbK dvi: Mfg - Cypress Semiconductor Corp. dvi: ModelsSec - LUsbK_DeviceGroup.NTAMD64 dvi: InstallSec - LUsbK_Device dvi: ActualSec - LUsbK_Device.NTAMD64 dvi: Rank - 0x80ff0001 dvi: Signer - Not digitally signed dvi: Signer Score - Not digitally signed dvi: DrvDate - 12/04/2011 dvi: Version - 3.0.5.1 dvi: {Build Driver List - exit(0x00000000)} 06:33:01.033 dvi: {DIF_SELECTBESTCOMPATDRV} 06:33:01.033 dvi: No class installer for 'CY-Stream' dvi: Default installer: Enter 06:33:01.033 dvi: {Select Best Driver} dvi: Selected driver installs from section [LUsbK_Device] in 'c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf'. dvi: Class GUID of device remains: {ecfb0cfd-74c4-4f52-bbf7-343461cd72ac}. dvi: Set selected driver complete. dvi: Selected: dvi: Description - [CY-Stream] dvi: InfFile - [c:\windows\system32\driverstore\filerepository\cy-stream.inf_8a68470b\cy-stream.inf] dvi: Section - [LUsbK_Device] dvi: Signer - [Not digitally signed] dvi: Rank - [0x80ff0001] dvi: {Select Best Driver - exit(0x00000000)} dvi: Default installer: Exit dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 06:33:01.049 dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 06:33:01.049 dvi: No class installer for 'CY-Stream' dvi: Default installer: Enter 06:33:01.049 dvi: Default installer: Exit dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 06:33:01.049 ndv: Device install status=0x00000000 ndv: Performing device install final cleanup... ndv: {Core Device Install - exit(0x00000000)} ump: Server install process exited with code 0x00000000 06:33:01.049 ump: {Plug and Play Service: Device Install exit(00000000)} dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 06:33:01.065 dvi: No class installer for 'CY-Stream' dvi: No CoInstallers found dvi: Default installer: Enter 06:33:01.080 dvi: Default installer: Exit dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 06:33:01.080 ndv: {Update Driver Software Wizard exit(00000000)} <<< Section end 2011/12/21 06:33:04.411 <<< [Exit status: SUCCESS] ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
|
Hmm... I downloaded http://usb-travis.googlecode.com/files/libusbK-3.0.4.0-bin.7z and used the contained libusbK-inf-wizard.exe, which wrote the cat file on my Windows 7 machine. The copied snipplet from the log file was the last install approach, maybe it was influenced by the previous trials. I asked the customer an he told me that SP2 is installed on the computer. I had expected that the cat file generated on my Windows 7 machine works on Vista too, but Vista (both 32 and 64bit) complain about the circumstance that the driver is not signed and offer this red dialog to continue anyway. This behaviour is same if the driver is generated on Windows XP, where no cat file is generated. On XP (32bit) the behaviour is sloghtly different. The selection box shows the device with the exclamation mark that the driver is not signed, but the dialog box which ask the user if really want to install an unsigned driver is not shown. |
|
|
On 12/22/2011 1:43 AM, Ekkehard wrote:
> Travis wrote >>> The installer was generated with the inf file generator from the libusbk >>> SDK >>> on a Windows 7 64bit machine. >> Hmm.. the libusbK InfWizard does not generate a .cat file and it seems >> that you have one. ;) >> > Hmm... I downloaded > http://usb-travis.googlecode.com/files/libusbK-3.0.4.0-bin.7z > http://usb-travis.googlecode.com/files/libusbK-3.0.4.0-bin.7z and used the > contained libusbK-inf-wizard.exe, which wrote the cat file on my Windows 7 > machine. > I will look into this. I just tried again and do not get a .cat file. I would encourage you to try again, but I'm not calling you a liar. ;) This is handled by libwdi so maybe I am missing something. > Travis wrote >> One thing I notice is this line: >> ! inf: Package was already in store: skipping Driver Store >> add >> >> I believe this means it is using a driver package that already exists in >> the driver store; not the one you specified. >> You can remove these with the 'pnputil' command line tool. This tool >> requires admin privs. >> List: pnputil -e >> Remove: pnputil -f -d oemXX.inf >> > The copied snipplet from the log file was the last install approach, maybe > it was influenced by the previous trials. > I agree. ..but I would still remove any old packages if possible. > Travis wrote >> If possible, install service pack 2. There is a blurb in the WDK >> release notes that states Vista can have problems with WinUSB, but >> presumably this was fixed in SP1. (WinUSB and libusbK or both KMDF based) >> http://msdn.microsoft.com/en-us/windows/hardware/gg487438 >> > I asked the customer an he told me that SP2 is installed on the computer. According to the log file it is a SP1. [Device Install Log] OS Version = 6.0.6001 Service Pack = 1.0 Suite = 0x0100 ProductType = 1 Architecture = amd64 > I had expected that the cat file generated on my Windows 7 machine works on > Vista too, but Vista (both 32 and 64bit) complain about the circumstance > that the driver is not signed and offer this red dialog to continue anyway. > This behaviour is same if the driver is generated on Windows XP, where no > cat file is generated. > On XP (32bit) the behaviour is sloghtly different. The selection box shows > the device with the exclamation mark that the driver is not signed, but the > dialog box which ask the user if really want to install an unsigned driver > is not shown. > > If you want to send me your driver package, I would be happy to test on my vista 64 system. Perhaps there is something small we are overlooking. If it fails for me too then it will make thing a whole lot easier! Regards, Travis ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
|
|
I double checked the exe file: it does create a cat file under Windows 7 64bit.
Yes the header of the log file shows SP1, but the file is large (50MB) and the first entries are 3 years old. So the entry in the header is useless :-) I have sent you the driver setup via "Transfer Big Files" to your private e-mail address Best regards Ekkehard |
|
|
On 12/22/2011 5:47 AM, Ekkehard wrote:
> I double checked the exe file: it does create a cat file under Windows 7 > 64bit. lol.. I am using win7 64bit too. Apparently there is something wrong here in the wizard. :) > Yes the header of the log file shows SP1, but the file is large (50MB) and > the first entries are 3 years old. So the entry in the header is useless :-) Yes, I see. So it probably does have SP2. > I have sent you the driver setup via "Transfer Big Files" to your private > e-mail address > Thanks. I have it and will get back to you shortly with my results. Regards, Travis ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
Re: Driver installation failed, Error 39, Vista 64 bit
|
|
In reply to this post by Travis
On Thu, Dec 22, 2011 at 1:46 AM, Travis <[hidden email]> wrote:
> On 12/21/2011 12:52 AM, Xiaofan Chen wrote: >> On Wed, Dec 21, 2011 at 4:47 PM, Xiaofan Chen<[hidden email]> wrote: >>> You may want to check if that Vista 64bit machine has been set up >>> to block unsigned driver package? > > I'm not sure this is even possible. An invalid .cat file should cause > windows to display the signed driver warning prompt. I cannot find any > policy settings that change this behavior is Vista or 7. Did you have > something specific in mind? > I forgot where I read it. It might be some posts in the OSR ntdev mailing list and might involve some 3rd party software management package. But I could not find anything now. Maybe I mixed it up with something else. -- Xiaofan ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
Re: Driver installation failed, Error 39, Vista 64 bit
|
|
In reply to this post by Ekkehard
On Thu, Dec 22, 2011 at 5:43 PM, Ekkehard
<[hidden email]> wrote: >> Hmm.. the libusbK InfWizard does not generate a .cat file and it seems >> that you have one. ;) >> > Hmm... I downloaded > http://usb-travis.googlecode.com/files/libusbK-3.0.4.0-bin.7z > and used the contained libusbK-inf-wizard.exe, which wrote > he cat file on my Windows 7 machine. > Hmm, that is really strange, you may want to delete the old driver package and then try again. libusbK's libusbK-inf-wizard.exe does not generate a cat file. -- Xiaofan ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
Re: Driver installation failed, Error 39, Vista 64 bit
|
|
In reply to this post by Ekkehard
On 2011.12.22 13:47, Ekkehard wrote:
> I double checked the exe file: it does create a cat file under Windows 7 > 64bit. The latest version of Libwdi will indeed create a cat file. It's the only means to avoid additional security prompts during installation. Not sure why Travis doesn't seem to see one. Do you get one when extracting a K driver with Zadig? Now the "A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider" errors are normal and do not impair the installation process... but only for the cat file. You seem to receive those for the .dll and .sys however, hence the pruned from copy, which means that Windows considers these files unusable, hence the ultimate CM_PROB_DRIVER_FAILED_LOAD. This is looks like the problem we need to address. Now, there are two possibilities here: - the digital signature on the .sys & .dll binaries is rejected by your system (unlikely, since a valid Authenticode certificate is used, which Windows should accept) - the (signed) hashes of the .sys and .dll from the cat file, which are also validated during installation, are being rejected because, unlike what is the case on most systems, the cat file is being deemed invalid. On way we can try to find out if the latter is the issue is if you ask the end user to find the extracted driver files, delete the cat file, and then try to install the driver manually (by right clicking on the device in device manager and then pointing to the inf). On a standard machine, this should work, but the user will be prompted with a "Windows's can't verify the publisher of this driver software". If, on the other hand, there is a restrictive policy in place on the end user's machine, they may get a different message, which might shed light on the problem. I'll see if I can play with policies on my machine to try to replicate the problem, as I suspect this might be the culprit, but if you could get your customer to try a manual installation after deleting the cat f Regards, /Pete ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libusb-win32-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel |
«
Return to LibUSB Dev - Win32
|
1 view|%1 views
Loading...
| Powered by Nabble | Edit this page |