Please could you let me know if there is anything I can use or an alternative method to deal with this.

Robocopy is a great alternative though, it is a solid tool that is not bothered by the long path limitation and it can be called from PowerShell.

There are no additional considerations aside from different variables in PowerShell when compared to the command prompt, eg: env:systemroot instead of systemroot.

You can try Robocopy but it didnt helped me at all and made the situation worse.

I am using its enterprise edition currently Give it a shot and try its trial version.

It supports UNICODE and over MAXPATH (260 characters) file path names.

All of these suggestions assume you have some sort of write access on the network shared foldercomputer.

If you cant do any of these then you might need help from your administrator.

It can delete, copy, move and bulk rename long path files or locked file easily.

My only complaint is that its command line doesnt appear to have a switch to Displays files that would be copied, where XCOPYs L switch is great for versioning via script prior to the actual copy.

By using our community you consent to all cookies in accordance with our Cookie policy.

Xcopy File Path Limitations