Answered by:
Windows 10 IrDA: USB-IrDA adapter not working ?

-
Hi!
After upgrading Windows 7 Pro to Windows 10 Pro 64-bit, the USB-Irda adapter doesn't work anymore. Below you will find the DM dialogs related to this USB-IrDA adapter. My PC is Fujitsu Esprimo C5731.
When checking the driver INF file, it looks like it is implemented as NDIS miniport driver.
I also tried to update driver from manufacturer site by using Troubleshoot Compatibility mode to resolve driver problem but no success either.
Has Microsoft dropped support for IrDA on Windows 10 or is the problem driver related ?
Any tips how to resolve the issue other than return to Windows 7 ?
BR,
// Markku
Question
Answers
-
It appears that your driver isn't being loaded, likely because of a certificate problem. Win10 has new signing requirements documented here.
Azius Developer Training www.azius.com Windows device driver, internals, security, & forensics training and consulting. Blog at www.azius.com/blog
- Marked as answer by Brian Catlin [MVP]Moderator Friday, August 07, 2015 6:48 PM
All replies
-
Wow, people still use that? I suspect it isn't supported anymore.
Look at the installer log file C:\Windows\INF\SetupAPI.Dev.log to get more information on what failed
-Brian
Azius Developer Training www.azius.com Windows device driver, internals, security, & forensics training and consulting. Blog at www.azius.com/blog
- Proposed as answer by ProDev7 Friday, December 16, 2016 10:39 PM
-
Yep, Sport swatches manufactured by Polar use IR protocol for exercise data transfer between swatch and PC app. Millions of customers using Polar products, I suppose.
The SetupAPI.Dev.log related to dongle installation below. The problem seems to be when starting the device:
Device not started: Device has problem: 0x1f: CM_PROB_FAILED_ADD.
>>> Section start 2015/08/06 17:06:54.936 cmd: "C:\WINDOWS\system32\mmc.exe" C:\WINDOWS\system32\devmgmt.msc dvi: {DIF_UPDATEDRIVER_UI} 17:06:54.941 dvi: Class installer: Enter 17:06:54.945 dvi: Class installer: Exit dvi: Default installer: Enter 17:06:54.959 dvi: Default installer: Exit dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 17:06:54.968 ndv: {Update Driver Software Wizard for USB\VID_9710&PID_7780\5&10C6AE7B&0&2} ndv: Driver package 'g:\polar usb-ir dongle drivers\asix electronics\mcs7780_windows_drivers_v1.3.2.0_setup_v1.0.1.0\program files\asix electronics corporation\mcs7780 usb-infrared adapter windows drivers\64-bit\mosuir64.inf' exists under 'C:\WINDOWS\System32\DriverStore\FileRepository\mosuir64.inf_amd64_ff584e1d39dbb631\mosuir64.inf' (oem19.inf). dvi: Searching for hardware ID(s): dvi: usb\vid_9710&pid_7780&rev_0001 dvi: usb\vid_9710&pid_7780 dvi: Searching for compatible ID(s): dvi: usb\class_ff&subclass_00&prot_ff dvi: usb\class_ff&subclass_00 dvi: usb\class_ff dvi: Class GUID of device remains: {6bdd1fc5-810f-11d0-bec7-08002be2092f}. dvi: {Plug and Play Service: Device Install for USB\VID_9710&PID_7780\5&10C6AE7B&0&2} ndv: Driver INF Path: C:\WINDOWS\INF\oem19.inf ndv: Driver Node Name: mosuir64.inf:ed86ca11221ae399:MosIrUsb.Dev:1.3.2.0:usb\vid_9710&pid_7780 ndv: Driver Store Path: C:\WINDOWS\System32\DriverStore\FileRepository\mosuir64.inf_amd64_ff584e1d39dbb631\mosuir64.inf dvi: Searching for hardware ID(s): dvi: usb\vid_9710&pid_7780&rev_0001 dvi: usb\vid_9710&pid_7780 dvi: Searching for compatible ID(s): dvi: usb\class_ff&subclass_00&prot_ff dvi: usb\class_ff&subclass_00 dvi: usb\class_ff dvi: Class GUID of device changed to: {6bdd1fc5-810f-11d0-bec7-08002be2092f}. ndv: {Core Device Install} 17:07:27.260 ndv: {Installing device - USB\VID_9710&PID_7780\5&10C6AE7B&0&2} 17:07:27.263 ! ndv: Device class {6bdd1fc5-810f-11d0-bec7-08002be2092f} is not configurable. dvi: {DIF_ALLOW_INSTALL} 17:07:27.269 dvi: Using exported function 'NetClassInstaller' in module 'C:\WINDOWS\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Class installer: Enter 17:07:27.275 dvi: Class installer: Exit dvi: Default installer: Enter 17:07:27.293 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 17:07:27.296 dvi: {DIF_INSTALLDEVICEFILES} 17:07:27.298 dvi: Class installer: Enter 17:07:27.299 dvi: Class installer: Exit dvi: Default installer: Enter 17:07:27.301 dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 17:07:27.305 flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\mosuir64.inf_amd64_ff584e1d39dbb631\MosIrUsb.sys' to 'C:\WINDOWS\system32\DRIVERS\MosIrUsb.sys'. dvi: {DIF_REGISTER_COINSTALLERS} 17:07:27.388 dvi: Reset Device: Resetting device configuration. 17:07:27.392 dvi: Reset Device: Resetting device configuration completed. 17:07:27.394 dvi: Class installer: Enter 17:07:27.397 dvi: Class installer: Exit dvi: Default installer: Enter 17:07:27.400 dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 17:07:27.404 dvi: {DIF_INSTALLINTERFACES} 17:07:27.405 dvi: Class installer: Enter 17:07:27.408 dvi: Class installer: Exit dvi: Default installer: Enter 17:07:27.410 dvi: Default installer: Exit dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 17:07:27.414 dvi: {DIF_INSTALLDEVICE} 17:07:27.415 dvi: Class installer: Enter 17:07:27.417 dvi: {Install DEVICE} dvi: {Writing Device Properties} dvi: Strong Name=oem19.inf:ed86ca11221ae399:MosIrUsb.Dev:1.3.2.0:usb\vid_9710&pid_7780 dvi: {Writing Device Properties - Complete} inf: AddService=MosIrUsb,0x00000002,MosIrUsb.AddService,common.EventLog (mosuir64.inf line 39) dvi: Add Service: Modified existing service 'MosIrUsb'. dvi: {Install DEVICE exit (0x00000000)} dvi: Install Device: Configuring device class. 17:07:27.471 dvi: Install Device: Configuring device class completed. 17:07:27.472 dvi: {Restarting Devices} 17:07:27.474 dvi: Restart: USB\VID_9710&PID_7780\5&10C6AE7B&0&2 !!! dvi: Device not started: Device has problem: 0x1f: CM_PROB_FAILED_ADD. dvi: {Restarting Devices exit} 17:07:27.701 !!! dvi: Class installer: failed(0x0000001f)! !!! dvi: Error 31: A device attached to the system is not functioning. dvi: {DIF_INSTALLDEVICE - exit(0x0000001f)} 17:07:27.766 !!! ndv: Error(0000001f) installing device! ! ndv: Queueing up error report since device installation failed... ndv: {Installing device - exit(0x0000001f)} 17:07:27.894 ndv: {Core Device Install - exit(0x0000001f)} 17:07:27.895 dvi: {DIF_DESTROYPRIVATEDATA} 17:07:27.897 dvi: Class installer: Enter 17:07:27.898 dvi: Class installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 17:07:27.900 ump: {Plug and Play Service: Device Install exit(0000001f)} !!! ndv: Device install failed for device. !!! ndv: Error 31: A device attached to the system is not functioning. ndv: {Update Driver Software Wizard exit(0000001f)} <<< Section end 2015/08/06 17:07:33.576 <<< [Exit status: FAILURE(0x0000001f)]
- Edited by pulmark Friday, August 07, 2015 6:39 PM
-
It appears that your driver isn't being loaded, likely because of a certificate problem. Win10 has new signing requirements documented here.
Azius Developer Training www.azius.com Windows device driver, internals, security, & forensics training and consulting. Blog at www.azius.com/blog
- Marked as answer by Brian Catlin [MVP]Moderator Friday, August 07, 2015 6:48 PM
-
Hi!
Ok. Thanks for the info.
I'm not the driver developer for this dongle, but I have done some driver development earlier for Windows 2000 and also for Windows 8.1. For Windows 8.1 it was a bit PITA to test drivers during development but some-how it was possible to bypass the driver signature checking and also use some test signing procedures.
Does these features exist in Windows 10 also ?
Possible to use test signing for 3rd party drivers not developed by yourself for testing ?
Thanks,
// Markku
-
-
Tried disable driver signature check approach, but no success either.
A bit different error anyway:
! dvi: Device restart was skipped (DONOTCALLCONFIGMG). !!! dvi: Exception encountered while calling Class Installer! !!! dvi: Error 998: Invalid access to memory location. !!! dvi: Class installer: failed(0x000003e6)! !!! dvi: Error 998: Invalid access to memory location. dvi: {DIF_INSTALLDEVICE - exit(0x000003e6)} 23:48:11.407 !!! ndv: Error(000003e6) installing device!
I think I will give-up for today and maybe try the test signature approach during weekend.
Thanks anyway Brian!
// Markku
>>> [Device Install (Hardware initiated) - USB\VID_9710&PID_7780\5&10c6ae7b&0&2] >>> Section start 2015/08/07 23:48:10.532 dvi: {Build Driver List} 23:48:10.532 dvi: Searching for hardware ID(s): dvi: usb\vid_9710&pid_7780&rev_0001 dvi: usb\vid_9710&pid_7780 dvi: Searching for compatible ID(s): dvi: usb\class_ff&subclass_00&prot_ff dvi: usb\class_ff&subclass_00 dvi: usb\class_ff dvi: Created Driver Node: dvi: HardwareID - USB\VID_9710&PID_7780 dvi: InfName - C:\WINDOWS\System32\DriverStore\FileRepository\mosuir64.inf_amd64_ff584e1d39dbb631\mosuir64.inf dvi: DevDesc - USB-Infrared Adapter dvi: Section - MosIrUsb.Dev.NT dvi: Rank - 0x00ff0001 dvi: Signer Score - WHQL dvi: DrvDate - 07/01/2013 dvi: Version - 1.3.2.0 dvi: {Build Driver List - exit(0x00000000)} 23:48:10.563 dvi: {DIF_SELECTBESTCOMPATDRV} 23:48:10.563 dvi: Using exported function 'NetClassInstaller' in module 'C:\WINDOWS\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Class installer: Enter 23:48:10.594 dvi: Class installer: Exit dvi: Default installer: Enter 23:48:10.641 dvi: {Select Best Driver} dvi: Class GUID of device changed to: {6bdd1fc5-810f-11d0-bec7-08002be2092f}. dvi: {DIF_DESTROYPRIVATEDATA} 23:48:10.641 dvi: Class installer: Enter 23:48:10.641 dvi: Class installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 23:48:10.641 dvi: Selected: dvi: Description - [USB-Infrared Adapter] dvi: InfFile - [c:\windows\system32\driverstore\filerepository\mosuir64.inf_amd64_ff584e1d39dbb631\mosuir64.inf] dvi: Section - [MosIrUsb.Dev] dvi: {Select Best Driver - exit(0x00000000)} dvi: Default installer: Exit dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 23:48:10.657 ndv: {Core Device Install} 23:48:10.657 ndv: {Installing device - USB\VID_9710&PID_7780\5&10C6AE7B&0&2} 23:48:10.657 ! ndv: Device class {6bdd1fc5-810f-11d0-bec7-08002be2092f} is not configurable. dvi: {DIF_ALLOW_INSTALL} 23:48:10.657 dvi: Using exported function 'NetClassInstaller' in module 'C:\WINDOWS\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Class installer: Enter 23:48:10.672 dvi: Class installer: Exit dvi: Default installer: Enter 23:48:10.688 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 23:48:10.688 dvi: {DIF_INSTALLDEVICEFILES} 23:48:10.688 dvi: Class installer: Enter 23:48:10.688 dvi: Class installer: Exit dvi: Default installer: Enter 23:48:10.688 dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 23:48:10.766 flq: File 'C:\WINDOWS\system32\DRIVERS\MosIrUsb.sys' pruned from copy. dvi: {DIF_REGISTER_COINSTALLERS} 23:48:11.250 dvi: Reset Device: Resetting device configuration. 23:48:11.250 dvi: Reset Device: Resetting device configuration completed. 23:48:11.250 dvi: Class installer: Enter 23:48:11.266 dvi: Class installer: Exit dvi: Default installer: Enter 23:48:11.266 dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 23:48:11.266 dvi: {DIF_INSTALLINTERFACES} 23:48:11.266 dvi: Class installer: Enter 23:48:11.266 dvi: Class installer: Exit dvi: Default installer: Enter 23:48:11.282 dvi: Default installer: Exit dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 23:48:11.282 dvi: {DIF_INSTALLDEVICE} 23:48:11.282 dvi: Class installer: Enter 23:48:11.282 dvi: {Install DEVICE} dvi: {Writing Device Properties} dvi: Strong Name=oem19.inf:ed86ca11221ae399:MosIrUsb.Dev:1.3.2.0:usb\vid_9710&pid_7780 dvi: {Writing Device Properties - Complete} inf: AddService=MosIrUsb,0x00000002,MosIrUsb.AddService,common.EventLog (mosuir64.inf line 39) dvi: Add Service: Modified existing service 'MosIrUsb'. dvi: {Install DEVICE exit (0x00000000)} dvi: Install Device: Configuring device class. 23:48:11.375 dvi: Install Device: Configuring device class completed. 23:48:11.375 ! dvi: Device restart was skipped (DONOTCALLCONFIGMG). !!! dvi: Exception encountered while calling Class Installer! !!! dvi: Error 998: Invalid access to memory location. !!! dvi: Class installer: failed(0x000003e6)! !!! dvi: Error 998: Invalid access to memory location. dvi: {DIF_INSTALLDEVICE - exit(0x000003e6)} 23:48:11.407 !!! ndv: Error(000003e6) installing device! ! ndv: Queueing up error report since device installation failed... ndv: {Installing device - exit(0x000003e6)} 23:48:12.125 ndv: {Core Device Install - exit(0x000003e6)} 23:48:12.125 dvi: {DIF_DESTROYPRIVATEDATA} 23:48:12.125 dvi: Class installer: Enter 23:48:12.125 dvi: Class installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 23:48:12.125 <<< Section end 2015/08/07 23:48:12.688 <<< [Exit status: FAILURE(0x000003e6)]
-
Tried installing and using driver via signing it with test signature. I signed both catalog and binary (sys) file. Also added the test signature into Trusted Root Certificate Store and turned my PC into development mode to enable installation of test signed drivers.
No success. Still the same errors.
>>> [Device Install (DiShowUpdateDevice) - USB\VID_9710&PID_7780\5&10C6AE7B&0&2] >>> Section start 2015/08/09 14:28:12.801 cmd: "C:\WINDOWS\system32\mmc.exe" C:\WINDOWS\system32\devmgmt.msc dvi: {DIF_UPDATEDRIVER_UI} 14:28:12.817 dvi: Class installer: Enter 14:28:12.817 dvi: Class installer: Exit dvi: Default installer: Enter 14:28:12.832 dvi: Default installer: Exit dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 14:28:12.832 ndv: {Update Driver Software Wizard for USB\VID_9710&PID_7780\5&10C6AE7B&0&2} dvi: {DIF_SELECTDEVICE} 14:28:17.129 dvi: Class installer: Enter 14:28:17.129 dvi: Class installer: Exit dvi: {DIF_SELECTDEVICE - exit(0xe000020e)} 14:28:17.145 dvi: {DIF_SELECTDEVICE} 14:28:35.474 dvi: Class installer: Enter 14:28:35.490 dvi: Class installer: Exit dvi: {DIF_SELECTDEVICE - exit(0xe000020e)} 14:28:35.505 sto: {Setup Import Driver Package: g:\polar usb-ir dongle drivers\test\64-bit\mosuir64.inf} 14:28:46.443 inf: Provider: ASIX Electronics Corporation inf: Class GUID: {6bdd1fc5-810f-11d0-BEC7-08002BE2092F} inf: Driver Version: 08/01/2015,10.0.10240.16384 inf: Catalog File: MosIrUsb64.cat sto: {Copy Driver Package: g:\polar usb-ir dongle drivers\test\64-bit\mosuir64.inf} 14:28:46.459 sto: Driver Package = g:\polar usb-ir dongle drivers\test\64-bit\mosuir64.inf sto: Flags = 0x00000007 sto: Destination = C:\Users\Fujitsu\AppData\Local\Temp\{6df852f1-1cd4-044a-9e57-ec3c5410d438} sto: Copying driver package files to 'C:\Users\Fujitsu\AppData\Local\Temp\{6df852f1-1cd4-044a-9e57-ec3c5410d438}'. flq: Copying 'g:\polar usb-ir dongle drivers\test\64-bit\mosuir64.inf' to 'C:\Users\Fujitsu\AppData\Local\Temp\{6df852f1-1cd4-044a-9e57-ec3c5410d438}\mosuir64.inf'. flq: Copying 'g:\polar usb-ir dongle drivers\test\64-bit\MosIrUsb.sys' to 'C:\Users\Fujitsu\AppData\Local\Temp\{6df852f1-1cd4-044a-9e57-ec3c5410d438}\MosIrUsb.sys'. flq: Copying 'g:\polar usb-ir dongle drivers\test\64-bit\MosIrUsb64.cat' to 'C:\Users\Fujitsu\AppData\Local\Temp\{6df852f1-1cd4-044a-9e57-ec3c5410d438}\MosIrUsb64.cat'. sto: {Copy Driver Package: exit(0x00000000)} 14:28:46.537 pol: {Driver package policy check} 14:28:46.537 pol: {Driver package policy check - exit(0x00000000)} 14:28:46.537 sto: {Stage Driver Package: C:\Users\Fujitsu\AppData\Local\Temp\{6df852f1-1cd4-044a-9e57-ec3c5410d438}\mosuir64.inf} 14:28:46.553 inf: {Query Configurability: C:\Users\Fujitsu\AppData\Local\Temp\{6df852f1-1cd4-044a-9e57-ec3c5410d438}\mosuir64.inf} 14:28:46.553 inf: Driver package 'mosuir64.inf' is configurable. inf: {Query Configurability: exit(0x00000000)} 14:28:46.568 flq: Copying 'C:\Users\Fujitsu\AppData\Local\Temp\{6df852f1-1cd4-044a-9e57-ec3c5410d438}\mosuir64.inf' to 'C:\WINDOWS\System32\DriverStore\Temp\{52eafd99-9d91-1b4d-a779-3924ca133454}\mosuir64.inf'. flq: Copying 'C:\Users\Fujitsu\AppData\Local\Temp\{6df852f1-1cd4-044a-9e57-ec3c5410d438}\MosIrUsb.sys' to 'C:\WINDOWS\System32\DriverStore\Temp\{52eafd99-9d91-1b4d-a779-3924ca133454}\MosIrUsb.sys'. flq: Copying 'C:\Users\Fujitsu\AppData\Local\Temp\{6df852f1-1cd4-044a-9e57-ec3c5410d438}\MosIrUsb64.cat' to 'C:\WINDOWS\System32\DriverStore\Temp\{52eafd99-9d91-1b4d-a779-3924ca133454}\MosIrUsb64.cat'. sto: {DRIVERSTORE IMPORT VALIDATE} 14:28:46.599 sig: {_VERIFY_FILE_SIGNATURE} 14:28:46.615 sig: Key = mosuir64.inf sig: FilePath = C:\WINDOWS\System32\DriverStore\Temp\{52eafd99-9d91-1b4d-a779-3924ca133454}\mosuir64.inf sig: Catalog = C:\WINDOWS\System32\DriverStore\Temp\{52eafd99-9d91-1b4d-a779-3924ca133454}\MosIrUsb64.cat ! 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. sig: {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 14:28:46.631 sig: {_VERIFY_FILE_SIGNATURE} 14:28:46.631 sig: Key = mosuir64.inf sig: FilePath = C:\WINDOWS\System32\DriverStore\Temp\{52eafd99-9d91-1b4d-a779-3924ca133454}\mosuir64.inf sig: Catalog = C:\WINDOWS\System32\DriverStore\Temp\{52eafd99-9d91-1b4d-a779-3924ca133454}\MosIrUsb64.cat sig: Success: File is signed in Authenticode(tm) catalog. sig: Error 0xe0000242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted. sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 14:28:46.662 ! sig: Driver package signer is unknown, but user trusts signer. sig: Driver package certificate was successfully installed. sto: {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 14:29:03.381 sig: Signer Score = 0x0F000000 sig: Signer Name = WDKTestCert Fujitsu,130538539477748202 sto: {DRIVERSTORE IMPORT BEGIN} 14:29:03.381 sto: {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 14:29:03.396 cpy: {Copy Directory: C:\WINDOWS\System32\DriverStore\Temp\{52eafd99-9d91-1b4d-a779-3924ca133454}} 14:29:03.396 cpy: Target Path = C:\WINDOWS\System32\DriverStore\FileRepository\mosuir64.inf_amd64_57fbc9924cb580a9 cpy: {Copy Directory: exit(0x00000000)} 14:29:03.396 idb: {Register Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\mosuir64.inf_amd64_57fbc9924cb580a9\mosuir64.inf} 14:29:03.396 idb: Created driver package object 'mosuir64.inf_amd64_57fbc9924cb580a9' in DRIVERS database node. idb: Created driver INF file object 'oem57.inf' in DRIVERS database node. idb: Registered driver package 'mosuir64.inf_amd64_57fbc9924cb580a9' with 'oem57.inf'. idb: {Register Driver Package: exit(0x00000000)} 14:29:03.412 idb: {Publish Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\mosuir64.inf_amd64_57fbc9924cb580a9\mosuir64.inf} 14:29:03.412 idb: Activating driver package 'mosuir64.inf_amd64_57fbc9924cb580a9'. cpy: Published 'mosuir64.inf_amd64_57fbc9924cb580a9\mosuir64.inf' to 'oem57.inf'. idb: Indexed 2 device IDs for 'mosuir64.inf_amd64_57fbc9924cb580a9'. sto: Flushed driver database node 'DRIVERS'. Time = 62 ms sto: Flushed driver database node 'SYSTEM'. Time = 47 ms idb: {Publish Driver Package: exit(0x00000000)} 14:29:03.537 sto: {DRIVERSTORE IMPORT END} 14:29:03.537 sig: Installed catalog 'MosIrUsb64.cat' as 'oem57.cat'. sto: {DRIVERSTORE IMPORT END: exit(0x00000000)} 14:29:03.615 sto: {Stage Driver Package: exit(0x00000000)} 14:29:03.615 sto: {Setup Import Driver Package - exit (0x00000000)} 14:29:03.631 dvi: Searching for hardware ID(s): dvi: usb\vid_9710&pid_7780&rev_0001 dvi: usb\vid_9710&pid_7780 dvi: Searching for compatible ID(s): dvi: usb\class_ff&subclass_00&prot_ff dvi: usb\class_ff&subclass_00 dvi: usb\class_ff dvi: Class GUID of device remains: {6bdd1fc5-810f-11d0-bec7-08002be2092f}. dvi: {Plug and Play Service: Device Install for USB\VID_9710&PID_7780\5&10C6AE7B&0&2} ndv: Driver INF Path: C:\WINDOWS\INF\oem57.inf ndv: Driver Node Name: mosuir64.inf:ed86ca11221ae399:MosIrUsb.Dev:10.0.10240.16384:usb\vid_9710&pid_7780 ndv: Driver Store Path: C:\WINDOWS\System32\DriverStore\FileRepository\mosuir64.inf_amd64_57fbc9924cb580a9\mosuir64.inf dvi: Searching for hardware ID(s): dvi: usb\vid_9710&pid_7780&rev_0001 dvi: usb\vid_9710&pid_7780 dvi: Searching for compatible ID(s): dvi: usb\class_ff&subclass_00&prot_ff dvi: usb\class_ff&subclass_00 dvi: usb\class_ff dvi: Class GUID of device changed to: {6bdd1fc5-810f-11d0-bec7-08002be2092f}. ndv: {Core Device Install} 14:29:03.724 ndv: {Installing device - USB\VID_9710&PID_7780\5&10C6AE7B&0&2} 14:29:03.724 ! ndv: Device class {6bdd1fc5-810f-11d0-bec7-08002be2092f} is not configurable. dvi: {DIF_ALLOW_INSTALL} 14:29:03.740 dvi: Using exported function 'NetClassInstaller' in module 'C:\WINDOWS\system32\NetCfgx.dll'. dvi: Class installer == NetCfgx.dll,NetClassInstaller dvi: Class installer: Enter 14:29:03.740 dvi: Class installer: Exit dvi: Default installer: Enter 14:29:03.803 dvi: Default installer: Exit dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 14:29:03.803 dvi: {DIF_INSTALLDEVICEFILES} 14:29:03.803 dvi: Class installer: Enter 14:29:03.803 dvi: Class installer: Exit dvi: Default installer: Enter 14:29:03.803 dvi: Default installer: Exit dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 14:29:03.803 flq: Hardlinking 'C:\WINDOWS\System32\DriverStore\FileRepository\mosuir64.inf_amd64_57fbc9924cb580a9\MosIrUsb.sys' to 'C:\WINDOWS\system32\DRIVERS\MosIrUsb.sys'. dvi: {DIF_REGISTER_COINSTALLERS} 14:29:03.849 dvi: Reset Device: Resetting device configuration. 14:29:03.849 dvi: Reset Device: Resetting device configuration completed. 14:29:03.849 dvi: Class installer: Enter 14:29:03.849 dvi: Class installer: Exit dvi: Default installer: Enter 14:29:03.849 dvi: Default installer: Exit dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 14:29:03.865 dvi: {DIF_INSTALLINTERFACES} 14:29:03.865 dvi: Class installer: Enter 14:29:03.865 dvi: Class installer: Exit dvi: Default installer: Enter 14:29:03.865 dvi: Default installer: Exit dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 14:29:03.881 dvi: {DIF_INSTALLDEVICE} 14:29:03.881 dvi: Class installer: Enter 14:29:03.881 dvi: {Install DEVICE} dvi: {Writing Device Properties} dvi: Strong Name=oem57.inf:ed86ca11221ae399:MosIrUsb.Dev:10.0.10240.16384:usb\vid_9710&pid_7780 dvi: {Writing Device Properties - Complete} inf: AddService=MosIrUsb,0x00000002,MosIrUsb.AddService,common.EventLog (mosuir64.inf line 40) dvi: Add Service: Modified existing service 'MosIrUsb'. dvi: {Install DEVICE exit (0x00000000)} dvi: Install Device: Configuring device class. 14:29:03.912 dvi: Install Device: Configuring device class completed. 14:29:03.912 dvi: {Restarting Devices} 14:29:03.912 dvi: Restart: USB\VID_9710&PID_7780\5&10C6AE7B&0&2 !!! dvi: Device not started: Device has problem: 0x1f: CM_PROB_FAILED_ADD. dvi: {Restarting Devices exit} 14:29:04.193 !!! dvi: Class installer: failed(0x0000001f)! !!! dvi: Error 31: A device attached to the system is not functioning. dvi: {DIF_INSTALLDEVICE - exit(0x0000001f)} 14:29:04.256 !!! ndv: Error(0000001f) installing device! ! ndv: Queueing up error report since device installation failed... ndv: {Installing device - exit(0x0000001f)} 14:29:04.362 ndv: {Core Device Install - exit(0x0000001f)} 14:29:04.362 dvi: {DIF_DESTROYPRIVATEDATA} 14:29:04.362 dvi: Class installer: Enter 14:29:04.378 dvi: Class installer: Exit dvi: {DIF_DESTROYPRIVATEDATA - exit(0x00000000)} 14:29:04.378 ump: {Plug and Play Service: Device Install exit(0000001f)} !!! ndv: Device install failed for device. !!! ndv: Error 31: A device attached to the system is not functioning. ndv: {Update Driver Software Wizard exit(0000001f)} <<< Section end 2015/08/09 14:29:12.003 <<< [Exit status: FAILURE(0x0000001f)]
-
MSDN documentation says that CM_PROB_FAILED_ADD error is related to AddDevice() fn not working properly.
https://msdn.microsoft.com/en-us/library/windows/hardware/ff538951%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
Below is the image of usbview app that displays details about this USB-IrDa adapter device. No Open Pipes is the error there compared to other USB devices that are working:
-
Below is the installation file contents for the driver:
;;/********************************************************************* ; Installation script for MCS7780 (USB-IrDA Adapter) ; Target OS : Windows-64Bit ;;/********************************************************************* [Version] ;LayOutFile=layout.inf Signature = "$Windows NT$" Class = Infrared Provider = %ProviderName% ClassGUID = {6bdd1fc5-810f-11d0-BEC7-08002BE2092F} PnpLockDown = 1 DriverVer=08/01/2015,10.0.10240.16384 CatalogFile=MosIrUsb64.cat [Manufacturer] %MfgName%=MosIrDeviceList, NTamd64 [ControlFlags] ExcludeFromSelect = USB\VID_9710&PID_7780 [MosIrDeviceList.NTx86] %DeviceDesc%=MosIrUsb.Dev,USB\VID_9710&PID_7780 [MosIrDeviceList.NTamd64] %DeviceDesc%=MosIrUsb.Dev,USB\VID_9710&PID_7780 [DestinationDirs] MosIrUsb.CopyFiles = 12 DefaultDestDir = 12 [MosIrUsb.Dev.NT] CopyFiles=MosIrUsb.CopyFiles AddReg=MosIrUsb.AddReg, MosIrUsb.Params.AddReg, Uninstall.AddReg BusType=15 Characteristics = 0x84; NCF_PHYSICAL, NCF_HAS_UI [MosIrUsb.Dev.NT.Services] AddService = MosIrUsb, 0x00000002, MosIrUsb.AddService, common.EventLog [MosIrUsb.AddService] DisplayName = %MosIrUsb.SvcDesc% ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 3 ; SERVICE_DEMAND_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %12%\MosIrUsb.sys LoadOrderGroup = NDIS [MosIrUsb.AddReg] HKR, Ndi, HelpText, 0, %MosIrUsb.Help% HKR, Ndi, Service, 0, "MosIrUsb" HKR, Ndi\Interfaces, UpperRange, 0, "ndisirda" HKR, Ndi\Interfaces, LowerRange, 0, "nolower" HKR, Ndi, RequiredAll, 0, "MS_IrDA" [MosIrUsb.Params.AddReg] HKR,Ndi\params\TransceiverType,ParamDesc,,%strRXSEL% HKR,Ndi\params\TransceiverType,default,,"0" HKR,Ndi\params\TransceiverType,type,,"enum" HKR,Ndi\params\TransceiverType\enum,"0",,"Vishay TFD [Default]" HKR,Ndi\params\TransceiverType\enum,"1",,"Sharp GP2W100YP" HKR,Ndi\params\TransceiverType\enum,"2",,"Agilent 3602/3600" ;HKR,Ndi\params\TransceiverType\enum,"3",,"Infineon" ; ; IrDA Minimum Turnaround Time (value in microseconds) ; HKR,Ndi\params\MinTurnTime,ParamDesc,,%strIRDATURNTIME% HKR,Ndi\params\MinTurnTime,default,,"1000" HKR,Ndi\params\MinTurnTime,type,,"enum" HKR,Ndi\params\MinTurnTime\enum,"500",," 0.5 mS" HKR,Ndi\params\MinTurnTime\enum,"1000",," 1.0 mS [Default]" HKR,Ndi\params\MinTurnTime\enum,"5000",," 5.0 mS" HKR,Ndi\params\MinTurnTime\enum,"10000",,"10.0 mS" ; ; IrDA Speed enables ; ; ; Note: Miniport will always enable 9600, ; no matter what this key says ; HKR,Ndi\params\SpeedEnable,ParamDesc,,%strSPEEDENABLE% HKR,Ndi\params\SpeedEnable,type,,"enum" HKR,Ndi\params\SpeedEnable,default,,"4000000" HKR,Ndi\params\SpeedEnable\enum,"2400",, " 2400" HKR,Ndi\params\SpeedEnable\enum,"9600",, " 9600" HKR,Ndi\params\SpeedEnable\enum,"19200",, " 19200" HKR,Ndi\params\SpeedEnable\enum,"38400",, " 38400" HKR,Ndi\params\SpeedEnable\enum,"57600",, " 57600" HKR,Ndi\params\SpeedEnable\enum,"115200",, " 115200" HKR,Ndi\params\SpeedEnable\enum,"576000",, " 576000" HKR,Ndi\params\SpeedEnable\enum,"1152000",,"1152000" HKR,Ndi\params\SpeedEnable\enum,"4000000",,"4000000 [Default]" ; ; Specifies Write Depth to be used ; HKR,Ndi\params\WriteDepth,ParamDesc,,%strWRITEDEPTH% HKR,Ndi\params\WriteDepth,type,,"enum" HKR,Ndi\params\WriteDepth,default,,"20" HKR,Ndi\params\WriteDepth\enum,"01",, "01" HKR,Ndi\params\WriteDepth\enum,"02",, "02" HKR,Ndi\params\WriteDepth\enum,"03",, "03" HKR,Ndi\params\WriteDepth\enum,"04",, "04" HKR,Ndi\params\WriteDepth\enum,"05",, "05" HKR,Ndi\params\WriteDepth\enum,"06",, "06" HKR,Ndi\params\WriteDepth\enum,"07",, "07" HKR,Ndi\params\WriteDepth\enum,"08",, "08" HKR,Ndi\params\WriteDepth\enum,"09",, "09" HKR,Ndi\params\WriteDepth\enum,"10",, "10" HKR,Ndi\params\WriteDepth\enum,"11",, "11" HKR,Ndi\params\WriteDepth\enum,"12",, "12" HKR,Ndi\params\WriteDepth\enum,"13",, "13" HKR,Ndi\params\WriteDepth\enum,"14",, "14" HKR,Ndi\params\WriteDepth\enum,"15",, "15" HKR,Ndi\params\WriteDepth\enum,"16",, "16" HKR,Ndi\params\WriteDepth\enum,"17",, "17" HKR,Ndi\params\WriteDepth\enum,"18",, "18" HKR,Ndi\params\WriteDepth\enum,"19",, "19" HKR,Ndi\params\WriteDepth\enum,"20",, "20 [Default]" ; ; Specifies Read Depth to be used ; HKR,Ndi\params\ReadDepth,ParamDesc,,%strREADDEPTH% HKR,Ndi\params\ReadDepth,type,,"enum" HKR,Ndi\params\ReadDepth,default,,"20" HKR,Ndi\params\ReadDepth\enum,"01",, "01" HKR,Ndi\params\ReadDepth\enum,"02",, "02" HKR,Ndi\params\ReadDepth\enum,"03",, "03" HKR,Ndi\params\ReadDepth\enum,"04",, "04" HKR,Ndi\params\ReadDepth\enum,"05",, "05" HKR,Ndi\params\ReadDepth\enum,"06",, "06" HKR,Ndi\params\ReadDepth\enum,"07",, "07" HKR,Ndi\params\ReadDepth\enum,"08",, "08" HKR,Ndi\params\ReadDepth\enum,"09",, "09" HKR,Ndi\params\ReadDepth\enum,"10",, "10" HKR,Ndi\params\ReadDepth\enum,"11",, "11" HKR,Ndi\params\ReadDepth\enum,"12",, "12" HKR,Ndi\params\ReadDepth\enum,"13",, "13" HKR,Ndi\params\ReadDepth\enum,"14",, "14" HKR,Ndi\params\ReadDepth\enum,"15",, "15" HKR,Ndi\params\ReadDepth\enum,"16",, "16" HKR,Ndi\params\ReadDepth\enum,"17",, "17" HKR,Ndi\params\ReadDepth\enum,"18",, "18" HKR,Ndi\params\ReadDepth\enum,"19",, "19" HKR,Ndi\params\ReadDepth\enum,"20",, "20 [Default]" ; ; Specifies Read Threshold to be used ; HKR,Ndi\params\ReadThreshold,ParamDesc,,%strREADTHRESHOLD% HKR,Ndi\params\ReadThreshold,type,,"enum" HKR,Ndi\params\ReadThreshold,default,,"05" HKR,Ndi\params\ReadThreshold\enum,"00",, "00" HKR,Ndi\params\ReadThreshold\enum,"01",, "01" HKR,Ndi\params\ReadThreshold\enum,"02",, "02" HKR,Ndi\params\ReadThreshold\enum,"03",, "03" HKR,Ndi\params\ReadThreshold\enum,"04",, "04" HKR,Ndi\params\ReadThreshold\enum,"05",, "05 [Default]" HKR,Ndi\params\ReadThreshold\enum,"06",, "06" HKR,Ndi\params\ReadThreshold\enum,"07",, "07" HKR,Ndi\params\ReadThreshold\enum,"08",, "08" HKR,Ndi\params\ReadThreshold\enum,"09",, "09" HKR,Ndi\params\ReadThreshold\enum,"10",, "10" HKR,Ndi\params\ReadThreshold\enum,"11",, "11" HKR,Ndi\params\ReadThreshold\enum,"12",, "12" HKR,Ndi\params\ReadThreshold\enum,"13",, "13" HKR,Ndi\params\ReadThreshold\enum,"14",, "14" HKR,Ndi\params\ReadThreshold\enum,"15",, "15" HKR,Ndi\params\ReadThreshold\enum,"16",, "16" HKR,Ndi\params\ReadThreshold\enum,"17",, "17" HKR,Ndi\params\ReadThreshold\enum,"18",, "18" HKR,Ndi\params\ReadThreshold\enum,"19",, "19" ; ; The maximum number of outgoing frames that the miniport driver's ; NIC can handle at one time( i.e SendWindowSize ) ; HKR,Ndi\params\SendWindowSize,ParamDesc,,%strSENDWINDOWSIZE% HKR,Ndi\params\SendWindowSize,type,,"enum" HKR,Ndi\params\SendWindowSize,default,,"01" HKR,Ndi\params\SendWindowSize\enum,"01",, "01 [Default]" HKR,Ndi\params\SendWindowSize\enum,"02",, "02" HKR,Ndi\params\SendWindowSize\enum,"03",, "03" HKR,Ndi\params\SendWindowSize\enum,"04",, "04" HKR,Ndi\params\SendWindowSize\enum,"05",, "05" HKR,Ndi\params\SendWindowSize\enum,"06",, "06" HKR,Ndi\params\SendWindowSize\enum,"07",, "07" ; ; The maximum number of incoming frames that the miniport driver's ; NIC can handle at one time( i.e ReceiveWindowSize ) ; HKR,Ndi\params\ReceiveWindowSize,ParamDesc,,%strRECEIVEWINDOWSIZE% HKR,Ndi\params\ReceiveWindowSize,type,,"enum" HKR,Ndi\params\ReceiveWindowSize,default,,"04" HKR,Ndi\params\ReceiveWindowSize\enum,"01",, "01" HKR,Ndi\params\ReceiveWindowSize\enum,"02",, "02" HKR,Ndi\params\ReceiveWindowSize\enum,"03",, "03" HKR,Ndi\params\ReceiveWindowSize\enum,"04",, "04 [Default]" HKR,Ndi\params\ReceiveWindowSize\enum,"05",, "05" HKR,Ndi\params\ReceiveWindowSize\enum,"06",, "06" HKR,Ndi\params\ReceiveWindowSize\enum,"07",, "07" ; ; Turbo Mode On/Off ; HKR,Ndi\params\TurboMode,ParamDesc,,%strTURBOMODE% HKR,Ndi\params\TurboMode,type,,"enum" HKR,Ndi\params\TurboMode,default,,"1" HKR,Ndi\params\TurboMode\enum,"0",, "Off " HKR,Ndi\params\TurboMode\enum,"1",, "On [Default]" ; ; SIR Tweak Enable/Disable ; HKR,Ndi\params\SIRTweak,ParamDesc,,%strSIRTWEAK% HKR,Ndi\params\SIRTweak,type,,"enum" HKR,Ndi\params\SIRTweak,default,,"1" HKR,Ndi\params\SIRTweak\enum,"0",, "Disable " HKR,Ndi\params\SIRTweak\enum,"1",, "Enable [Default] " ; ; Power Down Enable/Disable ; HKR,Ndi\params\PowerDown,ParamDesc,,%strPOWERDOWN% HKR,Ndi\params\PowerDown,type,,"enum" HKR,Ndi\params\PowerDown,default,,"0" HKR,Ndi\params\PowerDown\enum,"0",, "Disable [Default]" HKR,Ndi\params\PowerDown\enum,"1",, "Enable " ; ; The Receive Mode Fast/Slow ; HKR,Ndi\params\ReceiveMode,ParamDesc,,%strRECEIVEMODE% HKR,Ndi\params\ReceiveMode,type,,"enum" HKR,Ndi\params\ReceiveMode,default,,"1" HKR,Ndi\params\ReceiveMode\enum,"0",, "Slow" HKR,Ndi\params\ReceiveMode\enum,"1",, "Fast [Default]" ; ; The Receive Sensitivity ; HKR,Ndi\params\ReceiveSensitivity,ParamDesc,,%strRECEIVESENSITIVITY% HKR,Ndi\params\ReceiveSensitivity,type,,"enum" HKR,Ndi\params\ReceiveSensitivity,default,,"5" HKR,Ndi\params\ReceiveSensitivity\enum,"0",, "Disable" HKR,Ndi\params\ReceiveSensitivity\enum,"5",, "Enable [Default]" ; ; SIR Turbo Mode On/Off ; HKR,Ndi\params\SirTurbo,ParamDesc,,%strSIRTURBO% HKR,Ndi\params\SirTurbo,type,,"enum" HKR,Ndi\params\SirTurbo,default,,"0" HKR,Ndi\params\SirTurbo\enum,"0",, "Off [Default]" HKR,Ndi\params\SirTurbo\enum,"1",, "On" ; ; The ExtendedMode feature Enable/Disable ; HKR,Ndi\params\ExtendedMode,ParamDesc,,%strEXTENDEDMODE% HKR,Ndi\params\ExtendedMode,type,,"enum" HKR,Ndi\params\ExtendedMode,default,,"1" HKR,Ndi\params\ExtendedMode\enum,"0",, "Off" HKR,Ndi\params\ExtendedMode\enum,"1",, "On [Default]" ; ; Debug Print Level Selection ; HKR,Ndi\params\DebugLevel,ParamDesc,,%strDEBUGLEVEL% HKR,Ndi\params\DebugLevel,type,,"enum" HKR,Ndi\params\DebugLevel,default,,"0" HKR,Ndi\params\DebugLevel\enum,"0",, "None [Default]" HKR,Ndi\params\DebugLevel\enum,"1",, "Errors " HKR,Ndi\params\DebugLevel\enum,"2",, "Warnings " HKR,Ndi\params\DebugLevel\enum,"4",, "Trace " ; ; ExtraBOFs Required ; HKR,Ndi\params\ExtraBOFs,ParamDesc,,%strEXTRABOFS% HKR,Ndi\params\ExtraBOFs,type,,"enum" HKR,Ndi\params\ExtraBOFs,default,,"0" HKR,Ndi\params\ExtraBOFs\enum,"0",, "00 [Default]" HKR,Ndi\params\ExtraBOFs\enum,"1",, "01 " HKR,Ndi\params\ExtraBOFs\enum,"2",, "02 " HKR,Ndi\params\ExtraBOFs\enum,"3",, "03 " HKR,Ndi\params\ExtraBOFs\enum,"6",, "06 " HKR,Ndi\params\ExtraBOFs\enum,"12",, "12 " HKR,Ndi\params\ExtraBOFs\enum,"24",, "24 " HKR,Ndi\params\ExtraBOFs\enum,"48",, "48 " ; ; Specifies the Time to wait(in micro secs) before transmission ; HKR,Ndi\params\TimeToWait,ParamDesc,,%strTIMETOWAIT% HKR,Ndi\params\TimeToWait,type,,"enum" HKR,Ndi\params\TimeToWait,default,,"700" HKR,Ndi\params\TimeToWait\enum,"0",, "0" HKR,Ndi\params\TimeToWait\enum,"10",, "010" HKR,Ndi\params\TimeToWait\enum,"20",, "020" HKR,Ndi\params\TimeToWait\enum,"50",, "050" HKR,Ndi\params\TimeToWait\enum,"100",, "100" HKR,Ndi\params\TimeToWait\enum,"250",, "250" HKR,Ndi\params\TimeToWait\enum,"500",, "500" HKR,Ndi\params\TimeToWait\enum,"600",, "600" HKR,Ndi\params\TimeToWait\enum,"700",, "700 [Default]" HKR,Ndi\params\TimeToWait\enum,"800",, "800" HKR,Ndi\params\TimeToWait\enum,"900",, "900" [common.EventLog] AddReg = common.AddEventLog.reg [common.AddEventLog.reg] HKR, , EventMessageFile, 0x00020000, "%%SystemRoot%%\System32\netevent.dll" HKR, , TypesSupported, 0x00010001, 7 [MosIrUsb.CopyFiles] MosIrUsb.sys [SourceDisksFiles] MosIrUsb.sys=1 [SourceDisksNames] 1 = %strDRIVERDISK%,,, [Uninstall.AddReg] ;HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%USB\VID_9710&PID_7780.DeviceDesc%,DisplayName,0,%DeviceDesc% ;HKLM,SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%USB\VID_9710&PID_7780.DeviceDesc%,UninstallString,0,MosIrUnInst.exe ;---------------------------------------------------------------; [Strings] ProviderName="ASIX Electronics Corporation" MfgName="ASIX Electronics Corporation" DeviceDesc="USB-Infrared Adapter" USB\VID_9710&PID_7780.DeviceDesc="USB-Infrared Adapter" MosIrUsb.SvcDesc="MosIrUsb.sys" MosIrUsb.Help = "The USB-IrDA is a fast IrDA infrared port. It can be used to establish wireless serial and network links to other computers." strRXSEL="Infrared Transceiver Type" strIRDATURNTIME="Min. Turn-Around Time" strSPEEDENABLE="Speed Enable" strREADDEPTH="ReadDepth" strWRITEDEPTH="WriteDepth" strREADTHRESHOLD="ReadThreshold" strSENDWINDOWSIZE = "Send Window Size" strRECEIVEWINDOWSIZE = "Receive Window Size" strTURBOMODE="Turbo Mode" strSIRTWEAK="SIRTweak" strPOWERDOWN="PowerDown" strRECEIVEMODE="ReceiveMode" strRECEIVESENSITIVITY="Receive Sensitivity" strSIRTURBO="SIR Turbo" strEXTENDEDMODE="Extended Mode" strDEBUGLEVEL="DebugLevel" strEXTRABOFS="Extra BOFs" strTIMETOWAIT="Time To Wait" strDRIVERDISK="USB-IrDA Device Installation Disc"
-
Hi,
I'm writing from Italy and I'm facing the same problem after the update from Windows 8.1 to Windows 10 and indeed now I cannot move anymore the data from my Polar watch to the PC.
With the "basic" set-up for drivers I was not able to solve the problem and I didn't find any updated driver from the irda-usb device supplier.
Unfortunatelly with the software I'm not skilled like you are so, I really hope you will find a solution and then you can share it.
I'm crossing my fingers...Thanks
Gianluca -
-
-
I e-mailed ASIX technical support yesterday and received a reply late last night. With permission...
"Thanks a lot for your inquiry. This is Allan Chou. I'm the technical support from ASIX Electronics
We can also reproduce this issue in our site and found there is no USB to IrDA product can work fine on Windows 10 system so far. Our engineers are investigating this issue and also trying to double check with Microsoft if the Windows 10 system can still support well the USB to IrDA products or not? We will update the revised driver onto our web site ASAP if the Windows 10 system can support well the USB to IrDA products. If you got any useful information to isolate this issue, please feel free to let us know to speed up to isolate this issue soon. Thanks a lot for your great feedback."
I asked for permission to post the reply to this forum.
"You are welcome to post my reply to Microsoft forum and can provide my contact information to Microsoft guys in case they would like to discuss with us for more details directly. Thanks a lot for your great helps"
I forwarded the URL for this forum to ASIX and they will be reviewing the detailed work by Pulmark. (I sent the URL o the forum in my initial e-mail but the posts were not reviewed prior to the preply from ASIC technical support).
What are the ethics about posting contact info on this site? Should I post the contact info for the ASIX engineer that replied to my e-mail inquiry??
- Edited by CR500AF Thursday, August 13, 2015 1:32 PM
-
You can post his contact info since he gave his permission, but do so in a way that the email address harvesting bots won't recognize it, otherwise, he'll be spammed within an inch of his life. For example: someone company.com (don't use @ or 'at' because the bots recognize those)
-Brian
Azius Developer Training www.azius.com Windows device driver, internals, security, & forensics training and consulting. Blog at www.azius.com/blog
-
-
Dear Brian,
This is Allan Chou. I'm the technical support from ASIX Electronics. Our engineers are investigating this MCS7780 USB to IrDA Windows driver installation failure issue on Windows 10 system, but we have no ideas why it cannot work on Windows 10 system yet. We had also verified the other USB to IrDA products on Windows 10 system but there is no USB to IrDA product can work fine on Windows 10 system so far.
For Windows 10 new certificate issue, we had verified our other products (such as USB to LAN/USB to UART/etc.) Win8.x WHCK drivers on Windows 10 system and they all work fine except the USB to IrDA driver. We had also verified MCS7780 Win8.x WHCK driver under Win 10 test mode (i.e. disabled the Disable Driver Signature Enforcement) but it got the same issue. So we don’t think this issue is caused by the new Win10 certificate rule issue.If possible, please help us to double check with MS engineers if there are any changes about the USB to IrDA products supporting between Win10 and Win8.1? If yes, please advise some details of the changes so we can modify MCS7780 USB to IrDA Windows driver to support WIndows 10 system soon. Thanks a lot for your great helps.
-
Same problem here. My ASIX USB-IrDA adapter no longer works in Win10 and can no longer sync my S625X Polar watch. Hope Microsoft and ASIX work something out pronto but with all the other Win10 glitches, I imagine (unfortunately) that making USB-IrDA adapters work is way down on Microsoft's list of priorities. Too bad for us!
-
...
If possible, please help us to double check with MS engineers if there are any changes about the USB to IrDA products supporting between Win10 and Win8.1? If yes, please advise some details of the changes so we can modify MCS7780 USB to IrDA Windows driver to support WIndows 10 system soon. Thanks a lot for your great helps.
Dear Brian,
Is there any chance you can help to check with MS guys on my questions and give us some hints to solve this issue soon? Thanks a lot for your great helps.
-
Hi Allan,
Just a note on the Polar IrDA device problem
Windows 8 worked for me only on a Yoga Pro 3. It did not work on a MS Surface Pro 3 (direct, dock or USB hub).
I have yet to test it on the Yoga Pro 3 w/ 10. Still doesn't work on a Surface Pro 3 w/ 10
-
I have requested that the developers take a look at this. Vacations may interfere with a timely response
-Brian
Azius Developer Training www.azius.com Windows device driver, internals, security, & forensics training and consulting. Blog at www.azius.com/blog
-
Please post a report to the Windows 10 feedback tool (so far I only found 2 posts there re. USB Irda adapters; both re UWATEC dive computers including mine). It doesn't seem to be a Polar specific issue but seems to affect all IRDA adapters.
The more posts in the feedback tool, the more likely this function comes back to Windows 10.
-
I found a bit more information about the problem:
http://answers.microsoft.com/en-us/insider/forum/insider_apps-insider_other/irda-not-working-build-10166/4318715b-7939-48e5-a339-7665f2bd3fcd
At least Polar USB-IrDA dongle has been working on Windows 10 build 10041 and then stopped working. So using this information it should be easier to identify the problem. Hope somebody inside MS is working on this problem.
// Markku
- Edited by pulmark Sunday, August 23, 2015 4:49 PM
-
HI - and thanks to Allan Chou for enligthening me about this fora.
Yes - I still use PolarProTrainer5 and my RS800CX.
New Polar gear do not support PPT5 and not IrDA - only sky-loading.
I have almost dayly trainings since 1990 and wil continu using PPT5 for comparishment.
I also want to be sole responsible for the data security on my own.
To the matter :
The driver worked fine up to build 10041 and haven't worked since.
As mencioned, I have the same issue and codes and suspecded also that ID-labeling could be the problem. In some way it is possible to unlock the need of driver ID.I tryed once in an earlier build, with no result. Now I can't remember how I did it - and if I did i correctly.......
Anyone of You have knowledge of the precidure ?
ASUS Sabertooth 990FX - FX4150 - XM3S 2x4GB - Intel 520 120GB.
- Merged by Doron Holan [MSFT]Owner Monday, August 24, 2015 5:00 PM part of thread
-
-
-
BTW, we also found the Windows 10 system has removed the “IrDA” application in Windows 10 Control Panel console (that is supported on Windows 8.1 system) so we suspect MS had removed some IrDA devices supporting features now.
==========
If possible, please help us to double check with MS engineers if there are any changes about the USB to IrDA products supporting between Win10 and Win8.1? If yes, please advise some details of the changes so we can modify MCS7780 USB to IrDA Windows driver to support WIndows 10 system soon. Thanks a lot for your great helps.
Dear Brian,
Is there any chance you can help to check with MS guys on my questions and give us some hints to solve this issue soon? Thanks a lot for your great helps.
- Edited by allanchou Tuesday, September 08, 2015 8:40 AM
-
-
-
-
Here is another Microsoft forum in which it is (unofficially) concluded that the IrDA stack has been removed from Windows 10 and any vendor desiring to implement an IrDA stack would have to go through Microsoft to get it to run under Windows 10.
https://social.technet.microsoft.com/Forums/en-US/096ff792-13fa-4552-be76-b19284f8ee75/irda-support-for-windows-10?forum=win10itprohardware
Hope Microsoft realizes the error of their ways and that a lot of us are going to be pissed that our expensive Polar watches no longer work (guess we're supposed to buy MS Bands.....).
And there is also this most informative post referenced in the social.technet.microsoft.com link that I posted 2 paragraphs above:
http://borncity.com/win/2015/09/02/windows-10-infrared-irda-stack-is-removed/
- Edited by Jim Lewis Friday, October 09, 2015 9:14 AM
-
-
-
IrDA stack is back and in device manager everything looks good but infrared light is not working and device not connecting but still a good step forward
At least on my computer Device manager is complaining that (with ASIX Irda) there is a problem with the driver:
This device is not configured correctly. (Code 1) Invalid access to memory location. [...]
-
IrDA stack is back and in device manager everything looks good but infrared light is not working and device not connecting but still a good step forward
Same for me - When I attempt to sync my Polar RS800 to Polar Pro Trainer 5 I get an error saying that a communications port could not be opened. -
-
-
-
-
Just received this email from Coolgear.
Since I am not using an insider version of Windows, I guess I will have to wait a bit more for the damn thing to work in the regular version of Windows.
Windows 10 now has working IrDA - Sorta
Our Supplier provided us with an updated driver last week, and we've been testing it here as best we could (we only have a few IrDA products to test with). Long story short, the driver they have given us is identical to the one already on our website (and ASIX's).As our last update mentioned, the current driver installs and seems to function fine in the current version of Windows 10, but Windows does not seem to understand how to use the IrDA devices beyond installing the driver. That seems to have changed in the latest pre-release (AKA "Insider Builds") versions of Windows 10.
The vendor recommends that anything newer than build 11082 should work, and our testing shows that the current version installed in the Fast Track is 14316. We found that Window 10 build 14316 will download and install the appropriate driver (v1.3.2.0) as well as launch the IrDA stack service now.We've tested the IrDA products we had around the office and found that all of them are working exactly as they had in previous editions of Windows.
Steps to get IrDA working in Windows 10:
1. Make Microsoft account. (If you don't have one already).
2. Sign into Windows 10 with your MS account. (If not already doing so).
3. Select to update to "Insider Builds". When prompted, pick the "Fast" option.
4. Update to the latest build offered. (NOTE: It may take up to 24 hours from joining the insider program before a specific build update is offered in Windows Update). -
As of May 2016, 10 months after the release of Windows 10 USB-IrDA adapters are still not working :
•The device is compatible with Windows 10, and the driver is automatically retrieved by Windows 10 and installed (Version 1.3.0.0 Dated: 18 May 2007) when the device is used for the first time. BTW Version 1.3.2.0 Dated: 1st Jul, 2013 is available on Coolgear's et ASIX's WEB site.
•BUT, Windows 10 currently doesn't have IrDA stack enabled. You currently won't be able to communicate with your POLAR watch, SCUBAPRO/UWATEC dive computer and a PC running on Windows 10.
•Microsoft has released insider preview updates of Windows 10 with IrDA stack enabled. However, these updates are currently available for Microsoft Insider (testers) only.
•Microsoft doesn't communicate on the availability of these latest updates for public use.
Hopefully in Windows 10 Anniversary update our USB-IrDA adaptors will function properly again!À ce jour soit en Mai 2016, 10 mois depuis le lancement de Windows 10 les adaptateurs USB-IrDA ne fonctionnent toujours pas :
•L'interface est compatible avec Windows 10. Le système lancera automatiquement la recherche de pilote à la première utilisation du périphérique et installera la Version 1.3.0.0 datée: 18 Mai, 2007. (Une version 1.3.2.0 datée: 1er Jul, 2013 est disponible sur les sites WEB de Coolgear et ASIX)
•CEPENDANT, à ce jour, la fonctionnalité de gestion de communication par infrarouge sous Windows 10 n'a pas encore été activée par Microsoft. La communication entre votre montre POLAR, ordinateur de plongée SCUBAPRO/UWATEC et un PC sous Windows 10 est donc pour le moment impossible.
•Microsoft a publié des mises à jour pour la version Insider Preview de Windows 10 dans lesquelles la communication par infrarouge est activée. Elles sont néanmoins actuellement disponibles uniquement pour les testeurs du programme Microsoft Insider.
•Microsoft n'a pour le moment pas fait d'annonce concernant la date de disponibilité de ces dernières mises à jour pour la version grand public de Windows 10.
En espérant que nos adaptateurs USB-IrDA redeviennent fonctionnels avec le lancement de la mise à jour Anniversaire de Windows 10- Edited by Claude.Qc Sunday, May 08, 2016 6:14 PM
-
My Polar Irda device does not work in Win 10 Home Insider Preview Build 14372.rs1_release.160620-2342. MosIrUsb.sys driver is version 1.3.2.0 date 2013-07-01 from ASIX Electronics Corporation. Status code is 31. SC QUERY IRMON, IRDA and even MOSIRUSB are in RUNNING state after command SC START them.