i use automap, yeah yeah. from version 2.8.5 i noticed a different behavior when starting maschine, all new plugins i bought, and where automapped.. where re-scanned at startup. the behavior: if start maschine the automap version will be loaded, next time i start machine the none automap version will be loaded. and so on. a toggle (not a native speaker). i was using windows 7 pro, but that installation had problems, so i upgraded to windows 10 pro. the behavior that i was afraid of; it now affects all plugins that are automapped. i am not yet ready with reinstalling everything, but did the test.. with plugins that i am installing. i own maschine 2.x for 2 years or so, never had this behavior problem. so: when starting maschine it rescans the automapped plugins; when last the time i started maschine it was the automapped version of the plugin, it loads the non-automapped version and when the last time it was the none automapped version of the plugin that was the chosen one (..), it loads the automapped version of the plugin. the normal behavior was: both versions where loaded, not always, in the sense, that certain plugins only showed as the automapped versions (which also happens in cubase, for some plugins). no problem. it was stable, no rescans.