Yep, it just happened to me too, in the most recent version (17.2.2, after being upgraded from 17.1.3), so it does not appear to have been properly fixed after all. :-(
(and I never had multiple installs of EmEditor on the system either, so that theory is most likely a red herring in regards to debugging this, provided this and the other answers above in this thread)