The Source Filename is Larger Than is Supported

A huge load of customers is dealing with a strange circumstance when struggling to copy or remove something on their PC. Affected customers report getting a Source Path Too Long short telling them. “The Source Filename is Larger Than is Supported” The source record names are greater than is maintained by the archive system.

This usually happens with a record (or more) shrouded in a movement of subfolders with long names. Whenever this happens, you can’t move, remove or rename any of the involved reports/coordinators. Consistently it is represented that they get this error happens when struggling to copy or delete records/coordinators.

Around here at ARZHOST, “The Source Filename is Larger Than is Supported”, we handle requests from our customers using Windows servers to fix similar issues as a piece of Server Management Services.

Today what about we see how our Hosting Expert Planners fix this issue for our customers.

What causes ‘The source record names are greater than is maintained by the report system’?

Windows might stimulate us saying “Source Path Too Long” close by the error “The source record names are greater than is maintained by the archive structure “The Source Filename is Larger Than is Supported”, as shown under:

The above error happens with a record (or more) canvassed in a movement of subfolders with long names. Whenever this happens, we can’t move, delete or rename any of the intricate records/coordinators.

Fundamentally, if an unequivocal record or coordinator is observed where it includes a lot of sub-envelopes that have broad names. Microsoft simply allows 268 characters in the envelope way subfolder. Whenever this cutoff is outperformed, “The Source Filename is Larger Than is Supported”. The entire envelope way will be locked from standard managing.

Why does the Source Path Too Long error occur?

The source record names are greater than is maintained by the archive structure will occur considering the way that Microsoft simply allows 268 characters in the envelope way subfolder. Whenever this cutoff is outperformed, “The Source Filename is Larger Than is Supported”. The entire envelope way will be locked from conservative dealing with.

If you’re doing combating to decide a comparable mix-up message, the procedures under will help you with settling the issue. Underneath you have a variety of systems that various customers in a similar situation have used to get the issue settled.

All of the methods presented below should resolve the issue. Feel free to follow whichever one has all the keeps of being more accessible to your current situation.



People Frequently Ask

Question # 1: How do I delete large file names?

Answer: To delete a too-long file, all you need to do is open a command prompt in the directory where the file is located and use a simple command to get the short file name. Open File Explorer and navigate to the directory where your files are located. Press and hold Shift, then right-click on an empty area.

Question # 2: What is ~$ filename?

Answer: From Wikipedia: “The tilde symbol is used to prefix hidden temporary files that are created when a document is opened in Windows. For example, when you open a Word document called “Document1. doc,” a file called “~$cument1. doc” is created in the same directory.

Question # 3: Can robocopy copy long file names?

Answer: Windows has a limitation where the entire path to a file cannot be over 265 characters. Microsoft has a command-line copy program called “Robocopy” (Robust Copy) that can copy files without this limitation. ROBOCOPY will accept UNC pathnames including UNC pathnames over 256 characters long.

Read More———

Question # 4: What does robocopy Mir do?

Answer: System administrators often have complex file transfer needs. Robocopy is a very powerful tool specifically, the Robocopy /mir command allows for robust and useful file and folder mirroring across folders and network shares.

Question # 5: How do I shorten a filename that is too long?

Answer: The option Short file names individually to reach a path length of x characters limits all file names to the set number of characters, depending on the total path length. This allows files from folders with fewer characters in the name to retain a longer name. The minimum length of the new file names can also be set.



How to Fix the slip-up ‘The source archive names are greater than is maintained by the record structure’?

“The Source Filename is Larger Than is Supported” By and by we will see the procedures that our Expert technologists follow to fix this issue.

Strategy 1: Deleting by bypassing the Recycle Bin

Our Expert technologists were successfully prepared to manage the issue by bypassing the Recycle repository absolutely. When struggling to remove the record or coordinator that is showing the error.

“The Source Filename is Larger Than is Supported”, basically select the report (or coordinator) that is showing the error and press SHIFT + Delete to forever remove the record (without going it through Recycle Bin).

System 2: Deleting a tree by making an interval index

“The Source Filename is Larger Than is Supported”, This physical philosophy incorporates making an interval coordinator arranged in the very inventory as the envelope that can’t be deleted.

  • Above all else, go to the root index of the drive which contains the coordinator tree that we can’t delete. For our circumstance, the root file is C:\, since we want to delete a movement of envelopes arranged in Documents. So go ahead and make a coordinator with a singular letter name in the root record.
  • Starting there forward, leave the single letter envelope until additional notice and investigate the inventory that we want to delete. At the point when we show up, select all of its substance and press Ctrl + X to cut them.
  • Then, at that point, investigate to and open the temporary coordinator (for instance, “The Source Filename is Larger Than is Supported”, envelope B) that we have as of late made and paste the substance by pressing Ctrl + V.
  • Then, move to the root file, right-click the temporary envelope and delete it.
  • Finally, “The Source Filename is Larger Than is Supported”, return to the main file and delete it.

If we have different envelope levels, we need to repeat the above system with all of them to have the choice to dispose of everyone. If this procedure was not practical, drop down to the accompanying method under.

System 3: Using the Microsoft Robocopy.exe mechanical assembly

“The Source Filename is Larger Than is Supported”, Most customers that attempted this technique definite that it worked flawlessly.

  • First thing, make an empty coordinator incomparable drive as the envelope with the long filenames. We named it unfilled.
  • Then, type “cmd” in Run brief and press Ctrl + Shift + Enter to open up a raised Command Prompt. When prompted by the UAC (User Account Control), click Yes at the brief.
  • Inside the raised request brief, type the going with to copy the empty envelope into the assigned coordinator, working with the eradication of the latest:
  • Robocop/MIR c:\*empty* c:\*targeted folder*

“The Source Filename is Larger Than is Supported”, Replace the *empty* and *targeted folder* placeholders with the certified names in our particular circumstance.

System 4: Using the Super Delete request line mechanical assembly

We can dispense with the irritating coordinators by using an open-source request line instrument called Super Delete. “The Source Filename is Larger Than is Supported”, To kill coordinators and reports that are showing the “source record names are greater than is maintained by the record system” error:

  1. Download the latest type of the Super Delete document.
  2. Then, eliminate the Super Delete zip coordinator and paste the Super Delete executable some spot sensible.
  3. Type “cmd” in Run brief and press Enter to open a Command Prompt window.
  4. Inside Command Prompt, use the CD request to investigate the space of SuperDelete.exe. If it is stuck into the root index of C, the request is plate C:\
  5. Then, at that point, use the going with the request to remove the coordinator or record that is showing the slip-up:
  • exe *fullPathToFileOrFolder*
  • Override the *FullPathToFileOrFolder* placeholder with the particular way in our particular circumstance.
  1. Press Y at the accompanying brief to assert the wiping out of the coordinator or report.

The coordinator or record is forever removed. “The Source Filename is Larger Than is Supported”, We can similarly effort to just rename the coordinators inside and it might discard this particular error.

Procedure 5: Use WinRAR programming

  1. First thing, open WinRAR if we have WinRAR presented on our structure.
  2. As of now, Browse to the particular record or coordinator with which we are facing this slip-up.
  3. As of now, select that record and snap-on Add.
  4. By and by, select Delete reports ensuing to documenting on the next screen.
  5. Snap OK.
  6. As of now, remove that recorded record furthermore accepting we want to delete that report earlier.

Accepting we want to move the archive. “The Source Filename is Larger Than is Supported”, reorder the record to a substitute region and a short time later eliminate it there.

Conclusion

In this way, “The Source Filename is Larger Than is Supported”. We saw how our Hosting Expert Planners fix the error. The source record names are greater than is maintained by the record structure”

70%OFF

Flash Sale

Hurry Up! Offer ends in
02 days
22 hrs
20 mins
36 secs
Buy Now