Windows 8 and 8.1 Forums

why this message occurs : the source file names are larger

  1. #1

    why this message occurs : the source file names are larger

    "The source file name(s) are larger than is supported by the file system. Try moving to a location which has a shorter path name, or try renaming to shorter name(s) before attempting this operation."
    Theoretically with NFTS system 256 characters can be used to name folders & files.
    However I had found the message above as I try to move/delete files from some folders named no more than 10 characters long.
    Every time I try to move/ delete files from such folders the message above comes up.
    I solved by renaming with shorter folder names.
    This post is an attempt to understand what is going on with such folders ? Thanks

      My System SpecsSystem Spec

  2. #2

    There is a max path length that it sounds like you are exceeding which is why renaming the folders to shorter names resolves the problem.

    Maximum Path Length Limitation

    In the Windows API (with some exceptions discussed in the following paragraphs), the maximum length for a path is MAX_PATH, which is defined as 260 characters. A local path is structured in the following order: drive letter, colon, backslash, name components separated by backslashes, and a terminating null character. For example, the maximum path on drive D is "D:\some 256-character path string<NUL>" where "<NUL>" represents the invisible terminating null character for the current system codepage. (The characters < > are used here for visual clarity and cannot be part of a valid path string.)
    Naming Files, Paths, and Namespaces (Windows)
      My System SpecsSystem Spec

  3. #3

    Yes , I had not noticed that there was a folder (with very long name) inside a folder (again with very long name) on which there were files with very , very long name. The author of the torrent I downloaded probably does not know there is a limit.
    It caused me a serious inconvenience , windows explorer started to behave oddly , I could no longer open , delete , create folders , rename files or folders. I had to reboot the system many times , finally I downloaded NAME FIX 4.0.2 to rename the long name folders. Solved. Thanks.
      My System SpecsSystem Spec

  4. #4

    Glad you found a solution.
      My System SpecsSystem Spec

  5. #5

    Painstakingly I did , thanks
      My System SpecsSystem Spec

  6. #6

    Error Even with Path Length of Only 218 Characters?

    I am running into basically the same problem as the OP. When I was copying a file to another drive, the error message was "Destination Path Too Long" I did a count of the number of characters in the path and it was only 218 characters (with spaces counted). I had read the references that imply a maximum path length available of roughly 260 characters, but I got my error at only 218. In this case, the destination drive is formatted as FAT32. I am guessing that FAT32 does not permit as long a path length as NTFS? I can work around this and will try one of the long path rename tools, but wanted to understand why it flagged a path of only 218 characters. Thanks.
      My System SpecsSystem Spec

  7. #7

    Re post #6: I think I have answered my own question. I had copied the path information from the address bar in a File Explorer window. That count gave me the 218 characters I noted above. However, I had not realized that the actual file name itself was not part of the address bar path. When I added in the characters from the actual file name, my character count went up to over 260. I see that I have been rather profligate with my folder and file names, so I shall go back and enforce more discipline on my naming conventions.
      My System SpecsSystem Spec

why this message occurs : the source file names are larger
Related Threads
Is it possible to sort a folder's contents with both File names and Sub-Folder names intermixed? I have projects in sub-folders, and 'support' files like this: projabc (sub-folder) projabc.txt (file) projabc.bat (file) amongst other projects. I would like all...
UTC in File Names in General Support
Is there a way to stop the UTC being added to file names? This practice is causing havoc with my RootsMagic family tree media references. With thanks for any solution, Allan.
Read more at: Support for Whitespace characters in File and Folder names for Windows 8, Windows RT and Windows Server 2012
Greetings forums' readers & helpers, ٩̢ ̗(Ӧ̮Ӧ)̢ ̗۶ I saw in many places these types of Windows 8.1 ISO files that are differentiated by capital letters. I know that the acronym RTM = “Release To Manufacturing”. But what about these:• AIO • ESD • WIM • VL • NVL I want to know which one...
Add Secret ?Hide File Names? Option in ?View? Menu in Windows Vista and 7 - AskVG I followed this guide but the option is not there. I was wondering if it works for any of you because I'm thinking Microsoft removed this feature on W8.
Solved Changing File Names in General Support
I have a directory in which I have a large number of genealogical records, 756 to be exact. The files are numbered FIN_1881_001_001 to FIN_1881_001_756. Due to an error when saving these files, I need to change these 756 file numbers to FIN_1891_001_001 to FIN_1891_001_756. Is there any easy...
Just upgraded to Windows 8 and I'm having an issue I never had in Windows 7. Whenever somebody sends me an archive (.zip, .rar, etc.) that contains file names that are in Japanese, they always appear garbled (文字化け). 1. I am using Outlook 2010 2. This happens through both WinRAR and Windows'...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook