WinXP msgina.dll & shlwapi.dll problem...

[sam]

ok i did not read all posts sorry but if you need to fix a .dll file look here for it and just download it again http://www.dll-files.com/

[uk nat 2003]

FIXED IT!

For anyone else who can't boot into XP,safe mode, or the recovery console because you have the System File Corrupted or Missing message then I recommend you use the script found on this Microsoft page:

http://support.microsoft.com/default...b;en-us;307545


There you'll find a script to repair your SYSTEM files, although you have to manually enter each line and not use the BATCH command (as that batch command is only available in the Recovery Console).

In my case I only had to use the single command line that copied SYSTEM.


Also download the Emergency Boot CD from here http://www.t4k.org/~ebcd/

and use that to boot your computer. I think everyone should have a copy of that CD lying around, personally. It's been a lifesaver too many times for me to count.

[M3T4L]

Ok, I was trying this method with the 6 boot disks and going into Repair mode. When I try and access the system32 folder on C: it tells me that there is no floppy disc or cd in the drive, although there is a Windows XP cd in there. Anyone else get that? By the way, my Hard Drive is on Raid 0. Any kind of help would be appreciated. Thanks

[tongle]

I had this problem and I was able to use last known good configuration, and I'm back on my comp. I don't know the after effects it might have, but I deleted the update file cuz I hate it now.

[aqueryus]

hi folks

in my quest to resolve this most aggrivating of problems, i saw the great advice you all have posted regarding the grief the latest service pak has caused.

i have a 1.2mHz AMD Duron, 128mB based pc with XP pro. it was running on a network that belongs to one of my clients for about 3 months. it was brought to me because it stopped booting.
i noticed the office was running yahoo messenger and also some kazaa/limewire stuff at the time they called me out. so i'm thinking .... hmmm virus..worm...??

well, it turns out after managing to boot to safe mode, i ran a complete scan with updated Norton 2002 and indeed found IRCtrojan virus. i followed norton procedures to remove the infection and managed to boot normally. however the pc continued to experience pop ups at a rate that was extremely unacceptable...rather than go thru the adware route. i decided to cut bait and scrap the entire thing and start from scratch. at this point happy to have retrieved the data off the disk.

deleted partition using xp disk, completely did a fresh install of XP pro, OFFICE XP, Calyx Point, Norton 2002 with latest update, and Adobe Acrobat. Then I updated XP with the latest service pak and security patches and all was well for a few hours until next day client reported that the computer was no longer booting again!

this time errors i received were exactly the same errors reported by patrick and the others on this thread, referencing the shlwapi.dll and winlogon following wtih failure to boot. i followed patrick's instructions to the letter renaming the old files and copying from the servicepack directory but no luck - although the error messages i was getting finally disappeared th pc would not boot passed the initial xp splash screen.

all i get is the mouse curser and a blank black screen once the little hourglass disappears. thinking that perhaps the dll files in question were somehow corrupt. i tried copying them from a different working XP computer and repeated the procedure above but still the pc won't boot, not even to safe mode darn it!

i have already spent a good 8 hours over the last 3 days dinking around with this darn thing and was hoping to avoid having to go through the whole clean install process again. i have not tried with fdisk/mbr or anyother low level format stuff, not sure if i should.

should i attempt to just reinstall XP over the old installation or let xp go through the automated repair process? will my data and settings be erased??? any advice is certainly welcome, for now i'm going to get a few hours sleep and move on to something else for a while. my brain is fried!

dreaming of the day that microsoft will finally get it together and clean up their buggy crap!

take care and thanks ahead for your help

/gisela

i'm from the hitchcock school, rather than freddy vs. jason ~rufus wainwright 2003

[kanmott]

Thanks all for your information!!!

After trying unsuccessful to follow all of the advice...I stumbled on this simple solution...Restoring Windows to a previous time...it seems to be working...for now, though I'm sure I will have to keep a look out for Q811493 so that I don't have the problem again.

If you can log-in to Windows...the screen will be blank

"Control + Alt +Delete" (will activate the Windows Task Manager)
from the File Menu select "New Task/Run.."
Click "Browse"
Select the "Local Disk (C"
"Windows"
"System32"
"Restore"
"rstrui"
"Open"

Hopefully the intro page for the Windows Restore will come up...you might have to click OK several times on the "AssocIsDangerous" message, but it should go away.
From there select a time when you know your computer was working last (I went back about a week).

Follow the instructions provided by Restore and the problem should go away. An most of your files should be safe and retriveable. Make sure, however to keep and eye on future updates because I think all I did was undue that install and it will probably come back...though I don't know.

Good luck

[bearb3ar]

Originally posted by sarahfelfel
hey everybody
this is sarah again, look 3 notes above.
finally i fixed mine. to access to my c drive i made a update windows disks (about 6 disks). then i boot the computer from a removable device (A) and put disks one by one. do not worry it won't delete your data. from there i accessed to my c:. then i burned a cd with all those 4 files that patrick has mentioned and everything worked fine. i burned cd because i was not able to copy stuff into system from the A.

thank you everybody.
Cheers *-:

These were the original instructions for us:

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] ****AT this point I could not execute cd.. [enter] by elimination I found out that cd .. works. Don't forget the space after cd
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

then remove the diskettes and type EXIT [enter]




Thanks to you guys for your tips... I thought my data was smoked.

[peterv]

hello all.

after taking all the steps "patricks way" it stops with the following message (translated from dutch)
unable to find entrypoint of procedure UninitialiseCriticalSection in DLL file Kernel32.dll.


i dit the same with the kernel file as in patricks method with the other 4 mentioned files, but no sccs.
anyone any idea??


help really wanted here

peter

[jnaeem]

Hi all.

can someone please explain how i can create the 6-disk to boot? i have downloaded the file on my comp at work, however i cannot save it on the floppy. the file is 2 big. i do have 6 floppies, but don't know how to save them.

thanks in advance

[Novagator]

Originally posted by bearb3ar



These were the original instructions for us:

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] ****AT this point I could not execute cd.. [enter] by elimination I found out that cd .. works. Don't forget the space after cd
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

then remove the diskettes and type EXIT [enter]




Thanks to you guys for your tips... I thought my data was smoked.

That worked perfectly Thank you very much, you guys are a life saver!! I was tired of rebuilding my laptop, why they don't put recovery console on the rebuild cds from HP, it beyond me.
Once again, thank you!