Hi @William_Street,
You have our apologies for the ongoing trouble here. The last update that we posted is still current:
This issue is limited to a very small number of devices that impact a very small number of our customers — That’s not to say that this isn’t an important issue for us to resolve, but we needed to make sure to get this specific older hardware in-house in order to do further testing.
We now have this hardware so our team is working on resolving and testing the solution and, as soon as that’s complete, we’ll be releasing the fix ASAP. These things take time, but I can assure you that our team is working to get this released as soon as possible.