Windows virtual pc terminal connection is currently busy

Notify me of followup comments via e-mail. You can also subscribe without commenting. Leave this field empty. Home About. In that case, two RDP users connected as usual and the third one faced this error.

Related Reading. Windows Update Stucks at Copying Packages to the December 17, November 18, November 9, Leave a Comment Cancel Reply Notify me of followup comments via e-mail. You're welcome! Tuesday, June 12, AM. Monday, September 17, PM. Thank you sir! It worked and we're back in business Monday, December 31, PM. Deleting the Windows XP Mode. Thank you, thank you, thankyou!!! Wednesday, June 19, PM.

Thanks a lot Bob, it's still saving peoples skins! Monday, October 14, AM. You're welcome, glad I could help! Monday, October 14, PM. This file is getting to be about 2GB in size,and even after deleting it and rebooting the physical machine, I'm still not able to log in.

Is that normal? When I switch the user account to try another user, I get an error message saying the original user is logged on, and do I want to log them off. I select YES, and a remote logoff begins, but that takes forever, and I typically have to hard end the VM, which I'm sure is not helping this scenario.

Membership in the local Administrators group, or equivalent, on the Terminal Server that you plan to configure, is the minimum required to complete this procedure.

If you don't select Allow users to connect remotely to this computer on the Remote tab, no users will be able to connect remotely to this computer, even if they are members of the Remote Desktop Users group. The default port assigned to RDP is To resolve this issue, determine which application is using the same port as RDP.

If the port assignment for that application cannot be changed, change the port assigned to RDP by editing the registry. After editing the registry, you must restart the Terminal Services service. After you restart the Terminal Services service, you should confirm that the RDP port has been correctly changed.

The listener component runs on the Terminal Server and is responsible for listening for and accepting new Remote Desktop Protocol RDP client connections, thereby allowing users to establish new remote sessions on the Terminal Server. There is a listener for each Terminal Services connection that exists on the Terminal Server.

Connections can be created and configured by using the Terminal Services Configuration tool. You can run the netstat tool to determine if port or the assigned RDP port is being used by another application on the Terminal Server. To determine which application is using port or the assigned RDP port , use the tasklist command line tool along with the PID information from the netstat tool. You should determine if this application can use a different port. If you cannot change the application's port, you will have to change the port assigned to RDP.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority. Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data. On the Terminal Server, open Registry Editor. To change the port for a specific connection on the Terminal Server, select the connection under the WinStations key.

Use the connection name and port number specific to your Terminal Server configuration. The qwinsta, netstat, and telnet tools are also included in Windows XP. You can also download and use other troubleshooting tools, such as Portqry. In the Details pane, right-click the connection you want to modify, and then click Properties. On the General tab, in Security layer, select a security method. The security method that you select determines whether the Terminal Server is authenticated to the client, and the level of encryption that you can use.

You can select from these security methods:. The Negotiate method uses TLS 1. If TLS is not supported, the server is not authenticated. If you select this setting, the server is not authenticated. If TLS is not supported, the connection fails.

This method is only available if you select a valid certificate, as described in Step 6. Additional server and client configuration requirements must also be met. For more information about requirements and tasks for configuring Terminal Server to support TLS authentication, see Configuring authentication and encryption.

In Encryption level, click the level that you want. For more information about these levels, see notes at the end of this topic. To use TLS 1.