GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together. Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub?
Sign in to your account. I just tested the latest version zip file with a fresh install of Windows 10 Pro x64 v build I just spent a couple of hours finding this, you need this code below. I also zipped up and attached the ini file. This latest file you attached worked for me too, I'm up and running with rdpwrap on Win10 Home version as of today July 23, Hmm that usually means the INI file is no good.
Let me grab another copy that I know that is working on a machine with the same version. Or if you reinstall basically you have to make sure you put the INI file back. Try the attached INI file again. Also one more thing, if you uninstall the Remote Desktop Services should start fine, so you could verify that. It also seems like the installer is not working. Another question, where does the ini file attached above go to patch the install?
Restart termservice. Use it. No need to restart the computer. Latest ini file worked for me too. Win10Pro Rebooting helped. I am on Build Any suggestions?Using RDP on Windows 10 Home 1909 Easly / RDP no Windows 10 Home 1909 Fácil (RDP Wrapper) 8.1/8/7
So for everyone who's running Service For me, it is working, see my post here: comment. My is not working after doing everything any suggestions?????????? Any new additions to the INI file? Do not run update. You saved my day.
How To Enable Remote Desktop In Windows 10 Home (RDP)
Thanks a lot. Dear shoeless22. Thank you for taking time to make that kind of helpful modification. Until now, I couldn't get a satisfying result and I'm starting to think that I may not be able to achieve the intended result. To explain briefly, Pagina 6900 trying to connect to my computer session from my Android smartphone using Microsoft Remote Desktop app.
So far, I've managed to make it work as it's supposed to so it logs off my computer when connecting to the session then I found out about RDP Wrap.GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Thank you j1nseng for Thank you for updating. It works with But single session per user doesn't work anymore. Testing More specifically, for console user1 and non-console user2, it is single session from user1 loopback to user2 on same workstation1, or from 2nd workstation2 logging on to user2, but from workstation2 logging on to user1 when user1 is already logged on to workstation1 at console will spawn a second session.
In other words, the console user can't be accessed remotely. StasCorp has done tremendous work on this. Be a shame for it to die. Would it be possible for another person be made an Admin for accepting pull requests and getting upto date releases?
The latest ini file worked great and RDPWrap has been a mainstay of my home 'support' life, but for new folk trying RDPWrap it just wont work as they wont know what to do and they end up putting out 'it doesnt work' reviews etc Or someone or a group can create a fork and manage it from a new git hub repository. I'm sure it is a lot of work for StasCorp, a labor of love.
Unfortunately he has clearly not kept up with the many Windows updates, which have increasingly broken RDPWrap by updating the termserv. It is very sad for those of us who have come to depend on RDPWrap.
But getting back to single session per userattached below is the ini file that solves that issue for We have a robust community here. I think it works fine. I don't see a need for a new admin or fork. Thanks gitgotgone for the edit. I think the community is terrific, and I admittedly get way more out of it than I put in. A newbie would be very frustrated at the lack of direction. At the very least the main readme file should admit that the download is likely not going to work out of the box, but that a little investment of time searching the boards will be worth it.
Hi, can you specify the difference so I could add to my file. It's very difficult to follow all issues, so I try to collect all in one place :.
I apologize, I wasn't very organized in my trial and error and I lost track of the different versions and changes. As best as I can recall I tried versions from the thread and may have made the edit to SingleUserOffset. The whole process is very disorganized, I agree, and I really didn't help that--sorry! The best I can suggest is to use a file compare tool. Good luck I can confirm, the settings from iofgdh post are working with SingleUser mode on One request though: Please do not post the complete file contents as a comment.
It makes the thread rather unreadable.Keep in touch and stay productive with Teams and Officeeven when you're working remotely. Learn how to collaborate with Office Tech support scams are an industry-wide issue where scammers trick you into paying for unnecessary technical support services. You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service number.
RDP works perfectly fine on the initial connection, but if the RDP session is disconnected, trying to reconnect shows either a black screen, a white screen, or a frozen "logging on" screen. The target VM becomes completely unresponsive. I have to forcibly power down the VM and start it up again. The graphics driver solutions for the black screen issue do not apply here because it's a VM, not a physical PC. Did this solve your problem? Yes No. Sorry this didn't help. Virtual Box VMs have a similar problem - they must be forcibly powered down if you disconnect an RDP session then try to reconnect it.
The freeze seems to occur at about the time when the RDP Host would be displaying the lock screen on the console. It is almost as if the problem is that the lock screen is already shown and it is trying to show it again just a guess. We have had the same issue but have found that Remote Desktop app in the store seems to be able to reconnect, its shows a screen briefly around "Unlocking PC" or something along those lines before logging back into the VM. The default windows RDP client version We have VMWare VM's that froze after a dirty disconnect but this app from the store seems to work for us.
Let me know if it works for you and maybe Microsoft can look into this for us. Thanks for the suggestion, but for me, the Remote Desktop app is not a solution.
Windows 10 1903, RDP broken if disconnect and attempt to reconnect
I am using it with the same. Possibly there is some setting in there that does not work with the app, I did not pursue it. I have the exact same problem, once someone connects they cannot properly disconnect. They run very slow and issues with performance. Set update to allow me to say yes so the next time and Upgrade occurs I get to test it first and get checkpoints to back out. Now how do I get this registered as a bug and get notification I have a patch that I can test out?
Yesterday I stumbled across a post that turned out to be the solution. April 14, Keep in touch and stay productive with Teams and Officeeven when you're working remotely. Site Feedback. Tell us about your experience with our site. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Andre for Directly Replied on September 18, Independent Advisor.
I'm here to help you with your problem.There is no Remote Desktop in Windows 10 Home. Since it was for home usage, Microsoft removed some features from Windows 10 home like group policy editor gpedit. These features are only available in the Pro and Enterprise editions. Technology firms tend to reserve a few features for their premium offerings.
Microsoft Windows 10 is no exception. Windows 10 Pro has more features than Windows 10 Home has but the former is also a costlier choice. The Home version has enough features for everyday users.
Upgrading to Windows 10 Pro just to use a specific functionality is not wise and when there are so many remote desktop apps available on Windows Store. Nevertheless, nobody can rule out the sophistication of a native Windows tool. Microsoft disabled the tool on Windows 10 Home but did not remove it entirely.
With a workaround, you can still enable the premium feature reserved for Windows Pro users without buying an expensive license of Windows 10 Pro. Trust me! All you need to do is to download a file and install it on your Windows 10 Home PC. The following steps will allow remote access to your Windows 10 Home computer remotely though the network. It should look similar to the screenshot below. There are a few things to note before you invite someone to remotely connect with your PC:.
You should avoid it in commercial settings. Only give remote access of your PC to people whom you trust or those bounded by a contractual or legal obligation. You can use the same username and password which you use to login to your system to log in through RDP. Windows Remote Desktop Alternatives While these steps are reasonable for most computer users, many people are not comfortable with the idea of patching their OS to add or remove features. At iTechtics, we suggest going for an inbuilt tool whenever possible over a third-party alternative.
Nevertheless, there are tens of remote desktop applications available for Windows You can use that application to establish remote connections to and from your PC without any workarounds. These applications also offer mobile and tablet apps.
I will start with my personal favorite and the most popular one—TeamViewer. Third-party apps also reduce the risks involved in enabling RDP port over the network. The native RDP app from Microsoft is vulnerable to all sorts of security threats especially when you allow access to your computer over the Internet.
TeamViewer is one of the most versatile remote desktop applications available for Windows and all major mobile and desktop platforms. The best part is the application is free for personal and non-commercial use and allows instant remote connection between two computers provided both the computers have the application installed and configured to connect. It does not need any default port to connect to the computer remotely. A potential competitor to TeamViewer, Anydesk is also free for personal usage is compatible with every device you can think of and it includes your Raspberry Pi in addition to usual mobile and desktop platforms.
For those who live and breathe in their Chrome browser or use a Chromebook, there is not a better option than Chrome Remote Desktop. The idea of using a pro feature on the Home version of Windows 10 without paying for an upgrade, while a fascinating idea, is a workaround at the end of the day.Before modifying termsrv. You can do this yourself by replacing strings shown below, or just download patched versions from this page.
To get back concurrent remote desktop connections, make the following changes:. The patched version can be download from here. The original, v To get back concurrent remote desktop connections, the make the following changes:. Original, v Find: 39 81 3C 06 00 00 0F 84 3F 42 02 The patched version can be downloaded from here. This way you don't need to touch termsrv. If all items under Diagnostics are green, you should be good to go.
Simply run update. 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.
Please help - thanks! I believe you need to upgrade to Pro. I'll be quickly corrected if I'm incorrect Gecata Here is patched dll for 32 bit Win10 Enterprise. Tested today with 7 users all day connected. Seems to work fine! Please someone to reupload because of download limits on free file sharing servers!
Nazar Hi, I've searched the net but could not find similar issues to mine. I have this weird issue where port is not listening by checking "netstat -na findstr ". The port is by default set to in the registry. The service is running normally by checking both services and "sc query termservice". There's nothing about RDP errors in the event logs. Though not related, I've also added RDP to the firewall just in case. All troubleshooting was done with either RDP service restart or reboot.
I've also tried using RDP Wrapper, the status is all green except "Listener state: Not listening" in red it does shows [fully supported].But there is a restriction on the number of simultaneous RDP sessions — only one remote user can work at a time.
If you try to open a second RDP session, a warning appears asking you to disconnect the first user session. Actually, the number of simultaneous RDP connections is limited rather by the license then by any technical aspect.
How to Allow Multiple RDP Sessions in Windows 10?
From a technical point of view, any Windows version with a sufficient amount of RAM can support simultaneous operation of several dozens of remote users. On average, MB of memory is required for one user session, without taking into account the launched apps. Those, the maximum number of simultaneous RDP sessions in theory is limited only by computer resources.
As a result, you have to edit this file using Hex editor each time, which is quite tedious. System modifications described in the article are considered as a violation of Microsoft License Agreement with all the consequences that come with it and you may perform them at your own risk.
RDP Wrapper does not make any changes to the termsrv. Thus, the RDPWrap will work even in case of termsrv. It allows not to be afraid of Windows updates. Based on the information on the developer page, all versions of Windows are supported. Windows 10 is supported up to the build althougheverything also works fine in Windowssee the solution below.
To install the RDPWrap, run the install. During the installation process, the utility accessing the GitHub site for the latest version of the ini file. To undo this, remove the -o flag in the install. When the installation is over, run the RDPConfig. Make sure that all elements on the Diagnostics section are green. Run the RDPCheck. It worked out well!
Now your Windows 10 allows two and more users to use different RDP sessions simultaneously. Thus, you can build your own terminal RDS server on any desktop instance of Windows.
Also interesting features of the RDP Wrapper are:. In my case, since there is no direct Internet access on the computer, the RDPWrap could not get the new version of the rdpwrap.
Therefore, the RDConfig utility showed the status [not supported].
Download the rdpwrap. Restart the TermService and make sure that the state [not supported] is changed to [fully supported]. Try to download the new rdpwrap.GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Note: RDP Wrapper needs the original termsrv. I see some x86 version are missing, e. Any Idea to get that version included?
I managed to replace the original with this version. And patch it with the. After that RDP service cannot start. Hi Guys. I make RDP working normally on W10 Pro version by instructions above from user ljf, printers are redirecting normally, but not using Easy Desktop print driver first but original driver which is installed on my computer Easy Desktop print driver is needed for some HP printers that don't support remote print through HP drivers.
If anyone solve this with printers pls write here. Every few days I have the same problem. My system gets updated, file version doesn't change, everything is green in the window, but RDP can't connect.
Every time I manage to find some new ini here and it works again but this time it just won't. I tried to use both updaters above. What else can I do? Please support for x86 version on I've run "re-install.