I looked up the support cases. First case looks to be closed due to no responses from you, and the second one was just opened a few days ago. Please keep working with our support on this new one to get the issue resolved fully, otherwise even version 19.5 will still have it
The issue is not exactly wide spread, so we may never be able to catch it in our QC labs either (and it might not be even a Veeam issue to start with). Thanks!