Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3664
  • Last Modified:

RDP not working after SP1 for Windows 2008 R2 installed

So, I finally decided to try out SP1 for Windows 2008 R2 on one of my domain controllers. It's been fine on my Windows 7 workstations and most member servers.

Anyways, I copied the SP1 executable (didn't want to wait for the download) to the server and waited. Then waited some more. It took about 2 and a half hours for it to complete. When it finally got back to the logon screen, the mouse and keyboard were frozen. Ugh. Tried to connect remotely but had no luck.

Power it off and back on again and all seemed okay. Got the message that SP1 is installed and seems to be working okay (this is just a domain controller/DNS server...nothing else).

A few days later and I'm trying to connect to the server remotely and I find that I can't. The server was fine before SP1. When I attempt to connect with mstsc, I'm prompted with the certificate dialog, I say "okay" (nothing unusual to me yet) and then the box disappears for half a second before the logon box reappears. Subsequent attempts don't have the certificate dialog, it just comes back to the logon prompt. No errors.

I can logon directly to the server console. When I check the logs, I see the "Windows logon service terminated unexpectedly" message at exactly the same time I attempted to remotely logon. Rebooted the server but the problem persists.

Port 3389 is active on the server(I can telnet to it) and I'm actually seeing success entries in the security log for my logon attempt followed by an immediate logoff success. The accounts I'm using have remote access rights and remote access is enabled (all terminal service clients). Using an account without proper rights will generate a "this account doesn't have rights" message as expected.

I'm tempted to rollback the service pack, but I really don't want to wait another 2 hours for it to be remove and I really don't want any more surprises. Has anyone run into this and is there a fix?

Thanks,
Tim
0
timmr72
Asked:
timmr72
  • 3
  • 2
1 Solution
 
Darius GhassemCommented:
Look over this link to see if this helps out

http://thebackroomtech.com/2010/08/31/fix-the-windows-logon-process-has-unexpectedly-terminated/

Make sure you have all other Windows updates applied

Go to Run type sfc /scannow
0
 
timmr72Author Commented:
Thanks for replying. I'm also seeing this (matching the failed windows logon times):

Event ID 20: Attempt to send connect message to Windows video subsystem failed.

It's only happening when attempting to connect via RDP to the server. I'm running sfc /verifyonly right now.
0
 
timmr72Author Commented:
Well, sfc /scannow seemed to do the trick (at least RDP is back). It had to run twice because it reached it's maximum for queing files to fix.

I'm surprised it worked. Also, I still show that I'm SP1 for 2008 R2, but I wonder if I can trust that? With all the post SP1 integrity issues, should I do anything else (reapply any patches/SP's)  or just be happy it's all working for the moment.

-Tim
0
 
Darius GhassemCommented:
You should be good to go
0
 
timmr72Author Commented:
Thank you.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now