LogonUI.exe - bad image

Question

Every time I turn on my computer get these two messages, LogonUI.exe - bad image

C:\Windows\system32\RpcRtRemote.dll is either not designed to run on Windows or contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vender for support.

And the other is, userinit. exe - bad image

C:\Windows\system32\userenv.dll is either not designed to run on windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vender for support.

And this is every time I turn the thing on, the only way I can work with the computer is to do a systems restore, then the thing will come up to the desktop and work great the rest of the day, I turn it off for the night, and the next morning, I get those same two messages. If I can't get this fixed I will go back to EX, atleast that operating system works right first time every time.....

Answer 1

Hi,

The repair didn't work for me. Here are the step I had to go through.

0)

Search for solution on internet. No good solution were found.

1)

Since fixing this issue was taking me time and I wanted the issue to fixed now, I thought that re-install windows was the quickest way for me to solve the issue.

2)

So I proceeded in re-installing Windows. This formatted both of my hardDrive (I don't know why). I was expecting the first hardDrive to be formatted but not both of them... So I lost all my data since I backuped all my data on the second harddrive. Just in case you ask yourself the question, I really have two physical hardDrive.

3)

After the re-installation of windows Vista completed, I proceeded in installing Windows 7 Upgrade PACK (From Window Vista to Window 7)

Unfortunately, when I installed Vista, I didn't choose the same language as the upgrade pack. 

So, I reinstalled again vista with the same language and then I was able to install the upgrade pack.

4)

After that, I did all windows update available and other stuff like setting up anti-virus.

5)

After that, I tried a few software on the internet to recover the data lost on my second harddrive.

None where free, so I ended up buying one. That way I was able to recover a lot of my data.

(Sadly, Recovering my data took me a lot of time)

Conclusion)

Since that, I do not have the issue anymore.

However, I have another issue that isn't related that is as annoying as the issue was.

So in short, format and re-install fixed the issue.

Having a simple solution at step 0 would have saved my quite a lot of pain. This is why I reply in other to help you create that simple solution  that surely will help other.

Bye

Answer 2

Hi,

Userinit.exe, is a specifies the programs that Winlogon runs when a user logs on. By default, Winlogon runs Userinit.exe, which runs logon scripts, reestablishes network connections, and then starts Explorer.exe, the Windows user interface.

RpcRtRemote.dll, is an Remote RPC Extension.

Try the following methods and check if it helps.

Method 1:

I would suggest you to boot the computer in Safe mode and check if the issue persists.

Safe mode starts Windows with a limited set of files and drivers. Startup programs don't run in safe mode, and only the basic drivers needed to start Windows are installed.

Boot to Safe Mode: http://windows.microsoft.com/en-US/windows7/Start-your-computer-in-safe-mode

If the issue does not persist in safe mode, then perform a clean boot to check if any third party application is causing the issue, as clean boot helps in eliminating software conflicts. Follow these steps to start the computer in clean boot.

How to troubleshoot problems using clean boot in Windows: http://support.microsoft.com/kb/929135  

Note: Once you are done with the troubleshooting, perform the steps in “How to reset the computer to start as usual after troubleshooting with clean boot “to reset computer as usual.

Method 2:

I would suggest you to try creating a new user account and check if the issue still persists.

New user account will help us to find out if the issue is with the user account or the computer settings.

Create a new user account: http://windows.microsoft.com/en-US/windows7/Create-a-user-account

Check if the issue resurfaces in a new user account, if it doesn't then transfer the files from the corrupted user profile to the new user profile.

Refer to the following article for instructions:

Fix a corrupted user profile: http://windows.microsoft.com/en-US/windows7/fix-a-corrupted-user-profile

**Note:**I would suggest you to verify the activation status refer the following steps to verify that you are successfully activated.

a.     Click the Start orb, click Control Panel, click System and Maintenance, and then click System.

b.     Under Windows activation, you can view your activation status.

Keep us posted on the status of the issue.

Answer 3

to assume that Lenovo computers distributed a Windows 7 disc with every computer is very far fetched, so with that being said, performing "In place or Repairing install" becomes almost impossible, does it not?

For as many people that have encountered this exact "RpcRTRemote.dll" issue, I have to believe there's a fix out there somewhere, somehow, etc.

The only way I can get around this issue is to hold the F8 key during initial start up & then scrolling down to "load without signature verification" or something similar to that.

As you can obviously see, I am not all that computer literate, but I HAVE retained functionality (for now).

Should I leave well enough alone???

Answer 4

Have done that over and over again, same results, This is an ongoing problem, after I run system repair the computer runs normally, but when I shut down for the night then boot the computer the next morning, I have those same two error messages, then a black screen with a cursor only telling me that this software is not genuine  Is there a Microsoft patch that could be causing this, I am at the end of my rope on this one

Answer 5

Try running the system file checker to possibly resolve the problem. How to run the system file checker - http://support.microsoft.com/kb/929833

Jim