Cannot Load Illegal Module Rdpwsx.dll

[Aleshia Ducharme]

Nowthe message has changed somewhat to:

This computer can't connect to the remote computer.

Try connecting again. If the problem continues, contact theowner of

the remote computer or your network administrator.Sincerely

Andreas

1014 TermServices

Cannot load illegal module: "C:\windows\system32\drivers\rdpwd.sys"I suddendly lost RDP connectivity to a Windows 2003 Server SP2 & XP Pro SP3

Box. I noticed that error in the event log. I copied rdpwd.sys from another

server that RDP was working properly, I replaced it, then rebooted the

server. This fixed it for me and I could RDP into the systems again. Hope this helps.

Hello,

I stood next to the server during reboot.

There are no error messages in the log.

When I let the server do its reboot there is no entry in eventlog that

TerminalServices have been started.

This obviously only occurs when I kill the service and then restart

it.

In

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService

\DependOnService

the entries are now:

RPCSS

TermDD

Still no RDP-Session possible.

Can't be because the server does not listen to 3389.

When and where is it being told to listen to the RDP port?

Why is there no error message when TermServices start but the port is

not being listened to?

S.th. goes wrong but is not recognized...

So what can I do?

Please don't tell me "re-install the server..."

All seems fine, just RDP isn't.Sincerely

Andreas

I'm not sure, but I think that initially, after installing SP2,

your server suffered from the problem described here:948496 - An update to turn off default SNP features is available

for Windows Server 2003-based and Small Business Server 2003-based

computers

that fits your description: After installing SP2 ... I could

not reach it through RDP.... At first the port 3389 was still being

listened on.... The server was kind of busy.Obviously, the situation has deteriorated after that, because now

it doesn't even listen anymore. To be honest, I've no idea what you

could do that you haven't already tried. Maybe apply SP2 once more,

and then the hotfix from 948496?

If that doesn't solve it, I think you will either have to call

Microsoft Support or re-install.

I would reinstall the server from scratch. Even if you would be

able to get rdp working (and I don't have a clue how), then you

would never be able to trust the server, because you've no idea

what has caused the problem and what more might be going on there.

And some of these services look really suspicious. An xbox game

port on a TS? Best to cut your losses and wipe it clean.

Hi Vera,finally I solved it.

I cleaned the services file (which to me looks like being standardized

by an automatic procedure).

There was always a virus scanner running and I scanned the server

without finding anything.

Before reinstalling the server (and some intricate software on it) if

figured to re-install modules.

So I threw out RDP-Tcp (again) then the HP Nework Configuration

Utility with its Teaming device (it is a HP Proliant server), then the

network adapters with the whole tcp-ip protocol.

After rebooting I re-installed and configured things one by one.

Finally I enabled Remote Desktop in System, Remote, Remote Desktop

(since installing and deleting Terminalservices disables RDP by

default).

In the end RDP worked.

Sincerely

Andreas

When you try to use a program on your computer, you receive an error that includes the User32.dll file in its description. This problem may occur for several reasons. This article contains general step-by-step methods that you can use to try to resolve this problem. The step-by-step procedures in this article will not take very much time to be completed.

This content is designed for a beginner computer user.

Windows stores instructions for graphical elements such as dialog boxes and windows in the User32.dll file. The User32.dll file is necessary to the operation of Windows. If this file is damaged, deleted, or removed, the system will no longer work correctly. If a program or a service accesses User32.dll incorrectly, the program or the service will not work correctly.

User32.dll errors are typically corrected by repairing the User32.dll file or by reinstalling the program, the hardware component, or the driver that is causing the error. If these procedures do not correct the User32.dll error, you can restore your computer to a condition before the error appeared by using the Windows System Restore feature.

Note If you cannot start Windows because of a User32.dll error, see the "Start your computer in safe mode and use System Restore" section.

Error messages are the most common symptom of User32.dll problems. User32.dll error messages describe the source of the error and indicate that the User32.dll file is involved in the error.

Here is an example of a User32.dll error message:

In this example, program refers to the name of a program that caused the User32.dll error message.

This article discusses some common causes of User32.dll error messages. Additionally, this article contains some common resolution methods. Start with the first resolution method, and if the problem that you are experiencing persists, go to the next method.

We recommend that you update your antivirus software after you run Windows Update. For more information about antivirus software that Microsoft supports, click the following article number to view the article in the Microsoft Knowledge Base:

You can also receive updates for Windows, Microsoft Office and other Microsoft applications in Microsoft Update. Microsoft Update brings you all the features and benefits of Windows Update plus downloads for other Microsoft applications that include Office. To use Microsoft Update, visit the following Microsoft Web site:

Under Recommended updates, click to select the Include recommended updates when downloading, installing, or notifying me about updates check box, and then click OK. If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.

For more information about how to schedule automatic updates in Windows Server 2003, in Windows XP, and in Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:

If the User32.dll error message appeared during or after you installed a program, a hardware component, or a driver, uninstall the program, the hardware component, or the driver. Then restart Windows, and reinstall the program, the hardware component, or the driver.

In Windows Vista: For information about how to reinstall programs, hardware or drivers in Windows Vista, click Start, click Help and Support, and then click Troubleshooting. You can also search for "uninstall or change a program," for "install a program," or for "installing new hardware."

In Windows XP: For information about how to repair programs, hardware, or drivers in Windows XP, click Start, click Help and Support, and then click Fixing a problem. You can also search for "add a program" or for "using add hardware."

It is best to let Windows automatically install drivers for your hardware. You should avoid manually updating a driver unless Windows is unable to find a driver for one of your devices, and you were able to obtain a driver some other way. Or, you may have to manually update a driver if technical support personnel ask you to install drivers from a disc or from the device manufacturer's Web site. If you decide to manually update a driver, follow these steps:

If you are not sure which programs on your computer are using User32.dll, use the Tasklist command-line tool to determine the programs that are currently using User32.dll. The Tasklist command-line tool displays the names of all programs that currently use User32.dll. To use Tasklist, follow these steps:

You can use Windows System Restore feature to restore Windows Vista and Windows XP to a time before you received the User32.dll error. For information about how to use System Restore in Windows Vista, visit the following Microsoft Web site:

306084 How to restore the operating system to a previous state in Windows XP

Important We recommend that you run Windows Update after you perform a system restore. For more information, see Method 1. We also recommend that you update your antivirus software after you run Windows Update. For more information about antivirus software that Microsoft supports, click the following article number to view the article in the Microsoft Knowledge Base:

If you cannot start System Restore, you can use Windows safe mode to start System Restore. For information about how to start Windows Vista in safe mode and to use System Restore, visit the following Microsoft Web site:

304449 How to start the System Restore tool at a command prompt in Windows XP

Use the Backup or Restore Wizard in Windows Server 2003 and in Windows 2000 to restore your computer to a time before you received the User32.dll error.For more information about how to restore Windows Server 2003 and Windows 2000, click the following article numbers to view the articles in the Microsoft Knowledge Base:

315396 How to troubleshoot startup problems in Windows 2000

Important We recommend that you run Windows Update after you perform a system restore. For more information, see Method 1. We also recommend that you update your antivirus software after you have run Windows Update. For more information about antivirus software supported by Microsoft, click the following article number to view the article in the Microsoft Knowledge Base:

If you try to perform the task that resulted in the User32.dll error message, and the error message persists, unfortunately this content is unable to help you any further. So, your next step is to see the "Advanced Troubleshooting" section in this article. If you must use advanced troubleshooting, and you are not an advanced user, you might want to ask someone for help, or you might want to contact Support:

3a8082e126