Move-Item Cmdlet can't move items between different PsDrives - by dreeschkind

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


18
0
Sign in
to vote
ID 161675 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 7/11/2006 11:45:04 AM
Access Restriction Public

Description

Move-Item Cmdlet can't move items between drives.

COM seems to have the same problem according to:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windows.powershell&mid=9e93a77c-27a6-48a2-a315-04fa236dd8f3&sloc=en-us

So this seems indeed to be related to the internal usage of some outdated API calls. This is limiting and disappointing.

How can this shell deserve the name PowerShell if it can't natively (i.e. 
without some scripted workarounds) move folders from one drive to another.
Even Windows Explorer could do this 11 years ago (not sure about Fileman.exe 
right now...). I don't care about different drives, all I care about are the 
provided source and target path names and my files and folders being moved.
Sign in to post a comment.
Posted by Microsoft on 7/15/2010 at 6:18 PM
This was erroneously closed as by design. It has been fixed in an upcoming version of the product.
Posted by Stephen Mills on 5/1/2009 at 9:30 AM
dreeschkind,

Why don't you reopen the case for them to look at it again? You can edit it and set it to active. Hopefully they will then at least respond, because I agree that "By Design" is an excuse. Even "Postponed" would have been a better answer. Maybe it will make it to V2, but it didn't make it in V2 CTP3 in any case. Looking at the help in V2 CTP3 makes that clear.
"Move-Item will move files between drives that are supported by the same provider, but it will only move directories within the same drive."
Posted by dreeschkind on 6/5/2007 at 3:24 PM
I really hope "By Design" is only true for version 1.
The next version of PowerShell has to have this feature because everybody would expect this to work.
Everything else is just *not* intuitive.
Posted by EE5275CE-92BE-4479-A76D-DE620E268B2A on 8/14/2006 at 4:36 PM
I don't think "By Design" is the right resolution.

The product was /designed/ to have this limitation? What good does this limitation bring the user?

I could see "Won't Fix" as a resolution, but "By Design"?