We’re still trying to reproduce the problem. Unfortunately, we failed to do so, even using the same environment as yours. A new update for XLS Padlock will be released in one or two days, with several internal changes. Hopefully it will fix the problem for you. If not, we’ll continue to send you debug versions to try to know the exact location of the error.