-
Notifications
You must be signed in to change notification settings - Fork 808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Windows 11 + Group Folders + VFS :: Unable to open file #5695
Comments
Same issue here. Problem only occurs with Windows 11. Several notebooks affected. Server version: 28.0.3 and Desktop Client version 3.12.1 |
3.12.2 also affected with 2MB+ files, but not all of them |
You also mentioned these two points:
Are you saying the problem does not occur when no special characters are involved? |
Hi Josh, this was fixed around 2 months after I opened the issue, so I will close it now. Thanks. |
This sill is issue here: @vagner-dias which version this was patched ? |
Hello. Bug still here with 3.14.3 an server 29.0.10 |
Bug description
When using group folders on a windows 11 client, I am unable to open any file after having successfully opened around 6 or 7 files and the NC Deskto Client gets stuck at the "sync" status
I get an error from windows 10 - 0x800701AA - the cloud operaçtion was not completed before the time-out period expired.
The same error does not happen on a windows 10 client.
DebugArchive:
DebugArchive.zip
Here is a screenshot
Steps to reproduce
Scenario:
Group folders app installed at the latest version
Expected behavior
files should be synced without problems
Which files are affected by this bug
any file
Operating system
Windows
Which version of the operating system you are running.
Windows 11
Package
Appimage
Nextcloud Server version
25.0.3
Nextcloud Desktop Client version
3.8.1
Is this bug present after an update or on a fresh install?
Fresh desktop client install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: