search

oblitum / Interception

The Interception API aims to build a portable programming interface that allows one to intercept and control a range of input devices.
http://oblita.com/interception
1.35k stars 269 forks source link

Winlogon Crashes on Windows 10 RDP #21

Open sr025 opened 8 years ago

sr025 commented 8 years ago

This problem is very easy to replicate: • Start from any Windows 10 installation (for example a clean install of Professional x64) • Enable Remote Desktop Services • Install Interception driver via "install-interception.exe /install" and reboot • Log into and out of an RDP remote session a few times • By the third or fourth time the remote client will hang at a black screen before it finishes the login

When this happens, you can check the Event Viewer Application Log. The Winlogon process shows a 4005 unexpected termination error but is not specific about the cause. If you uninstall interception and reboot the problem disappears.

oblitum commented 8 years ago

@sr025 Thanks, I've received your previous email, sorry but I have no time to take a look at this now. Touching Windows to debug drivers implies moving a lot of stuff which is not nice to do free of charge for me.

2812140729 commented 7 years ago

same problem and the problem affect server 2012 , win8 ,server2016 and win 10 . about 4-5 times rdp logon and disconnect, the rdp can't connect to the server any more. and will case winlogon 4005 error . this screenshot is from server 2016 after the issue occur server 2016 device

oblitum commented 7 years ago

This should be related with issue #25 given the fact this possibly happens after connection/disconnection of virtual devices associated with RDP. As stated on issue #25, this happens because Windows keeps increasing its internal device counter instead of reusing it and Interception supports up to 10 devices of each kind (without source access).

dkonigsberg commented 1 year ago

This might sound like a bit of a "me too", but I just wanted to drop by and say that this bug has been driving me nuts for years. What's worse is that I had completely forgotten that I even installed Interception on the problematic system, so I was chasing down every other possible cause. (And that system has been upgraded from Win10 to Win11, and had numerous driver updates, over that span of time.)

Thankfully, I no longer have a need for this package on that machine (it was part of a failed attempt at bodging a barcode scanner into doing what I want). But its still most definitely the sort of bug that could drive anyone nuts. Especially since there's really nothing about the bug that tells anyone where to point the finger.