Regarding the issue you described, we have not received any additional reports of similar behavior since your last message, and our internal tests with XLS Padlock under the latest Windows updates have not reproduced the problem. We regularly monitor Windows updates, and no recent changes have been identified that would impact XLS Padlock in this way.
Rather than a Windows or Office update, we suspect the issue might be related to specific Group Policy settings enforced on the company-controlled computer. These policies can affect file operations or application behavior in subtle ways. Additionally, while Norton Anti-Virus may not be the direct cause—especially since the software initially ran correctly—it could potentially interfere if its configuration changed or if a new security rule was applied.
We recommend checking the Group Policy settings and any changes applied by the IT department, especially those introduced around April. If possible, testing the same executable on a non-restricted environment or another machine without these company policies could help isolate the root cause.
Thanks.