The task you are trying to do can't be completed because remote desktop services is currently busy. Please try again in a few minutes. Other users should still be able to log on.
I have been getting this error ever since switching to Seven, same machines were using Windows XP Remote desktop successfully for years. Just using Seven now. It does not occur every time I connect to the host from a remote location. At the host machine, the only option is to to click on "OK." This brings me back to the same error. Cannot log in, cannot log out. There is no explanation for it. Trying again later doesn't work. Other users cannot log on. Only way to correct the scenario is restart/reboot/shutdown of the host computer. This problem is new.. Anyone have any ideas?
November 12th, 2009 6:53pm

The system is socket 478 with Asus P4P-800 E Deluxe MB, 3.4Ghz P4, 2 GB RAM. This was an XP machine which ran remote desktop well. The install is a plain vanilla install of Win 7. The latest drivers and windows updates have been installed. I agree, there is a conflict but if I have to begin unplugging hardware to get the machine to run correctly right under Win7, then we're heading down the same path as Vista's demise. As is, device manager reports all hardware is working properly. One thing I have noticed beyond the normal lockups, is that remote desktop on the host machine does not kick out after a remote connection has ended. This did not occur under WinXP. Apparently, the service doesn't seem to detect that the remote system has disconnected.
Free Windows Admin Tool Kit Click here and download it now
November 16th, 2009 1:27pm

Hi, Thank you for your update. At this time, I just want to know if you have performed clean boot to check this issue. Previously, I handled a similar issue and found that issue was related to software conflicts and I hope you can also check this. Thanks again for your efforts.Nicholas Li - MSFT
November 20th, 2009 2:50am

Is there any resolution to this bug? I have had this problem connecting to vista32 and win7-64 from xp32-sp3. The remote computer should never hang regardless of my misuse. This problem is NOT new, I have tried to resolve it with microoft forums and newsgroups before with no luck. The problem started when I updated to remote desktop connection client 6.0.6001.18000, there were zero problems with the earlier client. People have suggested reverting back to the older version, but hey, you can't. If you know the update number for the xp remote desktop connection from microsoft update perhaps I can find it and roll it back but I doubt it. Too often these issues are never resolved in these forums and we never hear if the problem was fixed. It's not fixed here. I'm not willing to go through all the diagnostic steps you have listed. If the connection can work once, it should work multiple times. It always hangs up on the first reconnection attempt. Edit: isn't it a little insidious that microsoft employees are going through these posts and marking them answered? Only the original poster should be able to decide if they are answered.
Free Windows Admin Tool Kit Click here and download it now
December 10th, 2009 10:34am

No, it HAS NOT been resolved. It has been ignored in the normal manner today's "support" techs do asking us to take those "idiot steps" which have been pushed on us for over thirty years by Microsoft whenever there is a problem they do not know how to fix! I have done everything, including reinstalling Windows 7 and the problem persists. I NEVER had any problems with this using WinXP but this version is VERY buggy. Please post if you find a way to revert back to an older version, because this greater, more secure version just isn't working right. And to be specific, you are correct. The problem occurs more often during a "reconnect." I basically have to reboot my machine every time this happens in order to log in. I'd gladly be willing to tool in anything for a smooth operation. It's making my overall impression of Windows 7 sink...
December 10th, 2009 1:25pm

I do not see where you are giving any info. to help you here.You need to tell us what OS is running on the remote PC'sI use RDP very liilte but have no problems when I do. I can use it between XP pro and win 7 without any lockup at all.I can also use it with a old term. server without lockup.I just connected and disconnected three times within seconds and it worked fine.Unless you are willing to do what is asked of you in these forums, you are not going to get help.so stop whining about what worked before and provide some info. so we can try to help.
Free Windows Admin Tool Kit Click here and download it now
December 10th, 2009 1:49pm

To add to the earlier information I gave in this thread: I have tried connecting using a laptop running Windows XP SP3, another laptop using Vista, and after upgrading the Vista laptop to Windows 7, I tried using both the ""super secure" remote desktop selection and using the "less secure" remote desktop selection. I tried connecting the Windows 7 laptop to a plain vanilla install on the desktop, on the host desktop computer, with Windows 7 Premium, Professional and Ultimate. Again, I usually do connect the first time from a laptop regardless of the the OS used. The problem is on the host desktop which doesn't seem to recognize when the remote sessions have ended. I know this because when I return to my desktop, the welcome screen always indicates that I am logged in, when I shouldn't be. I have to do a hard reset of the machine because logging in from the welcome screen causes a hang, with the screen saying "welcome" along with the spinning pointer and unresponsive keyboard. I'm not sure what you are trying to accomplish by "undoing" drivers during reboot. As I stated, I have already tested this using as "clean" a condition as possible to achieve a "safe" connection from another location. Like Paul said earlier, this should just work!! Especially since all the drivers in device manager report everything is running correctly in the host desktop. So if there are software conflicts, it's the software which must be in place to achieve a functional machine using Microsoft provided drivers. I think Microsoft needs to invest in some better R&D and quit relying on the goodwill of their customers to fix their buggy software! You call this "whining" but I call this "same ole, same ole" with Microsoft releasing too early and relying on their customers to do the reboots for them! UNSATISFACTORY! So, how do I get an older version of RDP running on this machine until this new version matures a bit?
December 10th, 2009 3:12pm

The required diagnostic information is the following: "The task you are trying to do can't be completed because remote desktop services is currently busy. Please try again in a few minutes. Other users should still be able to log on." Someone in programming at microsoft should be able to go to the code that produced this error message, examine it, and report back with an explanation on why the program shows it. If I just had that much information, a fix might be possible at some point. I just tested this a bit more, and there is not a similar bug when the remote is win 2003 server. As I said above, vista32 also has the problem, but with a different error message as I recall. It was with a remote vista host that I first noticed the problem after the remote desktop connection client update. I could connect to vista ok using the earlier client. It's strange there are only a couple of hits on google for this problem, this thread being one of them. Bing has no hits for it at all.
Free Windows Admin Tool Kit Click here and download it now
December 10th, 2009 4:08pm

I have to get this working. I've done the clean boot, with zone alarm truevector service disabled as well. The bug is still there, but in possibly a slightly different form. The reconnect always hangs, to the point where the box has to be hard reset to get back in. But the error message "The task you are trying..." is gone -- I just get the blue graphics with the spinning circle thing. This needs to be escalated at microsoft's side. I will post back here if I can get this fixed. Please let me know if you fix it also. We may have to support ourselves on this. There is no point ranting at microsoft.. they are totally inured to this approach. How can we get this bubbapcguy to go away?
December 11th, 2009 4:12am

I use ZA as well, Paul. I learned a long time ago that it works so well that sometimes, you have to unload the code completely so you can rule out strange behaviors. Thing is, the only time there has ever been any problem is with poorly written programs. None the less, I have ruled it out as well. I haven't been able to fix the erratic behavior of RD. I'm hoping this gets escalated, as well. If I find a cure, I'll be sure to get back here. Bubba be gone as far as I'm concerned....
Free Windows Admin Tool Kit Click here and download it now
December 11th, 2009 10:10am

I guess you two can just help each other, as no one else is.If it works for all of us it works, if it is not working for you then it is YOUR setup which needs to be looked at, but as you two do not think that is the case...CY-A.
December 11th, 2009 12:36pm

I use ZA as well, Paul. I learned a long time ago that it works so well that sometimes, you have to unload the code completely so you can rule out strange behaviors. Thing is, the only time there has ever been any problem is with poorly written programs. None the less, I have ruled it out as well. There may be an issue with zone alarm. This is from the readme on the last version of ZA Pro. c. Using Remote Desktop Connection to connect to your computer from another PC may cause Windows to stop responding and you will need to restart your computer. I am trying to navigate the maze of tech support with them, but will also try uninstalling ZA and see if problem goes away.
Free Windows Admin Tool Kit Click here and download it now
December 11th, 2009 4:42pm

Uninstalling ZA Pro 9.1.008 solved the problem. They recommended 9.0.114 but I find the bug is still there. Tech support now says it is a bug in all win7 versions and that they are working on it. You will have to uninstall ZA to use remote desktop.
December 11th, 2009 5:41pm

Hi, I suspect there may be some conflicts, please try the following to have a check: How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7 In addition, please also let me know the detail information about your hardware condition and which software you have installed. Thanks. Nicholas Li - MSFT You should just ask if people have zone alarm installed.
Free Windows Admin Tool Kit Click here and download it now
December 11th, 2009 5:54pm

Any word on the relevant portions of source code that displays the error message, and what circumstances would cause it to appear? i am also getting it, and i have no ZoneAlarm.
January 28th, 2010 10:39am

I suspect there may be some conflicts What sort of conflicts are you suspecting? If you could share your thinking, maybe it could work towards finding a resolution. i.e. if uninstalling 3rd party firewalls or performing a clean boot may suppress the symptoms, but we'd still have to find the cause.
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2010 10:44am

This thread is now deprecated. The discussion continues on http://social.answers.microsoft.com/Forums/en-US/w7programs/thread/91828bc5-92c4-4612-9ab7-aaeec6695fdd It is not related to ZoneAlarm. Steps to reproduce the problem: 1. Log onto the Windows 7/Windows Server 2008 R2 machine remotely using Remote Desktop Connection 2. Attempt to login to the machine interactively at the local console.
January 28th, 2010 10:54am

This thread is now deprecated. The discussion continues on http://social.answers.microsoft.com/Forums/en-US/w7programs/thread/91828bc5-92c4-4612-9ab7-aaeec6695fdd It is not related to ZoneAlarm. Steps to reproduce the problem: 1. Log onto the Windows 7/Windows Server 2008 R2 machine remotely using Remote Desktop Connection 2. Attempt to login to the machine interactively at the local console. I just replied in the other thread you provided a link to. I have not seen this "The task you are trying to do can't be completed..." error popup in over 6 weeks or so, and can't take the time to try and reproduce it. It may or may not have something to do with zone alarm. Microsoft won't say anything about it since they don't live here anymore, at least not in any valuable technical capacity. In my reply on the other thread I confirm the bug with zone alarm and remote desktop. The remote host hang is mentioned in the official zone alarm release notes, so I'm not making this stuff up. You must be seeing this error by means of an entirely different pathway not related to zone alarm. In my case, zone alarm might be exposing a weakness in the microsoft code or vice versa.
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2010 4:55pm

This thread is now deprecated. The discussion continues on http://social.answers.microsoft.com/Forums/en-US/w7programs/thread/91828bc5-92c4-4612-9ab7-aaeec6695fdd It is not related to ZoneAlarm. Steps to reproduce the problem: 1. Log onto the Windows 7/Windows Server 2008 R2 machine remotely using Remote Desktop Connection 2. Attempt to login to the machine interactively at the local console. Thanks for the link into this discussion. Zone Alarm is one part of the issues. I've also established that MS Essential Security also causes issues with RDP (see updates in the thread you've linked to). I'm also pretty sure that not all problem are caused by ZA and MS SE, but hopefully these leads might help others figure out what's going on with their systems....
February 8th, 2010 8:44am

I am having this same problem and I have ZA installed. I thought I would post so that bubbapcguy might realize that it is a lot more than two people having this problem.I am tired of these posts getting closed as answered as well. I have quite a few problems with Windows 7 that are all over the forums but Microsoft seems to not want to do anything about them. They all get closed as answered because we should reinstall windows 7 and then not install anything on it or try and use it with our current network setup.
Free Windows Admin Tool Kit Click here and download it now
February 17th, 2010 7:05pm

I too had the same problem when trying to log back in to my Windows 7 x64-bit pc after using remote desktop through a eee pc 1000 laptop (which has Xandors OS installed.) So once I had ended my session through the eee pc laptop, I would go back to my Windows 7 x64-bit desktop pc and try to log in but it would just hang at the welcome screen with the pointer going in circles. Issue went away once I uninstalled Zone Alarm free edition (using windows built in firewall now). I also uninstalled SuperAnti Spyware free edition just for the heck of it. Kuddos to Paul and Redeye dog for believing and keeping this alive.
June 29th, 2010 7:55am

I am not sure if it helps I am a server admin in my company, i found that if you uncheck the tick boxes both Printers Clipboard transfer & Printers in Remote Desktop Connection It might avoid the issue you are having Exact instruction: Open Remote Desktop Connection dialogue -> Under Local Resources Tab -> uncheck Printers & Clipboard tick boxes Hope this helps My guess is remote desktop takes to long to map your printer drivers to remote server / workstation, however it took too long to do so and got timeout Thats why you got that error message Just my guess!~~
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2010 9:15pm

I have always kept these unchecked to decrease the amount of memory being used during a session. The only thing I like to keep checked, but has been tested unchecked, is the clipboard so I can do fast cut & paste tasks, if needed. Thanks anyway.
July 20th, 2010 10:03am

Sometimes the net share access can lead this problem, when you disconnected from remote and then opened a share like \\server\d$ to access the sever. BTW you can use psshutdown which is in sysinternal toolset to restart the remote box without reaching it.
Free Windows Admin Tool Kit Click here and download it now
November 1st, 2010 11:43am

this worked for me. thanks JrbranchSuchit Gawali. Sr System Engineer
February 8th, 2011 2:39am

The following procedure helps me get users back on without having to reboot the server: http://sheltonial.blogspot.com/2011/02/windows-2008-r2-terminal-server-error.html
Free Windows Admin Tool Kit Click here and download it now
February 22nd, 2011 6:29pm

Im having the same problem. Suddenly our TS farm will not accept users any more because "RDP services is currently busy.. blabla" I have to reboot my farm every morning, and sometimes in the middle of the day.. Thii is driving me crazy. And when i try to run the hotfix it just says" this update is not applicable" So thats not very helpfull.. Anyone else managed to fix this?
May 9th, 2011 2:38am

I have seen the same problem that Paul and Red have had. so it is a problem within Win 7 itself.Richard Stremlow
Free Windows Admin Tool Kit Click here and download it now
June 16th, 2011 2:38pm

My server 2008 R2 Farm has been up and running for many months with no issues at all, until last week, and suddenly several users keep getting that same error. Unlike what others have reported though, my users are on Thin Clients not running XP or Win 7. By going through the event logs, I was able to find entries mentioning errors unloading things from the registry and it names the specific process ID's, and I do find those running. Once I kill those specific process ID's, the user can then log in. I am baffled as to what could be suddenly causing this. The previously mentioned hotfix is not applicable as it is included in the latest SP which is applied. Please post details if anyone has any ideasRon GIllis
June 20th, 2011 11:47am

I'm having this same problem all of a sudden on a Windows 7 Ultimate SP1 client. The client has no 3rd party firewall software installed, and is NAT'd properly. When I attempt to establish a terminal services connection to it, I am getting either of these messages: 1. This computer can't connect to the remote computer. The two computers couldn't connect in the amount of time allotted. Try connecting again. If the problem continues, contact your network administrator or technical support. 2. The task you are trying to do can't be completed because remote desktop services is currently busy. Please try again in a few minutes. Other users should still be able to log on. This client has worked perfectly fine for the past year — can a Microsoft developer please look at this bug and investigate its cause? Please let me know what debugging tools I can use to gather more information, to help isolate the bug to the correct library or device driver.If this post was helpful, please click the little "Vote as Helpful" button :) Trevor Sullivan http://trevorsullivan.net
Free Windows Admin Tool Kit Click here and download it now
November 28th, 2011 10:03am

I just had a whole string of these messages. I had a remote desktop session open to a 2008 R2 server from a Windows 7 64-bit desktop, but minimized. The remote server is being backed up over the network. Expand the remote desktop window to check on backup progress... the remote desktop window is solid black, and stays that way. Tried closing the window and reconnecting. Got the "currently busy, please try again" message. Try again, fails. Try again, fails. Look up the error, find this thread. Try again, fails. Try again, fails. Finally after doing this for several minutes the remote desktop finally appears. , So basically if the remote server is busy doing something else, remote desktop gives up trying to connect almost instantly and doesn't wait around for the remote server to not be busy. This looks like a bug. It should wait a reasonable amount of time for the remote session to establish on a busy server, like 30 to 90 seconds. Not 1.5 seconds. Otherwise the result is that a hung remote server that is at constant high load may never let the remote administrator connect, because of the near-instant connect-timeout.
December 13th, 2011 11:16pm

@ds5384: The rare times that it does happen to me, it's usually because of a failed logon attempt, or a session that gets disconnected unexpectedly. Next time that someone has this problem on an important system, they should push for Premier Support to investigate and publish a public hotfix. There's no reason that a failed logon session should hang the Terminal Services service indefinitely. Unfortunately the last time I experienced it, it was on my system at home, which doesn't exactly warrant a call to Premier Support.If this post was helpful, please click the little "Vote as Helpful" button :) Trevor Sullivan Trevor Sullivan's Tech Room Twitter Profile
Free Windows Admin Tool Kit Click here and download it now
December 23rd, 2011 10:19am

Very proud of you, Paul! Good job and well done! Now - as far as the Microsoft Tech guys, you sort of at least have to respect their attemt to help out. :) I agree they are quick to resolve a questions without the concent of the one who posted the question initially. This is what's really disapointing. But... we're here to help eachother. Let's make us better, our environments better, and why not - the Microsoft tech even better. Next time they'll know it better. Thanks Paul for all your dedication into addressing this issue.
May 17th, 2012 8:37pm

Hi there is a hotfix available. Just resolved thisfor me immediately. http://support.microsoft.com/kb/2661332
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2012 12:42am

Hi there is a hotfix available. Just resolved thisfor me immediately. http://support.microsoft.com/kb/2661332
July 20th, 2012 12:51am

Thanks, even though it's no longer affecting my servers, I'm glad to see they came up with something on this.
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2012 10:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics