Rdpwrap.ini for new win 10 updates

[j1nseng]

Here I add ini file for rdpwrap with such updates:

17134.706
17763.165
17763.292
17763.379
17763.437
18362.1

There maybe some loss of x86 settings, but who cares...

How to use:

1. Replace file C:\Program Files\RDP Wrapper\rdpwrap.ini with one from this post..
2. Restart termservice.
3. Use it. No need to restart the computer.

So, please feel free with feedback and additions.

rdpwrap.zip

[penasanc]

Works great!!!! Thank you

[mz8080]

How about 18362.53? Any idea?

[xinxin8816]

Nice! It's working well on 17763.437.

[ZeljkoManjkas]

This ini do not work on 17763.437 x86
Do you have values for x86 system?

[hobbelton]

i have version 17763.379 and replaced the ini file but after installation of safety update KB4493464 it stopped working. i had to unistall this update to get it back to work again.

[technics1210]

Great Work :-)
Works well with 17763.437

[naseblau]

THX

[dmcdivitt]

Thank you @j1nseng for 17763.437.

[shinhwas]

Thank you for updating. It works with 17763.437.
But single session per user doesn't work anymore.

[gitgotgone]

Works great with 17763.437--thanks!

[jgoedhard]

thanks

[dmcdivitt]

@shinhwas, I agree 17763.437 no longer has single user with this edit.

[gitgotgone]

@shinhwas , @dmcdivitt , I agree, unfortunately, single session per user does not seem to be working despite being checked in the config. Testing 17763.437

More specifically, for console user1 and non-console user2, it is single session from user1 loopback to user2 on same workstation1, or from 2nd workstation2 logging on to user2, but from workstation2 logging on to user1 when user1 is already logged on to workstation1 at console will spawn a second session. In other words, the console user can't be accessed remotely.

[v-mwalk]

StasCorp has done tremendous work on this. Be a shame for it to die. Would it be possible for another person be made an Admin for accepting pull requests and getting upto date releases?

The latest ini file worked great and RDPWrap has been a mainstay of my home 'support' life, but for new folk trying RDPWrap it just wont work as they wont know what to do and they end up putting out 'it doesnt work' reviews etc....

[gitgotgone]

StasCorp has done tremendous work on this. Be a shame for it to die. Would it be possible for another person be made an Admin for accepting pull requests and getting upto date releases?

The latest ini file worked great and RDPWrap has been a mainstay of my home 'support' life, but for new folk trying RDPWrap it just wont work as they wont know what to do and they end up putting out 'it doesnt work' reviews etc....

StasCorp has authority over RDPWrap, and he could give it to someone else. Or someone or a group can create a fork and manage it from a new git hub repository. I'm sure it is a lot of work for StasCorp, a labor of love. Unfortunately he has clearly not kept up with the many Windows updates, which have increasingly broken RDPWrap by updating the termserv.dll. It is very sad for those of us who have come to depend on RDPWrap.

But getting back to single session per user, attached below is the ini file that solves that issue for 17763.437. Thanks to those on https://github.com/stascorp/rdpwrap/issues/720, sorry I've lost track of who exactly to credit.

rdpwrap.zip