> Ask yourself if this could have happened with Windows 10's PATH editor. Yes …? Well, I dunno; I don't know how Windows 10's PATH editor works. Nonetheless,

> Ask yourself if this could have happened with Windows 10's PATH editor. Yes …? Well, I dunno; I don't know how Windows 10's PATH editor works. Nonetheless, the issue seems to be with magic interpretation of special configuration options, not with how those configuration options are entered. (Note also that the configuration was done programmatically, not by the user, so that there would have to be some kind of parse–deparse step anyway.)