Thanks for your input. I think there's some software bug causing this, the same hardware worked without issues for years and now, not all of us are affected (all devs are using the same laptop) Anyways, I won't waste too much time analyzing this, I'm doing mostly home office as a workaround and the ops guys are going to take a look next week.