Remote desktop for home premium hack

I tried everything, but this time I can not figure out, what is the matter. RDP Service is working and it accepts connections. However, every time when I try to remotely connect this computer, the RDP client is able to establish the connection.

However, it will disconnect immediately without any warning, or message etc. I can see quick flash of my desktop. When I logon this computer localy, I can see from taskmanager, that there is no other users logged on. So the logon fails. What can be the issue? I tried t0 use them all. I tried to restore the original. However, the result is the same, Is there any place to download prepatched termsrv. The latest update to the tool will work with the Windows update mentioned, as you can see from others commenting it works on the latest dll as intended.

If the checksum fails you have the wrong or an incompatible dll. The tool will now not recognize the original RTM dll because I replaced that patch with this one by now nobody should be using it. Which version and architecture of Windows are you using? Is it an original install media or some custom install?

Thank you for answer. I found this. If in default setting, GPO allows me to connect max 5 users, why i have this problem with 2 connected users? Hi HAL Any news on an update. Ok, I have updated the tool for the latest termsrv. Please try this version of the patcher and report back as I have been unable to test it properly.

Use this tool at your own risk…. I have a 5 session to one PC with Windwos 7 Pro. Used an earlier rdp patcer and everything works fin. After this year updates in widows 7 i musz use a new rdp patcher. Multiple session is back, but on PC, whith i have connectet, at least, 5 session via rdp, i see tle last logget user desktop.

For examle: 3 users : Admin, X1, X2. Admin is localy logged on PC , and i see an Admin desktop. You may have to re-start your pc. Dear Hal! Please fix the patch we did not have unfortuna telly restore points and can not revert the changes. Now we are sitting duck and can not work. Please let us know it you are fixed it. Thank you sir. Ran into the same problem and backing out kb worked for me.

Hoping someone will come up with a revised patch for this so further updates can be allowed. Because there is an updated termsrv. I second, package kb was causing the issue on my Windows 7 x64, once rolled back the dll revert to the patched version. We just got the latest windows update that happened yesterday and the Concurrent RDP patcher is now working now.

An update around Sept broke this again sadly, been an avid user. Yes, confirm. I have 60 computers running Win7 in my facility and rely on concurrent sessions heavily. I have had to disable these three updates on all.

I hope this helps: kb kb kb — rolled this one back yesterday. Last time this happened in I was lucky enough to find out online what bytes needed to be patched, so could update the program. Thanks, may I ask where you got that information from?

There appears to be only about 2 bytes difference from the old dll and I need to check this out before trying to update the patcher…. Could log in with two users remotely and one user locally being member of the Remote Desktop Users group. Kaspersky endpoint security seems to block this. Any idea how to allow in the rules of the firewall for concurrent connections?

It works fine without Kaspersky enabled. It worked for me for years, using xfreerdp package freerdp from Linux to Windows Home. But since yesterday when I ran Windows Update for the first time in 3 months, I get these errors:. Hi yesterday I have done fresh installation Windows 7 home premium SP1 and fully updated and the patch not is working for me.

I tried patch-unpatch a lot of times but remote desktop open and looks is goingo to work but close ver fast without errors. Latest version works great on updated Windows 7 Professional! Make sure you are using the version on the very bottom of the post!

Not working on latest updated version of Home Premium x64 — termsrv. In the freaking middle of the night. Still 2hours to make this freaking server with 25 employees work. Stressed out. The entire company would be on production hold. What could I do??! Found this site……. Man If I ever knew who had this solution patch?

I would personally send them a beer!! Worked perfectly first time. I am running Windows 7 Home Premium. Home Premium is not capable of RDP out of the box — that is why it is not working.

That will finish it up for you. Pls it would be so helpfull. Downloaded this today and can confirm that it is still working on windows 7 professional. Double click to run and enabled multiple logins per user, clicked patch and it kicked me off while it replaced the file.

Waited 2 minutes then hopped back in and tested multiple concurrent sessions. As BrankoH said, any chance the desktops can mirror one another? I can connect and fully remote in from my android tablet but only to the main user. I have a total of three users and when i try to remote into to ano other users it just keeps re-asking me for the password as if I had typed in the wrong passwords.

I tried to make two users to be administrators with passwords and it still only allows remoting to the first user that was originally the administrator. It works super good but only for one user in the desktop. Awesome solution….. Says that Windows 7 Enterprise is not supported. The patcher program is showing everything grayed out. I ran it on a different Windows 7 Professional machine and it worked fine. Will this work on Windows 7 Pro and Windows 10 Pro versions? What would happen if Microsoft decides to patch the file again.

Will it cause system instability? Should we backup the original termsrv file first before installing? Where is the file located? If Microsoft patches termsrv.

If that happens we would need to update the tool again to patch the newer dll. If it does happen, is there place where we can download the newer patcher or do we just go back to this site? I cannot see remote desktop options in system preferences. Hello there, thanks for the article, but i have a question, does this patch enables multimonitor on host? I ask that because my host has win7 pro, and by default that OS version does not support multimonitor.

I still do not see Remote Desktop options, only Remote Assistance. What gives? I installed the patch on both my computer and the one I want to remote into. Both are running Win 7 Home Premium. When I attempt to connect, it pops up the user and password input. I know it is the correct username and password. Any thoughts? You need to make sure the local user account for the machine you want to connect to is a member of the remote users group.

Click on Users, then find your account. The login name should be the first thing listed on the left. Then, go back, go to groups, and go to Remote Users group. Add your login account there if it is not already present. Unfortunately, that snap-in is not allowed on a computer running home premium.

Any other thoughts? After trying literally everything, I found a solution. There was a discrepancy between the login name and the account name on the profile in Win7HP. Normally, the login name is used for everything. Once corrected, I logged in without any issue.

Hope this helps! A recent Windows update seems to have broken rdp. April 12, Anyone else have this problem and knows which one? Found the problem. KB got installed again somehow. When I run RDP it still says unknown checksum with all the options greyed out.

Thanks very much. Reinstalled and ran the patch — worked just fine. Thanks again for your help! One more thing you need to do if you use Windows Firewall on your windows 7 home edition machine. You need to create a new inbound rule to allow port I want to remote desktop over the internet but it wont work.

I checked to see if the port was open at canyouseeme. I have a quick question. For example if I login with user X and worked on a word document.

Can u close the RDP session without logging out and then log back into the same session so I can continue my work? Also on the desktop where I installed the patch, if I have my main user logged in with multiple programs running with my current work opened.

Right now when I log in with the same user, it creates a new session and hence does not take me to the current working window. No messages. Nothing in event logs either. Tried the patched version with Windows 7 Starter that has KB installed.

Any ideas? The patcher does not work with the Starter Edition because it has some networking and RDP restrictions. Hi, it is possible to run this patcher with parameters?

I just found a great RDP patch that works with any version of windows. Remote desktop does not show on controlled computer [win 7 home prem ] but allows login using mstsc. Are we talking about the same thing? Perhaps you are unaware, but the entire reason that the Concurrent patch exists is to enable RDP hosting in a Home edition of Windows.

My computer is telling me that I will get the free upgrade to Windows However, this will be Windows 10 Home, which is not likely to include Remote Desktop. Does anyone know a way of making this work? I turned off the firewall already, and uninstall antivirus too.. Thanks for taking your time to update this tool. After installing your updated version on my RDP host, I can get to the screen where I enter the user name and password from my RDP client but nothing happens after that.

It would help tremendously to get this to work so I can do part of my work at home. If the patching process just involves changing some of the codes in Termsvc can you please show which codes I need to replace? Unfortunately we are unable to test the patcher or make edits for any language version other than English.

After windows update, And also, I repatched it with KB As colin said, I also have same symptom, it accept username and password, but then it never show any messages, no response… just as like blocked by something. Could you please let me know what is problem? Thank you in advance. Here the same issue.

You can add the username and password, but nothings happening. Keep up the good work!! Thank you for keeping this up to date. Some of the other versions of this have since stopped working, but after pulling the troublesome updates, your updated version does the job.

I am having a problem with changing the ports, though. Thanks again for keeping this up! Quick Heal is obviously talking rubbish, i. The result at Virustotal for the last released test version: virustotal. Tested with windows 7 family premium and both version of the patch. The original version worked perfectly… Now it accepts the username, asks for password, but the remote desktop never loads. It just terminates with no message. Worked like a charm. BTW: I did it remotely. Via RDP, of course.

No problems. CRP was waiting on the screen, so encouraged, I tried to unpatch. Actually the patcher could accept blindly all N variants: windows.

How can I increase that? Resolution: x Both are greyed out and not changeable. Does anyone know how I can increase that resolution? I was excluded by the patch using a windows 7 enterprise and found a more universal solution github. Great new version. Your modified patch worked.

It now says patched. Only help seems to be to uninstall KB update. Is it possible the patch only works on cracked Win7 and fails on genuine ones? Thanks for any ideas. Tried installing and was able to click patch. I just opened the extracted files from my downloads folder.

I downloaded your test file. When i Run it as administrator. It says termsrv. The original source code is available online, you can get it here: mediafire.

Update: Despite the error message about the process being in use by another user, the patch seems to have worked. When I run the patcher, it verifies the termsrv. When I tell it to Patch, it gives me an error that the file is being used by another process. The think is I ran all your patches I found on your page. Thank you very much! If you have tried the test file files. The patcher needs a completely unmodified dll to work.

Uninstall patch from Windows update. The RDP tool will definitely recognise a non modified termsrv. What is the maximum number of concurrent connections? Has anyone tried 8 or more concurrent connections? Hi, First of all thank you for your effort! The problem is ,in spite of patching correctly the library, remote desktop option does not appears on the menu.

Im new to this still learning. I did the patch it works but I cant log in can u help give me step by step on how to be able to access my computer. I had downloaded the pacth in november and Remote Desktop connections were working fine. This year they are not working, and I tried the above link.

There are two versions of our modified patcher, the version in the post for the latest patch and the version you link to is for the previous patch. You need to check which patches you have installed to work out which program you need to run.

It does not get borken by the Windows updates. It depends which recent patch you have installed from Microsoft. Hi, same problem.

It has been working until November Which version of Windows are you using? Any idea what can help? Many thanks in advance. Running well on W7 Home Premium x64 with all of Winblows latest updates for about a week now. I have a partner who has a Home Premium in her pc and some days the remote desktop did not work … the last update could help, remote desktop is working fine again, thank you very much!

Not sure which update it was, but I got it working again with the patches below. Maybe you can include them in the next version? Original termsrv. Yes, the same for me. But since last MS-update not working again. I removed the installation of update KB on one machine, and on the other I excluded it form the update process see the update details and uncheck the box and in both cases, worked perfectly afterwards. Worked great for years. Anyone know what to do to fix it? Yes in deed. Your update worked for a few weeks perfectly on 2 W7 Home systems.

But now again destroyed. Hopefully you can again fix the problem, good luck and MANY thanks!!! After the update uninstall update KB Personally I am not to concerned about security implications as my machines are on a secure internal network. One will need to hide the update in the Windows Update app otherwise it will be reinstalled. Obviously a proper solution would be an update to the wonderful Concurrent RDP Patcher tool … Thank you too Raymondcc for providing the tool.

Try it at your own risk…. This new patcher does not work for me on Windows 7 Enterprise SP1 x It appears Enterprise in unsupported. Is there an update to the RDP Patcher to resolve this? This has been reliable for several years but just stopped working on a windows home premium machine.

Anyone else having the same issue perhaps the last windows update? The connection neither connects nor errors out, appears to connect then nothing.. I have not had a chance to install it and test it. Here is a thread about it: forums. The latest updates for Windows 7 seem to have replaced termsrv. Can someone update the patcher as well? Looks like it might be this one: KB released on … support2.

Joined Jun 10, Messages Well, all windows OS have remote desktop built in. If on the other hand, you are looking for a VNC solution. Most are detected by AV scanners as malware due to thier nature and some are insecure.

Be careful with VNC products. Because the Remote Desktop on the other Computer is not enabled. If they are behind a router or firewall though, this will complicate matters, in which case, VNC or even better LogMeIN are better alternatives.

Both the desktop and the laptop are behind a wireless router and trend micro firewall. Im still looking at logmein. What do you think about this? Here are the directions?

Download termsrv. Extract Termsrv. Run the corresponding batch file for your Vista edition 5. Done Thanks. Joined Oct 1, Messages 5, To clear up any confusion there may be, Home Premium does have Remote Desktop that you can use to remote OUT with to any Windows version that supports it, no problem, the stickler is when you try to remote INTO a home premium system; then its a no go, unless you use the hack you found apparently.

To extract just make a temp folder of your own, put the zip file in it and right click extract You should be able to just click ok, ok, ok and the files will be extracted to the same folder. Then start a command window and run the corresponding batch file that matches your system and hope it works.

Personally, I am always a little worried about things like this. Espeicailly so call patched dll's, and when it comes to the terminal services dll. And if MS Updates ever decided to patch the termsrv. Personally, I'ld go with logmein, it does work, can be flakey, but it does work. For further info,,, here is the link to what and how the termsrv. Can you tell me how to do that? Apparently this is probably due to the fact Microsoft now owns GitHub, so updates to the. I have to make it work by using the method in this article.

Since this has recently become very topical please correct a large mistake in your article. Probably most people looking at RDP for the first time now are Win10Home users trying to connect to their work Win10Pro machines which should work just fine. If you scroll up a few comments to the one I left on , there are some instructions on how to do this while we await it getting updated.

Here are 2 posts where you can update the INI file after installation:. After that it worked for me for Windows 10 Home Good luck! And thanks to all who helped me get it running. If you are running a very recent version of Windows 10, you may need to update a settings file manually. This solved it for me. I successfully installed the RDP Wrapper. When I run the rdpconf. However when I run the rdpcheck. Any ideas? Same thing happens with KMSPico for example, which is a way to run unlicensed Windows copies as if they were legitimate.

Any idea? Windows 10 Advanced Configurations. Itechtics Staff Itechtics staff is a team of technology experts led by Usman Khurshid. We verify everything we write so that our users can be sure to trust us in everything we write. You can reach out to us for further help and support. Share on: Subscribe. I have my remote connectivity back!

Win10 Home Any update on this? Having the same issue. Windows 10 — Listener state: Not listening not supported …. This is not working as of