Dyllon, Security and Maintenance just shows "Malwarebytes is turned on." Could this be caused by having the real-time protection delayed 15 seconds? It's only happening on boot, and not again until subsequent boots; but not all boots and not all systems (I've never seen it).
I am thinking Windows is tripping on the DB version (or last update date) before MBCloudEA has a chance to run the update on startup. I'd like to be able to prove this as telling my users "just ignore it" is not an enviable proposition.