Well I'm having trouble reproducing it despite it happening originally on about half of my clients. Seems to happen immediately after patches and then goes away. Probably something to do with the patching process temporarily hogging resources on my computer that gets fixed after a reboot but I honestly have no idea.