*sigh*. Seeing this same behavior on a few more systems, but we can't find anything in common to isolate the issue.

How do Windows IT people remain sane with this house of cards?