Hi everyone. Yesterday, I started having problems with two programs that I'm using in Windows XP, File Manager (carried over from Windows NT) and Quickstart.exe, which is a service application used by OpenOffice 2.1. Neither program will run because when they're started, I get this message: (application filename) - Illegal System DLL Relocation The system DLL user32.dll was relocated in memory. The application will not run properly. The relocation occured because the DLL C:\WINDOWS\System32\SHELL32.dll occupied an address range reserved for Windows System DLLs. The vendor supplying the DLL should be contacted for a new DLL. I traced this problem to an errant Windows Update, rolled back to April 3rd and turned off Windows Update. It's the only way to make File Manager and Quickstart work. This is similar but NOT THE SAME as the problems with Realtek software. This has been suggested and has fixed some people's Illegal System DLL Relocation errors, but mine seem to be slightly different and affecting more software. I don't know if any other programs are affected. I have already applied the Microsoft Hotfix that fixes the Realtek issue but it doesn't work in my case. ================================= I'd like to figure out if I'm the only one having these problems. If anyone else out there is using File Manager (particularly the NT version) under Windows XP, can you tell me if you can still use it after the April 3rd updates? Is anyone else using OpenOffice 2.1 and having problems of any kind after the April 3rd updates? This problem is starting to drive me nuts :-( Any help would be very much appreciated.

Why don't you just remove the update or perform a restore to a previous setpoint. There is a patch for that update but I don't know if it will fix your issues. This is just MS at thier finest.

get openoffice.org 2.2 to see if that helps.

Hi everyone; I found the cause of all the trouble, it was a 3rd party theme/reskinning program called Vista Inspirat that I was using, it made changes to Shell32.dll and evidently these were screwed up by Microsoft's changes in the April 3rd updates. When I uninstalled the program, it restored the default system dll files including Shell32.dll which I promptly allowed Windows Update to do with as it pleased. Anyway, a big thank you to the people who made suggestions. But the main point I would like to make in this follow up is this: Anyone whos using a 3rd party enhancement on their computer and started having trouble after the April 3rd updates, get rid of that program because it's likely to be causing the difficulties.