\SystemRoot\System32\RDPDD.dll failed to load

\SystemRoot\System32\RDPDD.dll failed to load

  • Comments 114
  • Likes

 

This is an FYI post for an issue we've seen on a couple of Windows 2003 SP2 servers internally.  Hopefully if someone hits this in the wild they'll be able to find this post on the intertubes.

Symptom:

When attempting to connect from the client via RDP,  you would click “connect” and then soon after it would silently fail and “connect” would be clickable again.

Each time when attempting to connect, the server would log this event:

Event Type:   Information
Event Source: Application Popup
Event Category:      None
Event ID:     26
Date:         9/25/2007
Time:         12:13:57 PM
User:         N/A
Computer:     ServerX
Description:
Application popup:  : \SystemRoot\System32\RDPDD.dll failed to load

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00000000 006c0002 00000000 4000001a
0010: c0000017 c000009a 00000000 00000000
0020: 00000000 00000000

Our Resolution

A) We found that in our cases it was an issue with the ATI driver and by either rolling back the ATI driver for the display on the server or upgrading the display driver on the server resolved the issue.  Reports in the comments show the same for Nvidia drivers

B) In another instance it was found that by going to:  Display Properties --> Settings --> Advanced --> Troubleshoot, turn off "Hardware acceleration” resolved the issue as well without adjusting the drivers.

C) On the internet I've seen posts showing SFC to help but in my cases it did not.

Update from comments: 

D) A solution found at http://forums.nvidia.com/index.php?showtopic=67147&hl=remote%20desktop&st=60 worked for me (and others.)

It's a registry fix that increases the size of the session image space.  Add the following key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

"SessionImageSize"=dword:00000020

Where 00000020 is hex for 32

In any case the event was a red herring and was just a generic error being bubbled up from Win32k.sys..

 

Technorati tags: , ,
Comments
  • PingBack from http://geeklectures.info/2008/01/04/systemrootsystem32rdpdddll-failed-to-load/

  • I only had this problem after installing .NET 3. on W2K3-SrvHunSP2+Term Serv. Ati driver adjusting solved it.

    Thx!

  • Alright glad it helped!

  • Great info! I had the same problem after installing .Net 3.5....it was just driving me crazy!

  • I have a client with new Dell XP machines and nothing but seemingly random glitches with connecting to them via RDP. First it was BSoDs. ATI seemed the culprit from the bugcheck, but there was no updated Dell ATI driver. Updating with the ATI driver from the ATI/AMD website seemed to help, but there were still lockups after accessing via RDP the first time.

    Now, we've got a couple machines that just refuse the connection, with the above error you about. Imagine my surprise when ATI was your culprit!

    I think the VERY latest driver off the website is going to resolve my problem, but honestly? I've been trying to track this down for months.

    ATI + .Net is a clue. I couldn't get them to break out of the box, but after all our apps were on, they did it. One app installs .Net 2.0 - my money is on that combo.

  • Had this appear on XP Pro on a dual-core AMD system after updating the ATI Radeon drivers.

    Disabled Hardware Acceleration and RDP now works again.

  • I yesterday updated to nvidia driver 175.16, and remote desktop works nomore.

    It seems there's a strong relationship between video drivers and RD. But since this is a very old problem (i found many discussions about it which have been started in 2006 and 2007), MS should release a patch to solve it.

  • It's actually a problem with the card/drivers not with the OS.

  • Application popup:  : \SystemRoot\System32\RDPDD.dll failed to load is showing numerous times in my Event viewer - system folder after I try to RDP to my machine from another computer. Basically, I hit "connect" in RDP, and the little box flashes and doesn't do anything. I am running Windows XP Pro. I would like to add to one of the previous posts from a user named "Skynet." I just installed nVidia display driver 175.16, and that's when my RDP broke. nVidia and Microsoft have yet to fix this problem, but I will be contacting nVidia about it, tomorrow. I will let you all know what I find out.

  • UPDATE: I just wanted to confirm my previous post. nVidia display driver 175.16 BROKE my RDP. I rolled back the driver and restarted my computer. Lo-and-behold.... I was successfully able to RDP my machine from another machine. I'm definitely going to put in a support ticket or phone call to nVidia, tomorrow, to let them know of this problem.

  • Same here in Germay. After Nvidia Update. RDP stopped.

  • Unbelievable, but true. Of course, Murphy let me use a headless system (no display, no keyboard) when I discovered it. The win installation on that machine used to have an ATI card, now it uses an NVIDIA...so I´ll roll back the NVIDIA driver to a previous release and re-check.

    Why are we wasting our time with this .... uglyness???

  • It is ugliness, but the NVIDIA driver rollback finally saved me from over a week of changing security settings, uninstalling and reinstalling XP SP3, etc. RDP is working again.

  • rolled back nvidia driver and sure enough rdp working now...can't beleive it great work and thanks a mill

  • Had this problem on a XP Professional box with ATI graphics card. Updating the driver fixed the problem.

    Thanks a lot.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment