Comments on: The Path is Too Deep

By: Daryl

Daryl — Sun, 08 Nov 2009 14:08:01 +0000

“path too deep” error was coming up when I tried to transfer music onto my HTC Hero from T-Mobile via mounting the SD-Card using USB. A quick upgrade of the Andriod OS from T-Mobile website fixed it.

By: Patrick

Patrick — Fri, 25 Sep 2009 11:09:01 +0000

I was having this problem too when copying files from my PC to a Samba share on a Unix host. I changed the network card setting and it resolved it, for me on XP this was:
Start | Settings | Network Connections | right click – Properties | Configure (next to name of network card) | Advanced tab | Link speed & duplex. I changed the value from “Auto detect” to “100Mbps/Full duplex” and now it’s working fine and file transfers are much quicker. The setting name will be different if you have a different brand of network card to me (I’ve got “Intel(R) PRO/100 VM Network Connection”).

By: AKLEOS

AKLEOS — Wed, 23 Sep 2009 18:06:07 +0000

ok, so I will put this easy for people who just read the bottom posts. This has been stated throughout, but here goes.

1. This is a generic error message from Microsoft. It can mean anything.
2. If you get this error while transferring files over a network, switch the speeds so that they are the same on the sending and receiving machines. 10baseT with 10baseT or 100 with 100.
3. It could mean that you have a faulty hard drive. Run chkdsk with the /f switch.
4. If it is a problem with a USB drive connected with a cable, it could be a faulty cable. Change it.
5. You might have too many USB devices connected period. If you have hubs connected to hubs and devices in all those, there is not enough power for everything. Pick what you need or unplug everything, move the files, and plug it all back in.
6. You might have bad USB drivers. Uninstall and reinstall them.
7. Finally, and least likely, the file path and name is too long. Shorten it.

If you need instructions on how to do any of this, just scroll up and read the other posts or use the intergoogle.

Hope this helps.

By: itsmejohnnyt

itsmejohnnyt — Sat, 01 Aug 2009 03:53:03 +0000

A NEW USB CABLE FIXED IT FOR ME!!!

By: Nits

Nits — Thu, 09 Jul 2009 05:14:25 +0000

Mine was the same problem of path too deep, I changed the USB port and now my USB works fine. I think there was a problem in the extension wire I was using.

By: Bob

Bob — Thu, 09 Jul 2009 01:12:58 +0000

As previous post suggested- setting network adapter from auto to max speed cleared my problem that was through usb to external drives.

By: Bob

Bob — Thu, 09 Jul 2009 01:07:09 +0000

setting network adapter from auto to max speed cleared my problem that was through usb to x-drives

By: Chino

Chino — Sun, 21 Jun 2009 20:34:22 +0000

So no one has an easy hotfix for this problem….. can someone post a step by step for us guys that are still getting the plastic off the XT box and the 1/4 inch floppies…. com’on someone post a simple way to fix this problem and easy for Laymen to do. Please……

By: Simon

Simon — Thu, 18 Jun 2009 01:43:46 +0000

I had the same problem trying to copy a file from a server in one domain, to a server in another domain on the other side of the world, over a VPN.

Zipping the file didn’t help. Mapping a drive and using xcopy from a command prompt worked for me :-)

By: PAFFA

PAFFA — Sun, 14 Jun 2009 20:22:48 +0000

I tried all these – but it was a dodgy usb hub connection – reset it and the usb plug and was able to eliminate this error.

By: Kristopher Hoffman

Kristopher Hoffman — Wed, 10 Jun 2009 03:08:01 +0000

This is not only a network problem… and it has NOTHING to do with path length…

I am trying to copy a file from a USB pocket Hard Drive to my internal drive and I get the error.

The file is in the root on the Pocket Drive and the path I am copying to is d:\GH\

By: Tony Kresa

Tony Kresa — Wed, 27 May 2009 04:56:13 +0000

It is not a path error issue. It is an I/O timing device issue between hardware. (Comms Issue)

By: XP'd

XP'd — Wed, 08 Apr 2009 07:58:15 +0000

Helpful site and thread here.

I have a subfolder that causes Explorer to crash, and that cannot be opened by any other program, almost certainly because it contains many subfolders with deep paths and long file names. Windows XP won’t even let me rename the folder with a shorter name – just crashes.

Since I can’t recall all the subfolder names, I can’t use Robocopy to copy, move or rename.

Any ideas, such as a disk utility?

By: Chris

Chris — Thu, 15 Jan 2009 00:14:14 +0000

A few how tos
step 1 get robocopy from the windows 2000 resource kit.

to delete a path that is too deep:
step 2 create a dummy directory (ex.c:\dummyDir).
step 3 from a command prompt (Start–>Run, then type cmd)
type robocopy c:\dummyDir “c:\really really long anoying directory name her” /purge. this will delete every thing in the really anoying directory.

to copy a path to deep:
from a command prompt type robocopy

to move a path too deep, same as above but use the /MOVE switch.

Robocopy is by far one of the most usefull tools I have every worked with.

hope this helps,
Chris

By: Jeff Griffith

Jeff Griffith — Wed, 24 Dec 2008 18:53:52 +0000

Joe Jaworski – You are da man! I’d been battling this situation for a number of hours. Why oh why didn’t I switch the cables earlier? Because the SD Card reader I’m using is brand new! No excuse I know. I removed the cable and just plugged the reader itself into my USB hub (the cable was just an extension convenience) and BAM!!! Worked right away.

Thanks, Joe. Sure appreciate you.