It is known issue in v1.65.
And hopefully already fixed. More details in below thread:
Try the latest beta.