RTHDCPL.EXE -Illegal System DLL Relocation

My computer is now coming up with the following error after an update on my computer last night. It states System DLL user 32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLLC:\WINDOWS\system32\HHCTRL.OCX occupied an address range reserved for WINDOWS system DLLS. The vendor suppling the DLL should be contacted for a new DLL.
I am not sure how this can be rectified, please can you help.

V.

 

Hello vanpan and welcome to the Board,

Follow this thread - uninstall the MS patch.

http://www.windowsbbs.com/showthread.php?t=63637

Regards - Charles

 

http://support.microsoft.com/kb/935448/en-us

 

Charles,

In my case, there was no need to uninstall the update. I just used the patch that Microsoft put out (see the link in unicorne1's post) and the problem was fixed.

Mike

 

Hi Mike,

I know that now. When I made that post, this mess was just starting.

However, not all problems with this patch are RealTek related. There are other programs that this affected.

In really bad cases, systems can't boot up. This one might be an example, don't know yet. http://www.windowsbbs.com/showthread.php?t=63631

Regards - Charles

 

Charles,

I'm glad that the system I was working on only had the error message. I was just thinking that the patch would be a place to start if the system had RealTek installed. I was surprised by all the problems with the recent update when I came to this site. I didn't mean to disagree with you. I was just offering my solution.

Mike

 

Illegal System DLL Relocation

This error occurs right after downloading Windows Update 925902. The Hhctrl.ocx file that is included in Security Update 928843 and the user32.dll file that is included in Security Update 925902 have conflicting base addresses. This problem occurs if the program loads the Hhctrl.ocx file before it loads the user32.dll file.
The fix is: Go to URL: http://support.microsoft.com/kb/935448, and download the Fix. I had the same problem, and was advized about the correction. Works fine now.

 

Hi Mike,

I didn't think you were

In my post, I also linked to the first of these threads on this problem where all the subsequent "action" took place and the corrective MS patches are linked to.

Happy Easter Mike

Regards - Charles

 

Charles,

I was just hoping that I wasn't misunderstood. Glad I wasn't. I had a pretty good Easter. Hope yours was good also.

Mike