AFAIK the editor (oxide) worked in W10 pro 64 1607.
However, there the in-memory execution crashed the compiler. Although compilation to exe worked. That, too, was the case in win7 32 (possible due to running EMET?).
Now, in 1703, the comiler works, but the editor does not..
Yes, paths in O2HEdit are correct. As I wrote above, even creating a new file crashes the editor. It becomes unresponsive and hogs a core entirely.
Another quirk in oxide it that it always compiles to "_.exe", irrespective of the name of the file or any in-file hint.