Thank you for taking the time to report this, @bmc38119.
This should now be fixed with 1.2.9.7.4.
Please let us know if this is the case on your end. Thank you in advance.