How to Update rdpwrap.ini (RDP Wrapper)

Dennis Faas's picture

Infopackets Reader Tony G. writes:

" Dear Dennis,

Thanks for your previous article regarding RDP Wrapper, which allows me to connect to my media PC using more than one RDP (remote desktop protocol) session. This is incredibly convenient because the kids can be watching a movie on the media PC, I can still login to it through remote desktop without interrupting anything. The issue I'm having today is that Windows 10 recently updated to 10.0.17763.316, and now RDP Wrapper is broken. I have gone to the RDP Wrapper website and found other users complaining of the same problem. Many forum posts suggest I need to update the rdpwrap.ini file to make it work again. The problem is that I can't update the rdpwrap.ini file because I get 'access denied' or 'you do not have permission to open this file' when trying to save it using notepad. In other words, the file is in use. If I copy over top of the rdpwrap.ini (with another rdpwrap.ini file), I get the same issue - file is in use. The forum community doesn't seem to explain how to update RDP Wrapper step by step. Also, if I uninstall RDP Wrapper it reinstalls the default rdpwrap.ini file. I am going in circles and I have no idea how to update rdpwrap.ini. Can you help? "

My response:

Thanks for your question. First let's talk about what RDP Wrapper is and does, and why it needs updating - and better yet, why it's not always easy to update this fine program.

Note: I have linked to the byte offsets working on Windows 10 17763.775 [version 1809] as of October 11, 2019 further down. You can read my post in its entirety, or skip to that section now if you know how to update RDP Wrapper already.

What is RDP Wrapper?

RDP Wrapper is an amazing utility that 'wraps' over top of the Remote Desktop Protocol (RDP) found in MS Windows without actually patching any DLLs (termsrv.dll). It allows users to have more than 1 concurrent RDP session as commonly used with Windows Servers.

If you are a power user that uses RDP to control a network of computers, RDP Wrapper is a godsend.

Example of How RDP Wrapper Works: Media PC

Let's look at an example.

Let's say you have a super powerful 'server' machine (8 core, 16 thread, 32GB ram, etc) that not only serves files to your network of computers, but is also powerful enough to run virtual machines, and the like. You rely on this machine to do all your heavy lifting, which means that you probably connect to it quite often using RDP.

Now, let's say your server is also a media PC. It's attached to your main television, which is used to stream media via Kodi / view Netflix / play youtube videos, etc for the family. Normally, you can only connect to the server using RDP if no other users are active. In other words: if someone is streaming media on the server (as a media PC), you normally can't RDP into it, otherwise the other user that is streaming content would be kicked off.

That's where RDP Wrapper comes in. With RDP Wrapper, you can still stream media, and at the same time, allow incoming RDP connections to the server to do whatever it is you want to do - using a separate desktop. Think of it as having as many desktops as you need on one machine, in as many instances as you want (defined either by the number of users on the system, or how RDP Wrapper is configured to allow infinite connections from the same user).

RDP Wrapper: Sometimes Breaks after Windows Update

Unfortunately, RDP Wrapper does not appear to be updated by the developer as of last year.

That said, there is a big community of users using RDP Wrapper. A small handful of them have developed their own fixes (also known as "byte offsets") to get around various Windows Update issues that break RDP Wrapper.

The reason it breaks has to do with programming code updates to the dynamic link library (termsrv.dll) of the remote desktop protocol itself, courtesy of Microsoft. Unfortunately, finding the right fix (rdpwrap.ini byte offset) to make RDP Wrapper work again is not always easy to do because you often have to wait for a fix to be developed by the community, then wade through forum posts in search of said fix.

One place to look is the git repository provided by fre4kyC0de, as he seems to post update fixes to the rdpwrap.ini file as soon as they are available, though there are other community members that do the same.

How to Update rdpwrap.ini (RDP Wrapper)

In order to update the rdpwrap.ini file, you first need to stop the RDP service, otherwise you will get an 'access denied' error or similar.

To do so:

  1. Click Start, then type in "cmd" (no quotes); wait for CMD.EXE or Command Prompt to appear in the list, then right click and "Run as administrator".
     
  2. A black command prompt window should now appear. Type in the following into the command prompt and press Enter to execute the command:

    net stop termservice
     
  3. Next, make sure you have the latest RDP Wrapper installed. At the time of this writing, version 1.6.2 is the latest release. Also worth mentioning: do not patch your termsrv.dll or the RDP Wrapper simply won't work, even if you update the rdpwrap.ini file. I'm mentioning this because some RDP Wrapper forum users provide third party patches to the termsrv.dll; however, using this in conjunction with the new offsets will break RDP Wrapper.
     
  4. Next, patch your configuration file located at C:\Program Files\RDP Wrapper\rdpwrap.ini.

    There are two ways to update rdpwrap.ini: either (a) replace the entire rdpwrap.ini or, (b) patch / update your existing rdpwrap.ini.

    Option (a): to replace the entire rdpwrap.ini, you will need to find one provided by the community. As of April 15, 2019, this version of the rdpwrap.ini should work for Windows 10 Pro users up to Windows 10 17763.475 (at the time of this writing). In this case, download the .ZIP, extract it, then copy and paste the rdpwrap.ini over top of the one located in C:\Program Files\RDP Wrapper\rdpwrap.ini.

    Option (b): to update / patch your existing rdpwrap.ini yourself (without trying to obtain an entire rdpwrap.ini file from the community), search Google for "Windows 10 <your version number> rdpwrap.ini". Example: "Windows 10 17763.775 rdpwrap.ini" or similar would be a sufficient query, which should hopefully net you some search engine results with the proper byte offsets. Note you can find out which version of Windows you're running by clicking Start, then type in "winver".

    Once you find the proper byte offset for your version of Windows (or close to the version you're running), you will need to append the byte offset code to the end of your rdpwrap.ini file, which is located at C:\Program Files\RDP Wrapper\rdpwrap.ini.

    As of October 11, 2019 download and append this byte offset to your rdpwrap.ini by scerazy (tested and working on Windows 10 17763.775). Note that this is for Windows 1809, not 1903, where these byte offsets may not work - I have not tested. Feel free to test on your own!
     
  5. Next, restart the term service (remote desktop protocol) using the command line:

    net start termservice
     
  6. Now, test that your RDP Wrapper service is configured properly. To do so: download the latest RDP Wrapper release in .ZIP format; extract the .ZIP, then run RDPConf.exe. At the time of this writing, RDP Wrapper version 1.6.2 (zip) is the latest version.

    When you run RDPConf.exe, the "Wrapper state" should be "Installed", the "Service state" should be "Running", the "Listener state" should be "Listening" and directly to the right of that it should say [fully supported]. All of these values should be in green. If you see anything in red, then something is not working properly. You can also then test to see if RDP Wrapper is working by running the "RDPCheck.exe" program which will attempt use Remote Desktop Protocol (RDP) to connect to the same system @ 127.0.0.2. If you see a login screen then it is working.

I hope that helps. If you are still stuck, you can contact me for remote desktop support and I can look into this for you.

Did you find this Page Useful?

If you found this page useful, I ask that you kindly link to it in a forum post, perhaps on the rdpwrapper site / forum, so that others can find it in Google. Thanks!

RDP Wrapper Support for Windows 10 17763.771+

I kindly ask that you please do not email me asking for offsets. When RDP wrapper breaks on my Windows 10 "server" machine, I will update this page. I am currently running Windows 10 1809 on my "server" machine, so my RDP wrapper configuration may be different than yours especially if you're running Windows 10 1903. If you need help configuring or updating RDP Wrapper, I am available for hire where I can remotely connect to your machine and update it for you. Contact me here.

Additional 1-on-1 Support From Dennis

If all of this is over your head, or if you can't get RDP Wrapper working, I can help using my remote desktop support service. Simply contact me, briefly describing the issue and I will get back to you as soon as possible.

Got a Computer Question or Problem? Ask Dennis!

I need more questions. If you have a computer question - or even a computer problem that needs fixing - please email me with your question so that I can write more articles like this one. I can't promise I'll respond to all the messages I receive (depending on the volume), but I'll do my best.

About the author: Dennis Faas is the owner and operator of Infopackets.com. With over 30 years of computing experience, Dennis' areas of expertise are a broad range and include PC hardware, Microsoft Windows, Linux, network administration, and virtualization. Dennis holds a Bachelors degree in Computer Science (1999) and has authored 6 books on the topics of MS Windows and PC Security. If you like the advice you received on this page, please up-vote / Like this page and share it with friends. For technical support inquiries, Dennis can be reached via Live chat online this site using the Zopim Chat service (currently located at the bottom left of the screen); optionally, you can contact Dennis through the website contact form.

Rate this article: 
Average: 4.5 (8 votes)