Rdpwrap: Reconnecting to session not working (Win 10 Home 1903)

[neoc83]

I got RDPWrap working on Win 10 Home after the 1903 update with the solution provided in #837 . However, when I connect to my host and then disconnect (either by closing RDP or Start > Disconnect) I am not able to reconnect to the session again. It will bring me to the Windows login screen but when I enter password and try to connect, the screen freezes and nothing happens after that. I need to login to the host locally and reboot to make remote connection possible again. Issue happens all the time. Checked both connecting from local network and from internet.

Strange thing is, when the issue rises and I try to connect with TeamViewer, this won't work anymore either.

[neoc83]

I tried a RDPWrap re-install but no result. Tried another .ini file (taken from #845) but then I did not get the service running.

With the .ini from #837 the service and listener seems to run just fine but I keep having the problem: I cannot reconnect to a session after disconnecting.

[colinuu52]

I have the same experience as you, ie can remote connect once, but not again after disconnecting. I also find that processes running at the time when the login screen freezes also freeze. Login again locally gets things running again (reboot not necessary)

[Win 10 Home, after 1903 update]

[cosmos321]

See my solution here: https://github.com/stascorp/rdpwrap/issues/837#issuecomment-520130781

Everything is working perfectly with this configuration.

[snugglesftw]

@cosmos321 what about for version .267? we are having same issues

[neoc83]

See my solution here: #837 (comment)

Everything is working perfectly with this configuration.

Unfortunately, this is not working for me. I cannot connect at all with that configuration. I also tried adding x86 lines from my .ini file (I'm running Win Home x64 but you never know :-)) but no result.

Anyone else has a solution? I noticed that when I have logged in and logged out, stopping/restarting the termservice locally is not working. The service hangs in state 'stopping'.

[neoc83]

Some additional information that could help: I checked the event logs in Windows and found the following error log at times that I was having the issue (Microsoft-Windows-TerminalServices-LocalSessionManager/Operational):

An error occurred when transitioning from Disconnected in response to EvConnected. (ErrorCode 0x80070102)

[neoc83]

Just another update: after updating Windows the new termservice.dll version is 10.0.18362.267.
So I re-installed RDPWrap with the .ini file from here but got the same result.

I also replaced the .dll and .ini with an older version (as described here) and re-installed RDPWrap and after reboot still no luck.

[cosmos321]

Yesterday, i also got the update to the .267 version. Result: service broken. So i only duplicated the exact same lines from .53, stopped the "termservice" service, edited the rdpwrapper.ini, started the service again, and the result: everything is working fine.

Note: I´m using Windows 10 Pro x64

[colinuu52]

@cosmos321
The various reports of working/not working are pointing strongly to this issue being specific to Windows 10 Home v1903.
@neoc83
My version now is also .267 My experience is the same as yours.

[w1lddog2]

Yesterday, i also got the update to the .267 version. Result: service broken. So i only duplicated the exact same lines from .53, stopped the "termservice" service, edited the rdpwrapper.ini, started the service again, and the result: everything is working fine.

Note: I´m using Windows 10 Pro x64

Thank You! i had the same issue about session not reconnecting, but your ini fixed it.

[w1lddog2]

I talked to soon, today i tried again and the issue persist. Reconnecting to a session is not working. It just crash the machine (in my case VM, under Hyper-V).
I was able to roll back to last compilation which works greats, sadly i still have one server running VM that cannot roll back from the latest 1903.
On a side note the VMs are all running Win 10 Pro.

[s0nic9]

update: it seems last updates can use wddm drivers causing dwm.exe cpu high or hang system , when two remote users close session without log out and if one user close session without log out, no hang, but if reconnect to existing session , system hang on VM.

It works for me now, disabling that new setting using this GPO https://answers.microsoft.com/en-us/windows/forum/all/dwmexe-high-cpu-one-core-on-target-system-after/dbce0938-60c5-4051-81ef-468e51d743ab
update : one line registry then reboot

reg add "HKLMSOFTWAREPoliciesMicrosoftWindows NTTerminal Services" /v fEnableWddmDriver /t reg_dword /d 0 /f

[neoc83]

Thanks @s0nic9!! This solved it for me.

update : one line registry then reboot

reg add "HKLMSOFTWAREPoliciesMicrosoftWindows NTTerminal Services" /v fEnableWddmDriver /t reg_dword /d 0 /f

So if I understand correctly, this is an issue with the latest Windows updates and has nothing to do with RDPWrap. Glad this workaround helps but it would be better if the bug in Windows itself will be resolved.

[ankitT20]

Yesterday, i also got the update to the .267 version. Result: service broken. So i only duplicated the exact same lines from .53, stopped the "termservice" service, edited the rdpwrapper.ini, started the service again, and the result: everything is working fine.

Note: I´m using Windows 10 Pro x64

from where did you copy the code