msgina.dll error after updates - won't boot

[CR Optiker]

I'm running Windows 2000 Pro on one of my computers. This morning the
automatic update window popped up and I accepted the update. When it
finished and I tried to reboot, it failed withthe following two error
messages:

1. Title: MSTask.exe - Entry Point Not Found;

Message: "The procedure entry point FindExecutableW could not be located in
the dynamic link library SHELL32.dll"

2. Title: User Interface Failure;

Message: "The Logon User Interface DLL msgina.dll failed to load. Contact
your system administrator to replace the DLL, or restore theoiriginal DLL."

A digital picture of the two error message boxes is at
http://tinyurl.com/y9qbo9. Nice to have a digital camera around when you
can't do a screenshot!

Ther is a MSKB article that describes this with the solution at
http://support.microsoft.com/kb/836683. My temp file doesn't seem to be
encrypted since I can browse it and files from Linux. I've tried using F8
to get to the advanced options to boot to the last state before the update
per the MSKB article), but it won't boot - same error messages. I've tried
using two different boot floppies, but it doesn't recognize them as
bootable.

Linux is dual booted on that computer, so can get into the partition to at
least read it, but it's NTSF so can't write to it. I have the original
CDs, but don't know if that helps.

Any suggestions?

Thanks!
Optiker

 

[NewScience]

Can you boot into either of the Safe Mode or Safe Mode Command Prompt?
Somehow, something has modified you
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WinLogon
key.

Do you have any special Boot options - modified boot screen (Windows XP
scrolling bar screen) or modified Windows Welcome Screen?

 

[CR Optiker]

Can you boot into either of the Safe Mode or Safe Mode Command Prompt?
Somehow, something has modified you
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WinLogon
key.

Do you have any special Boot options - modified boot screen (Windows XP
scrolling bar screen) or modified Windows Welcome Screen?

[38 quoted lines suppressed]

I have no special boot options.

I haven't tried Safe Mode or Safe Mode Command Prompt. I have tried the
option that is supposed to revert back to the most recent working
configuration. I showed only one profile, and whne I tried it, it failed to
boot and gave the same error messages.

I am gradually getting down to wher I think I may be able to use the
original installation CD to enter a recovery console and ask to repair the
installation, and see where that gets me. Or, I am close to being able to
write to the Win2k NTSF drive with my dual booted Linux installation and go
in and replace the msgina.dll with a new one, h oping that maybe it somehow
was corrupted. There appears to be a msgina.dll in both the system32 and
system32\dllcache folders with the same size (and maybe same timestamp, but
not sure on that) as the replacement sent to me by somebody with a working
installation. So, maybe that's not the problem! My temp folder is not
encrypted, so the MS Knowledge Base article that says that's the problem
doesn't seem relevant,

Thanks! I'm slowly getting down to trying the installation disk recovery
mode, but will try the Safe modes as you suggest first.

Optiker

 

[NewScience]

It's funny because after I sent you that post reply, when I rebooted, I got
the same thing. Only I never got a Welcome Screen. The screen stayed black
and eventually a popup occurred telling me about msgina.dll.

When I rebooted in Safe Mode, I immediately open EVENTVWR.MSC to see what
the error was ... and surprise. The error actually came from lsass.exe.

I checked the rest of the system, using chkntfs c:, chkdsk c:, as well as
poking around in the registry and nothing.
So I took the chance and rebooted normally. Everything came up fine.

This seem to occur after a shutdown whereby Windows told me I had updates to
perform and the updates would be installed prior to complete shutdown.
After the system updated, shutdown (I didn't have the option to Restart),
the system wouldn't come up until I went thru what I mentioned above.

If you can reboot in Safe Mode Command Prompt ... the safest method since
the GUI interface does not come into place ... you can run a chkdsk /f c:
(you may wish to also try chkdsk /f /r c: from time-to-time for bad block
checking as well - just found this out about bad clusters).

Can you boot into either of the Safe Mode or Safe Mode Command Prompt?
Somehow, something has modified you
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WinLogon
key.

Do you have any special Boot options - modified boot screen (Windows XP
scrolling bar screen) or modified Windows Welcome Screen?

[38 quoted lines suppressed]

I have no special boot options.

I haven't tried Safe Mode or Safe Mode Command Prompt. I have tried the
option that is supposed to revert back to the most recent working
configuration. I showed only one profile, and whne I tried it, it failed
to
boot and gave the same error messages.

I am gradually getting down to wher I think I may be able to use the
original installation CD to enter a recovery console and ask to repair the
installation, and see where that gets me. Or, I am close to being able to
write to the Win2k NTSF drive with my dual booted Linux installation and
go
in and replace the msgina.dll with a new one, h oping that maybe it
somehow
was corrupted. There appears to be a msgina.dll in both the system32 and
system32\dllcache folders with the same size (and maybe same timestamp,
but
not sure on that) as the replacement sent to me by somebody with a working
installation. So, maybe that's not the problem! My temp folder is not
encrypted, so the MS Knowledge Base article that says that's the problem
doesn't seem relevant,

Thanks! I'm slowly getting down to trying the installation disk recovery
mode, but will try the Safe modes as you suggest first.

Optiker

 

[CR Optiker]

It's funny because after I sent you that post reply, when I rebooted, I got
the same thing. Only I never got a Welcome Screen. The screen stayed black
and eventually a popup occurred telling me about msgina.dll.

When I rebooted in Safe Mode, I immediately open EVENTVWR.MSC to see what
the error was ... and surprise. The error actually came from lsass.exe.

NewScience...I tried it. Here's (below) what I posted to grc.techtalk last
night where I have an active thread on this. As you can see, not doing it.
I'm about down to putting in ther Win2k installation CD and trying to do
the repair function.
-----------------------------------
(2) tried F8 --> Safe Mode (per suggestion on
microsoft.public.windows2000.general)

result - black screen, "safe mode" at corners, top center Windows 2000
info given as Build 2195, SP4Free

After n o activity, no cursor, for minuts, hit esc and got the same user
interface failure error as originally, but not the other message about the
entry point.

(3) tried F8 --> Safe Mode with Command Prompt (per suggestion on
microsoft.public.windows2000.general)

same as above in (2) except got a cursor and mouse active at what looked
like VGHA res. After minutes, got same error message as in (2).