XP-Pro SP2 MELTDOWN!

ParatoOptimal

Golden Member
Jan 27, 2004
1,094
2
81
I have a dual boot sys with w2k sp4 and xp-pro sp2.

Things started moving slow in XP-Pro SP2 last night.

I rebooted and got ...

Window Title Bar =
Services.exe Entry Point Not Found

Window Message =
The Procedure entry point AssocIsDangerous could not be located in the dyamic link library SHLWAPI.dl

Window Title Bar =
Winlogon.exe Entry Point Not Found

Window Message =
SAME AS ABOVE

Window Title Bar =
lsass.exe Entry Point Not Found

Window Message =
SAME AS ABOVE

I have to RESET to reboot.

I haven't set any GoBack points.
Booting to the last known configuration that worked produces the same results.

Booting to Safe Mode produces the same results.

I can still boot into W2K SP4.
I'm the administrator in W2K SP4.
I can access folders on my XP-Pro SP2 partition.

It serves me well to be able to access those files.
I guess I'll be backing-up those files and reinstalling XP over the old or refreshing it, if that's what they call it.
If that doesn't work, I'll be reformatting that partition and reinstalling.

For some reason, I couldn't get my Ghost working with XP. People online tell me that my version should work.
 

ParatoOptimal

Golden Member
Jan 27, 2004
1,094
2
81
You mean a repair with my XP CD?
I tried that but it couldn't write to the SHLWAPI.dll file.

I tried to reinstall XP over the current installation and got the same error that it couldn't write to or it couldn't find the SHLWAPI.dll file.

 

corkyg

Elite Member | Peripherals
Super Moderator
Mar 4, 2000
27,370
239
106
Try it in SAFE MODE. You can't do anything to that file when it is in use.
 

ParatoOptimal

Golden Member
Jan 27, 2004
1,094
2
81
My original post notes that the same thing occurs when I attempt to boot in to Safe Mode.

I found others who had the same problem with SP1 here ...

http://www.techimo.com/forum/showthread.php?p=1921496&posted=1#post1921496

I've had SP2 and all updates working well for the last three years.
This occured after MS Update and McAfee Update made some updates.

Those who experienced this problem with SP1 replaced their SHLWAPI.dll file with one from their SP1 disc.
I don't have an SP2 disc. It didn't occur because of SP2 but because of the latest updates of last night.

I DL'd, downloaded, a new SHLWAPI.dll file from www.dll-files.com.
It's much smaller than my current file.
I can change the NEW file's attributes. I can copy it to anywhere EXCEPT where it belongs, in the system32 directory.

I boot from my XP-PRO CD and enter Console Mode.
When I attempt to delete the old file, it can't be found.
DIR shows that it IS there.
It's attributes are ARCHIVE.
When I attempt to change it's attributes, it can't be opened.

It seems that I'm destined to reformat the XP partition and reinstall from scratch.

I read where this problem when experienced with SP1 could have been due to a failure to reboot right after applying SP1.

Well, in my case, Windows Update made several updates at once.
If a reboot was needed after a particular individual update, I'm screwed. It's bound to happen again in the future if I start from scratch and allow the last three years of updates to take place including the recent ones that caused the problem.

Of course, if it just required me to reboot after the last bunch took place instead of continuing my work and rebooting later in the evening, then I could start from scratch and not do any work while three years of updates take place so I would know when to reboot right after the last update took place.
 

Sandan

Senior member
Oct 9, 1999
558
0
0
Wow.....Sounds like it time to format C and start from scratch. I would also try to find out which update was the culprit and make sure it doesn't automatically initiate. You could turn off automatic updates giving you some more control. Good Luck
 

ParatoOptimal

Golden Member
Jan 27, 2004
1,094
2
81
I can't boot into XP at all weather it's full mode or safe mode.

I can boot into W2K where I installed the unlocker program.