Cannot open any .cpl files

[angryTech]

This computer is running Windows XP Home SP2.

When I right click on the desktop and select Properties I receive the
following pop-up message:

Window Title: RUNDLL
Message:
Error in setupapi.dll
Missing entry:s

When I open up Control Panel I can see all the icons, but double clicking on
any of them result in the same pop-up message described above. Also, trying
to open the .cpl (like desk.cpl) files from the run command also reslut in
the pop-up message. The setupapi.dll file does exist in the Syste32
directory, and I've replaced it. I also ran sfc /scannow, which did not find
any corrupted files.

I've tried various troubleshooting steps found on the web but nothing has
worked. I get the same pop-up message when I boot into Safe Mode, even when
logged in as a different user.

Any help would be greatly appreciated.

 

[MAP]

This computer is running Windows XP Home SP2.

When I right click on the desktop and select Properties I receive the
following pop-up message:

Window Title: RUNDLL
Message:
Error in setupapi.dll
Missing entry:s

When I open up Control Panel I can see all the icons, but double
clicking on any of them result in the same pop-up message described
above. Also, trying to open the .cpl (like desk.cpl) files from the
run command also reslut in the pop-up message. The setupapi.dll file
does exist in the Syste32 directory, and I've replaced it. I also ran
sfc /scannow, which did not find any corrupted files.

I've tried various troubleshooting steps found on the web but nothing
has worked. I get the same pop-up message when I boot into Safe Mode,
even when logged in as a different user.

Any help would be greatly appreciated.

Run the .cpl assoc. fix at the link below
http://www.dougknox.com/xp/file_assoc.htm
Note: a reboot may be required.

 

[angryTech]

Thanks for the suggestion Mike, but this did not fix my problem. I still get
the same pop-up message box when I try to open a .cpl file.

I made sure I rebooted the machine after I merged the registry settings.

 

[angryTech]

I tried an in-place upgrade of Windows XP (installing XP on top of itself)
and that did not fix the problem either.

In the end, I had to wipe the machine clean and start from scratch. Oddly
enough, that *did* work.