# Have you been bitten by the 260 character fully qualified path limit in windows?

**URL:** https://forum.kavli.tudelft.nl/t/have-you-been-bitten-by-the-260-character-fully-qualified-path-limit-in-windows/83
**Category:** Programming questions
**Created:** [2 June 2020 21:13 UTC](https://forum.kavli.tudelft.nl/t/have-you-been-bitten-by-the-260-character-fully-qualified-path-limit-in-windows/83 "2020-06-02T21:13:06Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![gsteele13](https://forum.kavli.tudelft.nl/letter_avatar_proxy/v4/letter/g/3d9bf3/32.png) [@gsteele13](https://forum.kavli.tudelft.nl/u/gsteele13)
#### Post date: [2 June 2020 21:13 UTC](https://forum.kavli.tudelft.nl/t/have-you-been-bitten-by-the-260-character-fully-qualified-path-limit-in-windows/83/1 "2020-06-02T21:13:06Z")

</div>

We certainly have… 😡 😡 😡 😡 😡 😡

> <https://stackoverflow.com/questions/27680647/does-max-path-issue-still-exists-in-windows-10>

(Our synology software fails to sync any file from windows that has a fully qualified path, ie including `c:\...all subdirectories...\filename.ext` that is longer than 260 characters…)

To at least help you figure out if you have files that are in this “danger zone”, I’ve made a stupidly small but maybe useful notebook for checking for danger files:

> **[SteeleLab / long-pathname-problem-hacks · GitLab](https://gitlab.tudelft.nl/steelelab/long-pathname-problem-hacks)**
>
> Delft University of Technology GitLab server

Future notebooks may include the option to automatically rename them so that they are shorter…but this is a start a least.