This was fixed for us by having an admin uninstall the CU, and then manually reinstall it (not using the automated deployment tool that installed the CU the first time);...