Microsoft Knowledge Base Email Alertz

(836683) - After you install the MS04-003 security update that is described in Microsoft Knowledge Base article 832483, you may not be able to start your computer. Instead, you may receive the following error message: The Logon User Interface DLL Msgina.dll...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 836683 - Last Review: February 20, 2007 - Revision: 1.5

"Logon User Interface DLL Msgina.dll failed to load" error message after you install the MS04-003 security update

System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows Vista Solution Center

On This Page

SYMPTOMS

After you install the MS04-003 security update that is described in Microsoft Knowledge Base article 832483, you may not be able to start your computer. Instead, you may receive the following error message:
The Logon User Interface DLL Msgina.dll failed to load. Contact your system administrator to replace DLL or restore the original DLL.

CAUSE

This issue may occur when your TEMP folder, as specified by the TEMP environment variable, is encrypted.

The installer that the MS04-003 security update uses extracts its contents to a subfolder of the TEMP folder. If the TEMP folder is encrypted, the update files are not successfully copied to the Windows\System32 folder when you restart your computer. One of the files that the MS04-003 security update installs is required by the Microsoft Graphical Identification and Authentication DLL file (Msgina.dll). The Msgina.dll file is, in turn, required by the Winlogon service.

RESOLUTION

To resolve this issue, first restore your computer to a working state. After you successfully restart your computer, install the MS04-003 security update by manually specifying a nonencrypted temporary folder.

Note When you successfully restart your computer after you experience the issue that is described in the "Symptoms" section, the MS04-003 security update is not yet installed on your computer.

Part 1: Restore your computer to a working state

To restore your computer to a working state, follow these steps:
  1. When you receive the error message that is described in the "Symptoms" section, click Restart.
  2. Press F8 repeatedly as your computer begins to restart. This triggers the Windows Advanced Options menu.
  3. Use the arrows on your keyboard to select Last Known Good Configuration, and then press ENTER.

Part 2: Manually install the MS04-003 security update

To obtain and install the security update, follow these steps:
  1. Download the MS04-003 security update, and then save it on your computer. For additional information about how to download this update, click the following article number to view the article in the Microsoft Knowledge Base:
    832483  (http://kbalertz.com/Feedback.aspx?kbNumber=832483/ ) MS04-003: Buffer overrun in an MDAC function could allow code execution
  2. Install the MS04-003 security update by running the installation package with the /T: command-line switch. This switch permits you to specify an unencrypted location for the installer to extract the package contents to. For example, to install the English-language version of the MS04-003 security update for Intel-x86-based computers, and to extract the files to the C:\alternate_temp folder, type the following at the command prompt:
    file_path\ENU_Q832483_MDAC_x86.EXE /T:C:\alternate_temp

MORE INFORMATION

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

APPLIES TO
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Server
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Home Edition
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Data Access Components 2.8
Keywords: 
kberrmsg kbprb KB836683
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Mark Reported as Irrelevant  
Written: 4/28/2004 9:57 AM
The 'last know good configuration' didn't work for me. I found another article on the microsoft site that might do the job: http://support.microsoft.com/default.aspx?scid=kb;[LN];329316 However, I don't have a second machine running W2k w/ SP2 and I'm not sure why they don't publish the file (SP2 version of Msgina.dll) anywhere so I can download it... so I'm kind of stuck right now. Also, I wonder if there is any way to install SP4 via the command line since microsoft claims this is fixed with SP4.

Pissed Reported as Irrelevant  
Written: 7/8/2004 12:35 PM
The "last known good configuration" did not work for me either. This happened on one of our Mobile Wireless forklift PC's, that I cannot brak open without breaking my warranty, I have to ship back to the vendor at my cost and I need it to work now! I will lose the use of the unit for at least 1 week. Sorry that there is nothing helpful here--- it helps me to vent.

charlie Report As Irrelevant  
Written: 6/6/2005 8:37 AM
The "last known good configuration" did work for me. The computer still does not work as it should but I can now save what is needed before continuing with what I expect will be a clean install of windows XP. Thanks for the tip.

WebSpinner Report As Irrelevant  
Written: 12/22/2006 5:17 PM
I too did not have any luck with the last known good config option. I even tried using my windows disk to go to the recovery console but instead it takes me to a screen to try updating Microsoft Windows again. As it was progressing it stopped at the msgina.dll and said it could not copy the file...it gave me an option to skip it or end windows setup. i'll post back to let you know if i was able to atleast get to a logon screen after setup is finished...i'm not feeling very confident about it though.