Local Security Authority Protection

Kenneth I am sure that in my case the service was not actually operational and was in fact in an error state. I dismissed that error and rebooted. It came back. It was persistent.

The root cause was that the security update enabled LSA (per fg2001) and for it to run core virtualization (SVM) MUST be enabled in the system BIOS. My system did not have the option turned on and therefore LSA did not operate. In fact, I couldn't even get to the core isolation option to turn it on or off because for that to present on your client you need SVM enabled.

That was the situation with my own client anyway.

My complaint was that MS enabled LSA in this update, it requires SVM, and can put users in the situation I was. With very little to go on for determining root cause.

Are you sure that there is a problem in the first place? Perhaps the False Positive is at play here. Many times, I check the status of my computer and there are no new issues. Virus checks show no issues.

I am not telling anyone what to do as they can do whatever they want to do. Just saying what happened in my case.

I heard remarks on doing something with the BIOS well if a person wants real problems when messing with the BIOS as if one thing goes wrong and the BIOS gets corrupted then one might just as well throw their computer in the junk pile because if a BIOS gets corrupted then the computer has become worthless.

Kenneth

Kenneth in my case there was no core isolation dialogue to be found.

Until I enabled virtualization (SVM) in the BIOS on the PC that option simply wasn't there in the first place. After that I was able to toggle the switch off and back on, then reboot, and the issue was cleared up.

Here is what I did to get the monkey badge off my computer. I went into the security and clicked dismiss. To this day no badge has reappeared.

Kenneth