Thanks for the report.

This phenomenon is caused by a change in the underlying Windows API's. I'll look into it, but I doubt there is anything I can change about it.

Regards,

Ruud