Same issue happening for our users with the new 17.4.2520 client. Please advise.