The issue you are facing was introduced by the Defender Engine update 1.1.25100.9002, and this is a known issue coming from the Defender product update. MCM relies on the local Windows Defender to query information about definition installation on the MCM server where the Endpoint Protection role is installed and the new engine update has blocked this causing the error you are seeing.
The issue is mostly cosmetic, not impacting the actual patching of definition updates on computers or servers.
The issue was already raised with the Defender team and it should be resolved with the Defender Engine update of December that should be available in the first part of December (around the 9th of December).