-
Notifications
You must be signed in to change notification settings - Fork 2k
Upgrading
The process of upgrading Cmder depends on the version/build you are currently running.
If you have a [cmder_root]/config/user[-|_]conemu.xml
, you are running a newer version of Cmder, follow the below process:
-
Exit all Cmder sessions and relaunch
[cmder_root]/cmder.exe
, this backs up your existing[cmder_root]/vendor/conemu-maximus5/conemu.xml
to[cmder_root]/config/user[-|_]conemu.xml
.- The
[cmder_root]/config/user[-|_]conemu.xml
contains any custom settings you have made using the 'Setup Tasks' settings dialog.
- The
-
Exit all Cmder sessions and backup any files you have manually edited under
[cmder_root]/vendor
.- Editing files under
[cmder_root]/vendor
is not recommended since you will need to re-apply these changes after any upgrade. All user customizations should go in[cmder_root]/config
folder.
- Editing files under
-
Delete the
[cmder_root]/vendor
folder. -
Extract the new
cmder.zip
orcmder_mini.zip
into[cmder_root]/
overwriting all files when prompted.
If you do not have a [cmder_root]/config/user[-|_]conemu.xml
, you are running an older version of cmder, follow the below process:
-
Exit all Cmder sessions and backup
[cmder_root]/vendor/conemu-maximus5/conemu.xml
to[cmder_root]/config/user[-|_]conemu.xml
. -
Backup any files you have manually edited under
[cmder_root]/vendor
.- Editing files under
[cmder_root]/vendor
is not recommended since you will need to re-apply these changes after any upgrade. All user customizations should go in[cmder_root]/config
folder.
- Editing files under
-
Delete the
[cmder_root]/vendor
folder. -
Extract the new
cmder.zip
orcmder_mini.zip
into[cmder_root]/
overwriting all files when prompted.