Comments
-
I'll second that workaround. We've been doing the same thing since having the same problem for the last release or two. No idea if it's an issue with WSM, but I suspect it was a Windows thing as (IIRC) it started after a monthly patch cycle earlier this year. Certainly it showed up without a corresponding WSM update (at…