OneDrive Max-Path Fix Delayed Again: Windows Sync Client Rollout Now Due Late October

What changed in MC1422063​

Microsoft 365 Message Center notice MC1422063 was updated on October 5, 2026. General Availability (Worldwide) now begins end of October 2026 (previously early October) and is expected to complete by end of November 2026 (previously end of October). The feature is tied to Microsoft 365 Roadmap ID 557563.

Neowin reported the change as a one-month delay. That's right for the finish date. The start date moved by roughly three weeks, from early October to the end of the month.

In short: expect the feature on tenants between late October and late November, not now.

This is the fourth slip​

The October change follows several earlier ones, which you can trace through the Message Center archive versions:

In July, Microsoft said rollout would begin late July 2026 and expected to complete by mid-August 2026. The August 17 revision moved it to mid-September 2026 (previously mid-August), with completion pushed to mid-October. The September 18 update then set it to early October 2026 (previously mid-September).

The Message Center archive at mc.merill.net lists six versions of the notice since it first appeared on July 9. Four of those revisions changed the end date. Adding it up, the planned start has slipped about three months since July. Microsoft hasn't explained any of the delays. Each update simply says "We have updated the timeline. Thank you for your patience."

Delays on client-side UX features are common, and repeated slips don't mean the feature is in trouble. They do mean you shouldn't treat late October as a firm date.

What's broken today​

The notice applies to all users of the OneDrive sync client on Windows desktop. The listed service is OneDrive for Business (Windows desktop sync client). It doesn't say personal OneDrive or macOS will get the same workflow.

Microsoft describes the current behavior this way: when a file or folder path exceeds the 520-character sync limit, the error message only states how many characters the path exceeds the limit and asks users to shorten it. It also notes that File Explorer limitations may prevent users from renaming paths over 260 characters, and the sync client may stop syncing until the issue is resolved.

That's a real catch-22. OneDrive tells users to shorten a path, and File Explorer may not let them rename it. Meanwhile sync is stuck. Microsoft says max-path errors are among the most commonly reported OneDrive sync issues.

Why 520 and 260 are both relevant​

Microsoft's support article on file path length limits lists several different ceilings:

• OneDrive sync: 520 characters. That's up to 400 characters of local path plus up to 120 for the OneDrive root folder.
• OneDrive and SharePoint in the cloud: 400 characters for the full decoded path, including the file name.
• File Explorer and the default Windows file system: 260 characters. Single file or folder names can be up to 255 characters.
• Office desktop apps: they can't open files whose full path is over 260 characters, because they use legacy Win32 APIs that enforce the MAX_PATH constant.

One correction to the coverage: Neowin put the 260-character limit down to NTFS. Microsoft's documentation describes it as a legacy Win32 API limit. With long paths enabled, Windows supports up to 32,767 characters, but each app has to opt in. File Explorer and Office desktop apps don't, so turning on the long-path Group Policy won't help most users.

As a result, a path can be within OneDrive's 520-character limit and still be impossible to open in Excel or rename in Explorer.

What the new experience will do​

When it arrives, the sync client will continue running and users will be guided through a custom rename and move experience. According to the notice:

Rename experience

• Shows how many characters over the limit the path is
• Highlights which parts of the path can be renamed
• Allows renames even when the path is over 260 characters

Move experience

• Shows over-limit character counts in a guided interface
• Warns about over-limit shared items in OneDrive
• Warns about over-limit items in shortcuts

The most important part is the rename that works past 260 characters, because that's exactly where File Explorer gets stuck. Keep expectations in check, though. Nothing in the notice says the 520-character sync limit is going up. This is a better error-handling workflow, not a higher limit.

What to do until it ships​

Admins: Microsoft says no admin action is required, and the update will arrive automatically through the OneDrive sync client. It suggests telling help desks about the change and updating internal OneDrive troubleshooting documentation. Given the delay, don't present the guided dialog as available yet, or as a workaround users can rely on.

Finding problem paths now. Microsoft's support page includes a PowerShell example that lists files with paths over 260 characters (change the path to match your OneDrive root):

Get-ChildItem -Path "C:\Users\JaneDoe\OneDrive - Contoso" -Recurse |
Where-Object { $_.FullName.Length -gt 260 } |
Select-Object FullName, @{Name="PathLength";Expression={$_.FullName.Length}} | fl

Interim fixes Microsoft recommends:

1. Rename from the web. If File Explorer won't rename an item, rename it in OneDrive on the web or on the SharePoint site. Once the path is short enough, it syncs normally. The web has its own 400-character limit, so this won't fix every path.
2. Flatten folder trees. Every level of nesting adds characters to the path.
3. Shorten the OneDrive root. For work or school accounts, the root usually includes the organization name ("OneDrive - Contoso"), which uses up characters. Admins can shorten it with the "Set a custom name for the OneDrive folder" Group Policy.
4. Sync less of deep shared libraries. For deeply nested SharePoint or Teams libraries, sync a subfolder instead of the whole library, or rename the shortcut after adding it.
5. Watch out after migrations. Moving files from other cloud services can combine folder structures and push paths over the limits without anyone noticing.

Success check: after a fix, the item should drop off the sync issues list under the OneDrive icon in the system tray, and sync should continue.

Analysis​

This kind of change saves help desks real time, which makes the repeated slips more frustrating. OneDrive users have complained about path limits on Microsoft's own Q&A forums for years. One post from 2022 argued that newer Win32 APIs had already solved the OS limitation and asked why would you guys go and create OneDrive to use old APIs?

The new dialog doesn't answer that complaint. File Explorer and Office will still stop at 260 characters. What it does is turn a confusing dead end into something users can fix themselves, without sync stopping. Until it rolls out, the best approach is the same as before: keep paths short, keep the OneDrive root short, and rename long paths from the web when Explorer won't let you.