Forum Discussion
SenseNdr.exe is slowly eating the memory
Hello, For a few days now, we have some Windows Server 2019 physical machines where almot all the memory is commited to sensendr.exe. If you terminate sensendr.exe, the process comes back after...
Yes, I was contacted by Microsoft yesterday.
They are going to push the new solution within 48hrs from the backend worldwide and that there is no further action needed from our side.
I will wait until monday and then I will remove our scheduled task to kill sensendr and we will see how it goes.
Fingers crossed.
They are going to push the new solution within 48hrs from the backend worldwide and that there is no further action needed from our side.
I will wait until monday and then I will remove our scheduled task to kill sensendr and we will see how it goes.
Fingers crossed.
Thanks for the update! We’re experiencing the same issue, so it’s reassuring to hear Microsoft is implementing a fix. If you don’t mind, please let us know if it resolves the issue on your end. Fingers crossed
- I contacted Microsoft again to check if the fix is really implemented because we had multiple servers experiencing the problem again this week-end. On my side, it is not solved yet.
- I received multiple alerts over the weekend for this. Latest was 5 minutes ago.
Security intelligence
Version 1.421.79.0
Nov 3, 2024 2:46:44 PM
Engine
Version 1.1.24090.11
Nov 3, 2024 2:46:44 PM
Platform
Version 4.18.24090.11
Oct 31, 2024 12:13:55 AM@ Everyone
I just got a mail from Microsoft that the solution/fix deployed last week was to solve a problem with a non-paged pool memory leak and not with the commited memory !!
In my case, the problem is not with the non-paged pool but with the commited memory.
Can you all tell me with what type of memory you experience a problem ?
I ask that because apparently I am the only customer case with the problem being with the commited memory !!
It's a big disappointment because I made it clear since the beginning of the case with MS that it was a problem with the commited memory.
MarcVDH
What is the version of your Security Intelligence Update for Microsoft Defender Antivirus.
I saw two versions while doing environment maintenance today:
KB2267602 (Version 1.421.79.0) - Current Channel (Broad)
KB2267602 (Version 1.421.82.0) - Current Channel (Broad)Issue still present today unfortunately.
You can look at the memory graphs of your monitoring system or look for Event ID 2004 in the Windows Event log.Windows successfully diagnosed a low virtual memory condition.
The following programs consumed the most virtual memory:
SenseNdr.exe (6400) consumed 99208146944 bytes (92.4 GB),
CVODS.exe (15108) consumed 1249665024 bytes (1.16 GB),
and MsSense.exe (3592) consumed 957243392 bytes (0.89 GB).
In the screenshot it just crashed the server, at least it rebooted itself...
