pekbro wrote:ProgramData is just a predefined folder destination for installshield,
it is not compulsory to use it. Even as a default, typically you would
group things in a unique directory, rather than clogging things up
with tons of flagged, product coded files.
Sorry, a well planned and considerate installation is not going to
resemble what NI has done at all.
Guidelines exist for a reason - so that third party programmers and builders, users, maintenance technicians, etc. know where to look for something. This is almost "enforced" in Mac OS X, where you can't have custom plug-ins folders, and all the support files go to Library/Application Support, for example - and has been like that since the very beginning of OS X. Even the applications themselves are self contained bundles, that only sees a double-clickable icon, and some system folders are hidden as well.
It's good to see NI follow the guidelines from the OS builders. If all the programmers followed as well, we would certainly had much less troubles to get the OS working always properly and with no issues. So, "a well planned and considerate installation" is the one the follows the guidelines from the OS makers . It's the safest path certainly, IMO
I have installed Komplete 11 this Summer over previous installations of Komplete, and didn't have any problems. I also installed it from scratch on another system, and didn't have a problem either. I left everything as default, therefore, the plug-ins are installed in Program Files/Native Instruments.
The only custom directories I use are for the libraries, but after I set those, everything goit installed properly.
I then go there, and copy the DLLs to the proper VstPlugIns folders, leaving the originals untouched. Never had a problem.
For those that are experiencing problems my advice is: Uninstall EVERYTHING, then reinstall using Native Access. All your problems will probably vanish.