Windows 10 InfraRed (IrDA) support without Insider Builds

UPDATE: This guide is no longer needed on Windows 10 after update v1511. Please ensure you have all updates installed.

Step 1: Make sure you’re running Windows 10 v1511 (November 2015).

1. Click on Start
2. Click on Settings
3. Click on System
4. Click on About

• The Version number will be indicated on the right side.
• If your version is higher than 1511 you’re likely enrolled in the Insider Preview program, and your adapter should already be working. I do no recommend continuing with this guide.
• If your version is lower than 1511 then you need to run Windows Update to catch up to the current release.

Step 2: Open an Elevated Command Prompt

1. Click on Start
2. Type “cmd”
3. Right-Click on “Command Prompt”
4. Click on “Run as Administrator”
5. Click “Yes” or “Allow” on the User Account Control notice

Step 3: The Fix

1. Type or Copy & paste this command in to the Administrator Command Prompt:
   • netcfg –u ms_irdanetcfg –c p –I ms_irda
   • To paste it:
     1. Copy it from above.
     2. Left click anywhere in the command prompt to bring it into focus
     3. Right-click anywhere in the command prompt to paste the current clipboard contents.
   • This is ONE(1) single command.
   • It should look similar this when you’re done (I’ve already done it, so my output is slightly different):

1. REBOOT
   • This is VERY important. It might appear that your Infrared Adapter starts working right away (it should start blinking after you complete the previous step) but NOTHING WILL WORK UNTIL YOU REBOOT.

Step 4: Test & verify

• Get out your dive computer, health monitor, phone, barcode scanner, etc and give it a test run.
• If you’d like to run some verification checks first:
  • Open another elevated command prompt (Step 2 above)
  • Run the following TWO(2) commands:
    • sc query irda
    • sc query irmon
  • Each command should return a small SERVICE_NAME prinout.
  • The important part is the “STATE” field, it should be “4 RUNNING”.
  • I had one gentlemen report back that the second command was not in the running state, but his dive computer still Sync’d fine, so it’s not 100% accurate.