If you start getting this stunning error on startup, you likely:
The solution is to search your hard drive for all instances of PSAPI.dll and rename them to something like PSAPI.old.
UPDATE: I've received one report where someone had trouble with this tip, and he suggested leaving the PSAPI.dll in c:\windows\system32 alone. I didn't, but you should be aware and possibly try first with that one DLL left alone.
This problem was debugged using ProcessExplorer to ask folks (other processes) WHERE their PSAPI came from...
Crisis averted, at least for me.
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. I am a failed stand-up comic, a cornrower, and a book author.
Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.