New
#51
Thanks. The issue no doubt rolled in on an update whenever it is not a malware. The question is which component, and which set of hardware. If I can narrow that down I can do more verbose logging to figure out why. At the least, if updates are removed, in theory, the problem will be too (given that all 'installed' components through updates are removed).
I have found reports of 100+ systems of the same kind (companies etc) coming across this issue over night. Thing is too if it persists, Microsoft will out out the patch in another months updates...