2 ms·
>SetCurrentDirectory allows setting the current directory to a UNC share. Exactly. The cmd prompt not setting UNC paths as current directory was introduced aro
by muststopmyths 4y ago
>SetCurrentDirectory allows setting the current directory to a UNC share.
Exactly. The cmd prompt not setting UNC paths as current directory was introduced around Windows 2000 (or maybe post-XP, it's been a while) to help legacy batch files being run from a share and then getting confused by being on a UNC path instead of one beginning with a drive letter.
This was also why, when you do a pushd \\server\share cmd.exe puts you on a mapped drive instead of directly on a UNC path.
If you use the Windows native version of tcsh, for example, you can happily use UNC paths as current directories and run commands (provided they don't try to parse drive letters from their CWD)