sashaqwert commented 2 years ago

This issue describes solutions to the Unknown and N/A problems seen in RDPConf (or RDP_CnC). These errors are usually caused by your antivirus software. Therefore, before installing RDP Wrapper, it is recommended to add the C:\Program Files\RDP Wrapper directory to the exceptions.

Compare your RDPConf with the screenshots below of the issues before taking action.

Problem 1

81126754-53682300-8f0a-11ea-8b37-598cfd71349d

In this case, you need to restore the C:\Program Files\RDP Wrapper\rdpwrap.dll file. It can be downloaded here: rdpwrap-DLL.zip Reboot is needed after this!

Problem 2

Service state: unknown. 163357705-250c5ea0-c8a7-4d48-9097-0660143236ad

In this case, the registry branch HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService was deleted (or severely damaged) by the antivirus. You need to restore it from a clean OS backup (where RDP Wrapper was not installed).

Restoring a registry branch from a backup:

Download .reg file
Open this (dual left click)
Press yes
Reboot

Ready backups: termService-REG.zip Additional info for BitDefender users

Problem 3

image_2021-07-05_14-32-50

Answer here: https://github.com/stascorp/rdpwrap/issues/384#issuecomment-355833698 Reboot is needed after this!

Problem 4

The solution is unknown. This problem usually occurs on systems that do not pass integrity (sfc /scannow). If you have found a solution, you can describe it by specifying information about the OS and the installed antivirus.

Important: RDP Wrapper is intended only for copies of Windows undergoing integrity checks.

Next steps

After all the methods, you need to reinstall RDP Wrapper, since the above methods simply "restore" the original system behavior (before installing RDP Wrapper).

Note

If everything is green in the RDPConf diagnostics, but concurrent sessions are not working, try running the following commands in CMD as an administrator:

net stop termService
net start termService

If only not listening on Home edition (and other is green):

net start termService

ghost commented 2 years ago

If everything is green in the RDPConf diagnostics, but concurrent sessions are not working, try running the following commands in CMD as an administrator:

net stop termService net start termService

Procedure performed and did not work. I also registered the path in the antivirus before reinstalling and it didn't work either. Even after all this and everything green, it only accepts 1 user as usual.

sashaqwert commented 2 years ago

If everything is green in the RDPConf diagnostics, but concurrent sessions are not working, try running the following commands in CMD as an administrator: net stop termService net start termService

Procedure performed and did not work. I also registered the path in the antivirus before reinstalling and it didn't work either. Even after all this and everything green, it only accepts 1 user as usual.

try modded version by @sebaxakerhtc https://github.com/sebaxakerhtc/rdpwrap/releases

JEmlay commented 2 years ago

If everything is green in the RDPConf diagnostics, but concurrent sessions are not working, try running the following commands in CMD as an administrator: net stop termService net start termService

Procedure performed and did not work. I also registered the path in the antivirus before reinstalling and it didn't work either. Even after all this and everything green, it only accepts 1 user as usual.

try modded version by @sebaxakerhtc https://github.com/sebaxakerhtc/rdpwrap/releases

I tried that a week ago (#1873 ). It does not solve this problem. I suspect a lot of these closed issues will need to reopened.

EDIT: Multiple people tried that, did not work.

kkm5848 commented 2 years ago

I have windows 11 22000.675.

This worked for me ! It restored the original remote desktop capability which wasn't working anymore.

Then followed all the instructions above. Installed RDP Wrapper than ran the autoupdate script (https://github.com/stascorp/rdpwrap/pull/1160) from the "c:\program files\rdp wrapper" directory which restored the rdp wrapper functionality (multiple logins!)

sebaxakerhtc commented 2 years ago

Multiple people tried that, did not work

That's strange, because for ~2000 people that's work You can ask for help in official Telegram channel or in my Discord channel.

JEmlay commented 2 years ago

Multiple people tried that, did not work

That's strange, because for ~2000 people that's work You can ask for help in official Telegram channel or in my Discord channel.

I've already asked for help in #1873

kkm5848 commented 2 years ago

It took a bit of effort -- I needed to also make sure to add the Downloads directory and the RDP wrapper installation directory in the list of exclusions for "Windows Defender"

sashaqwert commented 2 years ago

@kkm5848

add the Downloads directory

This directory is optional. It is sufficient to disable real-time protection for the duration of the installation.

Immediately after installation, it is safe to delete the downloaded file as it is no longer used by the OS.

frakman1 commented 2 years ago

The autoupdate script was what fixed it for me in the end. I show all my issues from initial failure to success here: #1959 (On freshly installed Win10 VM Home)

mboyden commented 2 years ago

We need to add one more registry update step to the instructions in the OP.

I had all the issues noted in the (updated) OP above, and it was due to Anti-Virus (BitDefender in this case). RDPConf showed Wrapper State: Not Installed and everything else came up gray. I implemented all the fixes noted above: create AV exceptions for the files quarantined (), restore missing registry settings for termsrv, update ini. Still RDPWInst would produce a 1053 error and RDPConf was all greyed out.

After more searching I finally found another pair of Registry fixes that finally fixed my issue: #1818.

Once I updated those 2 keys to add the TermService keyword and rebooted, it started working again (with the latest rdpwrap.ini, of course). Yay! And thanks to those who figured it out.