Rdpwrap: Windows 10 version 10.0.18363.657 Now Working.

[stvkodra]

Replace the rdpwrap.ini file in c:Program FilesRDP Wrapper with the one provided.
rdpwrap.zip

[EspacioCivico]

Thank you very much Stvkodra this if it worked for me, just replace with the one you share and that's it. I send you a hug

[ChrDav135]

Yep. Working for me.
Thanks very much stvkodra.

[itsAllDigital]

Replaced the ini file and the config tool says it's installed and fully supported but if I try it won't let another user connect without the first one disconnecting.

Windows Version is (10.0.18362.657)

[strarsis]

It works!

[jul974]

Hello,
It looks like the "wrapp updater" is not aware of that new .ini
Do you think it was released to the automatic updater ?
Can anyone to that ? (As I have no idea of how to do this)

[Korvinho]

Winver - 18363.657 - work !

[VelociRacer]

I have a 32-bit system and the above rdpwrap file only shows support for x64. Now Listener State is [Fully supported] but Not listening. Can someone please help? Is having 32-bit my problem? Does the rdpwrapper need to be updated to include 32-bit? Maybe the subject is a typo but I have 10.0.18362.657.

[a-lascu]

I am in the same situation as VeloiRacer. I have a Windows 10 x32 (18363.657). Can someone help us?

[stvkodra]

Try this file for x86 machines. No guarantee it will work.
rdpwrap.zip

[a-lascu]

Thank you, stvkodra.
Unfortunately it's not working.
My Win10 x32 is 18363.657 version.

[VelociRacer]

Thanks so much for the quick support. I tried the above rdpwrap.ini but still show Not listening [Fully supported]

Is it necessary to reboot? Or just swap out the file and run RDPConf to check for changes?

Also, I noticed the x64 lines are duplicated now in the ini file. May need to re-look at that.

[darkvampire1]

For me it was need restart windows. When status was ok and checker returns bad permissions.

[xrbh70]

Hi @stvkodra It work perfectly, Thanks

[a-lascu]

xrbh70, your win10 is x32 or x64?
I understand that it's working ok on x64 version but I have a x32 version.
And I reboot the system after copy the new rdpwrap.ini

[aileenka]

Replaced the ini file and the config tool says it's installed and fully supported but if I try it won't let another user connect without the first one disconnecting.

Windows Version is (10.0.18362.657)

I had the same problem with Windows version 18363.567.
Then I realized I did not stop the RDP service before replacing the .ini file.
Now it's working for me.

[a-lascu]

Still didn't work for Win10 x32 :(

[maantao]

While 64-bit works like a charm for multiple (different) user concurrent remote access, it appears that multiple sessions for same user is now broken / blocked. Appreciate if someone can confirm.

[darkvampire1]

Try set options "default RDP authentication" ,Applay, reboot

[darkvampire1]

Thank you, stvkodra.
Unfortunately it's not working.
My Win10 x32 is 18363.657 version.

CFG file must be in default path! c:/Programfile/RDP-Wrapper/
Not else!

[a-lascu]

I think the problem is in the last .ini file that stvkodra have posted.
As VelociRacer noticed there are some attributes duplicates for .x86 as you can see below.

[VelociRacer]

Very good. Not only that, but the last block of variables above should be circled in yellow as they x64 duplicates. Who's the boss who's going to clean up the ini file? ;)

---

From: [e-mail]
Sent: ‎2/‎14/‎2020 2:50 PM
To: stascorp/[e-mail]
Cc: [e-mail]; [e-mail]
Subject: Re: [stascorp/rdpwrap] Windows 10 version 10.0.18363.657 Now Working. (#988)

I think the problem is in the last .ini file that stvkodra have posted.
As VelociRacer noticed there are some attributes duplicates for .x
[Annotation 2020-02-14 214629]https://user-images.githubusercontent.com/49077001/74562614-e466d800-4f73-11ea-9511-747e88ed7cb3.jpg
86 as you can see below.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/stascorp/rdpwrap/issues/988?email_source=notifications&email_token=AORSXNSJLLUG4YSB2K7UKGTRC3YYXA5CNFSM4KT5QY4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL2HUJA#issuecomment-586447396, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AORSXNQSIDSS4PNPL63FCLDRC3YYXANCNFSM4KT5QY4A.

[Kbotz]

While 64-bit works like a charm for multiple (different) user concurrent remote access, it appears that multiple sessions for same user is now broken / blocked. Appreciate if someone can confirm.

Multiple sessions for same user are working here - for both W7x64 and W10x64.

Big ups to stvkodra for the updated file.

[a-lascu]

Nobody can help us with .ini for Win10 x32?

[maantao]

While 64-bit works like a charm for multiple (different) user concurrent remote access, it appears that multiple sessions for same user is now broken / blocked. Appreciate if someone can confirm.

Multiple sessions for same user are working here - for both W7x64 and W10x64.
Big ups to stvkodra for the updated file.

Seems like we still face an issue even with RDP Authentication AND latest stvkodra INI

Are we missing the obvious for concurrent same user access?

[sanchomdv]

This worked for me in win10 10.0.18362.657 32bits x86
https://github.com/stascorp/rdpwrap/issues/999#issuecomment-586757085

[Iskandare]

@ stvkodra Thank you , you re the best ! work perfectly for me on my 3 computer in version v 10.0.18363.657 on 64 bits

[Kbotz]

Seems like we still face an issue even with RDP Authentication AND latest stvkodra INI

Are we missing the obvious for concurrent same user access?

Maantao, a few things you can try or look further into:

First and foremost, don't forget the need for a single mandatory blank line at the end of your ini file and all Remote Desktop related services are started in Services.msc.

In the Session Shadowing Mode Section of the config file, maybe try "Full access without permission" or "Full access with user's permission".

Likewise in the Authentication Mode section, you could also try "GUI Authentication Only".

It could be a password settings related issue. Perhaps a Group Policy setting tweak will help, as per Local Group Policy Editor. Focus on settings in the Connections and Security subsections there. Just keep track of what you're changing so you can easily undo it if and as necessary:

*Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session Host*

Enabling "Always prompt for password upon connection" in GPE could possibly do the trick also. Or the opposite. Plus how you're setting up User name and Password in the General > Logon settings in the RDP connection itself.

Just some things you could kick around regarding this issue. Wish I could offer you more, or at least something more specific. It goes without saying you're probably going to have to experiment a bit to find the solution. But those are the things I would start with as any one might do the trick. Of course someone else might come along and deliver a magic bullet. But until then, those are my best educated guesses as it relates to the problem you're experiencing.

[VelociRacer]

Great thanks for sharing, I have the same OS and 100% in business with new .ini.

---

From: [e-mail]
Sent: ‎2/‎17/‎2020 11:31 AM
To: stascorp/[e-mail]
Cc: [e-mail]; [e-mail]
Subject: Re: [stascorp/rdpwrap] Windows 10 version 10.0.18363.657 Now Working. (#988)

This worked for me in win10 10.0.18362.657 32bits x86

999 (comment)https://github.com/stascorp/rdpwrap/issues/999#issuecomment-586757085

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/stascorp/rdpwrap/issues/988?email_source=notifications&email_token=AORSXNTGDP57J2RSDAPFT33RDK3XLA5CNFSM4KT5QY4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL7AQ2I#issuecomment-587073641, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AORSXNX4GNPXRLZYJBWX4DTRDK3XLANCNFSM4KT5QY4A.

[maantao]

Enabling "Always prompt for password upon connection" in GPE could possibly do the trick also.

WOW Thanks Kbotz - you did provide us with the "silver" bullet amongst ALL the possible variations.

We had previously noted that saving the user password during logon of the RDP connection would cause this issue to manifest itself. However post upgrade of ini (due to Windows Update) abstaining from saving the user password didn't seem to work.

BUT forcing the password request via Group Policy Editor did the trick. Not EXACTLY sure why saving the credentials causes the login to falter, other that requiring an EXPLICIT confirmation for a same user login.

Many Thanks to all who scratched their head on this one.

[Kbotz]

WOW Thanks Kbotz - you did provide us with the "silver" bullet amongst ALL the possible variations.

You did yourselves the biggest favor - you dug in and tried things out. And the conclusion you've drawn sounds logical. Plus there were lots of possible variations to be tested so you did well. All I did was provide a few pointers and clues to help get the ball rolling.

Thanks for the feedback. I've helped a few others in the past to boot, and been helped in return. Looking out for one another helps keep these kinds of communities strong. Happy RDPW trails.

[StarfighterJ]

Thanks stvkodra that did work but what happened to the Autoupdater? is it broken?

[Matheus-Garbelini]

Hi, it's working for 10.0.18362.657 but only for administrator.
Is there a way to make it work with a local user account?

[Kbotz]

Hi, it's working for 10.0.18362.657 but only for administrator.
Is there a way to make it work with a local user account?

This is a permissions issue and inherent to RDP. Here's a few links to help you around it:

Allow Non-Administrator Users to Access Windows 7 Home Premium Via Remote Desktop

How to Allow Standard User to RDP/Remote Access on Windows 7 and 10

Cannot Establish Remote Desktop Connection Using Non-Administrator Account

[Matheus-Garbelini]

@Kbotz Thanks, I've followed the tutorial which required adding a new register and worked fine.

[Kbotz]

@Matheus We'll call it different strokes for different folks. Glad it worked out.

[Saadalvi92]

tried every thing copied the latest file but still it's not working
any help!!!!!!!!

[VelociRacer]

Try changing port back to 3389

---

From: [e-mail]
Sent: ‎2/‎19/‎2020 2:09 PM
To: stascorp/[e-mail]
Cc: [e-mail]; [e-mail]
Subject: Re: [stascorp/rdpwrap] Windows 10 version 10.0.18363.657 Now Working. (#988)

[Screenshot (1)]https://user-images.githubusercontent.com/53086047/74866708-195c9b80-5375-11ea-9bf2-addc6e27ac0a.png
tried every thing copied the latest file but still it's not working
any help!!!!!!!!

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/stascorp/rdpwrap/issues/988?email_source=notifications&email_token=AORSXNRSN2OLTFCGBVQWMYLRDV7VHA5CNFSM4KT5QY4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMJC5UY#issuecomment-588394195, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AORSXNXHJWQQA2VBEALPOV3RDV7VHANCNFSM4KT5QY4A.

[Kbotz]

tried every thing copied the latest file but still it's not working
any help!!!!!!!!

Are you on 32-bit or x64? VelociRacer is right. Having no background history specific to your setup or what RDPW experience you may have, it might be better if you uninstall RDPW and start anew with a clean working baseline, then move forward from there. For example, if you've hardened your system in any way to improve security via gpedit or the registry, revert those changes back to their basic, default settings. Also temporarily turn off your firewall and anti-virus. Then after RDP Wrapper is uninstalled, make sure you can connect with a basic RDP handshake on default port 3389. Once that is established, redeploy RDP Wrapper -- again advisably on the default RDP port to keep things as simple as possible.

When reinstalling the utility, make sure you're doing so with the administrative privileges, to include all commands you run (right click, run as administrator). Run _net stop termservice_ in cmd.exe. Then append the new (applicable) code to the end of the ini config file, and ensure this ini file is indeed in the correct programs files directory. Also be sure you are leaving an empty line at the end of the text. Run _net start termservice_ in cmd.exe afterwards, or RDPWInst.exe via cmd.exe _RDPWInst -r_ . Then reboot your system. Next run RDPCheck to confirm the handshake process is working correctly, then RDPConf to validate this further while choosing your preferred interface options.

Consider trying a lighter authentication (security) mode in the configuration interface to see if that might help also (GUI only). Only after this is done and everything is working soundly (RDPW interface reflects all green) would I re-enable your firewall and anti-virus, custom configure your RDP port and harden connection security as desired. Harnessing a simple back to basics approach, while stepping things thru carefully, is often all it takes (and the difference between seeing red and green). 🌞

[psycmos]

Works Great for me too! X64

[fasteddieh]

Thank you very much @stvkodra this work for both of my remote servers. Wow.

[ArtyGator]

I tried everything but it's not working, listener's OK but it still says "not supported".
(Win 10 pro x64)

EDIT: I finnally solved this by putting the file in the correct Program Files directory. Thanks to @Kbotz for giving a helpful explanation.

[XelaUA]

It's works!!! Thnak you!

[Qroxyquan]

It's works!!! Thnak you!

[Driegos]

thanks bro

[danilo-91]

It works perfectly! Thanks!!!

[Lotus-Blue]

Replace the rdpwrap.ini file in c:Program FilesRDP Wrapper with the one provided.
rdpwrap.zip

Thank you very much Stvkodra this if it worked for me, just replace with the one you share and that's it. I send you a hug

[maestro2369]

Big Up !! It works ! Thanks a lot :)

[actanner]

Is there ANY chance that an ini file like this exists for an X86 machine? I have one lonely such computer which could benefit from an update. Thanks!!

[actanner]

My apologies to the group. I didn't read the entire thread. And thanks to sachmomdv for pointing me to an .ini file for 18362.657 x32 that works !

[affinityv]

Updated rdpwrap.ini file with sections for 10.0.18362.657 which cover both x86 and x64 now.

[wildwind122]

It works, thanks a lot !

[kenneth104]

Thanks it's works~

[Visors]

win10 18363.657
it works, thx a lot

[700nader007]

latest Windows 10 update (1909) and all green and working 100%
RDPWrap-v1.6.2-Win10pro 18363.657.zip

[affinityv]

Make sure your INI file is good, blank line at the end and otherwise intact.

[sicwolf]

Replace the rdpwrap.ini file in c:Program FilesRDP Wrapper with the one provided.
rdpwrap.zip

Thanks for your information!
It works for me.

[CmdLnInt]

Replace the rdpwrap.ini file in c:Program FilesRDP Wrapper with the one provided.
rdpwrap.zip

I need to do this remotely ie I cannot stop terminal service. Is there some other way to update the ini?

[thanhtam23]

Replace the rdpwrap.ini file in c:Program FilesRDP Wrapper with the one provided.
rdpwrap.zip

I need to do this remotely ie I cannot stop terminal service. Is there some other way to update the ini?

you can replace the ini file directly then just restart will do

[Iskandare]

command prompt : net stop termservice, replace rdpwrap.ini and after net start termservice

[CmdLnInt]

Replace the rdpwrap.ini file in c:Program FilesRDP Wrapper with the one provided.
rdpwrap.zip

I need to do this remotely ie I cannot stop terminal service. Is there some other way to update the ini?

you can replace the ini file directly then just restart will do

The file is open so I cannot replace it

[CmdLnInt]

command prompt : net stop termservice, replace rdpwrap.ini and after net start termservice

I am already connected remotely. I suppose I could try this in a batch file or powershell script.

[ioan321]

Works for me. Ur an amazing man.

[santomalo]

hi, does anyone have the new .ini for the new
version 10.0.18362.1082

[affinityv]

@santomalo Please create a new link and provide the termsrv.dll as well as the version that RDPConf.exe shows for it.

[affinityv]

Okay, if it is the same as per this issue, then it is covered with this INI.