Onedrive continually uploading issue.

Question

I had the same problem as this one:

https://answers.microsoft.com/en-us/msoffice/forum/all/onedrive-continually-uploading-issue/2fa0950b-1e43-479e-8582-63c895090f93

(I do not understand why the thread was locked.)

I had the same reason code in the StallErrorSummary:
StallErrorSummary = [... Reason:334 ...

Answer 1

After months I realized that the problem is that OneDrive is unable to synchronize symlinks created from Within WSL (Windows Subsystem for Linux). Not only that, OneDrive also fails badly on those symlinks it constantly reports that it is uploading them :(

In addition to that I found out that there is no suitable way how to get the list of files which are in this problematic state. Having that list would make my research much easier and faster.

As a workaround it is possible to replace the Linux-style symlinks with Windows-style symlinks. Unfortunately they are difficult to create from within WSL and their creation requires elevation of permissions.

Here is a script which makes it easier to create the Windows-style symlinks from within WSL: https://github.com/vbrozik/vb-shell-tools/blob/main/scripts/wsl/lnw

Answer 2

Dear Vaclav,

Thank you for reaching out to the Microsoft Community. We are pleased to assist you.

I appreciate the detailed information you provided regarding the issue with OneDrive and WSL symlinks. I understand that dealing with synchronization challenges can be quite frustrating.

It is encouraging to know that you have identified a workaround by substituting Linux-style symlinks with Windows-style symlinks, despite the need for elevated permissions and the complexities involved. The script you shared from GitHub **** to facilitate this process is very valuable.

In relation to the difficulty, you experienced in obtaining a list of problematic files, I suggest utilizing a PowerShell script to identify and list all symlinks within your OneDrive directory. This script should assist you in pinpointing the files that are causing issues. Below is a straightforward example:

Get-ChildItem -Recurse -Force | Where-Object { $_.Attributes -match "ReparsePoint" } | Select-Object FullName

Please understand that our initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution.

We appreciate your understanding and cooperation.

Have a great day and take care! 😊 

Sincerely, 

Naren | Microsoft Community Moderator