Hi Alex, we have the same problem with KB5004442 in some legacy code... Could you please post your solution? Did you use the current 3.0 version ? I can't find the latest version of the source code ... I am thankful for any help