Web updates stopped working

Hi,
We are using 2024 version of padlock, but we started to have issues with web updates, users are no longer seeing the “Update available” dialog.
Here is the old exe file properties:


The new exe compiled:


The .inf file content:


Older compiled files don’t get the update, all settings are done right, web update files are uploaded to server.

The only thing that comes to my mind is that it might be a bug in padlock related to file versioning: The issue started when we changed the major version from V1.x.x.x to V2.x.x.x, before changing to V2.x.x.x all worked without problems.
Is there anything else we can do to find the cause?
thank you

I am not understanding anything.
What does this mean?
I thought that XLS padlock is fully secured to export a very secured products for Excel spreadsheet applications. And that it won’t be cracked either.
I was still beginning to study it to apply their features on my products??
now i am very confused about what is happened wrong now ???
Please help me out what is happening around here …???
I was also trying to figure out that to add more security layered with XLS padlock using the DoneEx XCell Compiler to use to add further 6 layers at least to what the XLS padlock to make it really hard to be cracked to the secure the vba codes and the formulas and reduce the chances of reverse engineering to work on cracking any EXE files and so … ???

I am really worried now???

does it mean the XLS padlock can be easily cracked ???
the EXE file can be cracked easily ???

Well, I think you’re right, you did not understood anything

Web updates is a way to release new exe versions to your users. When you release a new version of your tool, your users will receive a message in their exe that “a new version is available” and they can get the new version automatically.
It does not mean that xlspadlock ot the exe can be cracked.

Question: Does Padlock allow checking for a new version from vba?
It will be very useful to check for updates and start the update process from excel, but there is no such code provided in documentation.
thank you

catalinbombea said:

Question: Does Padlock allow checking for a new version from vba?
It will be very useful to check for updates and start the update process from excel, but there is no such code provided in documentation.

Click to expand...

This is added to our TODO list. Thanks.

Thank you.
Still have a question related to the update process:
Have observed this behavior: I get the notification, press the Get update button, but the old version opens.
However, NEXT time I open the same old exe, the new exe opens up.
I guess that is how update process is designed?
I find it confusing, as a user will expect to see the new version after they get the update. There is no notification to clarify things to users, to say at least something like: “Update completed. Close and reopen the application to start using the new version.”
thank you

Hi,
For your feedack, we have the same problem again.
We changed from version 2.x.x.x to 3.x.x.x, users are not receiving the update again. Everything else is the same, so it is clearly a bug in your process, we followed all instructions.

And there is another bug.

When we open the exe, we see the “validating your access” dialog, which goes off after a few seconds, then nothing happens. It looks like the exe stops processing, we have to open again the exe, the second time opens properly, so there is clearly a bug in this process too.

Thank you

Thank you for your report. Before changing to 3.x.x.x, have you tried minor updates such as 2.5.x.x? If yes, did it work?

For the validation problem, if the EXE stops without any warning nor error message, there is probably some interference while the EXE is trying to access to the Internet. Have you checked the Windows Log Viewer for any related error?

All versions between 2 and 3 was received by users. Version 3 is not received, same happened when we changed from 1.x.x.x to 2. When we released 2, users had to download manually the latest version from website because padlock was not able to see the new update. After the manual download, everything worked as before, they received all minor versions.
Now we have to ask all users to manually download again.
There is no related log in windows logs.

We’ll investigate this issue again. Especially changing the first number in the version reference. Thanks again for your report!

Blockquote Have observed this behavior: I get the notification, press the Get update button, but the old version opens.
However, NEXT time I open the same old exe, the new exe opens up.
I guess that is how update process is designed?
I find it confusing, as a user will expect to see the new version after they get the update. There is no notification to clarify things to users, to say at least something like: “Update completed. Close and reopen the application to start using the new version.”

Click to expand...

Can we display a custom message to users after the update is downloaded?

This is on our TODO list.