After the. NET Framework update is installed, the Remote Desktop solution cannot be implemented.

Previously, when Windows XP SP3 was used, the Remote Desktop could not be used after vs2008 was installed. Later, there was no way to reinstall SP2, and the problem was unknown.

Today, Windows 2003 is patched and cannot be connected after it is restarted. Later, I saw an article on the Internet.ArticleThe problem is finally solved.

To:

After windows is updated, the Remote Desktop cannot be connected.

Run the netstat-An command to check whether port 3389 is on.

View System logs and find the "pop-up application"Program: \ Systemroot \ system32 \ rdpdd. dll failed to load ".

I checked a lot of information online and said it may be caused by the ATI or NVIDIA graphics card driver. However, I have not updated the graphics card driver recently.

It is caused by Net Framework 3.0 SP2. This is possible because the patch has just been installed.

Follow the solution below:

Open the registry:

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

Add a "DWORD" with a hexadecimal value of 20.

"Sessionimagesize" = DWORD: 00000020

Where 00000020 is hex for 32

After the machine is restarted, the Remote Desktop can be connected again.

The following is the solution URL:

Http://blogs.technet.com/brad_rutkowski/archive/2008/01/04/systemroot-system32-rdpdd-dll-failed-to-load.aspx

 

The solution is as follows:
1. temporarily disable the firewall on your computer.

2. When the client cannot log on to the server of Windows Server 2003, ping the IP address and computer name of the server of Windows Server 2003 from the client to check whether the server can be pinged. Click "Start> Run" and enter "cmd"> Ping-T **. ** (Server IP address) to check whether packet loss exists.

3. When a problem occurs, use other clients in the LAN to log on to the Windows Server 2003 server using the Remote Desktop to check whether the server is successful.

4. We recommend that you try clean Boot once to eliminate problems caused by third-party software.

A. Run msconfig.

B. Select selective startup under normal conditions.

C. Clear the check boxes for process system. ini file, process win. ini file, and load startup items, but retain the original boot. ini.

D. Under the service, first hide all Windows Services, and then select disable all.

E. Then restart. Check whether the problem persists.

5. Temporarily uninstall the installed SP2 patch on Windows Server 2003 to check whether the problem persists.

6. Set the value of ignorereguserconfigerrors.

A. Open Registry Editor.

B. navigate to the following subitem: HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server

C. Create a New DWORD Value in the window menu on the right.

D. Name the new value ignorereguserconfigerrors.

E. Right-click ignorereguserconfigerrors and click "modify ".

F. Set "value data" to 1 and "base" to "decimal ".

G. Exit Registry Editor.

End
For details, see MicrosoftCommunityAn article
Http://social.microsoft.com/Forums/it-IT/windowsserversystemzhchs/thread/5302ccb5-bb70-4a3d-8291-743fc7f005cd