Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

*.BAT executed from network path shows error message #1318

m0n opened this issue Nov 15, 2017 · 2 comments

*.BAT executed from network path shows error message #1318

m0n opened this issue Nov 15, 2017 · 2 comments


Copy link

m0n commented Nov 15, 2017

CMD.EXE's UNC Check .reg

ConEmu build: 171109 x64
OS version: Windows 10 LTSB v.1607 x64
Far Manager: version 3.0 (build 5095) x64 (latest nightly as of 2017-11-15)

When I execute a *.BAT file from FAR when active panel is a network path:

\\Server\Shared\Music > play_audio.bat song.mp3

...then *.BAT executed well but I get this annoying error message:

CMD.EXE was started with the above path as the current directory.
UNC paths are not supported.  Defaulting to Windows directory.

To dismiss this message I already set HKEY_CURRENT_USER\Software\Microsoft\Command Processor\DisableUNCCheck=1 (see attachment "CMD.EXE's UNC Check - disable.reg")

This registry setting works in plain FAR, but it not works when FAR started from ConEmu :(

That's the problem =)

@Maximus5 Maximus5 reopened this Nov 15, 2017
Copy link

Support UNC paths in cmd.exe ?

Copy link

m0n commented Nov 15, 2017

Ahhh man.....

I spent 2 hours for making this bug-report... XD ConEmu settings are so huge, I didn't thought there is a separate checkbox for this functionality.

Many thanks Maximus5!

@m0n m0n closed this as completed Nov 15, 2017
Maximus5 added a commit that referenced this issue Nov 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

2 participants