Win2K to WinXP Upgrade Error

[James Farris]

Recently I tried to upgrade my Win2K Pro OS with WinXP.
Installation seemed to go fine but when everything was
finished and the system restarted I had to then select my
username (no option to enter anything differently) and
enter my password. At that time I received the
error, "The procedure entry point AssocIsDangerous could
not be located in the dynamic link library SHLWAPI.dll"
with a Title Bar saying "Explorer.EXE - Entry Point Not
Found".

I found and followed a Knowledgebase article that referred
to a similar problem with a different file and a slightly
different message which indicated you should perform a
repair and replace the file that is referenced which in
this case was "SHLWAPI.dll", I did this, with no
improvement. Next steps will be to start up in recovery
mode and copy the file via the floppy disk from another
W2K system and see if the older version of the file will
work. Any other suggestions would be greatly appreciated.

 

[Nicholas]

Did you run the Windows XP Upgrade Advisor prior to
upgrading to Windows XP Pro? It would have alerted
you to any software programs that may have a compatibility
issue with XP.

How to Perform a Windows XP Repair Install
http://michaelstevenstech.com/XPrepairinstall.htm

[Courtesy of Michael Stevens, MS-MVP]


--
Nicholas

------------------------------------------------------------------------


| Recently I tried to upgrade my Win2K Pro OS with WinXP.
| Installation seemed to go fine but when everything was
| finished and the system restarted I had to then select my
| username (no option to enter anything differently) and
| enter my password. At that time I received the
| error, "The procedure entry point AssocIsDangerous could
| not be located in the dynamic link library SHLWAPI.dll"
| with a Title Bar saying "Explorer.EXE - Entry Point Not
| Found".
|
| I found and followed a Knowledgebase article that referred
| to a similar problem with a different file and a slightly
| different message which indicated you should perform a
| repair and replace the file that is referenced which in
| this case was "SHLWAPI.dll", I did this, with no
| improvement. Next steps will be to start up in recovery
| mode and copy the file via the floppy disk from another
| W2K system and see if the older version of the file will
| work. Any other suggestions would be greatly appreciated.
|
|

 

[James Farris]

I did, the only conflict and one that I was willing to
live with involved the IBM Power Management software.
Everything else (there were three other things) and I
removed them prior to upgrading, no hardware conflicts.