Sign in with
Sign up | Sign in
Your question

rdpdd.dll problem

Last response: in Windows XP
Share
Anonymous
April 30, 2005 1:25:14 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I have a freak problem with Remote Desktop under WinXP Pro SP2. When I try to
open a session, it says connecting for a few seconds and the window then just
closes without an error message. The machine I'm trying to connect to then
records the following error message 8 times in the system event protocol:
Application popup: : \SystemRoot\System32\RDPDD.dll failed to load
So the remote desktop display driver won't load on the host machine...But
why??
The dll itself seems to be fine. I ran system restore. It's version
5.1.2600.2180 and a file size of 92,168 bytes.
The machine has all the latest patches and all the latest drivers.
This problem started around the time when MS released its latest security
patches. Around that time, I also updated my nVidia display drivers to the
then newest version (installed the newest one just yesterday). I can't
remember whether it still worked after installing the newer nVidia drivers,
or not. I think it did.

Any ideas?

Patrick Schmid

More about : rdpdd dll problem

Anonymous
April 30, 2005 8:59:28 PM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Try going back to a restore point created prior to updating the nVidia drivers.

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...


"pdschmid" <pdschmid@discussions.microsoft.com> wrote in message
news:78EF6C02-367A-48BB-9C72-79CDF78D5F55@microsoft.com...
>I have a freak problem with Remote Desktop under WinXP Pro SP2. When I try to
> open a session, it says connecting for a few seconds and the window then just
> closes without an error message. The machine I'm trying to connect to then
> records the following error message 8 times in the system event protocol:
> Application popup: : \SystemRoot\System32\RDPDD.dll failed to load
> So the remote desktop display driver won't load on the host machine...But
> why??
> The dll itself seems to be fine. I ran system restore. It's version
> 5.1.2600.2180 and a file size of 92,168 bytes.
> The machine has all the latest patches and all the latest drivers.
> This problem started around the time when MS released its latest security
> patches. Around that time, I also updated my nVidia display drivers to the
> then newest version (installed the newest one just yesterday). I can't
> remember whether it still worked after installing the newer nVidia drivers,
> or not. I think it did.
>
> Any ideas?
>
> Patrick Schmid
Anonymous
May 1, 2005 10:09:15 PM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Also try running sfc /scannow to make sure that the particular DLL is
not corrupted...
Related resources
Anonymous
July 14, 2005 12:06:01 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I am having this problem also, but for about a week it went away and now it
has returned. I don't have a restore point that goes back to when I first
noticed it, and sfc /scannow didn't help (although it did seem to need to
replace some files because it requested the cd).

Is there any way to force remote desktop to create some more debugging
information?

Thanks everyone.

"pdschmid" wrote:

> I have a freak problem with Remote Desktop under WinXP Pro SP2. When I try to
> open a session, it says connecting for a few seconds and the window then just
> closes without an error message. The machine I'm trying to connect to then
> records the following error message 8 times in the system event protocol:
> Application popup: : \SystemRoot\System32\RDPDD.dll failed to load
> So the remote desktop display driver won't load on the host machine...But
> why??
> The dll itself seems to be fine. I ran system restore. It's version
> 5.1.2600.2180 and a file size of 92,168 bytes.
> The machine has all the latest patches and all the latest drivers.
> This problem started around the time when MS released its latest security
> patches. Around that time, I also updated my nVidia display drivers to the
> then newest version (installed the newest one just yesterday). I can't
> remember whether it still worked after installing the newer nVidia drivers,
> or not. I think it did.
>
> Any ideas?
>
> Patrick Schmid
Anonymous
July 28, 2005 2:23:48 PM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I found the problem. It was the av.dll from Trillian. Ultravnc locked up my
system when Trillian loaded so I was able to figure out the issue with that,
but remote desktop works fine now also.
I renamed the dll and everything is ok now.

"Andrew Martin" wrote:

> I am having this problem also, but for about a week it went away and now it
> has returned. I don't have a restore point that goes back to when I first
> noticed it, and sfc /scannow didn't help (although it did seem to need to
> replace some files because it requested the cd).
>
> Is there any way to force remote desktop to create some more debugging
> information?
>
> Thanks everyone.
>
> "pdschmid" wrote:
>
> > I have a freak problem with Remote Desktop under WinXP Pro SP2. When I try to
> > open a session, it says connecting for a few seconds and the window then just
> > closes without an error message. The machine I'm trying to connect to then
> > records the following error message 8 times in the system event protocol:
> > Application popup: : \SystemRoot\System32\RDPDD.dll failed to load
> > So the remote desktop display driver won't load on the host machine...But
> > why??
> > The dll itself seems to be fine. I ran system restore. It's version
> > 5.1.2600.2180 and a file size of 92,168 bytes.
> > The machine has all the latest patches and all the latest drivers.
> > This problem started around the time when MS released its latest security
> > patches. Around that time, I also updated my nVidia display drivers to the
> > then newest version (installed the newest one just yesterday). I can't
> > remember whether it still worked after installing the newer nVidia drivers,
> > or not. I think it did.
> >
> > Any ideas?
> >
> > Patrick Schmid
!