Infrared not recognized

Anonymous
2019-05-22T19:34:31+00:00

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)

Windows for home | Windows 10 | Devices and drivers

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 No comments
Answer accepted by question author
Anonymous
2019-06-19T21:33:58+00:00

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

Was this answer helpful?

60+ people found this answer helpful.
0 comments No comments

77 additional answers

Sort by: Most helpful
  1. Anonymous
    2019-06-16T15:24:30+00:00

    I could not agree more with your statement: "I would guess most people will do 1903 as an upgrade. If you have any idea how the failure of the IrDA dongle to load I think that would be the way to approach it".

    Clearly there is a change in the way MS manage the IrDA between 1809 and 1903 (which has been on going since 1511).

    My only real question is if an upgrade from 1809 to 1903 drops the infrared; can the PowerShell scripts remove / reinstall the IrDA stack? 

    • If yes the answer is simple, fix the broken IrDA stack / protocol.  MS has several quirks, such as making changes by running a script or GUI interface buttons does not always give the same result in all condition (sometimes deliberate to stop poking fingers breaking things and sometimes oversights that get corrected..

    I can try to decipher event viewer if you encounter problems; if you decide to investigate to help understand better

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-06-16T14:40:51+00:00

    Working this morning. Can't find any problems.

    I found out about this issue from a forum called ScubaBoard, a world wide diving exchange. The ScubaPro brand of computer that uses this IrDA

    is very common so I did this whole 1903 upgrade, then clean install as an experiment. As you see, lots of problems. It would be more reassuring if something had been definitively discovered so it could be fixed. As it is I have no idea how to even troubleshoot the initial failures.

    I have not looked at the [event viewer]. I can do that if you think there might be useful information. It's a bit above my 'pay grade', since I generally can't interpret it very well.

    I would guess most people will do 1903 as an upgrade. If you have any idea how the failure of the IrDA dongle to load I think that would be the way to approach it. I'm open to putting the upgrade version back on (I have a Macrium backup) if you are willing to work on that.

    Thanks for hanging in there.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-06-16T07:04:48+00:00

    FWIW I have checked on an 1809 machine, with IrDA working and I get the same results as you for the PowerShell command.  This looks like the PowerShell stuff is brand new in 1903, and likewise the add on option also.

    I hope it stays working for you.  Good Luck.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-06-16T02:36:15+00:00

    OK, booted the [clean install] 1903 system. Ran that first Powershell command, got this: 

    Name         : Network.Irda~~~~0.0.1.0

    State        : Installed

    DisplayName  : IrDA infrared

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

    DownloadSize : 604101

    InstallSize  : 2472466

    Mostly similar to your results. Not similar to the results I got on the 1809 system with IrDA working.

    ****

    Here's the interesting part. 

    I had shut down the system. So I booted it up, I plugged in the dongle, brought up Smarttrak > this time it WORKED!

    I brought up Subsurface > this time it WORKED!

    I had done nothing to affect this other than shut down, and reboot. I have done this at least 4x after doing all upgrades and loading the dongle drivers and the dive software. It's been re-booted plenty.

    Each time I get a different result.  I'm glad things are working....now, but I can't say that my confidence level is particularly high.  Guess I'll see tomorrow.

    Was this answer helpful?

    0 comments No comments