To resolve this issue if the affected VM(s) are not actively using the LWD filter to be protected by solutions such as VMware Cloud Disaster Recovery (VCDR) or Dell PPDM or Replication solutions, you can detach the filter from them.
To accomplish this, please see the steps and script listed in KB - Putting ESXi into Maintenance mode, vMotioning or reconfiguring a VM fails due to the vmwarelwd ioFilter being attached
Monitoring the memory usage.
# memstats -r group-stats -v -s name:parGid:eMin:eMinPeak:rMinPeak:consumed:consumedPeak -u KB | grep -i vmx
### Above command will list the vmx group ID.
### First column is VMX Group ID
# watch memstats -r group-stats -v -s name:parGid:eMin:eMinPeak:rMinPeak:consumed:consumedPeak -u KB -g <VMX group ID>
### Use the VMX Group ID from first command and replace it with <VMX group ID>
### You need to monitor consumed and consumedPeak column
### Example:
-------------------------------------------------------------------------------------------------------
gid name parGid eMin eMinPeak rMinPeak consumed consumedPeak
-------------------------------------------------------------------------------------------------------
363 test-vmx.v00-0x4305ff1026b0 264 1072 134788 134788 1044 134788
-------------------------------------------------------------------------------------------------------