Antimalware service executable eats memory

Anonymous
2025-02-04T08:12:19+00:00

title. it's always taking 200-300 mb of memory.

I tried:

disable windows security, got hit with this setting is managed by your (non existent) administrator

end task, got access is denies

command prompt things, did nothing

edit group policy, did nothing

enable disableantispyware in regedit, got hit with access is denied

tried to give myself permission to enable disableantispyware, access is denied

in case I missed any, I basically tried everything you can find online. no matter what I do, either nothing happens, access is denied or this setting is managed by your administrator

I'm about to flip this is my computer, I should get to choose what to do. I am the administrator and only user

Windows for home | Windows 10 | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

61 answers

Sort by: Oldest
  1. Ramesh Srinivasan 87,865 Reputation points Independent Advisor
    2025-02-05T09:03:18+00:00

    Thanks. I've sent the request to access the file.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-02-05T09:08:34+00:00

    it's shared

    Was this answer helpful?

    0 comments No comments
  3. Ramesh Srinivasan 87,865 Reputation points Independent Advisor
    2025-02-05T09:30:35+00:00

    The capture timing wasn't correct because the Windows Security app was already running before the trace began. As a result, its activity couldn't be captured.

    Try a boot trace. Please see "Gather boot log files" in this ESET article.

    https://support.eset.com/en/kb6308-using-proces...

    Step 3 in that article says: "Restart your computer, reproduce your issue and then run Process Monitor. Click Yes at the prompt to save the boot log."

    In that step, after enabling the boot trace and restarting the system, launch Windows Security. After the UI loads with grayed-out controls, open Process Monitor and save the boot log.

    Share the zipped file.

    Standard Disclaimer: There is a link to a non-Microsoft website. The page appears to provide accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as PUPs (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-02-05T20:11:06+00:00

    Was this answer helpful?

    0 comments No comments
  5. Ramesh Srinivasan 87,865 Reputation points Independent Advisor
    2025-02-06T00:56:46+00:00

    Sorry, the log is corrupt. This happens on some systems, but the reason is not apparent. I'm afraid we have to try again, or use the earlier method. If using the earlier method, terminate securityhealthservice.exe and sechealthui.exe in Task Manager before running the trace. After tracing begins, launch Windows Security.

    Was this answer helpful?

    0 comments No comments