CMD does not support UNC paths as current directories

cmd path unc
Nelson picture Nelson · Jul 13, 2017 · Viewed 23.1k times · Source

We have batch scripts that seem to run fine however I am editing one of them to include some new work and when manually running the script (by double-clicking from windows explorer) I get the above error message each time a pushd command in the script is encountered. These are pushd commands that have been there since the year dot and the scripts are running fine. Is there a difference between the batch script running manually and when started by a scheduler? How can I disable the error message when running manually (if this is possible)?

Answer

Arsalan Kazmi picture Arsalan Kazmi · Nov 26, 2018

I have some advice - consider rewriting your script in PowerShell. PowerShell allows the current working directory to be on a network. PowerShell as a whole is more versatile and powerful than CMD is. It's also cross-platform. Consider switching.

Related questions

Set a path variable with spaces in the path in a Windows .cmd file or batch file

I'm new to script writing and can't get this one to work. I could if I moved the files to a path without a space in it, but I'd like it to work with the space if it could. I …

Read More
How to get folder path from file path with CMD

I need path to the folder that contains cmd file. With %0 I can get file name. But how to get folder name? c:\temp\test.cmd >> test.cmd P.S. My current directory != folder of the script.

Read More
How to update PATH variable permanently from Windows command line?

If I execute set PATH=%PATH%;C:\\Something\\bin from the command line (cmd.exe) and then execute echo %PATH% I see this string added to the PATH. If I close and open the command line, that new string is …

Read More