nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Loading Issue: Massive X could not be loaded." message in Komplete Kontrol after updating BIOS

Seanbox

After my laptop updated its BIOS, Massive X will not open, despite using it in Ableton before the update. In Komplete Kontrol the preview of Massive X presets still play, but when I clear the cache after going through 26 VST's (used to be 49) it has a section of loading specifically Massive X 1/1 (used to be 1/2 and 2/2). I've troubleshooted multiple options: Checking AVX, clearing cache of Komplete Kontrol and Massive X, checking if there's an update for my audio and graphics drivers, making audio go through an audio interface, getting rid of the exclusive mode for the audio driver, removing all plug-in locations from Komplete Kontrol except VST3, (which lowered VST count on startup splash), and redownloading NTKDaemon and Native Access (which fixed Native Access trying to download NTKDaemon every time it opened). I even went into BIOS and tried to disable AVX Offset and Intel Virtualization, but those weren't options, and I did a pagefile reset.

The LLM is starting to get into stuff that seems dangerous and its been wrong multiple times during the process so I'm weary of continuing to troubleshoot through it.

Find more posts tagged with

Native Access 2

Komplete Kontrol SW

Accepted answers

All comments

PoorFellow

https://community.native-instruments.com/discussion/51840/loading-issue-massive-x-could-not-be-loaded-message-in-komplete-kontrol-after-updating-bios

"Loading Issue: Massive X could not be loaded." message in Komplete Kontrol after updating BIOS

Does this include in the standalone version of Komplete Kontrol app ?

Have you tried Resetting the Komplete Kontrol Database ? Then run stand-alone app version of KK prior to using in any DAW (give it plenty of time to regenerate DB).

To see if it is of any help then you can also try removing Massive X , then start DAW and KK, then close apps and then re-install Massive X.

Vocalpoint

Updating your BIOS - has nothing to do with correct operation of Komplete Kontrol.

And a screencap of the error would help.

Seanbox

@PoorFellow @Vocalpoint
Attached is the error message.

I've reset the database multiple times during my troubleshooting. I uninstalled Massive X and its factory library, launched and exited KK, reinstalled Massive X and its factory library, and I'm still having the error.

Vocalpoint

https://community.native-instruments.com/discussion/comment/269162#Comment_269162

Hmm

First thing that caught my eye is this:

Just wondering exactly why you would be using KK - without an actual Kontrol Series Device.

It should look like this - if one is present:

Second question - what happens if we do not use Komplete Kontrol at all in Ableton - and just try to load Massive X onto a track by itself?

Update when you can.

Seanbox

@Vocalpoint

I'm currently not at my studio, so my midi controller isn't connected right now.

When loading Massive X onto a track by itself, it finally opened! It took a bit to work through all of the presets. However, when going through KK again outside of Ableton, the same error showed up. I went back into another Ableton project and loaded Massive X, and it opened just fine without having to work through the presets. KK still would not open Massive X in Ableton.

Vocalpoint

https://community.native-instruments.com/discussion/comment/269165#Comment_269165

That error seems to be starting in Ableton then. Either by its plugin scan or lack thereof

Seanbox

@Vocalpoint

Even with KK not loading Massive X outside of Ableton?

Vocalpoint

https://community.native-instruments.com/discussion/comment/269167#Comment_269167

Apologies. If this is occurring in KK standalone - that is a KK issue.

My first move there would be to delete the KK database. Instructions are scattered around the forums here on how to do this properly.

VP

Seanbox

@Vocalpoint

I've reset the KK database multiple times during my troubleshooting.

PoorFellow

https://community.native-instruments.com/discussion/comment/269169#Comment_269169

What is your Komplete Kontrol version ? And what is your N.A. version ?

When loading Massive X onto a track by itself, it finally opened! It took a bit to work through all of the presets.

Was that using Massive X as a VST or as a VST3 ?

In Komplete Kontrol standalone plugin preferences then supposing that you opened VST3 in DAW as OK then have you tried removing check-marks in Massive X VST versions and left only check-mark in Massive X VST3 , then closed preferences and exit Komplete Kontrol and then re-opened Komplete Kontrol again to see if that makes any difference ?

Vocalpoint

To add to Poorfellows update…

Check this path and make sure both are valid (ignore the L drive as that is my specific location - yours will be different):

And check here as well:

If both of these areas within Komplete Kontrol are as above - then I am out of suggestions.

Also - show us what you have going on under Preferences→File Locations within Native Access - here is mine:

Seanbox

@PoorFellow @Vocalpoint

The fact that Massive X is not showing up in Manager despite being in the folder could be the problem.

I'm unsure how to know if I was using Massive X as a VST or VST3 in Ableton.

Seanbox

@PoorFellow @Vocalpoint

Massive also does not show in C:/Program Files/Common Files/Native Instruments or VST3

Vocalpoint

https://community.native-instruments.com/discussion/comment/269214#Comment_269214

Well - now we have the cause. Can't load a plugin if it's not there.

"Massive also does not show in C:/Program Files/Common Files/Native Instruments or VST3"

You must have some sort of install issues here

For anything to work - these two need to be here:

Native Access installs ALL VST3 plugins (by default) to the system specific directory which is:

C:\Program Files\Common Files\VST3

We (users) cannot redirect this location or influence it either.

I would also run a search - system drive wide - on where "Massive.vst3" and "Massive X.vst3" actually are.

Pop up a screencap when you find them.

PoorFellow

https://community.native-instruments.com/discussion/comment/269214#Comment_269214

Your Komplete Kontrol plugin scan paths looks wrong to me .

There should be no plugins at : C:\Program Files\Common Files\Native Instruments

And you should not install plugins to D:\NI Content either

All plugins should be installed to their default directories at the system drive C:

I'm unsure how to know if I was using Massive X as a VST or VST3 in Ableton.

That would be extremely easy to determine : open Ableton and do it again and then see if it is VST or VST3 .

The fact that Massive X is not showing up in Manager despite being in the folder could be the problem.

Yes , But Massive Xis in what folder exactly as what ? The Massive X should show as type VST3 at : C:\Program Files\Common Files\VST3

Massive also does not show in C:/Program Files/Common Files/Native Instruments or VST3

Massive or Massive X ? , Anyway neither should show at : C:/Program Files/Common Files/Native Instruments

They should both show at : C:\Program Files\Common Files\VST3 as type VST3

Quick links

Unanswered questions