Yeah, it’s a such a bummer. People would suggest all kinds of solutions but few actually work. Enabling APCu and Redis help greatly with performance but they didn’t do anything for stability. The maxChunkSize fix helped to some degree too. In the end though it was all too much.
Good luck!
I too worked in IT for over 20 years and I agree with your assessment 100 percent. Increasingly the solution is to sit out on updates and let the dust settle. It shouldn’t be this way (and it use to be different) but I just don’t have time to be hanging out in forums waiting for answers.
I don’t think it’s unreasonable to want software that has been tested and generally “works” from the word go, but it seems that’s too much to ask now.
Word!
I worked in IT desktop support most of my life too and saw this phenomenon getting worse and worse over time.
From updates being exciting, bringing something new… to updates being dreadful and bringing problems.
Everything from macOS and Windows to application software updates was blocked at work, sometimes for months, until we made sure that they wouldn’t cause any major problems.
The devs no longer seem to care about testing or it’s a cost cutting measure that transfers the expense of software testing onto the users.
But, at home, with limited resources, I can’t extensively test every update, so, for the last several years, I followed a permanent update blocking policy until software becomes incompatible or an update brings new features I really need (which is almost never).
Just to add my debugging results here in order to help others with the same struggles.
I researched deeper the cause I mentioned earlier about the problematic use of the Virtual Files, more specifically the crash of this DLL-file: C:\Program Files\Nextcloud\nextcloudsync_vfs_cfapi.dll.
I was talking about Nextcloud Sync app version 3.17.0.189, in this version the known problem with Virtual Files is resolved.
The problems I was mentioning were happening on a Windows 10 version 20H2.
After some research on that, there is a clearly known bug in Windows 10 20H2 on this matter, the virtual files, so the cause of the crash.
We have another Windows 10 version 22H2 (which is the latest W10 version) and not having an issue. It seems that this Virtual File problem in Windows 10 is resolved in this W10 version.
Yes, we do never device updates once they work stable. Cascade costs due unpredictable behaviors are worse. Of course updates are important, especially on business critical environments, but these pc’s are not. That is bit roughly the policy.
So, to end the ‘story’. We probably found the unstable cause and factor.
Mostly we will replace this W10 device with a brand new machine. The device is at least 5 years old.
We would never have reached a lifetime of 5 years when doing permanently the updates.
In last 5 years application moved from desktop to web where browsers became the main app to do things, and as you know, they are eating all your mem. So imagine this evolution together with permanent updates. We would have been forced to replace the device after 3y or something. But this last paragraph is off the record. 
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.