Sunday, April 5, 2015

RDP Failures after Windows 2008 R2 SP1 Install


After we installed SP1 on a Windows Server 2008 R2 system, RDP sessions could not be established - they would just be disconnected after login.
Looking at the Application log on the affected machine showed errors whenever RDP was attempted as follows :
EventID: 1000
Level: Error

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: 0x4f1f9e66
Exception code: 0xc0000005
Fault offset: 0x000000000000a793
Faulting process id: 0xc6c
Faulting application start time: 0x01cd2e6fa5ad2399
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: C:\Windows\system32\rdpcorekmts.dll
Report Id: 1500f935-9a63-11e1-9ff7-000c29b0e256


A search of the internet revealed this page where it became clear others had seen the same issues.
It was clear from the log above that the version of rdpcorekmts.dll on this system was 6.1.7600.16952, and this seems to cause issues in some circumstances.
As I had console access to the server, I noticed other patches were also waiting to be installed, specifically KB2667402. From some of the comments, this looked like it may resolve the issues we were seeing so I installed only this update, followed by a reboot of the server and all was well again.
*NB - After install of KB2667402, the version of rdpcorekmts.dll changed to 6.1.7601.17767

UPDATE
A small update to this post as I've encountered this problem a few times since...
The MS KB2667402 update is definitely to blame for the RDP failures. I have a couple of potential solutions :
  • Uninstall KB2667402 before running the 2008 SP1 install. After the reboot, install KB2667402 and reboot again.
  • Install 2008 SP1 as normal, but before rebooting run the KB2667402 update - this usually works, but not always.
If you already cannot get to the server via RDP, you can re-install KB2667402 via PSExec, reboot the server then you should be able to RDP to it again.


source:http://www.greytrust.com

No comments:

Post a Comment