Thank you! It seems version “e” and later have solved this issue. Both problem workstations have self-updated to “e” and do not have this issue. We will update to patch “g” today. Thanks for the help!
Same issue experienced here. Application/file exclusions do not seem to help. Only solution is pausing the protection, opening the database, then resuming protection.