Fixed slow Kontakt 7 and Battery...Cleaned up registry

pnutbutta · 2024-09-24T11:45:26+00:00

There was an error rendering this rich post.

For those with windows, I was having very slow loading times on loading either Kontakt 7 or Battery 4, and Maschine in multiple DAWs and standalone. I have been doing some "house cleaning" recently with clearing out old and unused plugins, samples, apps etc. I decided to give CCleaner a go and see what it found with the registry. I made a backup and let it scan and fix everything. I only noticed it cleaning up entries for apps that were no longer installed. I have no idea exactly everything it did, but NOW anything NI loads very snappy in Reaper. I tested with multiple projects. My jaw was on the floor.

I did need to fix a few plugins and apps after, but I did not touch or run Native access or plugin settings AT ALL. It just worked. I just want to throw that out there as an idea for those with similar issues.

Peace

Find more posts tagged with

Battery 4

Kontakt 7

Comments

Vocalpoint

Would love to know two things:

Which reg settings got cleaned out?
And - I see you use Reaper. There was a thread around here where one specific user has had non-stop issues with Komplete Kontrol 3 crashing, freezing etc. You wouldn't happen to be using KK in Reaper - are you?

pnutbutta

https://community.native-instruments.com/discussion/comment/179552#Comment_179552

I am not sure at this point, but I am betting CCleaner has a log somewhere I can dig through. I did take a backup of the registry and I might be able to compare old and new.

Cubase with anything NI is the same, and loading very fast. Cubase is very finicky with plugins so I have been trying to streamline all the junk in my plugin folder.

pnutbutta

Ok just discovered CCleaner does not keep logs because the developer says that defeats the purpose of what the software is about. I would tend to disagree because a small log file compared to the gigabytes of other junk that it deletes is almost negligible. Anyway, there are some other registry tools I discovered that might work as good or better:

https://www.pcworld.com/article/536489/registry-cleaner.html

One thing you can try with any of these is just do an analyze, and take some time to go through and find anything NI related before doing the repair to see what's there.

Quick links

Unanswered questions