Hi everyone,

I’ve noticed that many of us using the Bob Dule releases (or similar "Add Library" tools) end up with a significantly slower Kontakt startup time. The culprit? These scripts often inject hundreds of registry entries for libraries we don’t even use or have installed.

When Kontakt 7 or 8 boots up, it tries to scan every single entry under the Native Instruments registry path. If you have hundreds of entries with empty ContentDir values (ghost libraries), Kontakt hangs while trying to resolve these paths.

I’ve put together a quick PowerShell script to automate the cleanup. This script scans your registry and deletes the entire parent folder (Key) for any library where the ContentDir is empty or missing.To give you an idea of the impact: Before I did this cleanup, opening Kontakt 8 took over half a minute. Now, it launches in just 6 seconds.

Spoiler: The fix

The Fix

1. Registry Cleanup: Run PowerShell as Administrator and execute the following:

$regPaths = @(
"HKLM:\SOFTWARE\Native Instruments",
"HKLM:\SOFTWARE\WOW6432Node\Native Instruments"
)

Write-Host "Scanning for ghost library entries..." -ForegroundColor Cyan

foreach ($root in $regPaths) {
if (Test-Path $root) {
$keys = Get-ChildItem -Path $root
foreach ($key in $keys) {
$contentValue = Get-ItemProperty -Path $key.PSPath -Name "ContentDir" -ErrorAction SilentlyContinue
# If the entry exists but the path is empty/whitespace
if ($null -ne $contentValue -and [string]::IsNullOrWhiteSpace($contentValue.ContentDir)) {
Write-Host "Removing ghost entry: $($key.Name)" -ForegroundColor Yellow
Remove-Item -Path $key.PSPath -Recurse -Force
}
}
}
}
Write-Host "Done! Your registry is now clean." -ForegroundColor Green

Hope this helps anyone dealing with a sluggish Kontakt! If you have other tips for optimizing NI's database, feel free to share below.
（I write this thread and Powershell script via Gemini）

 

Last edited: Feb 21, 2026

Interesting, got me curious (for vkDanilov's portable though). I don't see anything offensive in terms of performance, other than hanging for 5 seconds on this single font query???

 

This is ---------- amazing. Did even speed up my really luggish Komplete Kontrol start-up process. Wow. thank you

 

the empty ContentDir are comming from the NI Key Adder,
that parse NativeAccess.xml to add all the products (actually 2719 products) in regedit.
this was the old way to hack Native Access 1 to add anything and unlock the download.

they protected more the server since NativeAccess2 with api request, to brake the free party.

i keep it in Kontakt button because you can still use it with Native Access 1, see all products for informative purpose, also to copy the changelog text that v2 don't enable. (using ctrl+a , ctr+c) to select and copy the text

so this is normal that it goes faster with less regedit entry. you should also clean .json files
because NI products read regedit fist to generate the json files, and load faster after, ignoring the regedit info once generated.

there is no more ContentDir paths in WOW6432Node now, if you have some it come's from outdated tools (nicnt generators) or very old mode keygens.


About the Lumen Roboto Medium font:
there is no font using this name in windows 11. i don't know from where it come's, there is only roboto medium found online.

you can still try to replace it by another 'as roboto-medium using regedit:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes]
"Lumen Roboto Medium"="Roboto-Medium"

i checked the gemini code generation that still need human correction to parse well NativeAccess.xml
there is a lot of bad not working result but i managed to make something working to list all products by SNPID, UPID, Name
that can be used to identify the RAS3 license in case you use a keygen.
this is the script to generate a text file on desktop.

Spoiler: NI product indentifier

$xmlPath = "C:\Program Files\Common Files\Native Instruments\Service Center\NativeAccess.xml"
$exportPath = "$env:USERPROFILE\Desktop\NativeAccess_Export.txt"

if (-not (Test-Path $xmlPath)) {
Write-Host "Error XML not found" -ForegroundColor Red
return
}
[xml]$xmlData = Get-Content $xmlPath
$products = $xmlData.SelectNodes("//*[local-name()='Product']")
$results = foreach ($p in $products) {
[PSCustomObject]@{
Name = $p.Name
SNPID = $p.SNPID
UPID = $p.UPID
}
}
$results | Sort-Object Name | ForEach-Object {
"| SNPID:{0,-36} | UPID: {1} | {2}" -f $_.SNPID, $_.UPID,$_.Name
} | Out-File $exportPath -Encoding utf8

Write-Host "Export OK" -ForegroundColor Green

 

Last edited: Feb 21, 2026