I'm not able to find it in Google anywhere. I'd start doing a couple things to dig a little bit as to what's going on...
A) sysinternals..run regmon and filemon (or procmon) to find out what exactly is getting the error when you try doing things. If you can't run anything, then this won't help much...
B) you can try the registry editor to see if this filename is stuck in somewhere to run before running other executables or particular components.
The alternative...probably best...is to wipe and reinstall, restoring your known-good data files. A rule of security is that if the system was compromised, you can never be sure that it doesn't have something else hidden in the filesystem or some other goodies that you won't be able to easily find, like a rootkit in an alternate data stream for NTFS.
If it were a Windows file or common file from, say, a security program, you'd be able to find it online. The fact that it's not coming up from google is fishy, and if you don't have the file anymore to examine for strings or evidence then it's not going to be easy to figure out. I'd speculate that something stuck that in there as a hidden component of another part of a dropkit or rootkit, but like I said...without evidence it's pure speculation.