Can you provide W10 / W11 screenshots of the Kontakt 8 Player folders, subfolders and content?

Hi, i'm new to using NI and am unable to install Kontakt 8 Player.

I experience basically the same nightmare as described here:

https://community.native-instruments.com/discussion/45616/help-every-install-operations-from-native-access-wont-actually-do-the-installation

I managed to install all other items in my library except the Kontakt 8 Player, no matter if i try to install it via Native Access or manually form the .exe.

Even when Native Access reports it was successfully installed, there is no folder or content labeled "Kontakt 8" anywhere to be found.

The NI Uninstall RegTool_64bit shows no "Kontakt 8 "to uninstall.

When i browse my "users/…/AppData/Local/Temp/" folder, it contains some mia folders, which obviously hold the files that need to be installed.

So my idea is to manually copy over the files to where they need to be placed. This has worked for some instruments according to this post

https://community.native-instruments.com/discussion/20335/advanced-guide-native-access-installation-problems-and-how-to-fix-them-manually

To be able to do so i would need to know these places or folders, including their subfolders and content.

If you have successfully installed Kontakt 8 (Player) on a W10 or W11 machine, would you perhaps help me out and share the path names as well as screenshots of the Kontakt 8 folders, subfolders and their content?

Thank you in advance

Find more posts tagged with

Accepted answers

All comments

DunedinDragon

Quite honestly the place I would start before trying to hack the system is to look in Native Access File→ Settings → File Management and check your Download Location and Application Location and make sure they're set to their defaults. Content Location can be any storage location you prefer for libraries, but you should leave those two set to the defaults which are 'C:\Users\Public\Downloads' and 'C:\Program Files\Native Instruments' respectively as they're used for system actions rather than content libraries. Or you can just click on the Restore Defaults button.

Vocalpoint

Cannot tell what this means:

But have a pretty good idea.

Are you running ON Linux or an actual Windows 10 install?

If it is the former - Linux is not supported.

Nativicus

Thanks for your replies so far.

To avoid further misunderstandings:

Yes, i run the NI apps on a Linux system IN a the WINDOWS compatibnility layer Wine.

I was able to install each and every of the NI apps and expansions in my library.

Either via NA or manually via the .exe.

It's only Kontakt 8 that misbehaves …lol

When the installer runs, it shows a brief message about installing a Visual C++ runtime - but unfortunately it doesn't show which one it is.

If i had to guess, it might well bet hat this runtime somehow causes a conflict or isn't installed properly,

But then again: why would only Kontakt 8 need or check for this runtime?

Anyway, does anybody here know which Visual C++ runtime it is?

Vocalpoint

Linux is not supported. Not sure what else to tell you.

PoorFellow

https://community.native-instruments.com/discussion/comment/241951#Comment_241951

Anyway, does anybody here know which Visual C++ runtime it is?

As already pointed out by VocalPoint then Linux is an OS not supported and installing on Linux is not supported .

However then: for your information :

Then if you download the Kontakt N.I. installer from Account downloads , then rather than installing then unzip the downloaded Kontakt installer , then in the unzipped folder there will be folder ( 'data' ?) in which in some sub-folder in folder tree you will then find the "vcredist" file in question - which ought to be the indirect answer to your question here.

Nativicus

Hmm, i appreciate your replies so far.

It looks like though that there still is confusion about what (some people think) i try to achieve, what is officially supported by NI, and what actually works.

I don't try or want to install NI software directly as Linux apps.

I've installed all my NI apps so far in a Windows Compatability layer.

If it helps to understand or to clarify:

You may think of this Layer as a special kind of virtual Windows machine or VM. Only that this machine doesn't come as a full fledged Windows, to avoid unneccessary bloat. Yet it allows you to add or install components like runtimes etc.

Let me recap once more why i posted here:

The ONLY NI software that i could not install this way so far is Kontakt 8 - all other apps of my library work as expected.

Unfortunately the error message the Kontakt 8 installer gives is not verbose enough to be of help.

That's why i came here looking for help.

In my first post i asked if people here that have successfully installed Kontakt 8 (Player) on a W10 or W11 machine, would perhaps help me out and share the path names as well as screenshots of the Kontakt 8 folders, subfolders and their content. So i might be able to manually copy over the files i gathered from a temp-folder.

So far nobody bothered to post any screenshot or path/folder-names. Too much effort perhaps?

Instead i get lectured about what is supported etc.

Because of the cryptic error message of the Kontakt 8 installer, i can only assume, that perhaps some runtime or the like might be missing in my "special VM".

That's why i asked for specific requirements for Kontakt 8. Again, i got lectured …lol

And what @PoorFellow suggested, seemed to be outdated.

At least at first glance.

Because the Zip of the Kontakt 8 installer just contains the installer .exe, nothing more.

Anyway, extracting the .exe further i could find a runtime, which turned out to be older than the one in my VM. Swapping the 2 runtimes back and forth did not make a difference.

So that runtime was not the culprit. The cause for the error must be something else.

And: why does the manual installation fail, while install attempts of Kontakt 8 via NA end reporting "succesfully installed". Yet NA shows no "Open" button for Kontakt 8, but still the "Install"-Button, and no Kontakt 8 folders are anywhere to be found (other than in temp)…

A mystery? Lousy coding? Or …"not supported "😜🤡?

Back to my initial idea: manually copying over the files.

Screenshots anyone?

PoorFellow

https://community.native-instruments.com/discussion/comment/242193#Comment_242193

Because the Zip of the Kontakt 8 installer just contains the installer .exe, nothing more.

I might have left room for a misunderstanding :

UnZip Kontakt 8 installer then rather than installing installer then unzip the Kontakt installer .exe, , then in the unzipped folder there will be folder ( 'data' ?) in which in some sub-folder in folder tree you will then find the "vcredist" file in question - which ought to be the indirect answer to your question here.

Vocalpoint

"I've installed all my NI apps so far in a Windows Compatibility layer."

Unfortunately - I still do not believe this scenario is supported.

No such thing as a Windows Compatibility layer listed here:

The above are the official requirements condition that NI tests Kontakt 8 with. And the requirements that a user must adhere to for normal operating conditions.

A mystery? Lousy coding? Or …"not supported "?

Mystery?: Not to any user using K8 within the system requirements (Windows 10/11 or MacOS 13,14, 15 and soon to be 16) as stated above are running normally.

Lousy coding: Nope - K8 is as stable as an app I have seen on the above OS requirements

Or…"not supported "? Ah - the correct answer.

"Back to my initial idea: manually copying over the files"

I think you are missing some very important technical considerations here. If you only knew just how many files are required for normal Kontakt operation. How many registry entries are created. How many auxiliary files created at runtime, via Native Access, via Kontakt and written back to areas all over a typical (supported) OS hard drive.

I once installed Kontakt 6 using my trusty Revo Uninstaller tool back in 2022 in "tracking" mode - where it records and then creates a list of everything the installer did during install - to arrive at a working state - and the resulting logfile had something like 1000 changes logged. All of them required for normal operation. I cannot imagine what is involved with K8 now.

"So far nobody bothered to post any screenshot or path/folder-names. Too much effort perhaps?"

As per above even with screenshots - you would be missing so many other required elements - highly doubtful this would result in any success.

@Poorfellow is trying to help you.

But I think if you were installing Kontakt into a supported environment - pretty sure the forum would be there for you as most of us always are.

Nativicus

@PoorFellow, @Vocalpoint

Guys, i really appreciate you are trying to help.

Unfortunately from my point of view it's not helpful to know that you don't think or don't believe that what i want to do is (not) supported or wouldn't work.

@PoorFellow I wonder why you bothered to clarify the installer unzipping process afterwards, but did not comment on the crucial question: … why does the manual installation fail, while install attempts of Kontakt 8 via NA end reporting "succesfully installed". Yet NA shows no "Open" button for Kontakt 8, but still the "Install"-Button, and no Kontakt 8 folders are anywhere to be found (other than in temp)…?

@Vocalpoint As long as nobody can explain how this all adds up, my best guess is indeed "lousy coding".

In my setup, all NI apps except Kontakt 8 work fine.

Thus imho "not supported" is just a killer phrase, but neither the explanation nor the help i look for.

@PoorFellow, @Vocalpoint No need for further replies / lectures …😜

PoorFellow

https://community.native-instruments.com/discussion/comment/242301#Comment_242301

No need for further replies / lectures

Then you ought not post comment that needs an answer , also I have not 'lectured you.

Guys, i really appreciate you are trying to help.
Unfortunately from my point of view it's not helpful to know that you don't think or don't believe that what i want to do is (not) supported or wouldn't work.

I was explaining why you generally should not expect us to throw a great effort into trying to solve the problem here.

Don't get me wrong , I myself am actually very sympathetic to your 'quest' here but I have little or no time for this now.

I wonder why you bothered to clarify the installer unzipping process afterwards, but did not comment on the crucial question: …

I think that I already told you as much once , Linux is not a supported OS. That does not mean that I can not extend a friendly hand and point out something which to me was obvious.

I wish you the best of luck with your endeavor.

Vocalpoint

"As long as nobody can explain how this all adds up, my best guess is indeed "lousy coding".

Actually - it's really simple - it's not supported.

AKA - you are on your own.

Quick links

Unanswered questions