Hello,
I am updating via Comfort Update from version 3.15.1 to 3.15.7 and when the update is going to be applied, the message attached to the screenshot appears.

Any idea how to fix it?

I can reproduce that issue. The updater is buggy.
As a paying customer you should open a ticket via support.
What PHP version is used on your installation?

The update.zip 569 KB (583.079 bytes) might have a format, which is not compatible with default zip extraction.

SHA256: 8CF75AF27EBF619572DA2A30603CA896E6A129909413D304A48B8C78F73157BB

I have opened a bugticket with your infos too.
bugs.limesurvey.org/view.php?id=14475

So, I could reproduce the bug with PHP 5.2 and PHP 7.
LS 2.6lts does not support any of them.
With PHP 5.6, everything works like a charm.

You closed the bugticket.
Everything works like a charm?

We have the issue with
LS 3.15.1
LS 2.06lts buildnumber 160524



For LS 2.06lts buildnumber 160524 I have the issue under
PHP 7.1 and PHP 5.6

The root cause is still unclear.

BTW: If tickets get closed with a reference to not supported PHP versions (which is here not the case), it would be wise to clearly state what PHP is supported (instead of PHP X.Y and higher).

jelo: if you can reproduce the issue with any version of LS on PHP 5.6 or PHP 7.2, you can re-open the bug with the correct PHP version.

The PHP version I stated when opening the bug was PHP 5.6.
So what did I do wrong?

PHP 7.2. is causing too much issues with LimeSurvey.
www.limesurvey.org/forum/development/117...2-and-limesurvey-3-x

So I only test LS with PHP 7.1.X and test with PHP 5.6.X. too. Older testversions are running under PHP 5.6.X.

I use PHP 7.2 on my computer, like most of the dev here, like denis, and we face no problems.

I spend 3 hours this morning to try to reproduce the comfortUpdate bug you're pointing out, and it clearlry happens only with wrong PHP version for 2.6

I can give a new try for 3.15

ok, I changed the way the download process is done from the server itself, it should work on most exotic config now.

Thanks for fixing the bug of Comfortupdate. The threadstarter (which was not me) might be a happy comfort update customer again.

thank you for insisting