-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Comments
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 |
Yep. Working for me. |
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) |
This comment was marked as spam.
This comment was marked as spam.
Hello, |
Winver - 18363.657 - work ! |
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. |
I am in the same situation as VeloiRacer. I have a Windows 10 x32 (18363.657). Can someone help us? |
Try this file for x86 machines. No guarantee it will work. |
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. |
For me it was need restart windows. When status was ok and checker returns bad permissions. |
Hi @stvkodra It work perfectly, Thanks |
xrbh70, your win10 is x32 or x64? |
I had the same problem with Windows version 18363.567. |
Still didn't work for Win10 x32 :( |
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. |
Try set options "default RDP authentication" ,Applay, reboot |
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: a-lascu<mailto:[email protected]>
Sent: 2/14/2020 2:50 PM
To: stascorp/rdpwrap<mailto:[email protected]>
Cc: VelociRacer<mailto:[email protected]>; Comment<mailto:[email protected]>
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 GitHub<#988?email_source=notifications&email_token=AORSXNSJLLUG4YSB2K7UKGTRC3YYXA5CNFSM4KT5QY4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL2HUJA#issuecomment-586447396>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AORSXNQSIDSS4PNPL63FCLDRC3YYXANCNFSM4KT5QY4A>.
|
Multiple sessions for same user are working here - for both W7x64 and W10x64. Big ups to stvkodra for the updated file. |
Nobody can help us with .ini for Win10 x32? |
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? |
This worked for me in win10 10.0.18362.657 32bits x86 |
@ 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 |
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. |
Great thanks for sharing, I have the same OS and 100% in business with new .ini.
…________________________________
From: sanchomdv<mailto:[email protected]>
Sent: 2/17/2020 11:31 AM
To: stascorp/rdpwrap<mailto:[email protected]>
Cc: VelociRacer<mailto:[email protected]>; Comment<mailto:[email protected]>
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)<#999 (comment)>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#988?email_source=notifications&email_token=AORSXNTGDP57J2RSDAPFT33RDK3XLA5CNFSM4KT5QY4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL7AQ2I#issuecomment-587073641>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AORSXNX4GNPXRLZYJBWX4DTRDK3XLANCNFSM4KT5QY4A>.
|
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. |
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. |
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 |
Big Up !! It works ! Thanks a lot :) |
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!! |
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 ! |
Updated rdpwrap.ini file with sections for 10.0.18362.657 which cover both x86 and x64 now. |
It works, thanks a lot ! |
Thanks it's works~~~~~ |
win10 18363.657 |
|
Make sure your INI file is good, blank line at the end and otherwise intact. |
Thanks for your information! |
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 |
command prompt : net stop termservice, replace rdpwrap.ini and after net start termservice |
The file is open so I cannot replace it |
I am already connected remotely. I suppose I could try this in a batch file or powershell script. |
Works for me. Ur an amazing man. |
@santomalo Please create a new link and provide the termsrv.dll as well as the version that |
Duplicate of #983 |
Replace the rdpwrap.ini file in c:\Program Files\RDP Wrapper with the one provided.
rdpwrap.zip
The text was updated successfully, but these errors were encountered: