NC35.0.3 Still file size 0 and some files can't be opened

Nextcloud Server version :
Nextcloud Hub 26 Summer (35.0.3)
Operating system and version:
Managed Server @ all-inkl.com
Linux dd51614 6.8.0-149-generic #149-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 23 13:21:10 UTC 2026 x86_64
Web server and version (e.g, Apache 2.4.25):
Apache
Reverse proxy and version _(e.g. nginx 1.27.2)
unknown
PHP version (e.g, 8.3):
8.5
Is this the first time you’ve seen this error? (Yes / No):
No
When did this problem seem to first start?
30.10.2026
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIO
Are you using CloudfIare, mod_security, or similar? (Yes / No)
No

Hi Nextcloud-Pros,

as reported in my last posting from 03.11.2026, I couldn’t open some files with Windows NC Client after updating to NC35.0.2. In Windows Explorer these files appeared with file size zero, and when I tried to open them, I got error messages like “Bad file format”. When I tried to open the files in a browser, the correct file size was shown and the files could be opened without any problem.

On my server, all files are encrypted with a serverwide encryption. As reported here, it was a known error, that NC35.02 had problems with calculating file sizes for encrypted files. This problem should be solved in NC35.0.3.

I updated my server and my Windows Client to NC35.0.3 this morning, but unfortunately, the problems with file size 0 and opening these files still persist.

What can I do, to let the correct file sizes appear in Windows Explorer and to open them here?

Thank you in advance for any tipp.

Bfn
Michael

@Silvernerd1 sounds like something is being blocked by your OS… do you have some kind of anti-virus/firewall software running on your OS?

this is a guess, bar using M$ OS :man_shrugging:

The only security software running is the Microsoft Defender. The problem appeared immediately after updating to NC35.0.2. And it didn’t disappear with NC35.0.3. The problem is also documented on Github → Wrong unencrypted_size for legacy base64 files: block size is read before the file header is applied · Issue #63662 · nextcloud/server · GitHub

Simply updating the Windows Nextcloud client did not solve the problem.
Additionally, it was necessary to completely delete the synchronisation in the settings menu of the client and to completely delete my local synchronisation folder. To be on the safe side, I rebooted my computer afterwards.
After that, I set up the synchronisation from scratch.
Everything works perfectly since then :blush::+1: