Hi . We locate VS2013 using the environment variable VS120COMNTOOLS. Checking that the environment variable is defined and matches your VS install location should clear things up.
I’ve encountered this issue once myself. In my case it ended up being that I had left a command prompt open while installing Visual Studio. So my cached environment didn’t include the new envvar.