search

stascorp / rdpwrap

RDP Wrapper Library
Apache License 2.0
14.74k stars 3.83k forks source link

Getting weird behavior when trying to RDP: "The object invoked has disconnected from its clients" after disconnecting from RDP #2217

Open cwm9cwm9 opened 1 year ago

cwm9cwm9 commented 1 year ago

Lately when I try to RDP into a client, it will connect and show me the login screen. If I try to log in, the moment I click login, the RDP connection is dropped (most of the time). Sometimes it will log me in, but when it does, it only works one time.

Whether I try to log in or not, whether I manage to log in or not, the moment the connection is ended (whether because it broke, I logged out, or I closed the window before logging in), the remote client login screen becomes completely borked. If the remote computer user locks their terminal or logs out and then tries to log back in (or unlock the terminal), they get the message, "The object invoked has disconnected from its clients," and are kicked back to the login screen. The only solution is a hard reboot.

If I uninstall RDP wrap, everything goes back to normal. (Except, obviously, with the normal RDP behavior.)

Any ideas what is causing this?

sashaqwert commented 1 year ago

Any ideas what is causing this?

  1. RDPConf screenshot, please!
  2. What is your Windows edition (Do not try RDP Wrapper on Enterprise multi-session :) and with RDS role )
  3. Are you using custom credentials providers (multiOTP, etc)
  4. Try sfc /scannow
mwkidd1 commented 1 year ago

*** IGNORE BELOW [Updated=2023-06-16 INI fixed mine]

On latest windows update, I am having I think the same problem. RDP into same machine different user account, it starts the login and then abruptly disconnects. OP didn't upload his Conf scrnshot but here is mine. OP didnt mention logs. In my log I have APPCRASH on LoginUI.exe now. Before updates had no problem. Tried latest ini for my ver. Tried sfc/scannow and dsim. It looks like win update updated TermSrv.

Fault bucket 1626829098879167324, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0

Problem signature: P1: LogonUI.exe P2: 10.0.22621.1 P3: cf0f816d P4: combase.dll P5: 10.0.22621.1485 P6: a8be94cc P7: 8001010e P8: 000000000009200b

Picture1