Failed to copy ConEmu.xml.default file at launch

[pooley]

Hi,

I just downloaded the 1.3.11 (latest version) (from the website and also tried the version from GitHub). Downloaded the mini version. Have tried unzip it in a "cmder" folder in different places (program files, then elsewhere like %USERPROFILE% when I read about the issues it might cause) but still the same at launch the cmder launcher answer me this :

Failed to copy vendor/ConEmu.xml.default file to vendor/conemu-maximus5/ConEmu.xml!

Not a big techie but I use this software at work and never had this kind of error (not the same version at work tho) but this time i put the exe in the bin folder.

I'm on a zenbook s13 (16Gb version) if this can help.

[daxgames]

I have never seen this issue. I have seen the opposite, when trying to copy %cmder_root%/vendor/conemu-maximus5/ConEmu.xml to c:/program files/cmder/config.

My guess is you originally expanded into c:/program files/cmder then moved cmder to %userprofile% bringing the permissions issue along with it.

Delete what you have. Download and expand a fresh copy into %userprofile%.

[daxgames]

Also what do you mean ' but this time i put the exe in the bin folder.'?

[daxgames]

@pooley ???

[pooley]

Sorry for the delay in the reply, I've been moving lately. I have re-installed the sftwaare and all went good. (the error message occures after the optional step (Place your own executable files into the bin folder to be injected into your PATH). But all went good after a fresh delete/install Le sam. 1 juin 2019 à 03:52, Dax T Games <[email protected]> a écrit :

…

@pooley <https://github.com/pooley> ??? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2092?email_source=notifications&email_token=ABKUF3HNQ2FWDHWHRI2FX6LPYHI5TA5CNFSM4HLVRKSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWWWKZY#issuecomment-497902951>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABKUF3BIPI2W5HWP4DP3ZNLPYHI5TANCNFSM4HLVRKSA> .

-- <http://www.el-be.fr>

[RajeshSamson]

I had solved my problem by just adding the root directory instead of Cmder/bin.

[Zolfikaar]

I have same problem for while, and just now i solve it by copying the file (ConEmu.xml.default) that the app can't copy

to the direction he want (/conemu-maximus5/)

[renatosviana]

I had the problem and solved opening it as Administrator.

[daxgames]

@renatosviana just dont put it in c:\program files.

[yassine-klilich]

I had the same issue, I have just moved the Cmder folder from C:\Program Files to C:\ and everything went well.

[yildizmy]

In addition to move the cmder folder to C:\ directory, you may also need to apply the following settings in order to run it as administrator for each start.

[KodiakFR]

Hi, it's late but look your Window Defender, for me it blocked the copy files.

[prox108]

I already solved the problem, it happens that you are copying the Cmder.exe file directly from the folder (Control + C and then paste on the desktop), the solution was to Right Click on the file, select "Create Shortcut" and accept to create it in the desktop.

[melanke]

I feel this problem could be avoided if there were an installer for cmder instead of a zip

[daxgames]

This is going to sound harsh. It is not meant to be. It is just an explanation.

It's not a problem if you don't unzip the zip where we tell you not to in the README.md

There is a reason Cmder should go in your user profile and not a 'public' readable Administrator only writeable folder.

The config folder could potentially contain user private stuff depending on what you put in it since Cmder is intended to be portable.

User private stuff should never be in C:\Program Files or any other public readable folder.

If you insist on putting it where we tell you not to, you can avoid the issue by launching Cmder with a command line arg that redirects the config folder to a user writeable path.

Cmder /c `%userprofile%\cmder

[18hyacinthe]

Me I just do (right click on the folder cmder) after go to the security option !

Just modify to allow settings (permission) for actual user ! And save it !

[chrisant996]

Me I just do (right click on the folder cmder) after go to the security option !

Just modify to allow settings (permission) for actual user ! And save it !

That makes it possible for viruses to infect the files there.

I realize that putting Cmder elsewhere also makes it possible for viruses to infect the files.

My point is that generally speaking, it's not a safe practice to grant write permissions to any \Program Files\ subdirectory. It's not a habit to get into.

[DRSDavidSoft]

Best would be to make sure that only the /config dir is writable, and preferably move it to AppData per user, and add some logic in Cmder where if the conditions a) installed in Program Files and b) AppData\cmder\config exists, load it from there.

I assume @cmderdev/core might not agree with adding "installation" support to Cmder and keep it an portable-only app, but I believe adding this feature would be nice. I use Cmder on my machines in a totally non-portable fashion, as I don't move it using a USB stick or cloud sync. I've just "installed" it in Program Files, using @18hyacinthe's approach, even though @chrisant996's concerns are totally valid.

It's a bad idea to give un-necessary permissions to the Program Files folder, but in this case, you either need to keep Cmder in the root C:\ or some dir like C:\apps which doesn't look right to me. 🤷🏻‍♂️ Hopefully this will be addressed in something like #2788.

[daxgames]

No installer suport or special logic is required to use Cmder in a non portable way see the README.md sepcifically the /c [path] command line arg.