Infrared not recognized

this is the second time Microsoft has destroyed the infrared device installation by pushing a Win 10 update that has had the infrared support totally screwed up.  And both times it has been in the middle of a trip.  The first time it caused me to lose a lot of dive data when I could not offload the dive computer, and I had no internet access to research the problem and figure out what to do. 

Same thing this time, except that now I had internet access to find this page, and use the "Apps and Features" path to fix, and I didn't even have to use the driver which I had downloaded and still had from the last time.

The "Settings -> Apps and Features... " path was VERY useful!  Thanks!

I just wish Microsoft would test the Win 10 releases before pushing them down out throats.  I still have a dive logging application which died two releases ago and I haven't figured out what they did so I can fix.  If anybody knows anything I would appreciate any help.  The application is DIVE.LOG, produced by SUBGEAR

Thanks for coming back to me.

I finally sorted it out.

The driver was the problem as I suspected, and the clue was as I thought, the missing stusb2ir.sys

So ...

I searched the working system (C:\windows\system32) for stusb2ir.sys and found this in a folder called:

C:\Windows\System32\DriverStore\FileRepository\stus2x64.inf_amd64_ca896a7a5ddcf390

This folder is a diver repository complete .inf file.  This folder was missing in the busted system.

So on the good system I copied the folder to a stick, removed this, inserted it in the laptop, opened device manager, updated drivers on the STIr42xx device (!) and added the driver (have disk) pointing this at the stick and it installed.  Once installed, the dongle started flashing as it should, and "Voila!", all good.

So I fired up Smartrak, and uploaded the missing dives, and all good.

So there you go.

I did not know about the driver file repository and now I know, this is a marvelous support tool.

Thanks again to you (smile) and Fritz for your help.

If I see you around the dive community, I will definitely buy you a  beer or 2!

I apologise as I do not have this device so I cannot check anythings.

Do you have the stusb2ir.sys file anywhere on your computer?

PLease see the related information on Windows 8.

https://answers.microsoft.com/en-us/windows/forum/all/sigmatel-usb-ir-driver-and-windows-8/f34399a0-4983-49d7-a09c-c4a3ce80786e

I uninstalled the STIr42xx (there is no check box to remove the drivers).  Removed the IRDa feature from Windows. Rebooted.  Downloaded the drivers and installed. (I note these refer to MosChip Semiconductor Technologies). Rebooted.  Installed the IRDa feature, then connected the dongle.  Same error conditions.  So I manually mapped the STIr42xx driver to the "existing driver" for InfraRed and this attached.  Rebooted.  SOme progress as the device is showing as InfraRed devices.  But when the dongle is inserted Device Manager now reports, "This device cannot start. (Code 10).  {Operation Failed}.  The requested operation was unsuccessful."  So while this is some progress, I am not yet convinced that the MosChip Semiconductor Technology is correct for this device.

I also note that the working system (desktop) shows Device Manager>InfraRed devices>USB 2.0 IrDa Bridge which is the Microsoft driver, while the laptop (broken system) shown Device Manager>USB-Infrared Adapter (!) which is the Scuba Pro MosChip driver.

So I reckon the issue remains that the MS driver stusb2ir.sys is the answer, not the generic scubapro drivers.  But I cannot work out how to restore this driver.  It is obviously missing from /online and also the restore image and of course these days, no original CD.

Needless to say I am not excited with Microsoft (again) at the moment.