10.0.19041.84 not working with any of the new .ini files

[azerioxal]

I've been trying to get the Windows 2004 Release Preview going. I've checked through the issues for new ini files and tried several that others have had success with. For me, with each file, every time I load an RDP session, the first works fine. Any other sessions fail with a generic failure to connect, whether it's a second simultaneous sessions, or a disconnect and reconnect. A full reboot allows a reconnect.

I'm currently using this ini file, which works fine if I downgrade to prior versions of Windows.

I'm running this in a VM, if that might have any issues that I've missed in my research.

Any thoughts?
Thanks!

[SquawkWoof]

I am also seeing this problem. It worked until 1909 and broke in 2004. I have the auto-updater setup and it does not resolve the problem. Seems it's completely broken in 2004.

[robbak]

Hey, guys, the stascorp rdpwrapper github is back up! When did that happen!

Let's all get local mirrors of it.

SquawkWoof, the .ini files on this site are out of date, but several other people maintain updated files. Th easiest way to set it up is to use the autoupdate.bat file available here on issue #860. This batch file pulls .ini files from a couple of these other users repositories. This includes .ini files that work with 2004.

[StarfighterJ]

I am so glad this is back up and thanks on those who kept it going on other hub areas.

[phongtran7]

This link can help:
https://github.com/Octanium91/rdpwrap

[rcarosio59]

https://github.com/Octanium91/rdpwrap if I use this .ini file the RDP connection gets the connection without asking and it takes out the user that is connected and if I run the RDPConf.exe it says that is fully supported.
If I use this one: rdpwrap_10.0.18363.476_1909.ini it ask if you want to disconnect the other user, and if I run the RDPConfig.exe it doesn't show if is supported or not.

[robbak]

Then congratulations, it is now working properly. If configured in the right way, you can log back in on the local computer and have a second session for that user, but you cannot prevent it from taking over the local session when you connect remotely. If a second user needs to use that computer, then create them a second account on that computer.

…

On Tue, 9 Jun 2020 02:14 rcarosio59, ***@***.***> wrote: https://github.com/Octanium91/rdpwrap if I use this .ini file the RDP connection gets the connection without asking and it takes out the user that is connected and if I run the RDPConf.exe it says that is fully supported. If I use this one: rdpwrap_10.0.18363.476_1909.ini it ask if you want to disconnect the other user, and if I run the RDPConfig.exe it doesn't show if is supported or not. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1079 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMCGIVCTKTTRDE76YGPJ2DRVUE5JANCNFSM4M3BVA7Q> .

[dmcdivitt]

This configuration at https://github.com/Octanium91/rdpwrap does not work for W10 2004, DLL version 10.0.19041.84 on any of my machines. I found the same rdpwrap.ini change on many different pages. Editing the DLL does work. At http://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/ toward the bottom in a comment by Krox it says:
"On Windows 10 x64 2004 you should replcace 39 81 3C 06 00 00 0F 84 D9 51 01 00 на B8 00 01 00 00 89 81 38 06 00 00 90 in the termsrv.dll file"
This worked on all my machines. Can someone see why the rdpwrap.ini change does not produce the same?

[rcarosio59]

Then congratulations, it is now working properly. If configured in the right way, you can log back in on the local computer and have a second session for that user, but you cannot prevent it from taking over the local session when you connect remotely. If a second user needs to use that computer, then create them a second account on that computer.
…
On Tue, 9 Jun 2020 02:14 rcarosio59, @.***> wrote: https://github.com/Octanium91/rdpwrap if I use this .ini file the RDP connection gets the connection without asking and it takes out the user that is connected and if I run the RDPConf.exe it says that is fully supported. If I use this one: rdpwrap_10.0.18363.476_1909.ini it ask if you want to disconnect the other user, and if I run the RDPConfig.exe it doesn't show if is supported or not. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1079 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMCGIVCTKTTRDE76YGPJ2DRVUE5JANCNFSM4M3BVA7Q .

Thank you

[robbak]

Do not replace your .dll files with ones edited or distributed by others. It breaks things, and re-introduces patched security flaws.

Install rdpwrapper to program files/rdpwrapper, and replace the included .ini file with the one in Octanium91's repository linked above. If you are still having problems, try other .ini files posted to other issues on this repository. If you still can't get it to work, start a new issue with your problem.

[dmcdivitt]

The Octanium91 change does not work. It's the same change I've seen on numerous pages. I'm very used to applying ini file changes following windows updates, by looking at properties of termsrv.dll, getting the version, then see what exists for that version. This time it just doesn't work. I found edits that can be made to the dll and posted that. It works. I don't want to do it that way. I'm hoping someone with knowledge can see why the ini file change does not work. If so I will restore the dll and continue using rdpwrap.

[grix25]

This link can help:
https://github.com/Octanium91/rdpwrap

Can confirm
ini. file is legit and working
Tnx

[DinantKistemaker]

Had same problem. Listener state not supported. This rdpwrap.ini 100% fixed it for me:

https://github.com/Octanium91/rdpwrap

[dmcdivitt]

The Octanium91 change did not work because I needed to reinstall rdpwrap. Never needed to do that before. That allowed the Octanium91 change to work.

[DinantKistemaker]

@dmcdivitt Sure, that could be; I did reinstall the rdpwrap as well in a previous attempt to solve the problem. So, maybe that was part of the solution.

[rvsingh011]

Confirm working :
https://github.com/Octanium91/rdpwrap

[Mahdifarzaneh]

Confirm working :
https://github.com/Octanium91/rdpwrap
tnx

[ThoseITGuys]

I also have this issue where its all green and when a remote user tries to connect it wants to sign the local user out.

I tried the INI suggest above but once implemented. the remote user (seperate account on the PC) logs in and the current local users screen changes to the remote user desktop and they cannot move or anything. They can watch what the remote user is doing but they cannot move until the remote user disconnects then they see their user desktop again

[sebaxakerhtc]

Duplicate of #1004