Don't know if this was solved, but i'll just leave this here in case somebody needs it. I had the same problem with R2R's Kontakt 6.7.1, and apparently people have been having trouble with other releases since time immemorial. So let me sumarize my adventure through the solutions i could find, in the order i did them in case that's important, i don't know, i just click things:

-Reinstall Visual C++: No change
-Reinstall Kontakt (also tried bobdule's version for good measure): No change
-Mess with MS config in case of conflicting software on startup: No change
-Used SFC/scannow command, also DISM related ones: No change
-Reset Reaper to default settings: Worked partially, would still show error message after reboot.
-Run Reaper as admin: Worked. No error message so far.

Hope it helps somebody at some point in time.

 

Running an app as admin under Windows generates new problems. One of them is you can't drag'n drop files to reaper. But it's a good starting point to find the real problem.

If reaper runs without errors as admin the problem seems to have to do with rights. Maybe in the reaper directory or a directory where the called DLLs reside there are write/execute rights missing.

I would try to give the user "everyone" write/execute rights with explorer in the DLL directory/Reaper directory and check if you can run Reaper outside admin context.

 

Last edited: Jun 6, 2022

I tried running Reaper in as admin, not worked
Tried changing rights of the portable Kontakt folder, not worked.
Never had such difficulty with a program...

 

Yeah, unfortunately . No biggie though.

Just for good measure i checked the rights on the reaper folder for "everyone" (or at least i think it is, since this thing is in spanish), also checked the kontakt folder, and where the DLLs are. They all had write/execute rights.

Damn. Well it was worth the shot.

 

Yes of course it was worth.
I'll have to try with the older version I have, I think it was 5.8 , at least this one accept self-made libraries.

 

It's a MacOS issue that Apple seems to have a hard time to fix.
It's getting worse with longer OS uptimes and it has nothing to do with specific apps or CPU load.

 

As stated in my first post:
System Win 10

So no... Not in my case at least.

 

I have the solution...the problem is with your FIREWALL!!! If you don't want to give Reaper full internet access, you can create a custom ruleset and just allow destination address 127.0.0.1. You're welcome

 

Thank you maximefelton and welcome to the forum.
Interesting, but this means that I would have to let Reaper connect to the internet. Why would it be done that way?

 

I'm no networking expert but 127.0.0.1 is your local computer. I think plugins like Kontakt need to communicate internally with the host (Reaper) using networking protocols.

I don't know which firewall you are using,( I'm using Comodo Internet Security) but you only need to allow Reaper to listen for internal connections (from 127.0.0.1 to 127.0.0.1). It won't connect to the Internet this way You can aslo add another ruleset underneath to block all other source and destination address.



You can follow the connections log if you feel paranoid

 

Last edited: Oct 22, 2022

Thank you for the explanation.
OK, I understand.
Yes I feel paranoid when a cracked program ask for connection, specially when cracked by a (still) unknown cracker.
I'm using Evorim free firewall. and I can do rules based on IP.

 

I was getting the damn Visual C++ runtime error using every other releases of Kontakt (R2R,bobdule...) not just this one. Hope this helps someone else.

 

Last edited: Oct 22, 2022

This will surely help. I'll try when I can and I'll get back to report.

 

Last edited: Oct 22, 2022

There is the possibility that Kontakt Portable includes a (probably older) different version of the famous VC_redist.exe that conflicts with the regular one used by other windows programs like Reaper.

I think it's not the case with Reaper and Kontakt 6.7.1. For some others plugins it is. But haven't tested this exact combination of version.

PS. I've always run the DAWs with admin privileges and firewalled
PS2. Oops. Didn't remember this was already mentioned. Sorry, perdón, arigatogosaimas,...

 

Last edited: Oct 22, 2022