Possible fix for Flirc disconnected on Windows 10

[W3CB]

_{Hi guys,}

<sub>If you can't connect to your Flirc (Generation 1) on Windows 10, this guide might help you.
If you are uninterested about the possible cause of this problem go ahead and scroll down to "Try this"

From the beginning I thought the issue was caused by the software/firmware, plain and simple. As it turns out, that's not it...</sub>

<sub>I've tried versions from v.3.10.0 to latest 3.22.4.and all reported the same thing.
After troubleshooting all day long I believe this particular issue has risen all of the sudden, in my case. After two major Windows updates.

Everytime A feature update is installed all USB Devices are re-installed. But not always in the same place.
If you ever used the Device Manager and checked "Show hidden devices" You've probably seen some grayed out devices. These are devices that aren't currently connected OR they've been installed in another location.

So if Flirc was installed on location A prior to an feature update. Flirc might now be installed on location B. Where on location B some other device was previously installed and are now casing mayhem...that is my theory anyways after doing what I did which you now will read about.</sub>

<sub>Try this
1. Open the Device Manager by Right-Clicking the Windows Logo on the Taskbar.
2. In Device Manager, select View and "Show Hidden Devices"
3. Remove Flirc from the USB port and uninstall the software, then remove the Flirc folder.
4. In Device Manager, uninstall (Delete, Enter) any grayed out devices in all the areas shown on the picture.
5. Restart.
6. Install latest Flirc.
7. Connect the Flirc.
8. If it doesn't work. Try using different driver for your USB controller* Then repeat 1-7.
9. Let me know how it goes.</sub>

_{* especially If you have an ASMedia controller with native drivers from 2016 Flirc GUI will not work. Confirmed on a fresh Windows install.}

Edited July 10, 2019 by W3CB

[arabesc]

7 minutes ago, W3CB said:

_{From the beginning I thought the issue was caused by the software/firmware, plain and simple. As it turns out, that's not it...}

<sub>I've tried versions from v.3.10.0 to latest 3.22.4.and all reported the same thing.
After troubleshooting all day long I believe this particular issue has risen all of the sudden, in my case. After two major Windows updates.

Everytime A feature update is installed all USB Devices are re-installed. But not always in the same place.</sub>

I should notice that I don't have any issues with all of the other USB-devices, such as Bluetooth adapter, mouse/keyboard receiver or USB-CEC adapter. They all work as before.
Why is Flirc so special?

[W3CB]

1 minute ago, arabesc said:

I should notice that I don't have any issues with all of the other USB-devices, such as Bluetooth adapter, mouse/keyboard receiver or USB-CEC adapter. They all work as before.
Why is Flirc so special?

Beats me. My other devices also works fine. 

[jason]

1 hour ago, arabesc said:

I should notice that I don't have any issues with all of the other USB-devices, such as Bluetooth adapter, mouse/keyboard receiver or USB-CEC adapter. They all work as before.
Why is Flirc so special?

Yeah, I'm at a loss. I can't reproduce this.

@arabesc

Can you please let me know if this is happening with you and if W3CB suggestion work?

[arabesc]

58 minutes ago, jason said:

Can you please let me know if this is happening with you and if W3CB suggestion work?

I'll try at the weekend.

I can add that I've launched the latest Flirc app many times and all the time it shows disconnected status, but one time it became connected. I don't know how it happened and I can't reproduce it since then.
There can be some sort of conflict or race condition.

[jono0007]

I am also experiencing this issue with my Gen 1 flirc. I attempted to set it up tonight for the first time in awhile (years). Not getting any connection in flirc software at all. I've tried all of the instructions above, but I haven't seen any change. The flirc is visible in Device Manager. Unfortunately, I can't say when this problem began since this is the first time I've used the device in awhile. Logs attached.

flirc_log.txt

[W3CB]

15 minutes ago, jono0007 said:

I am also experiencing this issue with my Gen 1 flirc. I attempted to set it up tonight for the first time in awhile (years). Not getting any connection in flirc software at all. I've tried all of the instructions above, but I haven't seen any change. The flirc is visible in Device Manager. Unfortunately, I can't say when this problem began since this is the first time I've used the device in awhile. Logs attached.

flirc_log.txt 210.69 kB · 0 downloads

Sorry to hear that. What can you take a screenshot of the device manager like the one you see in my picture.

BTW, is flirc connected directly to an USB port or via a USB hub?

Edited June 14, 2019 by W3CB

[jono0007]

[W3CB]

On what controller is Flirc connected? The DAEMON Tools Lite Virtual USB Bus or Renesas? if on any of these please do step 1-4 and connect Flirc on the Intel controller see if that works.

Edited June 14, 2019 by W3CB

[arabesc]

I've deleted Flirc device from the Device Manager, ticked the checkbox to delete its drivers. I've uninstalled Flirc software and checked that there's no Flirc folder in the Program Files remains.
Then I've installed the latest Flirc app and it has started to work without the issue.
So, it seems the issues comes from the app update.

[W3CB]

On 6/15/2019 at 6:04 PM, arabesc said:

I've deleted Flirc device from the Device Manager, ticked the checkbox to delete its drivers. I've uninstalled Flirc software and checked that there's no Flirc folder in the Program Files remains.
Then I've installed the latest Flirc app and it has started to work without the issue.
So, it seems the issues comes from the app update.

Huh, from the app update?

[MonoLyf]

I have a gen 1 Flirc, it wouldn't show up in the windows app and would say disconnected etc.

So I installed the Flirc app on a raspberry pi and it detected the Flirc straight away and prompted a firmware update from 1.x.x to 3.11.0. since the firmware update, it now detects in the windows 10 app. So maybe the latest version of Flirc on windows doesn't like gen 1 Flirc's with firmware 1.x.x?