Infrared not recognized

Anonymous

Upgraded to Windows 10 ver 1903 and the infrared device is not working. Got this:

Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Dalvic do you still have the problem?

Try to remove and re-add the Infrared. It is probably more reliable to use the PowerShell Commands (If you are not comfortable you can try the interface which may not work.

Power Shell to Add / remove IrDA infrared components

Run PowerShell as administrator

Query state of the IrDA components:

get-WindowsCapability -online -Name "Network.Irda~~~~0.0.1.0"

Unistall

Remove-WindowsCapability -online -Name "Network.Irda~~~~0.0.1.0"

Add

add-WindowsCapability -online -Name "Network.Irda~~~~0.0.1.0"

Query state of the IrDA components:

get-WindowsCapability -online -Name "Network.Irda~~~~0.0.1.0"

An example of the results (Thanks to FritzMerkel) of the scripts when fixing IrDA issue.

PS C:\WINDOWS\system32> get-WindowsCapability -online -Name "Network.Irda~~~~0.0.1.0"

Name : Network.Irda~~~~0.0.1.0

State : NotPresent

DisplayName : IrDA infrared

Description : Support for IrDA devices. Requires special IrDA hardware.

DownloadSize : 604101

InstallSize : 1236233

PS C:\WINDOWS\system32>

Then the others:

PS C:\WINDOWS\system32> Remove-WindowsCapability -online -Name "Network.Irda~~~~0.0.1.0"

Path :Online : TrueRestartNeeded : False

PS C:\WINDOWS\system32> add-WindowsCapability -online -Name "Network.Irda~~~~0.0.1.0">>

Path :Online : TrueRestartNeeded : False

PS C:\WINDOWS\system32> get-WindowsCapability -online -Name "Network.Irda~~~~0.0.1.0"

Name : Network.Irda~~~~0.0.1.0State : InstalledDisplayName : IrDA infraredDescription : Support for IrDA devices. Requires special IrDA hardware.DownloadSize : 604101InstallSize : 1236233

Alternative: on windows interface:

To remove:

Go to Settings -> Apps and Features -> Optional Features

Select IrDA Infrared and click uninstall.

To Install

Go to Settings -> Apps and Features -> Optional Features

Add a feature (top of list)

Select IrDA Infrared from the list.

It installs and should be visible in the Optional Features list.

Go back to Control Panel\All Control Panel Items and hopefully you will now see Infra Red icon and features.

If this does not work do use the PowerShell commands

0 comments

77 additional answers

Anonymous

2019-11-03T14:17:14+00:00

That [DIVE.LOG, produced by SUBGEAR] is not the same as Dive Log 6.0 I take it? What are you using now? May be time to move to Dive Log 6 or Subgear. Both are good and well supported, UNLIKE the trash that often comes out from the 'big dive computers sales companies' who only want to sell the computers.

Which version of Win10 do you have, Home or Pro? Both have methods to (mostly) stop upgrades. Good policy with Win10 is to stay WELL behind the upgrade curve. Let other people be beta testers.
Was this answer helpful?

0 comments No comments
Anonymous

2019-11-07T16:35:08+00:00

The DIVE.LOG is the one produced by Subgear which was came with the XP10 dive computer. It is a pathetic piece of unfriendly software that, unfortunately, I used because I didn't know any better and now I have a lot of dive data in. It still runs in my Win 7 machine, but won't run in the Win 10 Home machine.

I installed Subgear in the Win 10 Home machine after concluding it was time to move off DIVE.LOG and it worked fine until the most recent Win 10 "upgrade" which broke it, just like it broke Dive.Log back in the winter of 2016. That caused me to lose a lot of data until I fixed it At that time, I managed to locate and reinstall the Infrared driver and brought Dive.Log back to life. This time, when Win 10 broke Subgear I again reinstalled the driver and brought Subgear back to life in the Win 10 machine. At least I recognized the symptoms and managed to fix the problem before I lost dive data off the dive computer when it rolled off with new dives.

So, for the time being, I have Dive.Log in the Win 7 machine, and Subgear in the Win 10 machine. The problem with jury rigging Win 10 to stop or postpone the "upgrades" is that you don't know the damage that's coming to you until you install it , and then it's too late. I don't have a set up nor the time to Beta test a Win 10 release before I permanently install it.. I worked in IT for a major energy company for 32 years doing world-wide support for an in-house developed management information system, and I would have NEVER released a product with bugs like these, or I would have killed the developers by passing it on to me for release, or my customers would have killed me.

With respect to Subgear's Dive.Log: does anybody know how to export the data to, say, a CSV file? According to its documentation, Subgear can import that. I have 8 years' worth of dive data in Dive.Log which I am going to be reduced to printing it with it's crude printing capabilities and then lose it when I have to migrate the Win 7 machine.
Was this answer helpful?

0 comments No comments
Anonymous

2019-11-07T16:39:00+00:00

PS: I really should have mentioned that I didn't even have to use the previously downloaded IR driver. The "Settings - Apps and Features ..." fix using the Windows interface worked like a charm
Was this answer helpful?

0 comments No comments
Anonymous

2019-11-08T22:48:59+00:00

It would appear Dive Log 6.0 may be able to import from Subgear XP10. Surely there is some kind of export function?

https://divinglog.de/english/features/import.php

Going forward, as Win10-1909 is going to be thrust upon us (I'm still using 1803), if you don't already I suggest you get an disk imaging program (I use Macrium Free), and make a full backup before any major or dicey change. Saved my butt a few times.
Was this answer helpful?

0 comments No comments