Windows 10 Pro: USB IrDA adapter driver installation failed

Polar USB IrDA dongle doesn’t work on Windows 10 Pro. Below are the details after upgrading Windows 7 to Windows 10, 64-bit.

Fujitsu Esprimo C5731 (D3004-A1)

USB-IrDA Adapter Manufacturer:

ASIX Electronics Corporation

This device is not configured correctly. (Code 1)
Invalid access to memory location.
To find a driver for this device, click Update Driver.

Driver Management concluded the process to install driver mosuir64.inf_amd64_ff584e1d39dbb631\mosuir64.inf for Device Instance ID USB\VID_9710&PID_7780\5&1D1C12FA&0&2 with the following status: 0x3E6.

After running the latest Windows 10 update, still not working:

Replies (245) 

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

I worked for a company that supply software to work with our products through an IRDA link. We recommend (at present) a Lindy USB-IRDA dongle:

We are still supporting customers of our products (and will continue to do so) but this is becoming a real headache, especially when issues like this crop up.

I read this article with interest and believed it was the answers to my prayers. I have followed the instructions here but still struggling to get my dongle to work.

— Run Windows update over and over until there are no more updates available. Now running Windows 10 Version 1511 (OS Build 10586.545).

— Uninstalled and re-installed drivers over and over. I have also repeated this after the next thing I tried.

— Followed the command prompt instructions about re-binding the irda. I do however, get the message below when trying the netcfg -u ms_irdanetcfg -c p -I ms_irda:

. ms_irdanetcfg is not installed.

Trying to install ms_irda.

Is this my issue? That that the ms_irdanetcfg is not installed in the first place? I can’t think of anything else to try. Any suggestions welcomed!

Irda usb bridge драйвер windows 10

Вопрос

I represent a medical equipment company one of whose products relies heavily upon the IrDA functionality built into Windows.

Windows 10 does not currently support IrDA.

Please can a Microsoft representative confirm whether support has been dropped permanently, or that it is simply due to a short-term technical problem?

If the latter, when might support be reintroduced?

Many thanks in advance.

Ответы

We received lots of issues/complains about the IrDA device no longer works under Windows 10, However since there is no official formal declaration or article released yet, I cannot give your formal answer about this. Personally yes, seems like Infrared IrDA-Stack is removed from Windows 10. In the past, many vendors are using the IrDA stack, implemented in Windows. In previous Windows system, USB infrared receivers don’t need their own drivers or IrDA stack. It simply works. Now if Microsoft has removed the IrDA stack in Windows 10 RTM, so all USB infrared receivers/devices are bricked. Only, if a vender already has implemented its own IrDA stack and provides Windows 10 compatible software, the infrared receiver/devices may work. So at the present stage, our best bet would be device vendor.

Unfortunately we have not informed that if or when Windows 10 will bring it back in the future days, here is blog about this which has very good reference about this.

Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Irda usb bridge драйвер windows 10

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

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 ?

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

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

Azius Developer Training www.azius.com Windows device driver, internals, security, & forensics training and consulting. Blog at www.azius.com/blog

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.

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

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 ?

Sure, you can disable checking as described here and put the machine in Test Signing Mode as described here

Azius Developer Training www.azius.com Windows device driver, internals, security, & forensics training and consulting. Blog at www.azius.com/blog

Tried disable driver signature check approach, but no success either.

A bit different error anyway:

I think I will give-up for today and maybe try the test signature approach during weekend.

Thanks anyway Brian!

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.

MSDN documentation says that CM_PROB_FAILED_ADD error is related to AddDevice() fn not working properly.

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:

Same here. I’m sure there are many of us watching and hoping that you guys will find a way to make this work which we’re able to make use of after Polar ‘ditched’ us. Good luck.

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??

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)

Azius Developer Training www.azius.com Windows device driver, internals, security, & forensics training and consulting. Blog at www.azius.com/blog

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.

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.

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.

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

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:

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.

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.

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.

Please help to double check with MS’ engineers on this issue and let us know if they have any suggestions to improve this issue. Thanks a lot.

I have emailed again

Azius Developer Training www.azius.com Windows device driver, internals, security, & forensics training and consulting. Blog at www.azius.com/blog

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.

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.

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.

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:

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

I had «solved» using Ubuntu but. I do confirm!

Now with W10 Preview 11082 also my Polar ST725X and Sitecom irda USB dongle are back working again !

Thanks Tjatte for the info.

Ik Zou Graag Weten hoe je this Opgelost heb ontmoet je IrDA USB Dongle.

Met vriendelijke groet

Zou u mij hierover wat Uitleg Kunnen Geven, heb Zelf Een Polar RS400 Bijv. 11,802 downloaden en sycronized en Waar, heb Zelf al gezocht op Ubunto

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