First off, thanks for creating this. Made it much simpler to enable RDP on my Win8.1 Home install, so that I don't have to do a clean install of Win8.1 Pro.

Now to the problem - it seems that only one Network adapter is bound to RDPWrap - I'd like to be able to choose which one to use (or even better, let me choose priority, so that if one is disconnected, it binds to the other). I can't seem to find any way to do this?

Hello,

I've tried to install the binaries on a French installation of Windows 7 but it failed.

Is this a known limitation ?

Thanks,

Listener state:NOt listening [not supported]

How do I enable shadowing?
From rdp config is set to allow but I can't shadow...

Regards,

Hi, I just installed the rdpwrap with the current INI (using the youtube video guide). When I run the Config tool everything is green except the listener state which says "not listening".

I'm not sure what information to add to help solve this problem, so I'll just throw in some infos I can find:

• I upgraded Windows 7 Home Premium to Windows 10 Home
• Version next to wrapper state: 1.5.0.0
• Version next to service state: 10.0.10240.16384
• Port is 3386
• I verified that "Remotedesktop" is allowed in the Firewall rules
• I (obviously) can't connect using the check tool

I'm not sure if this is a bug or if I'm doing something wrong. Any help would be appreciated. If I can get any more data to help with this I'd be glad to provide them (given some directions where to retrieve them).

Greetings!

build 9926 has changed the major version of termserv.dll from 6 to 10.

After some asm debugging I found out the new offsets (I only have x64 version):

[10.0.9926.0]
; Patch CEnforcementCore::GetInstanceOfTSLicense
LocalOnlyPatch.x64=1
;;;OFFSET = 0x61
;;;BASE   = 0x95F90
LocalOnlyOffset.x64=95FF1
LocalOnlyCode.x64=jmpshort
; Patch CSessionArbitrationHelper::IsSingleSessionPerUserEnabled
SingleUserPatch.x64=1
;;;OFFSET   = 0x43
;;;BASE     = 0x12F90
;;;;instruction = 0xBB 0x01 0x00 0x00 0x00
;;;                   ^^^ +1 offset
SingleUserOffset.x64=12A34
SingleUserCode.x64=Zero
; Patch CDefPolicy::Query
DefPolicyPatch.x64=1
;;;
;;;BASE     = 0xBDF0
;;;OFFSET   = 0x15
DefPolicyOffset.x64=BE05
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
; Hook CSLQuery::Initialize
SLInitHook.x64=1
SLInitOffset.x64=24EC0
SLInitFunc.x64=New_CSLQuery_Initialize

[10.0.9926.0-SLInit]
bFUSEnabled.x64       =EEBF0
lMaxUserSessions.x64  =EEBF4
bAppServerAllowed.x64 =EEBF8
bInitialized.x64      =EEBFC
bMultimonAllowed.x64  =EEC00
bServerSku.x64        =EEC04
ulMaxDebugSessions.x64=EEC08
bRemoteConnAllowed.x64=EEC0C

Hi.

Running Windows 10 Pro 64Bit fully updated.

While having Multi Session Per User active and the user logged in locally. (Maybe with a locked desktop)
I then login remotely with the same user and switch to the local user via task-manager.

The next time you try to login remotely or locally it just return "There was a error in the DLL file." after you type in user and password.

You can only click ok and then it returns to the password prompt.
A reboot is then necessary to get it back up and running.

Can u please update it to the new Windows 10 Build.
Thanks for your awesome work.

We are experiencing technical issues with x64 version on some machines. There is unknown exception somewhere in the code, here are related comments and logs:
#33 (comment)
#33 (comment)
#33 (comment)
#34 (comment)
#38 (comment)

For the advanced users who encountered the same problem, use Visual Studio 2013 or higher to debug the DLL file and to find actual reason of exception.

Test cases:

• VirtualBox - Windows 10 Home x64 - no issue

Hi there, thanks for the precious tool.

You may do these simple changes to install.bat and uninstall.bat, so that when you double-click on theses batch files, they will work too :

• install.bat, line 2:
  "%~dp0RDPWInst" -i
• uninstall.bat, line 2:
  "%~dp0RDPWInst" -u

Hi
I'm not sure if it's just me being incredibly thick, but I can't seem to get it to allow more than one session in Windows 10 pro. Everything is green, but I always get the screen saying it must log out the other user first (both with and without one session per user selected, RDP user being a different one from logged in user).

On a side note for anyone still having trouble with ini files, etc. The easiest thing to do it to download the latest 1.5 version under the Releases header on github, then use the "Download as Zip" button on the main github page to download the whole source as a zip. Unzip the Release zip, and from the source zip file, in the res folder, copy the two un/install.bat files over the ones in the unzipped release folder. Then right click and run the install.bat as administrator to install. Once done, go to the rdpwrap folder in program files and copy into it the rdpwrap.ini from the res folder in the source zip file. Run rdpconf from the unzipped release zip, and as they say, Bob's your Uncle (whoever Bob is, he he)!
Alex

Hiya,

kinda lost in troubleshooting here - win 10 - wrapper 1.5 with new config installed fine and nicely but ending up like using no wrapper at all ...

diag stats...

rdpwrap log...

No real clue how to troubleshoot further - any advice will do tho ^^

--rgds marcO

I think I describe it in a detailed way here http://stackoverflow.com/questions/32281940/how-to-publish-or-export-x86-and-x64-c-version-of-rdpwrap?noredirect=1#comment52442417_32281940

It seems that the zip files do not contain an RDPWinst executable. Not being a programmer I don't know what to do.

Hello,

I just recently gave this a shot with Windows 10 Consumer Preview Build 10532. I can't seem to get it to work with this build. Any help would be greatly appreciated. I think it is because of the version of the termsrv.dll I have included a link to the dll.

http://wikisend.com/download/456260/termsrv.dll

The wrapper is incredibly helpful, especially for system administrators. Therefore it would be great to be able to roll it out via GPO software deployment, but for that a MSI package would be needed.

Hi, this is a great software, just discovered that doesnt works the start program at logon, is there anyway to provide support to this?. Thanks

Hello,

Installation is failing on Windows 7 (French fresh install and fully up to date) as you can see :

[*] Installing...
[*] Terminal Services version: 6.1.7601.18637
[+] This version of Terminal Services is fully supported.
[*] Configuring TermService...
[*] Starting TermService...
[-] StartService error (code 1068).
[-] Failed to set up TermService. Unknown error.

Any suggestion as to how I could overcome the issue ?

Thanks,

Seb

I added a remotefx GPU to windows 8 and then tried using rdpwrap and it fails. I removed the remotefx GPU and then the rdpwarp succeeded.

Please help me use rdpwrap while running a remotefx GPU.

The GPU is: firepro s7000

I've a commercial version of a "similar" of rdpwrap the problem is always the same: in some cases a windows update changes something, then rdp does not work until next software release.
Solution would be logging all the successfull (= not critical against rdpwrap) windows updates
would be great to "invent" a way to extract from a pc all the updates and send them automatically to a server. I like .net programming (because is fast very fast for RAD programming and works also in linux with mono), so I would like to collaborate and help in that way if someone wants too!
I still do not use windows 10: i know there is another issue: you cannot avoid automatic updates unless you do not install a tool "https://support.microsoft.com/en-us/kb/3073930".

In case it wasn't clear enough from the title line - this is not an issue with RDP Wrapper. I've been trying to get the RDP connection from my Win7 desktop to my Win8 desktop quicker - it's been really slow. I've tried several things - and most recently this:

http://superuser.com/questions/515180/rdp-connection-from-windows-7-8-to-server-2012-is-slow/571750#571750

Will that interfere with the (awesome!) functionality of RDP Wrapper?

Thanks,
Eliezer

I've used RDP Wrap successfully on many different computers of all types.

I've never had any issue before now.

The PC is running Windows 8.1 Professional and the Terminal Services version is 6.3.9600.17415.

I have removed the AVG anti-virus completely from the system and it is now only using the default Windows Defender - which I've used before without any issue.

What is happening is that we are able to use a Remote Desktop Connection to connect to the "server" PC and we are presented with the normal User Log In screen and we are able to actually log into to the server as the user - briefly. The desktop session is created and the desktop is displayed completely - but after about 5 seconds a message box opens and explains that there is a problem and that the sessions needs to close. I don't have the exact message text but that is the gist of the message.

I have tried changing the desktop display from a photo to a solid color - thinking that the image could be somehow causing the session to quit. I've checked all of the normal permissions - remote desktop is allowed and we are not requiring NLA. Each user is an Administrator and also a member of the Remote Desktop Users group.

It is almost like there is something that is realizing that RDP is running and then it is being shutdown by something - without explanation.

Has anyone seen this? I would LOVE a prompt answer as I really need to get this working asap - thank you to everyone in advance for your assistance.

Charlie

Не получается запустить RDPWrapper.

ini-файл заменен на новый (от 17.07.2015), RDPConf показывает, что все ок.

лог:

>>> SvchostPushServiceGlobals
Loading configuration...
Configuration file: c:\program files\rdp wrapper\rdpwrap.ini
>>> SvchostPushServiceGlobals
Loading configuration...
Configuration file: c:\program files\rdp wrapper\rdpwrap.ini
>>> SvchostPushServiceGlobals
Loading configuration...
Configuration file: c:\program files\rdp wrapper\rdpwrap.ini
>>> SvchostPushServiceGlobals
Loading configuration...
Configuration file: c:\program files\rdp wrapper\rdpwrap.ini
Initializing RDP Wrapper...
Base addr:  0x00007FFA36000000
SvcMain:    termsrv.dll+0x000000000000CDF0
SvcGlobals: termsrv.dll+0x00000000000345A0
Version:    10.0.10240.16384
Freezing threads...
Resumimg threads...
<<< SvchostPushServiceGlobals
>>> ServiceMain
<<< ServiceMain
>>> SvchostPushServiceGlobals
>>> SvchostPushServiceGlobals
Loading configuration...
Configuration file: c:\program files\rdp wrapper\rdpwrap.ini
>>> SvchostPushServiceGlobals
Loading configuration...
Configuration file: c:\program files\rdp wrapper\rdpwrap.ini

I'm running Windows 10 Home. I installed RDPWrap v1.5 and updated the rdpwrap.ini file.
When I restarted rdpwinst I get a couple of StartService error (code 1056) in the CMD window and in the RDP Wrapper Configuration the Listener state is Not Listening.

This is my first time working with RDPWrap and I'm not too knowledgeable with this type of installation. Any help would be greatly appreciated.

Windows 10 RTM Pro x64

Steps to reproduce:

• Install RPWrap, make sure to update rdpwrap.ini to the lastest
• Set the configurations as follows:

[Enable RDP Check, Single User Session Uncheck, Default Auth, Shadowing with request]

• Lock your desktop
• Go to another pc.
• Create an RDP session to your installation with the same user as you used above
• Minimize it but do not close
• Create a second RDP session to your installation with the same user as you used above
• Disconnect both sessions. Do not Sign Out.
• Try RDPing again or try log locally. In both cases you will be greeted with a screen similar to this:

[Empty blue screen with a single string "Error in the DLL" and "ok" button underneath]

The only thing you can do now to get in is power-cycle and loose all your work.

This is the content of the log file after the power-cycle:

Initializing RDP Wrapper...
Base addr:  0x00007FF949CB0000
SvcMain:    termsrv.dll+0x000000000000CDF0
SvcGlobals: termsrv.dll+0x00000000000345A0
Version:    10.0.10240.16384
Freezing threads...
Patch CEnforcementCore::GetInstanceOfTSLicense
Patch CSessionArbitrationHelper::IsSingleSessionPerUserEnabled
Patch CDefPolicy::Query
Hook CSLQuery::Initialize
Resumimg threads...
<<< SvchostPushServiceGlobals
>>> ServiceMain
<<< ServiceMain
>>> CSLQuery::Initialize
SLInit [0x00007FF949DA23B8] bServerSku = 1
SLInit [0x00007FF949DA3470] bRemoteConnAllowed = 1
SLInit [0x00007FF949DA3460] bFUSEnabled = 1
SLInit [0x00007FF949DA23B4] bAppServerAllowed = 1
SLInit [0x00007FF949DA3468] bMultimonAllowed = 1
SLInit [0x00007FF949DA23B0] lMaxUserSessions = 0
SLInit [0x00007FF949DA346C] ulMaxDebugSessions = 0
SLInit [0x00007FF949DA3464] bInitialized = 1
<<< CSLQuery::Initialize
Initializing RDP Wrapper...
Base addr:  0x00007FFCE1CC0000
SvcMain:    termsrv.dll+0x000000000000CDF0
SvcGlobals: termsrv.dll+0x00000000000345A0
Version:    10.0.10240.16384
Freezing threads...
Patch CEnforcementCore::GetInstanceOfTSLicense
Patch CSessionArbitrationHelper::IsSingleSessionPerUserEnabled
Patch CDefPolicy::Query
Hook CSLQuery::Initialize
Resumimg threads...
<<< SvchostPushServiceGlobals
>>> ServiceMain
<<< ServiceMain
>>> CSLQuery::Initialize
SLInit [0x00007FFCE1DB23B8] bServerSku = 1
SLInit [0x00007FFCE1DB3470] bRemoteConnAllowed = 1
SLInit [0x00007FFCE1DB3460] bFUSEnabled = 1
SLInit [0x00007FFCE1DB23B4] bAppServerAllowed = 1
SLInit [0x00007FFCE1DB3468] bMultimonAllowed = 1
SLInit [0x00007FFCE1DB23B0] lMaxUserSessions = 0
SLInit [0x00007FFCE1DB346C] ulMaxDebugSessions = 0
SLInit [0x00007FFCE1DB3464] bInitialized = 1
<<< CSLQuery::Initialize

This isn't an issue with RDPwrap, but it might be an enhancement request. :-)

I have a VM that is running Win 8.1 Enterprise x86, and would like to be able to RDP to this box, and carry on from where I left off, last time I was using it, either RDP or console. Currently, making a normal RDP connection (no RDPwrap installed), making a new connection always logs off the existing (console or RDP) session first. Does anyone else see that as well?

If UAC is enabled - there is no other way to install RDPWrap than:

1. launch elevated cmd
2. change dir to rdpwrap folder
3. execute install.bat

to fix this one line must be changed in install.bat:

RDPWInst -i

to

%~dp0RDPWInst -i

and in uninstall.bat

RDPWInst -u

to

%~dp0RDPWInst -u

renewed files will work from windows explorer as expected and there will be no need in 1&2

This is awesome for me as I have Windows Basic on my tablet.
But does anyone know what the legal status of this is? To me it looks fine because you are not patching the dll with a hacked or unlicensed dll, just loading it with different parameters.

i installed successfully, updated the ini (followed the youtube video https://www.youtube.com/watch?v=W9BpbEt1yJw) but when i restart the RDPWInst.exe i get this:

not sure what it could be..please help...

Hello,

I can see in your code that you change some variables for RemoteApp, so I tested RemoteApp on Windows 7 Pro x86 (6.1.7601.18637).
However, this is not working at all.

Full Desktop remote sessions are working fine, but RemoteApp not.
Do you have any idea on how this could work ?

Also, do you know how to activate Debug Messages for termsrv.dll ? I wanted to help you, but I cannot see these Debug Messages with WinDbg...

Hi,

This is the termsrv.dll of version 6.1.7601.18637 (Win7 HomePre).
Hope this will help you improving this great project. :)

Download link: https://www.dropbox.com/s/tzfskbdz6i70jvt/termsrv.zip?dl=0

Thanks.

Sorry if this isn't the place to ask but ive been using this for a long time and now its doing my head in

Currently running
Windows 10 Technical Preview
Builld 10041

I have RD-Clip installed with the latest .ini however it just doesn't do it.
I'e tried uninstall reinstall soooo many times

I still get the other user is logged in error message.

Have attached config and error screen.

Love you work appreciate it.

Hi,

I have installed rdpwrap to Windows 10 enterprise. After upgrading ini file rdpconf said fully supported and everything is working fine.
But when I try it it won't allow more than one active rdp session.
Tried to find the log file, but there is no rdpwrap.txt on the root of the c:
Also tried to compile the latest x64 rdpwrap.dll, but the result is the same.

Any idea?

madar

can you write the using operation such as one exe

Hello,

I have a problem with Win7 (all versions) / RDPWrapper 1.5.
With kb2574819 / kb2592687 / kb2830477 (installed on the client)
if I conect me to a windows 7 pc (with or without these update) and I select in the rdp client (experience settings: LAN> 10Mbit + all boxes checked / and DisplaySettings: full screen).
When I minimize the window and restore then : I have a black screen ... I have to deconecter me and reconnect ...
If the client has not these update all works well ...

there is a solution ?

First Test :
PC1 (server) with RDPWrapper 1.5 without kb2574819 / kb2592687 / kb2830477 : Win7 x64 Ultimate
PC2 (client) without RDPWrapper with kb2574819 / kb2592687 / kb2830477 : Win7 x86 Starter

Second Test :
PC1 (server/client) with RDPWrapper 1.5 and with kb2574819 / kb2592687 / kb2830477 : Win7 x64 Ultimate
If I conect on 127.0.0.2 I have the same issue ...

Microsoft appears to be going crazy with updates to termsrv.dll lately.

KB3000850 for Win 8.1 and Server 2012 R2 is a very large (700MB+) update roll-up that updates termsrv.dll to version 6.3.9600.17415.

Because of the large number of things included in this update I'm not clear yet exactly why the file was updated, but it clearly is, so we need yet another update to RDP Wrapper to keep concurrent sessions working.

I was reading an article on Forbes:

http://www.forbes.com/sites/gordonkelly/2015/06/16/why-windows-10-upgrades-automatically-on-windows-7-and-windows-8/

which said:
In short: every Windows 10 Home upgrade is installed automatically, with no option to decline it.

Might that squash the terrific functionality of RDP Wrap?

Sadly I had to uninstall RDPWrap due to a strange intermittent "hanging on bootup" issue.
It was such a strange issue and very hard to isolate that RDPWrap was somehow causing it - but after uninstalling the wrapper, all is well now.
Basically, upon bootup & first login, a strange hanging effect was noticed in Windows 7 SP1 x64. Event viewer indicated the following errors whenever this phenomenon occurred:

• A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.
• A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CryptSvc service.
• The server {F9A874B6-F8A8-4D73-B5A8-AB610816828B} did not register with DCOM within the required timeout.

(the third error's CLSID refers to "Terminal Services Connection Manager Class")

It's not clear to me why RDPWrap was causing these issues, but since RDPWrap touches each of the 3 services mentioned above, I thought there might be a connection. After uninstalling RDPWrap I am no longer getting this behaviour.

Is there any possibility of getting this working on windows 10 home? (which is what my tablet seems to be running)

RDPconf shows the listening state as Not Listening [Not Supported] after installation, prior to install it just says Not listening

Can use rdpWrap with two user?

Now Windows 10 has hit RTM, it would be great to have a new release supporting it.

Thanks

I've been using rdpwrap on Windows 7 starter with Single Session Per User option activated, which works great. A user will have the same view of desktop/running apps whether its login directly from the console, or (later) logging in thru remote desktop. Obviously only one session for that user can be connected at the same time.

I'm trying to replicate the setup on Windows 10 home, but it doesn't work. I've replaced the ini file with the one from latest git (https://github.com/binarymaster/rdpwrap/blob/master/res/rdpwrap.ini). However, when an rdp client is connected, all connected sessions are logged out (including the console), and then closed. Even the new connected client is disconnected. If I try to connect again at this point, it works, but all running application on that user desktop is gone (obviously due to being force logged out).

Disabling Single Session Per User option allows multiple sessions from the same user (e.g. from console, and from several remote desktop connections), but each one has different sessions (e.g. different running app), which is not what I want. Trying to connect to existing session as suggested on #28 (task manager -> users -> select session -> connect) logs out the session instead (it shows "Signing Out", and then the rdp session is disconnected)

Is there a workaround or fix to achieve Single Session Per User the way it works in windows 7?

I saw #34 , but I already use latest git tip (and the symptom is different).

Any ideas?

I have try the version 1.5 but dont work, there is any solution?

replaced INI, restarted - by the way for those who could not copy the file even if it was elevated that were getting the cryptographic service lock... do it in elevated command prompt. that solved my issue.

i restarted just in case but it it says service is stopped and listener is not listening.

since i am on official upgrade via a dell purchase i can provide ANY file for analyzing if needed.

[Windows 8.1] When a user is logged in locally and is playing game at the moment [for example], if I connect to that computer through rdp with "sound stay on local computer" setting - local user loses sound completely and needs to log in again. I basically want this to work like it did on Windows 7 [It played sound from two users at the same time from same speakers].

Hi,

This is the install log :
Installer v2.2
Copyright (C) Stas'M Corp. 2014

[*] Notice to user:

• By using all or any portion of this software, you are agreeing
  to be bound by all the terms and conditions of the license agreement.
• To read the license agreement, run the installer with -l parameter.
• If you do not agree to any terms of the license agreement,
  do not use the software.
  [] Installing...
  [] Terminal Services version: 10.0.10240.16384
  [-] This version of Terminal Services is not supported.
  Send your termsrv.dll to project developer for support.
  [] Configuring TermService...
  [] Starting TermService...
  [+] TermService found (pid 1116).
  [] Shared services found: CryptSvc, Dnscache, LanmanWorkstation, NlaSvc
  [] Extracting files...
  [+] Folder created: C:\Program Files\RDP Wrapper
  [+] Extracted config -> C:\Program Files\RDP Wrapper\rdpwrap.ini
  [+] Extracted rdpw64 -> C:\Program Files\RDP Wrapper\rdpwrap.dll
  [] Configuring service library...
  [] Checking dependencies...
  [] Checking CertPropSvc...
  [] Checking SessionEnv...
  [] Terminating service...
  [] Starting CryptSvc...
  [] Starting Dnscache...
  [-] StartService error (code 1056).
  [] Starting LanmanWorkstation...
  [] Starting NlaSvc...
  [-] StartService error (code 1056).
  [] Starting TermService...
  [] Configuring registry...
  [] Configuring firewall...
  Ok.

[+] Successfully installed.

It's a clean install of Windows 10 Home French version. (How can I send you this file ?)

Thx

Unfortunately, after installing RDP Wrapper, when I log in via Remote Desktop the explorer.exe process stays at a constant CPU usage between 30-60% (making the overall CPU usage between 80-100%). Without RDP Wrapper the explorer.exe process hovers around 0%.

Any suggestions?

EDIT

Apparently during the process of installing RDP Wrapper the icon cache for one of the desktop icons became corrupted (it was showing nothing). Using ProcessMonitor I was able to identify that the explorer.exe process was continuously trying to display this icon and thus was consuming a lot of CPU time. Rebuilding the icon cache per the instructions below resolved the issue:
http://www.sevenforums.com/tutorials/49819-icon-cache-rebuild.html

As long as RDP Wrapper wasn't the cause of the icon cache problem then I think everything is now OK.

I follow the installation instruction:

• download the latest released RDP WRAPPER, version 1.5
• run the install.bat
• run the RDPCheck.exe -- failed
• run the RDPConf

I see that Windows 10 home edition has already been supported, where am I wrong?
Should I download the source codes and compile myself?

Hi, I upgraded my system to Win10 Build9926(x64) and found this is not working. Then I copied the content of rdpwrap.ini from the latest code to local, restarted system and then the entire remote desktop service refused to start.

RDPConf.exe prompt:
Wrapper state: Installed ver. 1.5.0.0
Service state: Stopped ver. 10.0.9926.0
Listener state: Not listening [fully supported]

Is the Win10TP3 version still in developing?

The RDPWinst file is not a windows executable file and I don't have the expertise to make it one. Can you help?