-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
20H2 Build: 19041.789 Not working #1314
Comments
Thanks for your hard work |
no solution so not good ( |
yeah for now 789 build not in the wrapper ini file. so if you have autoupdater when they update the ini you will have it |
Can someone post the new INI please? |
@yuasa54 can you please post your new ini file or copy the lines? thank you |
|
thx |
It fully works! Thanks!!!! |
Nice reverse engineering job. Thank you. |
MarcinWerra's change worked for me. |
It fully works! Thanks MarcinWerra !!!! |
MarcinWerra Thank you. It works great. |
@MarcinWerra there is any guide/tutorial/article where i can try to learn how to update the ini file by myself? |
When I tried to create the parameters for the .ini file myself for the first time, I watched the video on Youtube very carefully "Practical reverse engineering (for RDP Wrapper)" Recommended tools: |
Single session per user |
1 similar comment
Single session per user |
SingleUserOffset.x64=0CB22
|
here more precise test in both cases ie ---testing from host computer connecting with user name and password entered In client works as Single session per user set active connecting with user name and password entered on logon screen works as Single session per user set inactive ---testing from remote computer mixing both types of login behaves as Single session per user set inactive regards |
I stand by my opinion however GUI authentication only (windows login screen) - enables many sessions for same user, each login creates a new session, disconected sessions are not reused, disconected users should be logged out via (fe.) task manager->users->logoff user Network level authentication (client login dialog) - makes that user can open one (mostly) rdp session, disconected session (one) is reused, if there is more disconeccted sessions, then system behaves as above. question is: do code which handles "Single session per user" functionality could be patched ? regards ps. |
I cannot reproduce your problem.
rdpwrap/src-x86-x64-Fusix/RDPWrap.cpp Lines 722 to 740 in a5c64a4
The code between lines 722 and 740 looks fine to me. This function does not randomly change the code. With the patch SingleUserOffset.x64 = 0CA4C, SingleUserCode.x64 = Zero is patched CSessionArbitrationHelperMgr::IsSingleSessionPerUserEnabled With the patch SingleUserOffset.x64 = 0CB22, SingleUserCode.x64 = Zero is patched CSessionArbitrationHelper::IsSingleSessionPerUserEnabled But the strangest thing is that, with the patch disabled by SingleUserPatch.x64 = 0, it also works fine for single session per user and multi session connections. PS. @lha314981 :-) Może prędzej się dogadamy po polsku. (Proszę odezwać się przez Messenger https://www.facebook.com/WerraMarcin/) |
So at least RDP Wrapper is working on halfway. INFO UPDATE |
The following worked for me .. LocalOnlyPatch.x64=1 [10.0.19041.789-SLInit] bInitialized.x64=106028 |
termsrv 10.0.19041.789.zip
The text was updated successfully, but these errors were encountered: