<![CDATA[NetXMS Agent on Windows Server - Physical Free memory returns incorrect value]]>Using 2.2.16 agent on Windows Server 2016 an incorrect value is returned for System.Memory.Physical.Free . It currently returns values near zero, but the actual value is 6GB at that time as seen from task manager. When i look at task manager and checked used memory, i can see the System.Memory.Physical.Used is returned correctly.

bug?

AgentMemory1.png

AgentMemory2.png

]]>https://forum.netxms.org/topic/6081/netxms-agent-on-windows-server-physical-free-memory-returns-incorrect-valueRSS for NodeFri, 13 Nov 2026 09:00:59 GMTSat, 10 Aug 2019 11:13:00 GMT60<![CDATA[Reply to NetXMS Agent on Windows Server - Physical Free memory returns incorrect value on Sat, 10 Aug 2019 20:52:52 GMT]]>ah my bad indeed on the Free vs Available part. classic mistake. sorry. understood.

]]>https://forum.netxms.org/post/26265https://forum.netxms.org/post/26265Sat, 10 Aug 2019 20:52:52 GMT<![CDATA[Reply to NetXMS Agent on Windows Server - Physical Free memory returns incorrect value on Sat, 10 Aug 2019 12:36:36 GMT]]>The value NetXMS returns is correct. Your system does not have 6GB of free memory, it has 1.4GB.
It is using 2.1GB for applications and 4.5GB for Cache. Adding that up means the system is using 6.6GB of RAM, which leaves 1.4GB free (which is shown on the graph, the returned value is not "near zero").

You are confusing free memory with available memory. Memory used for caching is "available", but it is not "free".
Available memory is a different DCI: System.Memory.Physical.Available and it would have returned a value of 5.9GB at that time, which also matches your Task Manager screenshot.

]]>https://forum.netxms.org/post/26262https://forum.netxms.org/post/26262Sat, 10 Aug 2019 12:36:36 GMT