Hmmm...., that is a bit strange. The good news is that the problem disappears in a newer version. I tried it with
ash-6.5.1717.2-w32-upd.zip and it seems to work as expected. 1716.7 was in the middle of a flurry of tinkering related to some bugs discussed (at length!) in
this thread, so it isn't too shocking that there were oddities.
So perhaps an update is the best solution.