I have a customer who is planning on moving all their files from an NTFS Windows Server 2008 R2 based file storage to a cloud based storage system. As part of our standard due-diligence, we discovered a lot of long file paths (over 255 characters). I remoted into both a Windows 10 and Windows 7 computer to run some tests. I found it very odd that I was able to open, save, manipulate, move, etc. some of the longest paths with no issues whatsoever. On both Windows 7 and 10, I wanted to verify that the paths were actually too long for Windows. I used Explorer's "copy path" feature and noticed that Explorer was presenting me with the 8dot3 or short file path instead of the long path I was expecting (see screenshot). On every other network I have tested this on, I see the entire path, not the shortened path.