No, this would only affect CoreMIDI logging - if at all - all other logging continuo to work. A reboot fixes the situation. But I might be led astray, I have no way to verify if CoreMIDI msgs from other components also do not log. Maybe only the CoreMIDI driver does not get loaded in that situation. I will report here if I find a reliable way to reproduce. For now I am assuming it's a bogus effect of something else.

Thank you very much, Kevin, for your suggestions and disclaimers. And be assured this is nothing a user will ever see from us! This is only to tidy up my development/test machines from the mess the development does to it... Thanks!

Thanks, Justin!

The place where finally all issues are buried.