Thanks for your feedback by email. Issue tracked down and was not related to a change in v7.64.