Hi Terry_J​, from memory, the article or public information on this issue listed a KIR that you can use to disable the hotfix that is causing this issue. Have you attempted to use this KIR?