I have a user that I sent an updated workbook compiled in the newest padlock version. That replaced a workbook created in the previous padlock version. When they try to save a file in the new version, the save dialog box opens and when they go to enter a new file name the entire workbook closes without saving.
I cannot replicate the issue on my computer.
I resent them the compiled workbook made in the previous padlock version and it saves just fine again.
They are using Excel 365 that is current on updates. I had them restart computer, no change.
Any ideas? Something they need to clean out on their computer to use the updated version?
When saving on both the 2013 and 365 versions in the 2019.1 compiled workbook it did this weird thing too… when clicking “Save” from within the “File” tab, the secure save box opens then it freezes for a minute, the whole workbook closes and then a new blank Excel file opens on it’s own (not within the EXE)
I am having the same issue not being able to do “secure saves” with the newest XLS Padlock 2019.1 exe using Excel 2016 on Windows 10. When trying to do a secure save from a secure workbook application it closes/crashes before the save as window appears. In my case the problem started this week while three weeks earlier I had no issue at all. Playing around a lot I managed a few times to get a secure save but could not find out why it worked except that I was not loading settings from a template. When Installing the older 2017.0.1exe it fixed the problem. Checking the event viewer, I find the following error message for the failed saves:
Event 1000, Application Error
Faulting application name: excel.exe, version: 16.0.11929.20254, time stamp: 0x5d61204b
Faulting module name: B9C34A01.dll, version: 0.0.0.0, time stamp: 0x5d2dd4f5
Exception code: 0xc0000005
Fault offset: 0x002ea1a9
Faulting process id: 0x4a0
Faulting application start time: 0x01d5612dc734cfff
Faulting application path: C:\Program Files (x86)\Microsoft Office\Root\Office16\excel.exe
Faulting module path: p:\Office\4NON1\B9C34A01.dll
Report Id: 1972522d-48fd-44d8-b369-7513a5b958fb
Faulting package full name:
Faulting package-relative application ID:
Any Idea what is happening?
Sounds like compiling in 2019.1 using a template created in 2019 might be the issue.
I was loading a template that had been created in 2019 into 2019.1 and the saved file was not working once compiled in 2019.1. Once I reverted back to 2019, loading the same template saving works again.