Apparently that bug where CIS (latest) hogs processor and PSU is back.
OS is still Win10 64 bit. Will upgrade to Win11 later so not gonna do uninstall/reinstall procedure.
Apparently that bug where CIS (latest) hogs processor and PSU is back.
OS is still Win10 64 bit. Will upgrade to Win11 later so not gonna do uninstall/reinstall procedure.
Do you have any screenshots and list of other running processes at the time of the hogging?
Apparently if no restarting computer for a month then hogging starts or CIS had scheduled scan going on.
Hi Cuser,
Thank you for reporting.
Could you please share us any related screenshot ?
Thanks
C.O.M.O.D.O RT
saw this before with CIS on Windows 10.
If it only begins to hog after a month of uptime, it’s often one of two things:
cmdagent.exe stuck loopingcheck task manager → confirm it’s cmdagent.exe using CPU. then look at CIS scheduled scans and disable monthly/idle scans.
Additionally, it’s not optimal to use CIS (HIPS + autosandbox) without rebooting for a month. It’s a service state problem, not your PSU, if a reboot resolves it immediately.
To see the true story, take a snapshot of the CIS process skyrocketing.