Skip to content
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

Windows 10 version 10.0.18363.657 Now Working. #988

Closed
stvkodra opened this issue Feb 12, 2020 · 66 comments
Closed

Windows 10 version 10.0.18363.657 Now Working. #988

stvkodra opened this issue Feb 12, 2020 · 66 comments

Comments

@stvkodra
Copy link

Replace the rdpwrap.ini file in c:\Program Files\RDP Wrapper with the one provided.
rdpwrap.zip

@EspacioCivico
Copy link

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
Copy link

Yep. Working for me.
Thanks very much stvkodra.

@itsAllDigital
Copy link

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

This comment was marked as spam.

@jul974
Copy link

jul974 commented Feb 13, 2020

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
Copy link

Korvinho commented Feb 13, 2020

Winver - 18363.657 - work !

@VelociRacer
Copy link

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
Copy link

a-lascu commented Feb 13, 2020

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

@stvkodra
Copy link
Author

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

@a-lascu
Copy link

a-lascu commented Feb 13, 2020

Thank you, stvkodra.
Unfortunately it's not working.
My Win10 x32 is 18363.657 version.
Annotation 2020-02-13 224629

@VelociRacer
Copy link

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
Copy link

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

@xrbh70
Copy link

xrbh70 commented Feb 14, 2020

Hi @stvkodra It work perfectly, Thanks
imagen

@a-lascu
Copy link

a-lascu commented Feb 14, 2020

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
Copy link

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
Copy link

a-lascu commented Feb 14, 2020

Still didn't work for Win10 x32 :(

@maantao
Copy link

maantao commented Feb 14, 2020

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
Copy link

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

@darkvampire1
Copy link

Thank you, stvkodra.
Unfortunately it's not working.
My Win10 x32 is 18363.657 version.
Annotation 2020-02-13 224629

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

@a-lascu
Copy link

a-lascu commented Feb 14, 2020

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.
Annotation 2020-02-14 214629

@VelociRacer
Copy link

VelociRacer commented Feb 14, 2020 via email

@Kbotz
Copy link

Kbotz commented Feb 15, 2020

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
Copy link

a-lascu commented Feb 16, 2020

Nobody can help us with .ini for Win10 x32?

@maantao
Copy link

maantao commented Feb 17, 2020

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

image

Are we missing the obvious for concurrent same user access?

@sanchomdv
Copy link

This worked for me in win10 10.0.18362.657 32bits x86
#999 (comment)

@Iskandare
Copy link

@ 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
Copy link

Kbotz commented Feb 17, 2020

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 Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote 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
Copy link

VelociRacer commented Feb 18, 2020 via email

@maantao
Copy link

maantao commented Feb 18, 2020

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
Copy link

Kbotz commented Feb 18, 2020

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.

@Lotus-Blue
Copy link

Replace the rdpwrap.ini file in c:\Program Files\RDP 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
Copy link

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

@actanner
Copy link

actanner commented Mar 4, 2020

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
Copy link

actanner commented Mar 5, 2020

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
Copy link

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

@wildwind122
Copy link

It works, thanks a lot !

@kenneth104
Copy link

Thanks it's works~~~~~

@Visors
Copy link

Visors commented Mar 9, 2020

win10 18363.657
it works, thx a lot

@700nader007
Copy link

700nader007 commented Mar 10, 2020

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

@affinityv
Copy link

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

@sicwolf
Copy link

sicwolf commented Mar 20, 2020

Replace the rdpwrap.ini file in c:\Program Files\RDP Wrapper with the one provided.
rdpwrap.zip

Thanks for your information!
It works for me.

@CmdLnInt
Copy link

Replace the rdpwrap.ini file in c:\Program Files\RDP 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
Copy link

Replace the rdpwrap.ini file in c:\Program Files\RDP 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
Copy link

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

@CmdLnInt
Copy link

Replace the rdpwrap.ini file in c:\Program Files\RDP 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
Copy link

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
Copy link

ioan321 commented May 1, 2020

Works for me. Ur an amazing man.

@affinityv
Copy link

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

@affinityv
Copy link

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

@sebaxakerhtc
Copy link

Duplicate of #983

@sebaxakerhtc sebaxakerhtc marked this as a duplicate of #983 Apr 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests