Interceptor blocking all input when using wireless devices

[dafzor]

I've been using capsicain for a few weeks now and started to get an issue when resuming from sleep were I'd no longer be able to use any of my input devices after switching to mainly wireless (mix of bluetooth and 2.4g wireless)keyboards and mouses.

I'm still not 100% sure it's capsicain bug, but all points to it and have not had the issue since uninstalling the interception driver which was 3 days ago (if it happens again without capsicain I'll close this issue).

The behavior is as following:

• After waking up from a long sleep occasionally keyboard input would no longer work
• Plugging in a new usb keyboard would also not work
• Unpluging HID devices that were still working (keyboard or mouses) and plugging them back in would also make them stop working
• Before windows loaded the keyboard would work normally (i wake up from sleep by keyboard key press)
• Using Wireshark usb sniffer I could see usb package from the keyboard being received like it was working normally, however input would be registered
• Restarting capsicain would not fix the lack of input
• Rebooting the computer would make input work normally again

So summarizing, after windows slept for a long time any input device that disconnected would no longer register any input until the computer rebooted again. The input device would still be connected to the computer, send USB packages with data but no input would be registered until rebooting.

[dafzor]

It's been now a week since I removed the interceptor and haven't had the issue since making me feel confident it was the cause.

I've copied the issue to https://github.com/oblitum/Interception/issues/139 as well.

[cajhin]

Thanks for troubleshooting this. Unfortunately, I have no idea what causes this. For years, I have observed erratic wireless devices every time a Windows update is installed on my work laptop, until I reboot.

What Windows version do you use, and did you try what happens with interception installed but capsicain not started?

[dafzor]

What Windows version do you use, and did you try what happens with interception installed but capsicain not started?

On my personal system I tried having capscain not start at all and the issue still happened, only removing the interception driver did the issue resolve itself. I was loosing input every day after putting the system to sleep for the night.

On my work system I've retained capscain and interceptor driver installed but moved all devices of Bluetooth to their own dongles or wired which so far for over a week as kept the issue away although on my work system it was less frequent.

The only difference I noticed with my new input devices is that they don't seem to be responsive as soon as my computer woke up, only responding 1-3s after I started pressing keys.

Further details about my system if it's relevant:

Personal System

• AMD Ryzen 5950x @ Stock
• Gigabyte X570 AORUS ELITE (rev. 1.0) Motherboard
• 64GB DDR4-3600MHz CL16
• Generic powered 4 port usb 2.0 hub (all devices bellow plug into it)
• Asus USB-BT500 Bluetooth 5.0 dongle
• ROYAL KLUDGE RK84 84 Keys Wireless keyboard
• Asus ROG Pugio II Wireless Mouse
• Windows 10 Pro (fully updated)

Work System

• Lenovo Thinkpad P1 gen2
• Intel i7-9750H
• 32GB RAM
• Lenovo Thunderbold3 Workstation Dock (230W, all devices bellow connect to it)
• Jabra Evolve2 65 Headset (with dongle)
• Logitec MX Master 3 Wireless Mouse (with dongle)
• Keychron k4v2 Wireless Keyboard (wired)
• Windows 10 Pro (fully updated)

[dafzor]

Got a reply on the interceptor issue, seems the 10 device limit is not connected but since it started, and every time wireless devices wake up they register as a new device.

My mouse and keyboard register as 6 devices, thus one reconnection cycle will go past 10 devices and break interceptor completely.

As such I'm unable to use capscain with my current hardware, I've made due with powertoys keyboard manager which wile less reliable/flexible does mostly work for my use.

Leaving it up to you if you want to close the issue here as well.

[cajhin]

Thanks, that's good to know. I wasn't aware that reconnecting bluetooth devices (possibly) increases the number of devices. Might explain the wireless issues I sometimes see after Windows update installation.

Note: turning my bluetooth Filco off/on, or sleeping Windows for a minute, does not result in new HIDs. Looks like the issue depends on more details.

I'll leave this open for now since it is a real issue. Only oblitum/interception can fix this.

[dafzor]

From my understanding the requirements for the fix are 400 USD/month in donations or individual comercial license to recompile the driver with higher limit.

So ATM this is a won't fix from interceptor side.

Additionally this is not isolated to Bluetooth, my devices use 2.4g wireless to connect, I don't know enough of windows internals to explain why my devices are getting new IDs.

On Mon 11 Apr 2022, 13:54 cajhin, @.***> wrote:

Thanks, that's good to know. I wasn't aware that reconnecting bluetooth devices effectively increases the number of devices. Might explain the wireless issues I sometimes see after Windows update installation.

I'll leave this open for now since it is a real issue. Only oblitum/interception can fix this.

— Reply to this email directly, view it on GitHub https://github.com/cajhin/capsicain/issues/70#issuecomment-1095013950, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMJTLSE3SLRRVRNYWBQNLTVEQOGPANCNFSM5SN4ZOPA . You are receiving this because you authored the thread.Message ID: @.***>

[darkhandz]

Having the same issue, I have to reboot my pc to recover my mouse and keyboard.

[cajhin]

update: v96 prints some debug information whenever Interception thinks a new device appears.

Looks like my bluetooth keyboard triggers "new device" when it goes to sleep after 1(?) hour, although the device id does not change. After 10 devices Interception blocks input, because dealing with 10+ devices appears to be some professional use that would require a paid license...

I'd say this is a soft bug in Interception, but I have little hope this will be fixed (no new versions coming up, because signing drivers has become really expensive and troublesome).