\SystemRoot\System32\RDPDD.dll failed to load

re: \SystemRoot\System32\RDPDD.dll failed to load

Craig Landis — Fri, 23 Sep 2011 06:27:36 GMT

Just had this problem on a 2003 SP2 machine after installing an Nvidia driver that showed up in Device Manager with Driver Date: 9/17/2008 and Driver Version: 6.14.11.7813.

Adding SessionImageSize of 0x20 fixed it, but then I figured I would install the latest 280.26 series Nvidia driver. After rebooting from installing that version, SessionImageSize was changed to 0x30, and RDP still worked.

Then I wanted to see if SessionImageSize was still even necessary on this latest driver version, so I deleted SessionImageSize from the registry and rebooted, and RDP still worked.

I did a LiveKD to view the effective SessionImageSize with no registry value set:

kd> dd nt!MmSessionImageSize l1

808af27c 00800000

So it seems the newer video driver is able to load within the default SessionImageSize, but older drivers had issues where you had to increase it to accomodate them.

This is a pretty good explanation of what is happening:

Video Driver not Loading on Windows XP

blogs.technet.com/.../video-driver-not-loading-on-windows-xp.aspx

And a KB on it:

You are unable to RDP to Windows Server 2003 or Windows XP

support.microsoft.com/.../2511009

re: \SystemRoot\System32\RDPDD.dll failed to load

Amar — Thu, 14 Apr 2011 18:52:20 GMT

It Really fixed my problem too. 5 stars

re: \SystemRoot\System32\RDPDD.dll failed to load

Eivind Gussiås Løkseth — Sat, 30 Oct 2010 19:30:50 GMT

I couldn't fix this problem, so I made a tool to restart my home server without using any Windows credentials. The tool is published at codeplex, here: remoterestart.codeplex.com

re: \SystemRoot\System32\RDPDD.dll failed to load

schilon — Fri, 30 Jul 2010 07:37:08 GMT

Serwer 2003 z GF7300 po aktualizacjach Microsoft RDP przestalo dzialac

Wpis w dziennkiku:

Application popup: : \SystemRoot\System32\RDPDD.dll failed to load

Dzieki zmiany w rejestrze pomogly

po restarcie dziala

pozdr.

re: \SystemRoot\System32\RDPDD.dll failed to load

michael from munich (germany) — Wed, 17 Feb 2010 20:49:59 GMT

Thank you so much - i even managed to

solve the problem remote without

sitting in front of the server with

psexec ... regedit /s session.reg

Thanks!

re: \SystemRoot\System32\RDPDD.dll failed to load

Hacker — Tue, 02 Feb 2010 18:14:35 GMT

BTW I used that fix on Windows XP Pro SP 3.

re: \SystemRoot\System32\RDPDD.dll failed to load

Hacker — Tue, 02 Feb 2010 18:11:45 GMT

I used the registry hack thing and added the value on each computer (host) and it worked and fixed the problem. Thanks. Who would have thought that it was graphic issue. Saved me.

re: \SystemRoot\System32\RDPDD.dll failed to load

Jakob — Fri, 22 Jan 2010 12:21:35 GMT

Thanks!

Driver roll back solved it!

(same problem as all the others)

re: \SystemRoot\System32\RDPDD.dll failed to load

Mike Klingler — Fri, 15 Jan 2010 19:22:07 GMT

Thanks for this post!

I searched for days trying to figure out what group policy, registry setting, etc, etc. etc. might have changed to cause this problem. Everything on the network worked fine except remote desktop.

After much searching I came across this blog in one of my hundreds of google searches. I had tried about everything I could think of, including updating motherboard chipset drivers, BIOS, network card driver, etc. I didn't even have the slightest thought that it might be the video card driver. Silly me!!!

The problem with just updating every driver on your machine, is that I have often had new problems show up after updating drivers, so I make it a policy to not update drivers if everything is working OK, If it ain't broke, don't fix it mentality. In this case this mentality stopped me from installing a video card driver even though I knew one was available because I didn't have a video problem, I had a network problem.

Again, thanks for this blog, I'm sure I'd have still been searching! :-\

re: \SystemRoot\System32\RDPDD.dll failed to load

Mike Klingler — Fri, 15 Jan 2010 06:10:15 GMT

Updating the ATI driver worked for me.