Folks,
Just noticed this becoming an issue on a Windows 2012 R2 Terminal Server after the last round of Patch Tuesday updates stemming from August 9th, 2016.
Typically, I'm rebooting the server every 24 hours to over-correct the issue - rebooting not being the best option here.
In previous discussions, it's advised to remove KB3002657 or KB3035132 from the server. Is this still the best option to restore full functionality even with the last round of patches and updates? Just to confirm, we are not using webroot as an AV solution.