no, I tried starting the win installer for 1.12.2 and it didn't do anything, then tried again with the universal installer, same issue, and then tried starting them both (separately)
using the command line, and got those errors
if it helps, it seems to be very similar to the problem at