You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Reimplement Windows file explorer context menue #640
Operating System: Windows 10/11 (tested on a fresh user profile)
Description
After installing the OpenCloud Desktop Client v3.0.0-beta.5 on Windows, the Windows Explorer integration does not show the context menu for sharing files.
Normally, when right-clicking on a synced file or folder, a submenu should appear allowing users to create or copy a sharing link. However, this submenu is missing entirely.
Steps to Reproduce
Install OpenCloud 3.6 server (linux & docker-compiose) and OpenCloud Desktop Client 3.0.0-beta.5 on Windows 11.
Sync a folder successfully with the OpenCloud server.
Open File Explorer and right-click any synced file or folder.
Observe that there is no OpenCloud share context menu (no option to create a share link).
Expected Behavior
When right-clicking a synced file, the context menu should include a OpenCloud submenu that allows creating or copying a share link.
Actual Behavior
The context menu entry for OpenCloud sharing is completely missing.
Additional Information
I created a brand new Windows user profile and installed the client again.
The issue persists even in this clean environment.
This suggests that leftover registry parameters or old configuration files are not the cause.
Screenshots
Possible Cause / Notes
It may be related to a missing or non-functional shell extension registration in this beta version.
changed the title [-]Windows file explorer context menue not shown (v3.0.0-beta.5)[/-][+]Reimplement Windows file explorer context menue[/+]on Nov 4, 2025
The shell extension was based on legacy apis and was already treated like a second class citizen by Windows.
With the Windows Store, it turned out that that that api is not supported for store applications.
We will reimplement the shell extension at some point in the future.
The shell extension was based on legacy apis and was already treated like a second class citizen by Windows. With the Windows Store, it turned out that that that api is not supported for store applications.
We will reimplement the shell extension at some point in the future.
Thank you for the clear explanation.
Would it be a workaround to publish a msi setup package like here #273 requested or is the shell extension currently fully not present in the setup package?
Context-menu-entry on Mac, Linux and IOS works without problems. It would be really good, to have this feature again in windows, also in terms of accessibility.
+1 for this feature. At the very least parity with the MACOS version would be great. Dropbox have managed it, so perhaps more resources is needed to make it happen?
Activity
[-]Windows file explorer context menue not shown (v3.0.0-beta.5)[/-][+]Reimplement Windows file explorer context menue[/+]TheOneRing commentedon Nov 4, 2025
The shell extension was based on legacy apis and was already treated like a second class citizen by Windows.
With the Windows Store, it turned out that that that api is not supported for store applications.
We will reimplement the shell extension at some point in the future.
cscholz commentedon Nov 4, 2025
Thank you for the clear explanation.
Would it be a workaround to publish a msi setup package like here #273 requested or is the shell extension currently fully not present in the setup package?
TheOneRing commentedon Nov 4, 2025
To be able to ship a msi there a several logistics problems to solve first.
I don't see a msi installer in the near future.
Michael1972 commentedon Feb 17, 2026
Context-menu-entry on Mac, Linux and IOS works without problems. It would be really good, to have this feature again in windows, also in terms of accessibility.
Thanks in advance
dougle03 commentedon Jul 7, 2026
+1 for this feature. At the very least parity with the MACOS version would be great. Dropbox have managed it, so perhaps more resources is needed to make it happen?
Reimplement the windows context menu