Thanks for providing the environment and version details.
We’ve seen this occur in the specific case where CPM clients are upgraded from build 1020 to build 1040. From your screen shot, it looks like the affected client is currently on CPM build 1040 so this is likely the issue. We have a Fixlet to resolve this and the best way to get it would be to open a support case with our team.