Move-Action: pasting script paths inside URN directory doesn't recognize paths as valid. #28354

Since Tab completion fixes it, the pasted path doesn't match the real file name exactly as PowerShell reads it. Two common causes, and both are easy to check:

1. Square brackets in the file or folder name. move is Move-Item, and its first argument (-Path) accepts wildcards, so [ and ] are read as a character range. '.\Drawing [Rev A].dwg' matches nothing and you get "Cannot find path". Tab completion works because it escapes the brackets with backticks. Use -LiteralPath, which takes the name as written:

Move-Item -LiteralPath '.\bar.ext' -Destination '.\foo\bar-rename.ext'

2. An invisible or look-alike character from wherever you copied the text. A non-breaking space, an en dash instead of -, curly quotes or a zero-width character looks identical but doesn't match. That's also what #24037 is about. To check, paste the path into this and look for anything that isn't plain ASCII (above 7E) such as A0, 2013 or 200B:

'<paste the path here>'.ToCharArray() | ForEach-Object { '{0} {1:X4}' -f $_, [int]$_ }

If it's this one, fixing the source text (or typing those characters by hand) solves it.

The network location itself shouldn't matter. Relative paths like .\bar.ext work fine from a \\server\share location. If you post the exact error message (and the name, with sensitive parts swapped out but brackets and dashes kept), it's easy to tell which case it is.