Yes, we are aware of the issue as of this morning since Microsoft released it yesterday for the "meltdown and spectre" issues at the intel chip level. The issue not only seen on windows 10, but other KBs in the microsoft catalog (expected to be pushed next week) also exposed the same in 2012, 2016 as well. Looks like some permissions issue changed with the update. We are working diligently to triage and determine root cause in order to find a fix. Stay tuned. Jeff
↧