Link to home
Start Free TrialLog in
Avatar of APPUND
APPUNDFlag for United States of America

asked on

Cannot RDP into machine with error RDPDD.dll failed to load

cannot rdp into machine with with error RDPDD.dll failed to load
I have tried sfc /scannow
running xp sp 2
tried replacing with one from another computer in the system 32 dir.
Avatar of ottobock
ottobock
Flag of United States of America image

Hello,

It may have to do with an ATI driver, or something else. Please have a look here:
http://blogs.technet.com/brad_rutkowski/archive/2008/01/04/systemroot-system32-rdpdd-dll-failed-to-load.aspx

Good luck!
Avatar of APPUND

ASKER

tried rolling back display driver.
Hmm, every single thing I am reading refers to the display driver. Here's another EE post: https://www.experts-exchange.com/questions/23130548/Remote-Desktop-does-not-connect.html?sfQueryTermInfo=1+"rdpdd.dll+fail+load"

Maybe try going to the mfg website and downloading the newest drivers for your PC.

I also found a post mentioned to turn down Hardware Acceleration in display properties - maybe worth a try. Though it did not work for this particular case, it's very easy to try:
http://www.deskshare.com/Resources/articles/dmc_turnoffhardwareacceleration.aspx

One last thought - have you tried running Windows Updates to download and install the newest version of RDP? (newer versions cache credentials and such, a slightly different look to the icon as well)
Good luck - I'll keep looking around and post any additional info I may find.
ASKER CERTIFIED SOLUTION
Avatar of ottobock
ottobock
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Argorian
Argorian

a bit old, but maybe this solution can help someone.
It worked for me.

If you increase the size of the session image space then you can run remote desktop.

Add the following registry key:

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

"SessionImageSize"=dword:00000020
Just as an FYI for anyone running into this problem in the future, if you do not want to revert back to an old driver, the registry fix posted by 'Arqorian' worked flawlessly for me. Thanks!
I have an NVIDIA GeForce 8400 GS with driver version 175.16 installed
Is that 00000020 hex or decimal?
to: STS-Tech
That is hexadecimal
Thanks for the reply- I guessed it was, and it did fix the issue!
Is the fix to add a DWORD Value under the Memory Management key or to create a new key under Memory management?
DWORD, not Key.
If you have a SessionImageSize dword, just modify it- otherwise create a new one.

Good Luck.
Thanks STS... Problem solved!
NP- but credit (if not points) goes to Argorian.  Glad I could help, though.
The "SessionImageSize" fix worked just great for a wonky NVIDIA GeForce 9300 GE. Only required a restart. No driver un/re install needed!
It has worked great for me on 3 out of 4 machines. I still have one that has the same symptoms, but this fix has not taken care of it. I even tried to increase the session image size a little more and rebooted agsain, but it still won't paly nice. Any ideas??
Got and ATI video card laying around?  That'll either fix it, or let you know it's a different problem.
I will check it. Thanks!
Hmmm.... Just got a call from one of our techs. He just tried to apply the fix and it did not work, just like the machine I was working. I checked his settings in the registry and they are correct. I just checked the card and this machine has an ATI Radeon HD 2400 XT card in it. I also checked the machine I was working on and it too has the same card.

Do we think that changing the video card may still be the next step here?
Hold the phone peeps. We just downloaded the latest driver for this card and we are in! It was updated 10/04/09 and has fixed the RD issue with these machines.