Hi Leonard, well I'm really glad that solves the mystery!

For the next v3 beta I'll see if I can fix that up or at the very least pop up a message saying that a file path with a * in it will not work properly when you try to use one.

In Windows the * character is not allowed for file names, because of the history of using a * for a "wild card" pattern in command line operations (like saying: del ab* means delete any files starting with the text "ab" and anything allowed after that), and the Windows OS itself handles prohibiting it in the system UI.

- Michael