I’ve just updated to 3.105 - same issue. I can, however, confirm that the issue is not present if used without VPN.
3.105