Sorry to hear that man, but I am so relieved my issue was corrected via the update. I imagine these updates often time cause issues for as many people as they wind up correcting!Actually, I didn’t have this problem on 16.1 but started happening on 16.2