That's just plain wrong, and I call into question the intelligence of
whoever came to that conclusion. He sent me an email saying "The simplest
way to fix the problem is to delete klprmon.dll
from your system32 directory." This would be great, except for the fact
that this I ALREADY deleted this file! Windows doesn't list it as a
process when I push CTRL-ALT-DELETE, which I'm not 100% sure it should but
would guess it would. Even if not, I'm displaying all files in Windows
Explorer (even hidden files and such) and the alphabetical listing goes
directly from keymgr.dll to kmddsp.tsp.

There isn't anything unconventional about my WinXP installation that I can
think of.

The only other way I can think of that the problem might still be caused
by this would be if WinXP had some kind of weird system of archiving dll's
so you can't just delete them; but I'm unaware of any such feature.

Let me be clear, this problem has not been resolved.

> According to CMU, the problem is being caused by the application
> klprmon.exe which is being loaded as a service on your machine.
>
>