First, while some of the things he encountered were indeed covered in my blog post on troubleshooting errors when changing the JVM that CF uses, one was new to me--and I have updated the post (and in thanks for that as a lesson learned, I did not charge him for my time). And we did initially make sure the problem was not about the bit-level of CF vs that of the jvm (see more in my blog post), etc. There were basically 3 things wrong.
About the "discovery" for me, Carl had above recommended here (as I do in my post) that for the sake of diagnosing the problem he should run cfstart from the command line, to see what it may report. That so often WILL give the answer of what's amiss. And he HAD done that. But note above in his his screenshot that he opted to do that via powershell rather than the windows command prompt.