Turns out the problem was already fixed in 1270.2 (Sep 5), which is posted (in -w32-upd.zip form) in the 6.0 release
bin-win directory.
The fix was retrofitted from 6.1.1358, but I hadn't gotten any reports about either the problem or whether the fix was good, so I held off on updating the Check-For-Updates server. I think you actually reported the underlying problem which led to the fix, but you then shifted over to 6.1 for further testing.
(This is a good example of how the idea of trying to maintain "stability" in 6.0 often yields less desirable results than the update-without-hesitation scheme driving 6.1)
ash60notes.txt