it worked. arigato, amigo

 

Copy from where?

 

Guys I can’t patch the vst3 file, but the standalone works fine outside of fl studio? How come when I run the patcher it won’t find the vst3 file

 

Sadly didn't work for me. Lost. I'm using the portable version instead to survive which gives no problems. many thanks Bob Dule for your work. I'll def buy you a beer.

 

Hi, I've been without luck with the lastest releases from Bob and being unable to upgrade since 7.1.8. But yesterday I realized that I had not uninstalled the old Service Center from NI and was messing with the registration of my Reaktor 6.5 (demoing it every time I turn on the computer) and suddenly I have, for now, a stable full registered version of kontakt 7.3.1 from doule as well. So if any of you have this Service Center laying around on the HDD, uninstall it and give it a go.

Cheers!

 

The "Native Access 2" install tip DIDN'T work for me, even though I did not run it as advised; however, the " "NativeAccess.xml" file copy & paste to Program Files\Common Files\Native Instruments\Service Center," & register again with Keygen" tip DID, & changed my Kontakt 7.1.8 installation from Demo to full.

The only catch for ME, was that I had to borrow the "NativeAccess.xml" file from my "Native Instruments Kontakt 7 v7.1.5 WIN-R2R" download, because the "Kontakt Full Options 7.1.8" download with the Bob Dule package that I used for my install didn't have it.

Anyway, that's MY story with a happy ending. But since it's looking to be an "Anything Goes" situation to successfully troubleshoot what is clearly a very exhausting issue to overcome with these so-called "patched" Kontakt v. 6-7 install choices, I truly wish everyone the best of luck!!

 

Hey, for unrelated reasons I had to do a clean install of Windows and now bob kontakt works like charm, stand alone and vst3, all fully registered with the copy/paste Native Access.xml to the designated folder without installing native access at all. On the old system I couldn't ran the Standalone, so I suspect that there are obscure files or regitry entrys from past versions that are interfering with the patching, not that the patch is bad. It's tottaly understandable the patch cannot be debbugged to a profesional level, and it's on our side to bring the bugs and problems so common... "anything goes situation"? "exhausting"? "so-called patched"? Be grateful that we can even test these things for free for the hard work of very little few.

 

you can directly update the NativeAccess.xml "content" from this url:
https://api.native-instruments.com/static/phints

simply don't forget to add the xml header
<?xml version="1.0" encoding="UTF-8"?>

 

...

 

Last edited: May 29, 2023

One thing I found with @bobdule version, and I’m sure he will correct where I’m going wrong but it seems like it could be OP issue too, is that unless you install all mandatory and optional plugin versions then the patcher fails. I just installed VsT3 first, but patcher failed as it looks for AAX first and says it cannot find and I can’t seem to get the patcher any further, so VST3 doesn’t get patched. I got around this by installing everything, patching was then fine as it found everything, and then I just manually removed the AAX and VST2 I do not need.

 

I don’t have NI app and have all NI software working,perfectly. NI Access is not necessary.

 

I have 0 (zero, none, nada, nin) "native access" garbage on my new production build (as well as my older one) - I have one instance of Kontakt 7.1.5 FULL (handles everything I throw at it), Battery latest, Absynth latest available (I had "massive" installed at one point but uninstalled it due to lack of use) - ALL Full scene releases, All Work fine including AAX (in au PT12.5HD) in all DAWS. My guess is a lot of these issues are caused by some installer at some point in the past screwing something up and it stays that way unless one does a Komplete Kleen sweep of NI off the system/registry and starts over (or simply rebuilds the OS).

 

that's what say all unlucky users.

 

all the NI applications are linked together via the NTKDaemon service, installed with native access.

the pal.db build managing the PAResource thumbmails use NativeAccess.xml to list products and enable the final db3 file for every product.

pal.db is a shared componant (used by every kontakt version) + komplete kontrol and Maschine. it is located in user document/native instruments/service center
db3 are located in user/app data

the link between all these files seems to be made by NTKDaemon that also check licenses.
this is why you should use native access, to get the complete fonctional structure for NI products.
the big shit come's from the thumbmail management, that give incomplete or bugged database build if something is missing.

why refuse to use it? every NI user have it installed. there is nothing to fear from this application.
only re keygen if license are overwrited by the opening (from free offer), or the silent NTKDaemon service, even when all is closed.

a legit account or trial account will overwrite some licenses. it is only a thing to know. the keygened licenses can use read only to prevent this.
all your shit come's from the missing component.

 

This is all the NI stuff I have installed, and you see it's on Windows 11 Pro and there is no NI Access app. Based on my machine, you just need to have the latest NativeAccess.xml present in the correct location. When you install the apps that use hardware, i.e. Maschine or Komplete Kontrol, it also installs the drivers for all these and includes the NTKDaemon that @bobdule refers to:







And you can see latest version of apps all working fine:

 

hidden serial numbers? why? or these software licenses are legit? =)

 

No reason really. More just in case it's niquely generated in some way so that I don't inadvertently jeopardise my own install by sharing it