But thanks to the good folk at Experts-Exchange’s assistance, I was good to go, attempting to move or delete the file generated the error you see above. Windows is pretty good at protecting itself. The most difficult part was replicating the script. I didn’t have a solution of the top of my head, but I thought I’d try and recreate the problem, and see if there was a simple solution. The little darlings had got hold of a script that recursively created nested folders, and as obviously this is hilarious it had happened multiple times. In a former role my colleague did a lot of work in schools and was forever coming across this problem when doing file migrations.Īs it transpired this was a problem at, yes you’ve guessed it a school that was a client. “Have you come across a problem deleting folders with long filenames?” I got asked this question twice in the first week at a new job. Try moving to a location which has a shorter path name, or try renaming to shorter name(s) before attempting this operation.

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

Free long path tool rename