Listener state: Not listening [not supported] #742

zhang-ray · 2019-04-12T07:02:07Z

OS: Windows 10 Home (Version 1803, OS Build 17134.706)

RDP Wrapper 1.6.2

I got Listener state: Not listening in RDPConf.exe; and RDPCheck.exe told me Socket connection failed.

The text was updated successfully, but these errors were encountered:

hwase0ng · 2019-04-12T10:11:17Z

Latest security update Security update KB4493464 on April 11, 2019 has just broken my RDP wrapper v1.6.2 with this very same message. Uninstalled this latest security update and it now works again.

zhang-ray · 2019-04-12T11:06:33Z

Latest security update Security update KB4493464 on April 11, 2019 has just broken my RDP wrapper v1.6.2 with this very same message. Uninstalled this latest security update and it now works again.

OK, thank you for your information 🙂

rmcgarity · 2019-04-13T20:21:20Z

I have the same problem.

fre4kyC0de · 2019-04-13T21:16:48Z

Add these offsets to your rdpwrap.ini:
https://github.com/fre4kyC0de/rdpwrap/blob/master/10.0.17134.706.txt

DeH4eG · 2019-04-14T13:52:41Z

Latest security update Security update KB4493464 on April 11, 2019 has just broken my RDP wrapper v1.6.2 with this very same message. Uninstalled this latest security update and it now works again.

Thanks, worked for me. 17134.648

rmcgarity · 2019-04-14T22:47:26Z

@fre4kyC0de
Thank you for this suggestion. I attempted your suggestion, but without success. I've not changed the RDPWrap.ini file before, so I may not have done it correctly. I did these steps:

Uninstalled RDPWrap, using the uninstall.bat file in a directory where I had extracted the RDP Wrap files (D:Downloads\RDPWrapcreated in my download directory called RDPWrap.
Ran RDPConf.exe and verified that it was uninstalled. However, the Service state was "Not listening".
Copy/Pasted the contents of the file above to Notepad, and saved it to .....Downloads/RDPWrap so that it is alongside the RDPWInst.exe.
Ran RDPWInst.exe
Ran RDPConf.exe and saw the same "Not listening [not supported]" error message.

I would be grateful if someone could either help me correct any misstep above.

linqifengyun · 2019-04-15T03:44:52Z

Latest security update Security update KB4493464 on April 11, 2019 has just broken my RDP wrapper v1.6.2 with this very same message. Uninstalled this latest security update and it now works again.

OK, thank you for your information 🙂

is that safe for going back?

42Drut · 2019-04-15T04:16:39Z

Thanks fre4kyC0de. Worked very well for me.

hwase0ng · 2019-04-15T04:40:51Z

Add these offsets to your rdpwrap.ini:
https://github.com/fre4kyC0de/rdpwrap/blob/master/10.0.17134.706.txt

Tested working for me, and this is after KB4493464 has been reinstalled by windows update :-)

hwase0ng · 2019-04-15T04:42:52Z

@fre4kyC0de
Thank you for this suggestion. I attempted your suggestion, but without success. I've not changed the RDPWrap.ini file before, so I may not have done it correctly. I did these steps:

Uninstalled RDPWrap, using the uninstall.bat file in a directory where I had extracted the RDP Wrap files (D:Downloads\RDPWrapcreated in my download directory called RDPWrap.
Ran RDPConf.exe and verified that it was uninstalled. However, the Service state was "Not listening".
Copy/Pasted the contents of the file above to Notepad, and saved it to .....Downloads/RDPWrap so that it is alongside the RDPWInst.exe.
Ran RDPWInst.exe
Ran RDPConf.exe and saw the same "Not listening [not supported]" error message.

I would be grateful if someone could either help me correct any misstep above.

You should append the offset to the rdpwrap.ini file. And don't forget to restart windows after that.

BarryBA · 2019-04-15T07:26:45Z

Latest security update Security update KB4493464 on April 11, 2019 has just broken my RDP wrapper v1.6.2 with this very same message. Uninstalled this latest security update and it now works again.

Thank you very much.
At the begining, my Listener state is: Not listening [not supported]
Firstly, I uninstalled the windows security update "KB4493464",
Then, following the suggestion of @fre4kyC0de , I added the offsets in the end of the file "rdpwrap.ini" （https://github.com/fre4kyC0de/rdpwrap/blob/master/10.0.17134.706.txt）,
Last, reboot. And the Listener state becomes: Listening [fully supported]
Thanks a lot to your suggestions @hwase0ng @fre4kyC0de

zhang-ray · 2019-04-15T09:10:43Z

Latest security update Security update KB4493464 on April 11, 2019 has just broken my RDP wrapper v1.6.2 with this very same message. Uninstalled this latest security update and it now works again.

Thank you very much.
At the begining, my Listener state is: Not listening [not supported]
Firstly, I uninstalled the windows security update "KB4493464",
Then, following the suggestion of @fre4kyC0de , I added the offsets in the end of the file "rdpwrap.ini" （https://github.com/fre4kyC0de/rdpwrap/blob/master/10.0.17134.706.txt）,
Last, reboot. And the Listener state becomes: Listening [fully supported]
Thanks a lot to your suggestions @hwase0ng @fre4kyC0de

These steps not worked well for me... After removing all KB security updates and adding the section into "rdpwrap.ini", I got Service state: Stopped and Listener state: Not Listening [fully supported] in RDPConf.exe

BarryBA · 2019-04-15T09:30:22Z

Latest security update Security update KB4493464 on April 11, 2019 has just broken my RDP wrapper v1.6.2 with this very same message. Uninstalled this latest security update and it now works again.

Thank you very much.
At the begining, my Listener state is: Not listening [not supported]
Firstly, I uninstalled the windows security update "KB4493464",
Then, following the suggestion of @fre4kyC0de , I added the offsets in the end of the file "rdpwrap.ini" （https://github.com/fre4kyC0de/rdpwrap/blob/master/10.0.17134.706.txt）,
Last, reboot. And the Listener state becomes: Listening [fully supported]
Thanks a lot to your suggestions @hwase0ng @fre4kyC0de

These steps not worked well for me... After removing all KB security updates and adding the section into "rdpwrap.ini", I got Service state: Stopped and Listener state: Not Listening [fully supported] in RDPConf.exe

Try to uninstall the rdpwrap and install it again. Then do the same steps.
I met the same problem before. And uninstall and reinstall solves it.

rmcgarity · 2019-04-15T22:26:19Z

@hwase0ng @fre4kyC0de
Thank you for responding. The directory containing RDPWInst.exe did not contain a RDPWrap.ini file, so I didn't ADD to that file; I simply created a new RDPWrap.ini and pasted in the contents of the 10.0.17134.706.txt file that fre4kyCode provided. I did reboot, both after uninstalling and after reinstalling, but still got the same result when I ran RDPConf.exe - "Not Listening". I'm running Windows 10 Home, 10.0.17134.706, build 17134. I don't know how to find the security patch version.

Please help me learn what I am doing incorrectly.

joebrug · 2019-04-15T23:01:00Z

@rmcgarity I might be misunderstanding what you're doing.. but when you INSTALL rdpwrap, it puts a rdpwrap.ini file in (at least on windows 7) "c:\program files\RDP Wrapper". This file will have some defaults in it already, which you should keep.. but you need to ADD the sections that @fre4kyC0de gave to the existing rdpwrap.ini file. Make sense? Install RDP Wrap program > edit rdpwrap.ini file it creates > add sections > save > restart PC.

rmcgarity · 2019-04-15T23:11:46Z

@joebrug Thank you for responding! I just removed the RDPWrap.ini file that I created, ran uninstall.bat, ran RDPWrap.exe, rebooted, and it did not create a RDPWrap.ini file in the directory. Any ideas why it didn't do this?

joebrug · 2019-04-15T23:18:56Z

@rmcgarity You mention you ran uninstall.bat, but what about install.bat? :) install.bat is what creates the rdpwrap.ini file in c:\program files\rdp wrapper\ (at least on Win7 x64).. the install.bat will tell you where it put it.

rmcgarity · 2019-04-16T00:47:27Z

@joebrug Thank you - Now it's listening! I didn't know where the RDPWrap.ini file was located.

feritgoksen · 2019-04-18T10:36:03Z

Should we reinstall the update after all of these?

hwase0ng · 2019-04-18T10:40:18Z

Should we reinstall the update after all of these?

If you are referring to the KB4493464 security update, windows will do it automatically for you :-)

feritgoksen · 2019-04-18T10:45:40Z

Should we reinstall the update after all of these?

If you are referring to the KB4493464 security update, windows will do it automatically for you :-)

I have done the steps the same. I uninstalled update, done steps, it worked. But when I installed update again same problem occured.

Gojakdzevad · 2019-04-19T05:47:30Z

If this issue appear again after removing KB 4493464 ( or 4493470 for Win 10 LTSB) you need to download
tool for hiding windows update ( https://www.repairwin.com/prevent-a-specific-windows-update-or-driver-from-installing-in-windows-10/)
Edit : RDPWrap is not only software that is affected with this update , i have similar problems with Fax client software

duytan412 · 2019-05-17T19:54:09Z

Thank you @fre4kyC0de Summarize for those who are not good at computer like me:

Install using install.bat in the zip file from https://github.com/stascorp/rdpwrap/releases
Copy the code from fre4kyC0de above to the end of C:\Program Files\RDP Wrapper\rdpwrap.ini file (You may need to give it permission. Properties, Edit, Choose Users, Allow in Full Control). Save it.
Reboot.

NataschaDeCraene · 2019-07-19T08:23:11Z

Hello,
I have the same issue.
But I don't have the specific KB4493464 installed on the Win10Home pc (1803).
I followed the instructions of duytan412 (adding the extra code to the ini-file).
I also used the suggested termsrv.dll, but I wasn't able to start the Remotedesktop services afterwards.
Any idea?

zaniety · 2019-07-23T21:02:00Z

7/23/19 windows version 17763.615
wont work for me any fix i get the not listening error i did the ini thing above didnt fix it any ideas

yurii20041 · 2019-08-20T08:23:47Z

Hi guys, that helped me with solving the issue for WIndows 10 home 1809:
https://www.vcloudpoint.com/fixing-the-problem-of-windows-system-patch-causing-concurrent-multi-user-login-failed/

Hope it will help.

arpcpro · 2019-09-25T13:17:57Z

Edit: It worked with rdpwrapper_ini_updater and re-install.bat. Super! :)

Thanks, but this is not very convenient since if windows updates itself on the remote computer, I might lose access to the machine.
Anyway I cannot get this to work on Win10 Home version 10.0.18362.356. There is no ini file for this version :(
Also my windows does not allow KB4493464 to be removed. It is simply not on the installed updates list.

surya002 · 2019-10-01T18:01:05Z

Thank you @fre4kyC0de Summarize for those who are not good at computer like me:

Install using install.bat in the zip file from https://github.com/stascorp/rdpwrap/releases

Copy the code from fre4kyC0de above to the end of C:\Program Files\RDP Wrapper\rdpwrap.ini file (You may need to give it permission. Properties, Edit, Choose Users, Allow in Full Control). Save it.

Reboot.

Does this work with the May 2019 Windows update? Because I tried all these steps and it is still not listening

MCarrDallasTx · 2019-10-01T20:52:07Z

So the INI add-on lines did not work for me.
Based on reading above ...
I looked at Windows 10 installed Windows updates and uninstalled the only security update I saw.
(Does not seem like a viable longterm solution.)
I'll try to attach a screenshot of the UNINSTALL KB4516058 in progress--not attaching, so there you are.
...
Now RDP Wrapper works fine.
I'm leaving the INI file add-on lines in place in case they are critical path.
This system is Windows 10 Home 64-bit version 1803 installed 9/17/19.

jh2222 · 2019-10-13T01:55:52Z

Not listening raised its ugly head again. This occurred after Windows 2019—KB4519338 was installed on my Windows 10 computer (Home version) on October 9, 2019. Any solution?

zzeuli · 2019-11-11T15:46:31Z

Hi jh2222.
I was in your same situation and the great "carlos107fer" commented on 29 Sep, made a solution that worked for me.
Follow the steps below:

stop the service running CMD as administrator
net stop termservice
Replace rdpwrap.ini in C:\Program Files\RDP Wrapper
net start termservice
Reboot your PC
rdpwrap_10.0.18362.267_x64.zip

jh2222 · 2019-11-12T15:18:30Z

Thanks zzeuli. Unfortunately, your proposed solution did not work.
I followed all the steps you suggested, including the replacement of rdpwrap.ini from the provided
rdpwrap_10.0.18362.267_x64.zip. Still the listening stated was not listening.
I am running Windows 10 Home, OS build 17763.805.
Maybe you are running an earlier OS build?

zzeuli · 2019-11-12T16:31:52Z

I'm sorry. For me was the only solution worked after the last Windows update 1903.
Since with every major Windows update RDP WRAPPER stops working, It happened to me 3 times, then I found the final solution I would recommend.
I purchased a Win 10 PROFESSIONAL Product Key for € 5 (ebay or Amazon).

Choose the W10PRO KEY that let you UPGRADE from Home to Pro.

Below the email text after purchasing
" If your upgrading from Windows 10 Home to Win 10 Pro. Before upgrading, make sure your device is up to date and running the most recent version of Win 10 Home.

There's no download needed to upgrade from Win 10 Home to Win 10 pro.
1: Select the Start button, then select Settings > Update & security > Activation.
2: Select Change product key, and then enter the 25-character Windows 10 Pro product key.
3: Your system will start upgrading. "

bye!

mcdachpappe · 2019-12-05T19:58:37Z

Hi jh2222.

I was in your same situation and the great "carlos107fer" commented on 29 Sep, made a solution that worked for me.
Follow the steps below:

stop the service running CMD as administrator

net stop termservice
Replace rdpwrap.ini in C:\Program Files\RDP Wrapper
net start termservice
Reboot your PC
rdpwrap_10.0.18362.267_x64.zip

Thank you very much for this solution. I'm currently on Windows 10 x64 Home [Version 1909 Build 18363.476] and this finally worked out for me.

Instead of providing a .zip file I'm going to provide the lines which have to be added to the existing rdpwrap.ini [located at: C:\Program Files\RDP Wrapper]:

[10.0.18362.267]
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=82FB5
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x64=1
SingleUserOffset.x64=0DBFC
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=1FE15
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=22DDC
SLInitFunc.x64=New_CSLQuery_Initialize

[10.0.18362.267-SLInit]
bInitialized.x64 =F6A8C
bServerSku.x64 =F6A90
lMaxUserSessions.x64 =F6A94
bAppServerAllowed.x64 =F6A9C
bRemoteConnAllowed.x64=F6AA0
bMultimonAllowed.x64 =F6AA4
ulMaxDebugSessions.x64=F6AA8
bFUSEnabled.x64 =F6AAC

Note: There must be an empty line at the bottom of the .ini file! Restart your machine and you should be fine :)

Thanks again to @zzeuli for this fix!

Cuchunlain · 2020-02-11T08:48:49Z

Hi jh2222.

I was in your same situation and the great "carlos107fer" commented on 29 Sep, made a solution that worked for me.
Follow the steps below:

stop the service running CMD as administrator

net stop termservice
Replace rdpwrap.ini in C:\Program Files\RDP Wrapper
net start termservice
Reboot your PC
rdpwrap_10.0.18362.267_x64.zip

Thank you very much for this solution. I'm currently on Windows 10 x64 Home [Version 1909 Build 18363.476] and this finally worked out for me.

Instead of providing a .zip file I'm going to provide the lines which have to be added to the existing rdpwrap.ini [located at: C:\Program Files\RDP Wrapper]:
[10.0.18362.267]
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=82FB5
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x64=1
SingleUserOffset.x64=0DBFC
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=1FE15
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=22DDC
SLInitFunc.x64=New_CSLQuery_Initialize

[10.0.18362.267-SLInit]
bInitialized.x64 =F6A8C
bServerSku.x64 =F6A90
lMaxUserSessions.x64 =F6A94
bAppServerAllowed.x64 =F6A9C
bRemoteConnAllowed.x64=F6AA0
bMultimonAllowed.x64 =F6AA4
ulMaxDebugSessions.x64=F6AA8
bFUSEnabled.x64 =F6AAC
Note: There must be an empty line at the bottom of the .ini file! Restart your machine and you should be fine :)

Thanks again to @zzeuli for this fix!

Good morning,
I have tried to make the proposed solution, and the result I get is this:

Wrapper state: installed
Service state: Stopped
Listener state: Not Listening [fully supported]

Then, I try to start the termservice from CMD to change the service state.

In CMD as administrator I execute the command "net start termservice" and it shows me the message: the process has been started successfully, but Service state continues in Stopped and Listener state in Not Listening.

Does anyone have any idea?
I'm running Windows 10 Education

Thanks

loggan26 · 2020-02-13T18:13:54Z

there is a new version in the last windows update, the rdpwrap.ini needs updated with the new version 10.0.18362.657. tested and it works fine as in the pic.

joebrug · 2020-02-13T18:16:12Z

So what did you add in the rdpwrap.ini?

loggan26 · 2020-02-14T08:42:49Z

[10.0.18362.657]
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=82FB5
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x64=1
SingleUserOffset.x64=0DBFC
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=1FE15
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=22DDC
SLInitFunc.x64=New_CSLQuery_Initialize

[10.0.18362.657-SLInit]
bInitialized.x64 =F6A8C
bServerSku.x64 =F6A90
lMaxUserSessions.x64 =F6A94
bAppServerAllowed.x64 =F6A9C
bRemoteConnAllowed.x64=F6AA0
bMultimonAllowed.x64 =F6AA4
ulMaxDebugSessions.x64=F6AA8
bFUSEnabled.x64 =F6AAC

Add this to the bottom of existing rdpwrap.ini leaving a space below the last line and save it!

Cuchunlain · 2020-02-14T08:57:03Z

Thanks to all of you, I finally solved it using the auto-updater mentioned in this post.
#860
This solution has worked for me on two computers with different versions of windows.

Greetings.

Isaacwm · 2020-03-23T11:19:28Z

Thank you @fre4kyC0de Summarize for those who are not good at computer like me:

Install using install.bat in the zip file from https://github.com/stascorp/rdpwrap/releases

Copy the code from fre4kyC0de above to the end of C:\Program Files\RDP Wrapper\rdpwrap.ini file (You may need to give it permission. Properties, Edit, Choose Users, Allow in Full Control). Save it.

Reboot.

Done this but still getting the 'Not Listening [not supported]' on config. Adding the lines @fre4kyC0de linked I assume is done by going to the end of the .ini file, making a new line then pasting in?

tohidul1 · 2020-04-02T06:10:18Z

Guys can you help me plz.
windows 10 pro v.1909

ChrisWLeon · 2020-04-12T14:17:47Z

Thanks to all of you, I finally solved it using the auto-updater mentioned in this post.
#860
This solution has worked for me on two computers with different versions of windows.

Greetings.

I have installed the updater and it works, but VirusTotal online flagged the autoupdate.bat file as a Trojan.DL.Scrip.VBS.Agent Malware?

jarbnyc2017 · 2020-04-20T19:17:09Z

Latest security update Security update KB4493464 on April 11, 2019 has just broken my RDP wrapper v1.6.2 with this very same message. Uninstalled this latest security update and it now works again.

uninstall updates sucks, is better to buy the version 10 pro

ChadThomsen · 2020-04-21T02:04:38Z

Last windows update broke it again.... and update to the rdpwrap.ini file? Thanks in advanced.

robbak · 2020-04-21T02:41:46Z

Check the version of your termserv.dll file. We know there is an update coming in the 05 2020 windows version (termsrv.dll version 10.0.19041.84), and drDrrae already has the offsets for the x86 file. See whether there are offsets for the version you have in the rdpwrap.ini file - the sections headed [10.0.nnnnn.nn], where the ns match your version.

…

On Tue, 21 Apr 2020 at 12:04, Chad Thomsen ***@***.***> wrote: Last windows update broke it again.... and update to the rdpwrap.ini file? Thanks in advanced. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#742 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMCGIVETKJHGROM2IXH4L3RNT5MTANCNFSM4HFN23GQ> .

robbak · 2020-04-21T02:47:44Z

Thanks to all of you, I finally solved it using the auto-updater mentioned in this post.
#860
This solution has worked for me on two computers with different versions of windows.
Greetings.

I have installed the updater and it works, but VirusTotal online flagged the autoupdate.bat file as a Trojan.DL.Scrip.VBS.Agent Malware?

That happens. Either get a better antivirus solution, or whitelist it. It is kind of understandable that an unrecognised bat file that changes system files will be marked as malicious.

TheArgentinian · 2020-04-25T16:52:17Z

Check the version of your termserv.dll file. We know there is an update coming in the 05 2020 windows version (termsrv.dll version 10.0.19041.84), and drDrrae already has the offsets for the x86 file. See whether there are offsets for the version you have in the rdpwrap.ini file - the sections headed [10.0.nnnnn.nn], where the ns match your version.
.

In English?

acyli84 · 2020-06-24T09:55:36Z

I have tried to copy a new set of values into ini file catering for the new version. But it does not work. There is an internal error when trying to remote desktop.

Lm-shen · 2020-09-05T07:30:32Z

OS: Windows 10 Home (Version 1803, OS Build 17134.706)

RDP Wrapper 1.6.2

I got Listener state: Not listening in RDPConf.exe; and RDPCheck.exe told me Socket connection failed.

I am also the same version, encountered the same problem, how do you solve the last, convenient to tell me

robione-nr · 2020-09-27T00:17:27Z

Same issue - service version: 10.0.18362.836

sebaxakerhtc · 2022-01-04T10:30:57Z

Duplicate of #721

adarshmadrecha mentioned this issue Oct 5, 2019

stop the service running CMD as administrator #889

Closed

sebaxakerhtc marked this as a duplicate of #721 Jan 4, 2022

sebaxakerhtc closed this as completed Jan 4, 2022

Listener state: Not listening [not supported] #742

Listener state: Not listening [not supported] #742

Comments

zhang-ray commented Apr 12, 2019

hwase0ng commented Apr 12, 2019

zhang-ray commented Apr 12, 2019

rmcgarity commented Apr 13, 2019

fre4kyC0de commented Apr 13, 2019

DeH4eG commented Apr 14, 2019

rmcgarity commented Apr 14, 2019

linqifengyun commented Apr 15, 2019

42Drut commented Apr 15, 2019

hwase0ng commented Apr 15, 2019

hwase0ng commented Apr 15, 2019

BarryBA commented Apr 15, 2019

zhang-ray commented Apr 15, 2019 • edited Loading

BarryBA commented Apr 15, 2019

rmcgarity commented Apr 15, 2019

joebrug commented Apr 15, 2019

rmcgarity commented Apr 15, 2019

joebrug commented Apr 15, 2019 • edited Loading

rmcgarity commented Apr 16, 2019

feritgoksen commented Apr 18, 2019

hwase0ng commented Apr 18, 2019

feritgoksen commented Apr 18, 2019

Gojakdzevad commented Apr 19, 2019 • edited Loading

duytan412 commented May 17, 2019 • edited Loading

NataschaDeCraene commented Jul 19, 2019

zaniety commented Jul 23, 2019

yurii20041 commented Aug 20, 2019

arpcpro commented Sep 25, 2019 • edited Loading

surya002 commented Oct 1, 2019

MCarrDallasTx commented Oct 1, 2019

jh2222 commented Oct 13, 2019

zzeuli commented Nov 11, 2019

Hi jh2222. I was in your same situation and the great "carlos107fer" commented on 29 Sep, made a solution that worked for me. Follow the steps below:

stop the service running CMD as administrator net stop termservice Replace rdpwrap.ini in C:\Program Files\RDP Wrapper net start termservice Reboot your PC rdpwrap_10.0.18362.267_x64.zip

jh2222 commented Nov 12, 2019

zzeuli commented Nov 12, 2019

mcdachpappe commented Dec 5, 2019 • edited Loading

Hi jh2222.

stop the service running CMD as administrator

Cuchunlain commented Feb 11, 2020

Hi jh2222.

stop the service running CMD as administrator

loggan26 commented Feb 13, 2020 • edited Loading

joebrug commented Feb 13, 2020

loggan26 commented Feb 14, 2020 • edited Loading

Cuchunlain commented Feb 14, 2020

Isaacwm commented Mar 23, 2020

tohidul1 commented Apr 2, 2020

ChrisWLeon commented Apr 12, 2020

jarbnyc2017 commented Apr 20, 2020

ChadThomsen commented Apr 21, 2020

robbak commented Apr 21, 2020 via email

robbak commented Apr 21, 2020

TheArgentinian commented Apr 25, 2020

acyli84 commented Jun 24, 2020

Lm-shen commented Sep 5, 2020 • edited Loading

robione-nr commented Sep 27, 2020

sebaxakerhtc commented Jan 4, 2022

zhang-ray commented Apr 15, 2019 •

edited

Loading

joebrug commented Apr 15, 2019 •

edited

Loading

Gojakdzevad commented Apr 19, 2019 •

edited

Loading

duytan412 commented May 17, 2019 •

edited

Loading

arpcpro commented Sep 25, 2019 •

edited

Loading

Hi jh2222.
I was in your same situation and the great "carlos107fer" commented on 29 Sep, made a solution that worked for me.
Follow the steps below:

stop the service running CMD as administrator
net stop termservice
Replace rdpwrap.ini in C:\Program Files\RDP Wrapper
net start termservice
Reboot your PC
rdpwrap_10.0.18362.267_x64.zip

mcdachpappe commented Dec 5, 2019 •

edited

Loading

loggan26 commented Feb 13, 2020 •

edited

Loading

loggan26 commented Feb 14, 2020 •

edited

Loading

Lm-shen commented Sep 5, 2020 •

edited

Loading