Not listening [fully supported] 10.0.18362.657

[f300]

Since the Feb/March Windows Updates I can't get RDPWrap to work.

I've uninstalled, rebooted, reinstalled, rebooted, etc multiple times. I'm using the ini from #1022 (comment) on Windows 10 Home 64bit

Any ideas?
Thanks!

[affinityv]

Can you do normal RDP without RDP Wrapper? If not, perhaps an AV has taken out the RDP Windows registry components. I have a couple of reg files in my repo, but I'm not sure if Win 10 Home is covered by the Win 10 Pro one.

[f300]

Can you do normal RDP without RDP Wrapper? If not, perhaps an AV has taken out the RDP Windows registry components. I have a couple of reg files in my repo, but I'm not sure if Win 10 Home is covered by the Win 10 Pro one.

Thanks for your reply! Ofc Home can't act as an RDP Server without RDP Wrapper, so I guess you mean Remote Assistance? That works fine. No AV apart from Windows Defender.

However, I have another PC here with exactly the same Windows and termsrv.dll version as the problem PC, but a much fresher Windows install. I've not tried RDP Wrapper on it until just now, but it works fine.

I've exported and compared the registry entries under Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService between the two systems and they are the same.

So, something has become misconfigured or corrupted on the problem system, as it should be working, but I have no idea where to look. SFC /SCANNOW finds nothing wrong.

[affinityv]

Windows Defender can stop rdp wrapper, make sure you have exclusions to protect it.

[f300]

I've added exclusions for the RDP Wrapper directory, rdpwrap.dll, RDPWInst.exe, etc and uninstalled / reinstalled - No change, still not listening.

[affinityv]

Whenever you do a reinstall, make sure you replace the ini file with one that supports your termsrv.dll version (shown in rdpconf). Then restart RDP Wrapper rdpwinst.exe -r

[kouwei32]

Same issue on 10.0.18362.657, using updated alt INI, and restarted the wrapper via -r. Fully supported but not listening. Notably, restart logs had "StartService Error (Code 1056)", but config says that the service is running

[Dashu-Xu]

Same issue on 10.0.18362.657, using updated alt INI, and restarted the wrapper via -r. Fully supported but not listening. Notably, restart logs had "StartService Error (Code 1056)", but config says that the service is running

have you solve the problem yet? I got the same problem but can you tell me where i can find the "restart logs", i want to check the service state as well... thx.

[kouwei32]

It is from the output of the command prompt when running the -r parameter. Not sure if this helps

[CaspianCanuck]

Using the latest INI file linked from affinityv's answer in issue #1022 fixed it for me.

[KevinH404]

Using the latest INI file linked from affinityv's answer in issue #1022 fixed it for me.

This fixed for me.

[f300]

Using the latest INI file linked from affinityv's answer in issue #1022 fixed it for me.

That's the ini I am already using.

[Zykov-Alexey]

thanks, #issue 1022 fixed

[jamco88]

Using the latest INI file linked from affinityv's answer in issue #1022 fixed it for me.

Where do you put the ini file?

[affinityv]

@jamco88 #1035 (comment)

[richw100]

If this is the same problem that I have had, I think it might be because you have inadvertently removed read access to the NETWORK SERVICE user to the .ini file when copying it across.

I'd suggest reinstalling, then instead of copying the new .ini file over, edit the one in C:\Program Files\RDP Wrapper with notepad running as Administrator , and copy the new contents across.

At the same time, I'd recommend giving "NETWORK SERVICE" write and modify rights on the RDP Wrapper folder, and comment out the ";LogFile=\rdpwrap.txt" line in the .ini file. This should force RDPWrap to write it's logfile into the RDP Wrapper folder, so you should be able to trace it working.

The logfile should contain some lines saying it is patching in between the "freezing" and "resuming" threads, as below. If you see these two lines together, it indicates that RDPWrap has failed to read the .ini file, so check permissions again.

Freezing threads...
Patch CEnforcementCore::GetInstanceOfTSLicense
Patch CSessionArbitrationHelper::IsSingleSessionPerUserEnabled
Patch CDefPolicy::Query
Hook CSLQuery::Initialize
Resumimg threads...

[richw100]

At the same time, I'd recommend giving "NETWORK SERVICE" write and modify rights on the RDP Wrapper folder, and comment out the ";LogFile=\rdpwrap.txt" line in the .ini file. This should force RDPWrap to write it's logfile into the RDP Wrapper folder, so you should be able to trace it working.

Though I should point out, for security reasons, it will be best to revert this so NETWORK SERVICE does not have unrestricted write/modify rights on the folder, .ini or .dll, and only allow it write access to .txt file!

[latware]

Using the latest INI file linked from affinityv's answer in issue #1022 fixed it for me.

worked for me too on

OS Name: Microsoft Windows 10 Home
OS Version: 10.0.19041 N/A Build 19041

just stopped service & replaced .ini in RDPwrapper directory, after restarting termserv I have RDP connection...

[jianwu]

Works for me: 10.0.19041.789
Use the solution in #1022, and instead of copy the ini file, I edited it to avoid permission problems. Finally, get it to work.

[ctmakro]

• use the INI file mentioned in Listener state: Not listening [not supported] #1022
• IMPORTANT: instead of copy the ini file, edit it to avoid permission problems.

[sebaxakerhtc]

Acceptable to #872