Updating and uninstalling VMX

Updating VMX: VMX provides a simple handy command which allows you to say “update vmx please” to download and install the latest version. Note that when moving to major versions i.e 2.2 to 2.3 or 2.x to 3.x for example it is always recommend that you uninstall the previous version first, then run the new full installer from your account. The full installer performs a few additional checks which may reduce the possibility of niggling problems. Details about using the uninstaller can be found further down in this article if you are unsure.

Using the auto updater from within VMX itself:

  • Step 1: Load up VoiceAttack and ensure VMX is loaded
  • Step 2: Say ‘update vmx please’ – The system should now grab the latest update from the server and automatically install for you.
  • Step 3: Once the installer has complete just click on FINISH, VoiceAttack will automatically load for you. Delete the old VMX profile from within VoiceAttack in the usual way, then click IMPORT within VoiceAttack and select the new VMX Dark Edition.vap. The .vap will be located in VoiceAttack/Sounds/VMX_Player. That’s it! Simply restart VoiceAttack.

Tip: You do not HAVE to use the ‘update vmx please’ auto update feature. You may always use the standard installer downloadable from ‘my account’ on DarkNebula.cloud if you wish. This may be useful if you have just uninstalled VMX, performing major update (i.e 2.2 to 2.3) or are re-installing after some troubleshooting. Simply follow the standard installation guide here https://darknebula.cloud/2019/10/12/installingvmx/

Uninstalling VMX:

Navigate to your VoiceAttack root folder (where VoiceAttack.exe is located) you will see an ‘UninstallVMX.exe’. Simply ensure that VoiceAttack is not running and then double click the uninstaller.exe and this will uninstall all VMX elements for you.


If you experience any other issues then please try starting VoiceAttack in Administrator mode prior to calling ‘update vmx please’ and also start VoiceAttack in Administrator mode when importing the new VMX .vap file into VoiceAttack. None of this should be necessary for VMX but your own Windows security settings might require it.

You may also like