Comments on: Xcopy: Insufficient Memory http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/ I will not fix your computer. Tue, 04 Aug 2020 22:34:33 +0000 hourly 1 https://wordpress.org/?v=4.7.26 By: George http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-300552 Tue, 22 Mar 2016 18:50:43 +0000 http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-300552

Thanks for this post, you pointed me the cause of the error. Not memory. Length of path! D’oh!

Reply  |  Quote
]]>
By: FGranados http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-211559 Sat, 24 Jan 2015 07:30:14 +0000 http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-211559

@ mrbios:You can also use Long Path Tool to sort out this problem.

Reply  |  Quote
]]>
By: Leopoldo Betancourt http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-52054 Tue, 17 Sep 2013 15:37:44 +0000 http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-52054

Hello there… I had the same problem… I´ve executed the following script:

robocopy
xcopy u:\*.* e:\documentos\ /O /C /Y /E /D

then I´ve tried changing the last parameter

robocopy
xcopy u:\*.* e:\documentos\ /O /C /Y /E /J

In both cases, after one hour I got the same error:

INSUFFICIENT MEMORY

Do you have an explanation and a solution for this? Thanks in advance

Reply  |  Quote
]]>
By: Anil http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-26385 Mon, 28 Jan 2013 16:38:10 +0000 http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-26385

It has the same problem on Win 7 – 64bit! Yikes!

Reply  |  Quote
]]>
By: bitkahuna http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-12580 Tue, 16 Jun 2009 17:59:17 +0000 http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-12580

Thanks very much for posting this. xcopy not copying certain (or in my case THOUSANDS of) files was a real problem. and i’m not using network shares, this is just on a server to an external drive.

Reply  |  Quote
]]>
By: mrbios http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-11741 Sat, 07 Mar 2009 23:33:54 +0000 http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-11741

Your welcome!

Reply  |  Quote
]]>
By: David Monaghan http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-11576 Fri, 20 Feb 2009 03:13:04 +0000 http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-11576

Thank you: I ran into this problem and am testing out the xxcopy solution now but have saved both for future use.

Reply  |  Quote
]]>
By: mrbios http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-8970 Mon, 05 May 2008 22:59:03 +0000 http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-8970

SOLUTION:

The source drive D: was FAT32 the Target is an xp box share drive formatted with NTFS mapped to Z:\ permissons Everyone Full Control. Both xp pc’s are running xp pro sp2.

The files that failed to copy were in a stored xp user profile folder (no in use and not in \documents and setings\ so there were no file lock issues. I ziped the user profile folder which was about 10 megabytes and the problem went away.

I then moved the two user profiles into a dir called d:\delme and created a bunch of really long folder names like “zzzzzzzzzzzzzzzzzzz33” and everything copied find, total files matched and so did size to the byte.

–> Microsoft does not acknowledge the problem on their web site.

SOLUTION:
I copied D:\DRIVERS (FAT32) to E:\DRIVERS (NTFS), both D: and E: are normal local SATA drives / partitions then I performed the copy again and it worked. The total number of files was: 3,438 and ~ 652 megabytes. The copy took an unusually long time 3 or 4 minutes when it should have taken less than 20 seconds. Usually, the copy speed is 30 to 40 MB/sec.

The problem seems to be related to the network redirector and or aka mapped drive’s inability to properly handle some file/folder name lengths or types going from FAT32 to NTFS.

Reply  |  Quote
]]>
By: Luke Maciak http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-8969 Mon, 05 May 2008 22:58:43 +0000 http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-8969

Yup – long file paths are usually the cause here. I recommend using Robocopy instead. :)

Reply  |  Quote
]]>
By: mrbios http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-8968 Mon, 05 May 2008 21:28:26 +0000 http://www.terminally-incoherent.com/blog/2007/02/05/xcopy-insufficient-memory/#comment-8968

I have the same problem with xcopy on xp sp2+ copying over a network mapped drive. It misses files. I suspect long path names or certain system files?

Reply  |  Quote
]]>