home hardware prices news articles forums photos user reviews
Go Back   Tech Support Forums - TechIMO.com > PC Hardware and Tech > Applications and Operating Systems
Join TechIMO for Free!
Register Blogs FAQ Members List Calendar Search Today's Posts Mark Forums Read
Topic: Hi ppl, Trying to fix brother in-laws pc.... He has WinXP Home... When it boots it gives this error.... WinLogon.EXE - Entry point not found. The procedure entry point AssocIsDangerous could not be located in ...
Reply Get bargains at  »  Dealighted.com
 
Thread Tools
Currently Active Users: 2244
Discussions: 186,224, Posts: 2,222,764, Members: 229,783
Old August 16th, 2003, 09:04 AM   Digg it!   #1 (permalink)
Member
 
Join Date: Feb 2003
Posts: 207
WinXP msgina.dll & shlwapi.dll problem...

Hi ppl,

Trying to fix brother in-laws pc....

He has WinXP Home...

When it boots it gives this error....

WinLogon.EXE - Entry point not found.
The procedure entry point AssocIsDangerous could not be located in the dynamic link library SHLWAPI.DLL

Click OK, then you get this one...

User InterfaceFailure.
The logon UserInterFace DLL msgina.dll failed to load.
Contact admin ect...Replace DLL or restore original DLL.

Search and found reference to win2000 server with this problem.

Search this site and found some but didn't see how they could help me salve this problem.

Cant boot into any safe modes.

Ideas plz.

Peace.

---Edit---
He had a Factory recovery disk so i booted that up, it gave me the chance to try xp restore option and rebooted, only to be told that hal.dll was missing so could not run restore. The next option was to re-install system files without a format. This worked.

Thanks to the ppl who took it on them selfs to read this.

Peace.
__________________
In the End, we will remember not the words of our enemies, but the silence of our friends.


Last edited by theonetruegod : August 17th, 2003 at 02:32 PM.
theonetruegod is offline   Reply With Quote
TechIMO.com Ads - Login or register for less ads.


Guest, Register Free! to remove this ad and get your tech support questions answered in minutes!
Old August 31st, 2003, 03:13 AM     #2 (permalink)
Junior Member
 
Join Date: Aug 2003
Posts: 2
I have the same error, how did you load the system files? I don't even have a dos prompt to do anything?

bbeh01 is offline   Reply With Quote
Old August 31st, 2003, 03:21 AM     #3 (permalink)
Mean Moderator
 
EvilRick's Avatar
 
Join Date: Oct 2001
Location: N of Music City, USA
Posts: 7,791
From what I read, you did just what was about the only thing to do . . . a "Do Over".



What I read.

EvilRick is offline   Reply With Quote
Old August 31st, 2003, 04:52 AM     #4 (permalink)
Junior Member
 
Join Date: Aug 2003
Posts: 1
Angry
winlogon failure with shlwapi.dll / msgina.dll errors

This is due to the installation of MS's Windows Updates, specifically (in this case) Service Pack 1 for XP (I've also read reports of Service Pack for IE causing a similar problem). MS's technical support line (US 1-800-936-4900) will provide free technical assistance in correcting the problem IF you have your Windows XP recovery CD (usually you get this with a new computer). Of course, you are going to have to insist on getting support from MS for the problem, because MS typically attempts to refer you back to the computer manufacturer who is contractually obligated to provide support for all preloaded software, Windows included. However, as this is a problem caused by a MS update to Win XP and not by the original software installation, MS is totally responsible - and I demanded that they assist with resolution of the problem. I did some research on the 'net (using my old 75 MHz Pentium and a 28.8 dialup, ugh!) and what appears to have happened during the "update" is that some critical files failed to be copied to the Windows\System32 folder during the installation of SP1 (shlwapi.dll and msgina.dll among them). The winlogon process WAS updated by SP1; when winlogon.exe runs, looks for these dll's, and finds mismatched versions, it fails to execute and XP fails to load.

Basically what it boils down to is that you won't be able to boot to a previous good configuration or boot into safe mode (other than Safe Mode with Command Prompt, and that only IF you're lucky). If you can boot to the NTFS command prompt, find the .cab file containing the Windows XP Setup program (setup.exe) and extract that file and run it, you should be able to do the repair installation (aka in-place installation) and restore XP to a usable condition. If your system originally came with XP preinstalled you'll typically lose all data in the All Users folder and default program templates and settings in the Default User folder, and you may be missing user-added Start menu shortcuts, items you've added to the Startup group, and documents, pictures, and music files in the Shared Documents folder. If you have made backups, of course, those can be restored without difficulty. There is actually a way to prevent these items being lost after a repair installation or recovery; it's a simple matter of deleting a .txt file from the \System32 folder *prior to the repair operation* (this can be done from the command prompt in Safe Mode with Command Prompt, or from the Recovery Console after booting from the Win XP CD). The command for deleting this file - a file created the first time Win XP was run on your computer, usually by the manufacturer - is as follows:

del /a /f C:\Windows\System32\undo_guimode.txt

(This assumes that C:\Windows is the folder where
Windows XP is located on your system. Replace with the correct path to the file, if necessary.)

I have some more information regarding this issue, but I won't include it here for the sake of those who don't need it/aren't interested. Feel free to email me directly <lady.erin@ukonline.co.uk> if you want the rest, or links to the sites where I found the information.

Cheers,

Erin
LadyErin is offline   Reply With Quote
Old August 31st, 2003, 07:27 AM     #5 (permalink)
Ultimate Member
 
lynchmob's Avatar
 
Join Date: Oct 2001
Location: Mid-Atlantic
Posts: 1,390
Quite the 1st post,erin. Very informative.
You dont happen to know Michael Chiew,do you?
Welcome to TIMO,Ladyerin and bbeh01
lynch
__________________
Seldom right,but never in doubt...

Last edited by lynchmob : August 31st, 2003 at 07:29 AM.
lynchmob is offline   Reply With Quote
Old September 1st, 2003, 07:56 PM     #6 (permalink)
Junior Member
 
Join Date: Sep 2003
Posts: 1
Send a message via AIM to freeflyinangel Send a message via Yahoo to freeflyinangel
Erin,
I have the same problem, but no recovery disk. Mine came with my computer. Could you please send me the details...or even the links where these could be found. I would appreciate it greatly.
thanks,
Angel
freeflyinangel is offline   Reply With Quote
Old September 4th, 2003, 12:03 PM     #7 (permalink)
Junior Member
 
Join Date: Sep 2003
Posts: 1
Hey guys-
Had the same issue last night- Called MS and worked with them for a bit over 3 hours- but got it solved.

First, yes- there is a problem with the installer... not sure what but as SP1 is updating your system, certain files get blasted...

To fix the problem without losing data due to a reinstall, you need to boot into a command line vai recovery disk or other means... You can go into recovery console with the XP disk or maybe even boot from a win98 floppy... not sure on that one-

Anyhow, you'll have to rename old files on the command line and then copy new ones back from another dir- once that is done, XP works as expected- well, it starts without error anyway.

BTW, the tech I worked with was awesome and indicated that this was such a recent issue that the notes he was working from to resolve this issue weren't on the knowledge base yet- but they would be soon.

Here are the steps...

XP / shlwapi.dll error after installing windows updates.
After installing service pack 1, and then installing some other updates (possibly
without rebooting) you get the error.

"Winlogon.exe. Entry Point Not Found The procedure entry point AssocIsDangerous

could not be found in the dynamic link library SHLWAPI.DLL."

<><><><><><><><><><><><><><><><><><><><><><><><><> <><><><><><><><><><><><><><>
*** Resolution ***

"Winlogon.exe. Entry Point Not Found The procedure entry point AssocIsDangerous

could not be found in the dynamic link library SHLWAPI.DLL."

You can only reboot after that.


1. Boot to Recovery Console.

2 . type the following commands
cd system32 [enter]

ren winlogon.exe winlogon.old
ren msgina.dll msgina.old
ren shell32.dll shell32.old
ren shlwapi.dll shlwapi.old

cd.. [enter]
cd servicepackfiles\i386 [enter]
copy MSGINA.DLL c:\windows\system32
copy SHELL32.DLL c:\windows\system32
copy WINLOGON.EXE c:\windows\system32
copy shlwapi.dll c:\windows\system32

if not there, expand from the cd

3 Type EXIT and hit enter

After I did the above, all was good. Hope this helps speed some of you along.
Best,
Patrick
pturner is offline   Reply With Quote
Old September 4th, 2003, 07:09 PM     #8 (permalink)
Junior Member
 
Join Date: Aug 2003
Posts: 2
How do i boot to the recovery console? Do i need the recover cd?
bbeh01 is offline   Reply With Quote
Old September 11th, 2003, 01:41 AM     #9 (permalink)
Junior Member
 
Join Date: Sep 2003
Posts: 1
Talking
Thanks Patrick

It worked like a charm. Thanks for saving us the late night call to Microsoft.
onramp1 is offline   Reply With Quote
Old September 12th, 2003, 11:05 PM     #10 (permalink)
Junior Member
 
Join Date: Sep 2003
Posts: 1
Cool
Thank You!

Thank you Patrick for your clear directions! Once I got the system booted, enough to access files, I followed them exactly with great success.

For those of you having trouble figuring out how to boot to the command prompt, consider what I did to get the job done.

Because the file system is NTFS, I was not able to boot using a Win98 floppy disk. What I did instead was take the main hard drive and change it to a "slave" drive. I then installed a new "master" drive and proceeded to install Windows XP Home Edition on the new drive.

Next, I booted off of the new drive and found that I was able to access all of the files on the original hard drive. After that I followed Patrick's instructions, except I had to change the drive letter to a 'd' where ever he mentioned 'c'.

The very last thing I had to do was to take the two drives out, return the original hard drive to its normal state, boot the computer and all was well.

Thanks again!
Bill
wjlloyd is offline   Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Posting Rules
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Most Active Discussions
Is It Just Me? (16968)
hi (7)
So GLAD winter's finally here !! (21)
FolderChat: Weekend time again! (284)
Folderchat Weekday thread (373)
Super folding (18)
Popular Online Pc Retailers (12)
AM2+/AM3 (9)
PSU recommendation, think mines is .. (14)
Recent Discussions
How to position dos window (0)
Super folding (18)
RETTEN.EXE missing (1)
HDMI Cables (6)
Is it worth the upgrade? (2)
Need advice from you experts... (2)
Help me to find Equivalent Powe.. (156)
Calculating KVA/MAX (7)
Why do you use "Vista".. (29)
Seald copy of windows 95 for sa.. (0)
Various items for sale (1)
Woot-off (5)


All times are GMT -4. The time now is 11:56 AM.
TechIMO Copyright 2008 All Enthusiast, Inc.



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28