top of page

LITIGATION SUPPORT TIP OF THE NIGHT

The views expressed in this blog are those of the owner and do not reflect the views or opinions of the owner’s employer. All content provided on this blog is for informational purposes only. The owner of this blog makes no representations as to the accuracy or completeness of any information on this site or found by following any link on this site. The owner will not be liable for any errors or omissions in this information nor for the availability of this information. The owner will not be liable for any losses, injuries, or damages from the display or use of this information. This policy is subject to change at any time. The owner is not an attorney, and nothing posted on this site should be construed as legal advice. Litigation Support Tip of the Night does not provide confirmation that any e-discovery technique or conduct is compliant with legal, regulatory, contractual or ethical requirements.

See my post on Running Regex Searches With a Grep Utility on the ILTA litigation support blog.

New tips for paralegals and litigation support profesionals are posted to this site each week. Click on the blog headings for better detail.

See How-To Videos on my YouTube channel.

32,767: the real Windows file path limit

Sean O'Shea
Jun 3, 2021
1 min read

Updated: Jun 4, 2021

The Litigation Support Tip of the Night for March 13, 2017 discussed how to get around the 255 limit for file paths in Windows Explorer in the Windows 10 operating system. The actual NTFS file system used by Windows actually has a far longer file path limit of 32,767 characters. See this post to the Microsoft Windows Developer site on Maximum Path Length Limitation., which confirms this is the limit. The reason why is that this is highest number that can be used for a 16-bit application written for early versions of Windows.