The source file name(s) are larger than is supported by the file system...

Anonymous
2010-03-31T00:50:57+00:00

"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."

There are about 10 subfolders on the computer. None can be deleted, moved or renamed without that message appearing. I've already tried UNLOCKER ASSISTANT & DELINVFILE to get rid of this folder. Once again, none worked. Command prompt did not work as well. Please help me, this folder will not go away on my desktop.

Windows for home | Previous Windows versions | Files, folders, and storage

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2010-03-31T12:48:05+00:00

First try deleting them by bypassing the Recycle Bin by using SHIFT-DEL(thanks, Michael Murphy) instead of just DEL.

Try using one of the following free products to delete the file/folder.  Unlocker at: http://www.softpedia.com/get/System/System-Miscellaneous/Unlocker.shtml or File Assassin http://www.malwarebytes.org/fileassassin.php (with or without Force Delete and you may need Force Delete in this instance: http://www.mydigitallife.info/2008/12/27/force-delete-cannot-delete-locked-or-in-used-files-or-folders-with-fileassassin/). These programs often work when normal Vista delete functions fail to operate properly.  You may have already tried Unlocker (I don't know if it's the same as Unlocker Assistant) but if this one if different, give it a try.

Here's an article on this topic (related to a different subject, but essentially the same problem) with a number of suggestions - one of which may work for you: http://www.howtogeek.com/forum/topic/how-to-delete-source-file-names-are-larger-than-is-.

I hope one of these options helps.  If not, post back and we'll see if we can find another answer.

Good luck!


Lorien - MCSE/MCSA/Network+/A+ --- If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2010-06-04T20:15:54+00:00

Hi everyone,

I tried all of the above and none of them fixed my issues, however I found out make a drive mapping about halfway into the folder structure you should be able to delete the latter half of the file heirarcy.

For example if you are getting the error trying to delete:

\\NAS.Device.Company.com\a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z

Then map a network drive Z: to

\\NAS.Device.Company.com\a\b\c\d\e\f\g\h\i\j\k\

This will reduce the file herarch down to a smaller path.  Open explorer and view the Z: drive.  It should contain a folder called L (in this example).

You should now be able to delete the L and its subfolders without an issue, thereby deleting half the folder hierarchy.  After that, disconnect the z: drive and try to delete whatever is left normally.  Problem solved!

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

69 additional answers

Sort by: Oldest
  1. Anonymous
    2010-03-31T18:44:43+00:00

    http://windows.microsoft.com/en-US/windows-vista/Keyboard-shortcuts

    SHIFT+DELETE Delete the selected item without moving it to the Recycle Bin first

    Cheers.


    Mick Murphy - Microsoft Partner

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2010-12-09T22:55:04+00:00

    This was the only suggestion that worked for me.  This is something that should work out of the box, though.  If you can create a folder through normal file system APIs, you should be able to delete a folder using the standard OS tools.  MS, anyone there listening?


    Ken Smith

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2011-01-23T04:03:19+00:00

    Thanks for posting this. This was the only one that worked for me as well.

    My files were created by VS 2010 when I tried to build a deployment package for a web site. It generated so much deep stuff that I could not remove it... until I mapped a drive deep in the path.

    As Ken said, is anyone at Microsoft listening?

    Was this answer helpful?

    0 comments No comments