A comment on the post about lsass.exe taking an unreasonable amount of CPU mentioned that it happened when Chrome ran. My situation also involved Chrome, so I searched for "chrome lsass high cpu" and found this Chromium issue page. One comment there discovered a workaround, which worked for me on the machine in question.
Remove the folder named with a SID that resides here:
%APPDATA%\Microsoft\Protect
Danger! That folder contains things related to a private key of some description that belongs to you. I do not know what will happen to cryptography-related things like EFS if you torch it. Consider backing it up first.
Thanks! It worked perfectly. Went from 65-85% CPU grind to 1-5%.
ReplyDelete