Nah, they’ve been pretty non-responsive about the whole issue.
Without wanting to rant, we are talking about business critical files here. When we use non-paid software we accept that we are relying on the good will of devs and donations we and others choose to make, so bugs and errors might not get addressed.
This is different. We are paying money so we can rely on things like this getting fixed.
It might be time to think about alternatives. The disregard for this bug is hindering my workflow.
Since we are on Linux, our team ended up moving to the Onedrive Client for Linux that’s linked above. We have been able to sync shared files again which is critical. It does have an annoying issue where some times, while modifying a file in Obsidian, the file doesn’t get uploaded correctly, and the onedrive client ends up making a backup of the file. But it’s a relatively minor annoyance to get shared files syncing working again.
Any updates on this issue? We depend on reliable data transmissions.
No comment or response from the company for over a month. Despite having paid for lifetime use of this we have ditched it, moved to the free open source alternative and everything works perfectly. Disappointing doesn’t come close.
Our most sincere apologies for not responding to this thread sooner. We can imagine how frustrating this has been for a lot of you and we are truly sorry for the huge trouble that this has caused.
This issue is still under priority investigation and we will provide an update as soon as we can.
Thank you for your patience and understanding.
Hi Mia & InsyncHQ,
Do we have any updates on this specific issue? It has been ongoing since November 25 and effectively makes OneDrive sync unusable in a professional context.
Is this problem ever going to be fixed? This is a critical feature for me and it has been extremely inconvenient not being able to view shared folders. I first reported this in Feb 2026 here: No shared folders listed in OneDrive after re-install and was told it was a “priority issue”. Since the first report of this problem was Nov 2025 it makes me wonder how slow you will be responding to non-priority issues.
This is now critically important for me, since another machine I have using Insyc performing a vital sync operation has been kept on an old version and was until this week still working (I was afraid to touch it until this was fixed) but the sync is now failing and I have now way to get it back. I am at the point where if this isn’t fixed ASAP I will need to find alternative software. I have experience of working with Sharepoint and Onedrive APIs professionally, so I’ll write it myself and cancel Insync if I have to.
I am using v3.9.11.60043
Hi everyone,
I’m now actively posting here in the hope that the insync-support will finally address this issue. I opened a ticket a while ago, but so far I haven’t received any real response.
The way shared folders work is very frustrating. Shared folders are practically unusable with insync.
Generally, only a single folder shared with me is displayed - and it’s always the most recent one shared with me.
If I set up synchronization for that folder, it works perfectly. But if a new folder is shared with me, the previous one is removed from insync, the synchronization is canceled, and all files on the local device are deleted. This happens regardless of whether I want it to or not. If I want to set up the sync again, I can no longer do so for the previous folder because it’s no longer available, it’s been replaced by the newer one.
Very frustrating.
Best regards, hoping this gets fixed
Hans
@Hans That’s a good description of the problem, looking at my Insync client I now realise this is what’s happening. If I look at the shared tab, I currently have a single entry for a spreadsheet, whereas if I go to Onedrive with a web browser I see many shared items.
This was described as a priority item by Insync, but clearly it is not. I suggest we keep posting to this thread asking for updates until something is done - assuming of course that I haven’t simply migrated away by the time this is fixed.
Hi @mia and the Insync team,
I’ve been following this thread and the recent reports from other users, but unfortunately, it seems that there is still no solution or clear explanation of what’s causing the problem.
I’ve now completely stopped using Insync for my OneDrive account and switched to the open-source client abraunegg/onedrive, which is successfully syncing my shared SharePoint/Teams folders.
As I explained in my previous post above, I managed to get these folders syncing by manually adding shortcuts to “My Files” in OneDrive and including their exact names in the client’s sync list.
What I find particularly surprising is that a working approach is already available and documented in an open-source project, while Insync, a commercial product that we pay for, has been struggling with this issue for quite some time.
Of course, I understand that the two applications have different implementations, and that what works in one may not be directly transferable to the other. However, since abraunegg/onedrive is open source, your engineers can inspect its code and investigate how it handles SharePoint folders, OneDrive shortcuts and Microsoft Graph API responses.
I’m not a developer, so I can’t determine the underlying technical cause, but I hope my findings can provide a useful starting point.
Could you please clarify a few things?
-
Are your engineers actively investigating this specific shared-folder issue?
-
Have they identified its root cause, or at least narrowed down the possibilities?
-
Have they considered examining how abraunegg/onedrive handles these folders?
I really appreciate the work of the Insync team, and I would genuinely like to return to using your software. However, after experiencing similar problems over several years, it’s becoming difficult to justify continuing to use a paid application for OneDrive when a free, open-source alternative is currently working better for my needs.
I hope we can get a more concrete technical update soon, even if a fix is not yet ready.
Thank you.
I’m going to be doing the same as @tafol and will be dropping Insync this week because of this problem, I’ve now got knock on impacts from this beyond my own inconvenience which means that I can no longer wait for a solution to this from Insync. This “priority issue” has been unfixed for months, as a developer myself who has worked with some of the same APIs that Insync will be using I just don’t understand how it could take so long to deal with this. So the only conclusion I can come to is that the issue has not been prioritised and no work has been done.
Dear insync @mia is there an update on this? I shall assume if no statement is made that you don’t care about this long standing bug and have no intention of fixing it.
Hi @tim1mw and @tafol, as well as everyone who has reported and expressed frustrations since this issue started.
I am very sorry for the long silence. I am urgently following up with our team to get a detailed update on the progress and what our next steps would be to finally put this long-standing issue to rest.
@mia any news? I’ve held off replacing Insync but I need timelines ASAP.
Our team is going to conduct a thorough internal testing. This will give us a clearer idea on the exact timeline, which we will share as soon as the testing period has confirmed that the fixes are stable and ready to go. Thank you for your patience!
That’s good to know, but this is now very urgent. I really need a fix within the next week.