Thank you, @Brad!
Yes, it’s easy to work around now that I understand what’s happening. Appreciate the fix! 
By the way, this is one of 3 bugs I encountered this past weekend while upgrading to 4.0, and that I reported on the forum. This one can also be worked around (seems to be an unintended side-effect of “Reset All”), but this one is tougher to avoid (error in SysEx evaluation).
Thanks,
Kevin