I get computation errors with the message "output file for ... absent".
As i'm using Windows 7 Ultimate 64bit i can't open linux tar.xz files and i also have no knowledge of linux so i'm unable to help you with this problem.
The updating of community preferences also doesn't work at the moment, maybe later.

Kind regards
XAVER

tar.xz can be opened using WinRar, WinZip, 7Zip, PeaZip, etc.

Error reports without task id or wu name are not much useful. I can see all the results and failures in the ops section, so I saw your error and same error by different computer already two day ago. And I updated the windows build so just leave your client attached and I will hopefully see the success!

And it is ok that you do not know Linux. It is much more helpful to receive test results and errors from Windows, because I do not know that :)

Can you detail the issue with preferences?

oh, and hit Update maybe. Boinc can sometimes come up with insane reconnection delays.

After suspending WUs i get a computation error when restarting (padls1_61729345_1, padls1_61437259_0). Is it also possible to use multithreading on WUs via app_config.xml file?

Duration of WUs seem also to have longer estimates than running them separately with Ms. Makarovas batch file.

I see from the logs, that the windows buid crashes. But I do not know why and it does not say.

Can you copy the exe from the boinc project folder to an empty folder and run it with arguments 1 1 1 1 1 1 1 1, please? That should exit quickly (those arguments do not produce results) and write files output.txt and stderr.txt. Paste the stderr and any error windows that might show up here.

Multi-threading will not be supported for boinc app, because boinc is pretty good at running the app enough times to utilize all CPU cores. Multi-threading offers no advantage here.

The windows build appears to be INCREDIBLY slow, even though enabled the O3 and no-debug optimizations.
Linux version on Ryzen at 4000 MHz checks around 30 * 16 squares per second. i5-5200U check around 16 * 4 squares per second. And the windows build checks only 2 * 16 squares per second on Ryzen at 3000 MHz.
BOINC then kills the app, because it is taking too long.

Ps: padls1_* boinc app does not show this statistics, postprocess.exe does.

Uploaded build 104 of windows app. Abort all running jobs and let it download new ones.

With build 104 WUs now resume correctly after suspending. As there is no checkpointing WUs start from the beginning after turning off and restarting BOINC.

Minor fault: No uploading of avatar or other choices in community preferences possible.

The tasks should not be running much more than 4 hours on your processor. Last contact was 7 hours ago. Please check on them.
Oh and I upped the timeout significantly so boinc wont be killing new tasks that are larger than expected.