No, it is not really. Sometimes this error happens even if I copy a file with a single character name from the root folder on any non-storage pool disc drive to one of the Windows Home Server shares. And this happens only when copying those files inside the server itself. There's no Path Too Deep in this operation. It's just an error message that doesn't explain anything.
The error won't happen if I copy files from one disc on the server to another folder on the server from a client PC. But this is no a feasible workaround because copying a bunch of 30 GB files roundtrip over the LAN is an exercise in patience, if you have tried network copies with Windows Vista.
I've submitted this as a bug during beta, applied a debug driver, installed a fresh copy of RTM, and submitted this as a bug again. So far no fix for this, not even in Windows Home Server Power Pack 1.
Of course it is not as bad as the Windows Home Server file corruption bug. Bad it is bad if you have large files that reside in a drive on your server and you want copied to the storage pool - for backup purposes for example.
I found out that this error only happens if you use the standard copy procedure: select file(s), Copy, select destination, Paste. Or drag and drop from source to destination.
So I decided to try alternative copy methods. And I found that Teracopy is much faster, can be paused/restarted and most important: it does not show the Path Too Deep error.
It can be configured to completely replace the standard method - even being invoked when you Copy & Paste or drag-and-drop a file or folders.
Other related posts:
Windows 8 Mail app not hyperlinking emails
Are we seeing the death of Windows RT?
Windows 8 Consumer Preview
comments powered by Disqus