http://blogs.technet.com/engauged/archive/2007/08/19/why-was-vsperfcmd-having-trouble-finding-drivers-that-were-in-the-same-directory-as-the-exe.aspxBecause the app refers exclusively to the path in the registry entry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSPerfDrv\ImagePath. And Don't forget the \??\ before the path name (although I don't know what that's for).en-USCommunityServer 2.1 SP1 (Build: 61025.2)