Home > Remote Desktop > Windows 2008 R2 Sp1 Rdp Not Working

Windows 2008 R2 Sp1 Rdp Not Working

Contents

I am running Hyper-V Server 2008 R2 SP1. Don't think restarting RDP will work though. RDP generally works the first time following a reboot, but any subsequent connections freeze at Welcome after entering the login credentials. thx! http://powerglobaldesigns.com/remote-desktop/windows-2008-rdp-clipboard-not-working.html

Thankfully after this I had a fully patched server and working RDP. Can you provide anymore details? I can log in locally. If you need to do all of this remotely and find that you still can't RDP the server after removing the two patches using the commands above I recommend running sfc /scannow click resources

Available Updates For Remote Desktop Services (terminal Services) On Windows Server 2012 R2

Can you RDP into the problem terminal server from itself (Using the Remote Desktop Client, connect to 127.0.0.1)? Reply Roland August 16, 2012 If you don't reboot after installing SP1, you can reapply that KB, without uninstall first. Microsoft Network Monitor 3.4 http://www.microsoft.com/downloads/en/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en Meanwhile, if you find other related Event log, please post here for the further research. I certainly didn't fancy not applying these patches to this server so I reapplied KB2621440 and KB2667402 via Windows Update, and rebooted the server.

  • But not all companies have their builds upgraded to SP1.
  • Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are
  • Very usefull !
  • I havetried all solution except reinstall the OS (it's not possible).
  • Back on my other machine, I was then able to RDP into it.
  • Reply Moty June 5, 2012 Thanks you saved me a lot of work.
  • We installed Service Pack 1 on some of the computers and now the Remote Desktop Connection is not working.

However, as of this morning, after appyling the last couple of patches. If I read you correctly. You can follow any responses to this entry through the RSS 2.0 feed. Available Updates For Remote Desktop Services In Windows Server 2012 R2 This allowed me to sidestep all the firewall and permissions issues associated with letting a remote user access WMI. share|improve this answer edited Jun 14 '12 at 1:13 Tim Long 1,40111636

Note that the problem on the guest OSes occurred prior to updating Hyper-V Serverto SP1. After a single Sp1 no longer accept RDP connections despite the port 3389 is open ... Hope this helps. You also receive an error message like this in the Application event log: "Faulting application name: svchost.exe_TermService, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1 Faulting module name: rdpcorekmts.dll, version: 6.1.7600.16952, time stamp: 0x4f1f9e66Exception

You can publish advertisements in local dailies so that your offer is read by maximum people willing to buy a home. Remote Desktop Hotfix Windows 7 No. John. reply Can you provide anymore Permalink Submitted by ingram on Sat, 08/11/2012 - 4:28pm.

Available Updates For Remote Desktop Services In Windows Server 2012

Rebooted.Went back to windows update and noticed two additional updates along withKB2667402. https://blogs.technet.microsoft.com/yongrhee/2011/07/31/list-of-remote-desktop-terminal-services-related-hotfixes-post-sp1-for-windows-server-2008-r2/ You can check the below article to get a suitable solution. Available Updates For Remote Desktop Services (terminal Services) On Windows Server 2012 R2 You should be able to re-install it in all cases after SP1 as SP1 makes it applicable again. Rds 2012 R2 Recommended Hotfixes I will follow suggestion of others here and uninstall it and then reinstall.

Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the Check This Out The other machine works perfectly ...... Thanks. Sunday, April 29, 2012 5:59 PM Reply | Quote 0 Sign in to vote Thanks x 10^6 Paszun! Remote Desktop Hotfix

Tested. If you do have this problem and do try those things, please, let us know if one or the other actually solves the issue. You can get it here: Windows 7 Server 2008 R2 Now start the services you stopped earlier. Source Privacy statement  © 2016 Microsoft.

e.g. Kb2821526 So, you should be able to start the server up normally and remotely uninstall the original version of the patch via WMI wmic /node: /user: process call create "powershell wusa /uninstall And observed I can't connect to this server using RDP.

Related This entry was posted on April 10, 2012 at 4:48 pm and is filed under WindowsServer.

Thanks John Monday, February 28, 2011 3:09 PM Reply | Quote 0 Sign in to vote Hi, Event ID 4005: This event indicates the windows logon process is If a regular user tries to login to a RDS Session Host and gets disconnected, remember to add the "User" or create a "Security Group" and add to Local Users -> It was the DC I upgraded, nice. Kb2933664 Cheers....

From this machine i can RDP to other machines, but from other system i cannot login to this system reply There are links to the Permalink Submitted by ingram on Mon, Tuesday, April 03, 2012 2:02 PM Reply | Quote 0 Sign in to vote I followed ALL the tips in here - including the reapplication of KB2667402 - and after all reply Finally, ir worked! have a peek here I looked to see if and KB2667402 was installed and it is.

Related Filed under Windows Tagged with broken, Event 4005, Install, Installation, KB2621440, KB2667402, R2, RDP, RDP not working, rdpcorekmts.dll, Service Pack 1, SP1, The Windows logon process has terminated unexpectedly, Windows Event log shows Winlogon failure (4005).