From #1343

Even more correct would be to specifically display a message that there was no default profile (though that might be too much for this release).

• If we load the profiles.json and the defaultProfile doesn't exist in the list of profiles, we should display an error specific to that failure case.
• We should also use the first profile as the default temporarily. We'll need to make sure not to persist this runtime change.

Maybe also:

• Check if the commandline is a path to a single executable, and if it is, warn if it doesn't exist? Dunno how we'd get the first arg from the commandline easily but it could totally be done.