Excellent that you were able to track it down, but I have to wonder if the PATH environment variable might be where the problem started.   The order in which the path elements occur can sometimes be critical to finding files, and while copying a file to where it's "expected" can solve the problem, it may be that the PATH just isn't set right, or failed to be updated to the new file location by the most recent product upgrade installation or other similar install.   I'd check your current PATH environment variable to see if that file would be found in any of the folders listed.   Alternatively, there may just be a registry entry that just points to the wrong folder, very possibly for the same reasons I suggested were possible causes of PATH problems.   Admittedly, the registry is a dangerous place to go, and one would want to verify the correctness (or incorrectness) of what you have before making a change, as well as have a backup of same before making a change.