SystemRootSystem32RDPDD.dll failed to load
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 https://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 https://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: Windows 2003, RDP, SP2
Comments
Anonymous
January 01, 2003
PingBack from http://geeklectures.info/2008/01/04/systemrootsystem32rdpdddll-failed-to-load/Anonymous
January 01, 2003
It's actually a problem with the card/drivers not with the OS.Anonymous
January 01, 2003
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/.../2511009Anonymous
January 01, 2003
Alright glad it helped!Anonymous
January 09, 2008
I only had this problem after installing .NET 3. on W2K3-SrvHunSP2+Term Serv. Ati driver adjusting solved it. Thx!Anonymous
January 24, 2008
The comment has been removedAnonymous
March 06, 2008
The comment has been removedAnonymous
March 25, 2008
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.Anonymous
May 15, 2008
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.Anonymous
May 29, 2008
The comment has been removedAnonymous
May 29, 2008
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.Anonymous
May 31, 2008
Same here in Germay. After Nvidia Update. RDP stopped.Anonymous
June 01, 2008
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???Anonymous
June 03, 2008
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.Anonymous
June 05, 2008
rolled back nvidia driver and sure enough rdp working now...can't beleive it great work and thanks a millAnonymous
June 06, 2008
The comment has been removedAnonymous
June 07, 2008
The comment has been removedAnonymous
June 07, 2008
Same here. 175.16 broke RDP for me. I rolled back the driver and it works now. As of this time 175.16 is still the latest driver. Thanks for sharing, guys.Anonymous
June 10, 2008
so which version is working for you guys?Anonymous
June 10, 2008
I'm using the nVidia 175.16 drivers, and am experiencing the same thing; yesterday it worked for one connection, after disconnect I can no longer connect. I'll just stick with VNC until they fix the driversAnonymous
June 19, 2008
Same issue after upgrading to Nvidia 175.16, really a pain because Spore is crashing with older drivers... then again, maybe I've created enough unnatural freaky creatures until the game comes out.Anonymous
June 20, 2008
Great info! I had Nvidia 175.16 driver version as well and could not remote into my PC. Once I installed driver version 6.14.11.6921 (12/5/07), I was able to remote into my PC. Thanks for the help!Anonymous
June 23, 2008
The Nvidia driver 175.19 released today has no resolution for this issue. My PC is only one of over 300 with Nvidia GeForce 6200 TM (but the only one with XP SP3), RDP is an often used feature. So we must avoid to install/build in this and the former driver over/in our RIS or WDS image for XP with integrated SP3 installations. Thank you NVidia :-( ReinhardAnonymous
June 24, 2008
install nvidia drivers 169.21 if you want remote desktop to work, nvidia still doesn't know how to make proper drivers and apparently microsoft doesn't know how to test drivers either.Anonymous
June 24, 2008
Just so its recorded somewhere. I was having a problem with my XBOX 360 connecting to my Media Center PC, it would just hang on the "Contacting . . ." screen. I had updated my NVIDIA card with the 175.19 driver recently and this seems to be the problem. Rolling back to the previous driver resolved my XBOX problem as it seems to rely on this same DLL to connect and show Media Center on my TV via the XBOX.Anonymous
June 27, 2008
Using nVidia 175.19 and having a similar problem. Rebooting fixes it for a while but then it returns. Anyone know where I can get an older version of the nVidia drivers for a GeForce 6800GT? thanks!Anonymous
June 30, 2008
The comment has been removedAnonymous
July 03, 2008
Thanks! Upgrading the nVidia driver fixed the problem for me. Who'd a thunk it ...Anonymous
July 10, 2008
The comment has been removedAnonymous
July 11, 2008
this just happened to me after i installed and rebooted http://pastebin.com/d75e1941e i'm running windows xp pro sp3.. this is REALLY odd..Anonymous
July 14, 2008
yep looks like a confirmed bug, was scouring the nvidia forums and found this: http://forums.nvidia.com/index.php?showtopic=67147&hl=remote+desktop I managed to use the drivers here http://www.laptopvideo2go.com/forum/index.php?showforum=94 and it fixed itAnonymous
July 15, 2008
The comment has been removedAnonymous
July 18, 2008
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_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory Management] "SessionImageSize"=dword:00000020 Where 00000020 is hex for 32Anonymous
July 18, 2008
The comment has been removedAnonymous
July 21, 2008
The comment has been removedAnonymous
July 21, 2008
The comment has been removedAnonymous
July 25, 2008
The comment has been removedAnonymous
July 27, 2008
same error for me. this was a life safer!!!!Anonymous
July 29, 2008
The comment has been removedAnonymous
July 30, 2008
Still getting this problem with 175.19 and RD. I'm not getting any system events when the login fails. I've checked my registry and that key doesn't exist, does anybody know if it's been renamed with SP3? I have SessionViewSize (defaults to 30) and SessionPoolSize (defaults to 4). Thanks a lot.Anonymous
July 30, 2008
This RDP issue began recently for me with our last influx of new workstations. They all have the newest Nvidia GeForce 98000 GTX graphics cards. Since disabling the graphics accelerator is not a option for us and I don't subscribe to using a earlier drivers I tried adding the registry key first. It solved the problem. I think I am going to call Nvidia about this. Thanks for everyones input. Very helpful. Steve BanfordAnonymous
August 05, 2008
Fix didn't work for me, although their 177 beta drivers did fix it. Seems they either know about it or it fixed itself. -ianAnonymous
August 19, 2008
http://www.nvidia.com/object/winxp_177.79_beta.html 177.79 beta solved it for me. xp sp3 w nvidia 8600 gtsAnonymous
August 27, 2008
The fix to add the registry key (no it doesn't exist beforehand) also worked for me. (And I wouldn't be typing this if it didn't.)Anonymous
August 30, 2008
This also fixed my loss of ability to print via LPR (Brother HL-1250, in case that's relevant and people are searching for a solution). I lost that, and remote desktop, after updating nvidia's video drivers.Anonymous
September 04, 2008
The comment has been removedAnonymous
September 10, 2008
The comment has been removedAnonymous
September 15, 2008
It did not work for me. (Nvidia-Card, XPSP3) MatthiasAnonymous
September 15, 2008
I started getting this problem on a computer I just built. It is an AMD X2 and a gigabit mobo with, this is the important part, on board ATI radeon hd3200. I did not disable hardware acceleration because of games I play, but I found installing the latest drivers from ATI's site fixed the problem. Solution for ATI? Get updated drivers.Anonymous
September 16, 2008
The comment has been removedAnonymous
October 01, 2008
I downloaded Nvidia 178.13 today (released Sept 25, 2008) and it solved the problem for me.Anonymous
October 09, 2008
Nvidia 178.13 also solved the problem for me. Amazing.Anonymous
October 10, 2008
I had this exact problem with an older (as of 10/10/2008) version of the NVIDIA drivers running on a GeForce 8600 controller. After installing the vresion 178.13 drivers, it is now allowing RDP sessions in. NOTE: We are also running this XP Professional station in /3GB mode.Anonymous
October 11, 2008
The comment has been removedAnonymous
October 15, 2008
Ca a marché pour moi apres un reboot! Merci beaucoup!Anonymous
November 03, 2008
This did the trick. Thanks. Add the following key: [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory Management] "SessionImageSize"=dword:00000020 Where 00000020 is hex for 32Anonymous
November 04, 2008
Cool!!!! Finally, after several months of only having VNC as a ways of getting to one of my boxes, I can finally use RDP again :)Anonymous
November 11, 2008
Very very happy I found you pages!! The regedit solution works for my Nvidia 8200, now RPD and Home Server Console are up and running again.Anonymous
November 12, 2008
Wow...this had been troubling me for a week+. I could RDP out to anything, but I was not able to connect to my machine using RDP from home, which was actually incredibly poor timing for it to fail. The day before, I installed a SQL Server test package on my machine which had required .NET 3.5 so I could learn more about SQL. I had installed SP3 a few months back, and had no connection issues until the .NET 3.5 was installed. I installed the latest ATI video drivers and it works fine now. THANKS!Anonymous
November 13, 2008
I was having the same problem described with my Nvidia 6600GT. I had display driver 175.19... Upgraded to 178.24 and now Remote Desktop works fine! Love, Doug.Anonymous
November 19, 2008
Thanks for the post. the registry fix took care of my problems without playing video driver rouletteAnonymous
November 24, 2008
Tried to paly with drivers, that did not help. However, reg fix did the trick! Thanks a lot!Anonymous
December 03, 2008
welp.. nothing is working for me. reghack nor the hardware acceration( which doesnt help since i want to use my 8800GTX. ). Mine however disconnects on connection but leaves no error in the logs. Back to vnc i guess.Anonymous
December 09, 2008
Great info - I have been updating my system so I can run GTA IV, and found that RD stopped working in the same fashion you described. The registry setting worked splendidly (disabling hardware acc or rolling the video driver back really isn't an option for those of us who play games).Anonymous
December 16, 2008
I would just like to say that this article has really got me "out of a pickle" as my MD has just got a new home PC and wanted to connect to it - but couldn't and she was not amused ! My IT company told me it was a problem with rdpdll.dll but their solution was too complicated for me to follow. So I searched and found this simple article .... and voila, problem solved 100%. Thank you so much. Regards, Julia Evans - IT Support Co-ordinatorAnonymous
December 16, 2008
Another possible fix: On the problem server I turned the colour quality settings from 32 bit down to 16bit. Immidiatly worked. Give it a try!Anonymous
December 27, 2008
The comment has been removedAnonymous
January 01, 2009
The comment has been removedAnonymous
January 02, 2009
The reg trick also worked for me. This bug has been affecting my pc for days!!!Anonymous
January 10, 2009
Thank you. In the process of trying to implement the fix, I discovered that NVIDIA released a new version of the river yesterday that fixes the problem. 181.20_geforce_winxp_32bit_english_whql.exeAnonymous
January 21, 2009
OK, I've found another, non-registry, non-driver or reboot related way in. Last few times it's happened to me, I've found that if I click the black screen repeatedly before the error dialog appears (as the screen is being updated) then it doesn't kick me out. Sounds odd, but seems to work if you're stuck with no other option.Anonymous
January 28, 2009
I just installed 181.22_geforce_winxp_32bit_english_whql.exe and this killed RD on my GeForce 8500 GT.Anonymous
January 28, 2009
The registry fix works also for the 181.22 driver :)Anonymous
January 28, 2009
Now, with the 181.22 driver and the registry fix, I get a "SystemRootSystem32ATMFD.DLL failed to load" message, but Remote Desktop works.Anonymous
January 29, 2009
Thanks, installing NVidia 181.22_geforce_winxp_32bit_english_whql on my system fixed the RDP issue but broke some Magic Rotation software that I installed with my new 26" Samsung monitor. I believe it is the desktop rotation software that broke RDP. I wish I had known I would have tried uninstalling that first to see if the issue was fixed.Anonymous
January 30, 2009
Updating my Radeon 2400 pro-drivers helped! This problem had been bugging me for days! Many thanks! /DonAnonymous
January 31, 2009
Registry fix causes Win32k BSOD sometimes , Brad mentioned above this. Any fix for this fix ?Anonymous
January 31, 2009
OK , correction - Win32k.sys was related to corrupted Cat 8.12 Everything's fine now - so far so goodAnonymous
February 04, 2009
Increasing the SessionImageSize did not work for me. Instead I was able to resolve the issue by removing the /3GB switch as mentioned in this KB article: http://support.microsoft.com/KB/942432 I tried increasing the desktop heap size to see if I could continue to use the /3GB switch, but it did not work. I ultimately had to remove the switch. Here are some articles on adjusting the desktop heap size: http://blogs.zdnet.com/Bott/?p=269 http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspxAnonymous
February 11, 2009
Many thanks for posting this! You saved me :-)Anonymous
February 12, 2009
Thank you so, so much. I rebuilt my media server recently and everything was go swimmingly installing drivers, etc, until, for apparently no reason, I was unable to remotely access the server from my other PC. I could do it the day before, but then experienced the symptoms above. I spent hours trying different things, searching the internet. I then started to stumble across websites suggesting it could be NVidia and then ATI drivers. Seemed bizarre to me, especially as I had the latest version (v9.1 at time of writing), but after removing hardware acceleration as suggested, it worked. Thanks again! PS Am I better off with the latest ATI drivers and Hardware Accn off? Or revert to Windows drivers and HA on?Anonymous
February 12, 2009
Thank you very much for the useful information! In my case, the RDP issue I had was because of the NVIDIA graphics driver I was using. Updating it with the latest drivers from NVIDIA's support site solved my problems. Thanks again for the blog!Anonymous
March 04, 2009
The comment has been removedAnonymous
March 09, 2009
Updating the ATI driver did solve the problem. Thanks Brad. SovathAnonymous
March 27, 2009
I had this same error appearing in the event log on a fresh install of XP on a new machine, after doing a Windows Update which included .net 3.5. Unfortunately it crashed the machine a few seconds after logon, every time. Suspected it was the display driver (ATI) as some screen corruption appeared alongsied the cursor as it froze. Rebooted in safe mode and applied the registry key you've added to the post, and all seems good. Thanks!!Anonymous
April 03, 2009
Congratulations on a job well done. Thanks. I am from Panama and bad know English, give please true I wrote the following sentence: "Cheap airline tickets vay - valerie weeks noah to replace her punish the peach cheap airline tickets vay - that is, the year use who does the progressive father." THX :-(, Slade.Anonymous
April 07, 2009
this saves my day, thanks for the solution.Anonymous
April 08, 2009
Although it wasn't an RDP problem this did help as it was a video driver issue that was locking up my PC! Good work!Anonymous
April 24, 2009
I had the exact same RDP symptoms as described above. However, by simply upgrading my Nvidia drivers to the latest release (April 02, 2009) and rebooting the problem was resolved. I am now again able to RDP as normal without any other changes required.Anonymous
May 12, 2009
Registry Fix at top worked. nVidia graphics driver was present but not updated. Cause most likely .Net Update from Microsoft Update.Anonymous
May 19, 2009
Option "d." just worked for me under XP SP3. Thanks!Anonymous
June 16, 2009
New drivers nvidia 185.85 fix the problem.Anonymous
June 29, 2009
Solution D worked for me as well. I had to restart the computer for it to work. I'm running XP SP3 and Nvidia drivers 6.14.11.7516.Anonymous
June 30, 2009
I cannot get it to work, none of the solutions given seem to work. Also, turning off hardware acceleration, driver rollback do nothing to solve te problem. I'm using a radeon 2400 XT. I cannot believe there is no fix from ATI for this problem as it seems to be going on for quite some time now (considering all the above reactions). I even do not get any error messages, nothing! I'm running a Windows XP Pro SP3 machine with ATI radeon Catalyst 9.6 drivers.Anonymous
July 28, 2009
I had the same error but on a Dell OptiPlex 960 with an nVidia 9300GE. Installing the latest nVidia driver worked for me.Anonymous
July 30, 2009
Patrick (or other) Do you need to upgrade the video driver on the Local (viewer) or Remote (server) computer? Thank youAnonymous
August 28, 2009
Really good blog! I downloaded newest nvidia Gforce drivers for 9 Series(9600 my card) On my HP Pavilion computer bought in Norway 2009. This fixed the problem! August 2009!Anonymous
October 15, 2009
"SessionImageSize"=dword:00000020 work for me! Thanks!!!Anonymous
November 11, 2009
After finding the error on the DLL in the event log I did a google and found this blog. A quick update of the NVidia drivers fixed the problem. Thanks MarkAnonymous
November 13, 2009
Dare I say it, "me too"!! SessionImageSize key corrected a problem we had been tearing our hair out over for 2 days, to one specific (older) machine. Our red herring thought it was networking and maybe RDC 5 vs RDC 6, it was only when i looked at the system logs from the server did i see the RDPDD.dll and that led me hear. Many Thanks...!Anonymous
November 18, 2009
Wow, it's November 2009 and this issue still persists, not yet addressed by MS, nVidia, Dell?? New Dell Optiplex 960 with nVidia GeForce 9300, XPSP3. Video driver change fixed here as well. Thanks to all for your posts.Anonymous
November 26, 2009
Con la agregada en el registro me anduvo perfecto, 1000 graciasAnonymous
December 13, 2009
I must say that I am glad to have found this blog. I have been fighting this since I setup a new WHS server in May 2009. I updated my NVIDIA drivers to 191.0 and can now use the WHS console and RDP from remote computers. THANKS!!!! BrianAnonymous
December 23, 2009
Registry fix worked for me. on a dell. fx5200 nvidia card tried latest update for video drivers with no fix, added the registry key and rebooted. all is well in the world of rdp again. cheers T.Anonymous
December 29, 2009
The comment has been removedAnonymous
January 14, 2010
Updating the ATI driver worked for me.Anonymous
January 15, 2010
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! :-Anonymous
January 22, 2010
Thanks! Driver roll back solved it! (same problem as all the others)Anonymous
February 02, 2010
The comment has been removedAnonymous
February 02, 2010
BTW I used that fix on Windows XP Pro SP 3.Anonymous
February 17, 2010
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!Anonymous
July 30, 2010
Serwer 2003 z GF7300 po aktualizacjach Microsoft RDP przestalo dzialac Wpis w dziennkiku: Application popup: : SystemRootSystem32RDPDD.dll failed to load Dzieki zmiany w rejestrze pomogly po restarcie dziala pozdr.Anonymous
October 30, 2010
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.comAnonymous
April 14, 2011
It Really fixed my problem too. 5 stars