Remote desktop connection windows 7 home premium 64 bit free
Looking for:
Concurrent RDP Patcher Enables Remote Desktop in Windows 7 Home Premium • .Accept Remote Desktop Connections in Windows 7 Home Premium - Super User |
Remote desktop connection windows 7 home premium 64 bit free.Concurrent RDP Patcher Enables Remote Desktop in Windows 7 Home Premium
- Update for RDP is available for Windows 7 SP1
Remote desktop connection windows 7 home premium 64 bit free -
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. It certainly is the cause of the failure of the terminal server patch, but I would like a longer term solution.
I have this problem that the remote will not start a program when connected. I must be doing something wrong can you help please. I want you to know I know the truth, of course I know it. I would be nothing without you. You can not pass the clipboard contents between computers; 2. You can not work remotely as an ordinary user. You have to be an administrator.
There is no interface to assign Remote Desktop access rights to users, and administrators have this access by default. There always seems to be some problem with some software when you go this route. I can not thank you enough for the folks that made this tool. RDP may not be the end all of how to remote in, but it is the best way to do it sometimes.
Thanks to this software, I can put on movies for my kid, or Music for him to go to bed to all from the comfort of my chair. This just made windows 7 just that much better. Well, at least not without tons of help. I have ran the patcher in the host computer, then, it installed successfully. May I know how to disable the feature of asking credential from the client computer in order to connect the host computer?
Downloaded and ran patch. Checked box for multiple logons and blank passwords. Ran patch. I am currently running W7 SP1. Hi I am using this patch on my win7 premium machine which is running my mailserver.
I am running MDaemon. If I go to the machine it all looks normal no sign of a crash. The mailserver is still running etc. The temporary solution is to start a configuration session for MDaemon — that unlocks everything. Much appreciated in advance. Wifi networks that are behind a router that is connected to the internet have their own network. This is what is know as a lan. Addresses which start with Malware Bytes just picked this up as a trojan.
Is this a false positive or have I exposed my machine.. I got this to work well with multi user. How can I enable this and shre the same screen.. This is good only in static ip address not in dhcp like in my country almost ISP here provides dhcp services and it was very difficult to open their ports to access other computers over internet… so I used teamviewer for remote desktop support… this is awesome software i like it very much….
If you utilise a Dynamic DNS agent, like noip. I have been using the concurrent patch for some time now in my HTPC. That way people can be watching a movie while I can do my own stuff remotely.
Really Windows 7 should allow multiple sessions by default. Tony 4 weeks ago. MeowMeow 9 months ago. HAL Author 9 months ago.
Olivier 1 year ago. Neil Brock 2 years ago. HAL Author 2 years ago. Rafael 2 years ago. A Nonny Mouse 2 years ago. Clem 2 years ago. Jose Macedo 2 years ago. Steve 2 years ago. Carlos 2 years ago. Alex 2 years ago. Sitonir 2 years ago. Nifti 2 years ago. Bill Jones 2 years ago. Cognicom 2 years ago. Joe S. Piero 2 years ago. Alexander 2 years ago. Vitaly 2 years ago. Jef 2 years ago. Wilfred Tan 2 years ago. Pawel Nowak 2 years ago. Orville 2 years ago. Xavier Bit 2 years ago.
Khanh 3 years ago. Alexander 3 years ago. Dee 3 years ago. Ivan 3 years ago. Joe Smith 3 years ago. HAL Author 3 years ago. Nick 3 years ago. Ro 3 years ago. Manny 3 years ago. Nick Mazzola 3 years ago. Jaime 3 years ago. TS 3 years ago. Juan Castro 3 years ago. Duncan Roe 3 years ago. CY 3 years ago. Key 3 years ago. Eranga 3 years ago. Rob 3 years ago.
Latino 3 years ago. Ruben Yeah 3 years ago. Mark 3 years ago. Bob 3 years ago. MB 3 years ago. Kam 3 years ago. Roger 3 years ago. The Argentinian 3 years ago. Greg 3 years ago.
G 3 years ago. Tommy 3 years ago. Joey 3 years ago. Deee 3 years ago. Cyberlunacy 3 years ago. Miguel 3 years ago.
Chris 3 years ago. Tyler Woodward 3 years ago. Reeeee 3 years ago. Maradas 3 years ago. MT 3 years ago. Adi 3 years ago. Alberto 3 years ago. GBS 3 years ago. Dush 3 years ago. SysAdmin 3 years ago. M 3 years ago. Tom 3 years ago.
Jay 3 years ago. Dejan 3 years ago. Astroman87 3 years ago. Duncan 3 years ago. David 3 years ago. Joc 3 years ago. Nando Argilli 3 years ago. Layne 3 years ago. Tyler 3 years ago. Kevin 3 years ago. Daniel 3 years ago. Yoes 3 years ago. Jack 3 years ago. GavDav 3 years ago. Sm1th 3 years ago. Phil 3 years ago. Rye 3 years ago. Holy 4 years ago. Logan 4 years ago.
Michael 4 years ago. HAL Author 4 years ago. Fil 4 years ago. Mark 4 years ago. Rick 4 years ago. SG 4 years ago. Miguel 4 years ago.
RR 3 years ago. Janis 4 years ago. HB 4 years ago. Vasco 4 years ago. Matt 4 years ago. Hammas Keiju 4 years ago. Adrian 4 years ago. Brendan 4 years ago. Nolan 4 years ago. Ron 4 years ago. Trenjeska 4 years ago. Podrock 4 years ago. Chris Hoogenboom 4 years ago. Peter 4 years ago. Jon 4 years ago. David M 4 years ago.
Josh T 4 years ago. Maguro 4 years ago. Mantorras77 4 years ago. Jerome 4 years ago. Luke1 4 years ago. Sm1th 4 years ago. SM Patcher 4 years ago. Gerry 4 years ago. ImSkiZZeR 4 years ago. Duncan 4 years ago. Samantha 4 years ago. Chris 4 years ago. Sergey 4 years ago.
Prot 4 years ago. Dave 4 years ago. Javier 5 years ago. Doug 5 years ago. Tur Le 5 years ago. Bente 5 years ago. Tom 5 years ago. GaryG 5 years ago. Guru 5 years ago. Salazaku 5 years ago. Sam 5 years ago. Brian 5 years ago. ShawnTrack 5 years ago. HAL Author 5 years ago. Wrelt 5 years ago. Daniel Sh 6 years ago. Cara 6 years ago. BrankoH 6 years ago. Uvires1 6 years ago. MohammaD 6 years ago.
HAL Author 6 years ago. Edward 6 years ago. James 6 years ago. Asimov 6 years ago. Derek Bowers 6 years ago. Ricardo 6 years ago. Drew 6 years ago. Jim 6 years ago. Jack Johnson 6 years ago. Victor 6 years ago. Ashish Sharma 6 years ago. Guna 6 years ago. Abhsihek 6 years ago. Michal 7 years ago. Duncan 7 years ago.
Jeff 7 years ago. HAL Author 7 years ago. Tom 7 years ago. Chrisi 7 years ago. Robert 7 years ago. Tblog 7 years ago. Sebastien 7 years ago. Mike 7 years ago. Shawn 7 years ago. James Wright 7 years ago. Peta 7 years ago. GRACE 7 years ago. Toxik 7 years ago. DK 7 years ago. Nemo 7 years ago. EvZ 7 years ago. Gamma 7 years ago. Eikfo 7 years ago. Juan 7 years ago. Edwin 7 years ago. Pat 7 years ago. LL 7 years ago. A 7 years ago.
Andy 7 years ago. Philip 7 years ago. Jaquan 7 years ago. Marc 7 years ago. Paul S 7 years ago. Eros 7 years ago. Adolfo 7 years ago. Oldsphere 7 years ago. Salah 7 years ago. RR 7 years ago. Wilson 7 years ago. ZoZo 7 years ago. Pollardon 7 years ago. The file versions were the same though. I presume the difference is because one is bits versus Was this reply helpful? Yes No. Sorry this didn't help. Choose where you want to search below Search Search the Community.
Search the community and support articles Windows Windows 7 Search Community member. Hi all. Remote Desktop can't connect to the remote computer for one of these reasons: 1 Remote access to the server is not enabled 2 The remote computer is turned off 3 The remote computer is not available on the network Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.
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 Report abuse.
Comments
Post a Comment