Generally spoken licensing issues can have two reasons:
1. The license key hasn't been entered correctly or not completely
Sign for this: Nothing happens upon clicking on "enter key".
Fix: Be sure to enter the whole user-id expression including name, id
and number in the upper field and not just the number.
2. Windows user account control (UAC) protection
Sign: No reaction when clicking into the blue window, and error message
saying "can't create license file" or plugin again unlicensed after re-launching
it showing the frozen license data when clicking into the blue area.
Fix: set the default running mode of your vst host to administrator: Right-click
on the host application shortcut, choose properties->compatibility and here check
"run as administrator" and confirm. It may be needed to re-license the plugin now.
Generally note that the plugin even when licensed successfully only will start working after
unloading and re-launching it.
More comprehensive infos:
1. The license key hasn't been entered correctly or not completely
A sign for this is that nothing at all happens when you click on "enter key"
after entering your license data. In this case again check if the key has been
entered correctly. A common mistake is only to enter a number in the upper field
instead of the whole user id line which consists of name and id plus number. So
be sure to enter the whole expression. Use copy & paste to avoid typing mistakes
and be careful not to add any additional space bars at the beginning or at the end
of the lines. If you type it in manually it's good to know that 0 in the lower line
always is the number and not a letter. In VFX mac use the windows paste (ctrl + v)
since the mac paste won't work within VFX.
2. Windows user account control (UAC) protection
Signs for this could be that nothing happens on clicking into the blue area (so no reg
window is showing up), or that upon clicking on "enter key" a message saying "can't create
license file" appears, or that the plugin after successful licensing again turns unlicensed
on next launch showing your license data upon clicking into the blue area in frozen state.
Such windows UAC based issues can arise when the plugin resides within the system's protected
area (which includes the program files folder which unfortunately in most cases is the default
plugin destination) and at the same time your vst host has no administrator permissions. In this
case windows either re-directs writing and reading to a save hidden mirrored place (called virtual
store) which sometimes works well (then you won't even notice it) but sometimes also not (then it
causes issues) or even completely blocks writing or any other actions of the plugin. If you're
interested you can read more technical background infos about windows UAC on this page:
Windows uac virtualization
The fix however is easy. There are three ways:
- set the default running mode of your vst host to "administrator"
- change the writing rights of the "SonicProjects" folder to allow writing
- have the plugin's place somewhere else than in the program files folder
Setting the default running mode to "administrator" is the easiest way to fix it and gives back the program
full writing rights. It won't affect functionality. The host providers often even recommend to do this.
It can be done like this: Right-click on the host application shortcut. Here choose "properties->compatibility"
and check "run as administrator" and confirm. Done!
Alternatively (method 2) you can change the rights of the "SonicProjects" folder (make
sure all subfolders are included too) to allow writing. This folder can be found in your
vst plugins folder. So right-click on the "SonicProjects" folder, choose properties->security,
and here choose the "user" line. Click on the "edit" button to change the rights.
In the popup-list check "write" to allow for writing to this folder as user and save.
Alternatively it also suffices to do this only with the "OP-X PRO-II" folder which can
be found within the SonicProjects folder. But if you do it for the whole SonicProjects
folder then normally all subfolders will be included.
Another method (method 3) would simply be to install the plugin to a different place
which is not protected, e.g. to your documents or music folder. You only have to add
this path then in the vst plugin properties of your sequencer.
Don't hesitate to contact us by email if your question could not be answered here.
Contact us
