KVR Audio

karrikuh · Post by **karrikuh** » Sun Aug 02, 2015 4:36 am

Just updated to Windows 10 64-bit and discovered ValhallaRoom is not detected anymore in my DAW (REAPER 64-bit). The ValhallaRoom 32-bit DLL is detected and working just fine.

Quick googling showed I'm not the only one with the issue:
http://forum.image-line.com/viewtopic.p ... 0&t=145946
http://forum.cockos.com/showpost.php?s= ... stcount=34

SirKen · Post by **SirKen** » Mon Aug 03, 2015 11:44 pm

I had the same issue when I was testing the Windows 10 Tech Preview. Installing the 3.5 .NET libraries fixed it for me. I think it has something to do with .NET version 4 not being compatible with some of the code that's in Valhalla libraries.

valhallasound · Post by **valhallasound** » Tue Aug 04, 2015 4:45 pm

I haven't installed Windows 10, and probably won't for the next several weeks. My guess, based on the .NET comment above, is that it may have something to do with missing .dlls for VisualStudio 2010 support. I would try running the following installer (assuming that it runs on Windows 10):

http://www.microsoft.com/en-us/download ... x?id=26999

This installs the .dlls that would be missing from your system. If this works, please let me know, as I can modify the next build to incorporate these .dlls.

Sean Costello

karrikuh · Post by **karrikuh** » Tue Aug 04, 2015 7:04 pm

Hi Sean,
I can happily confirm that installing the MSVC 2010 x64 runtime did the trick!
Instead of shipping the DLLs with your installer, I really recommend to statically link against the runtime though. It will save you and your users a lot of hassle...
Anyway, thanks for the hint!

boomblip · Post by **boomblip** » Tue Sep 01, 2015 11:34 pm

I am having the same problem but the runtime installation isn't fixing the error, any other things I could try.

Crackbaby · Post by **Crackbaby** » Fri Jan 08, 2016 10:43 pm

This helped me solving ABL3 not being found

The runtime that is. So big thanks ^_^

euphorrik · Post by **euphorrik** » Fri Feb 03, 2017 5:45 am

Thank you Sean for the great plugins and mentioning the fix and thanks to karrikuh for confirming it. Just spent four hours trying tweak every little setting in Ableton and Windows. Had to reinstall VintageVerb like 15 times and try to make sense of the damn Ableton logs. Happy to say the plugin was finally recognized!

Anyone using Live 9, make sure to hold ALT when you click rescan after installing the framework to do a full rescan of the plugin folder. It might not find it otherwise.

Ivan_C · Post by **Ivan_C** » Wed Feb 08, 2017 1:31 pm

Sean > in the Projucer, in the Release settings for Visual Studio, always set "use static runtime" in the "Runtime Library" settings for removing the issue above of your users forever

bitterkitten · Post by **bitterkitten** » Sat Sep 30, 2017 2:57 am

Already tried the aforementioned things (although those were already installed in my fresh win10pro x64 + creator's update install).

If no suggestions, I will try posting in the Reaper forums, though it appears that the same solutions have been tried.

Thanks!!

valhallasound · Post by **valhallasound** » Sat Sep 30, 2017 6:39 pm

If you are using the 1.5.1 update from your valhalladsp.com user account, all of the above discussions should be moot. The 1.5.1 update was rebuilt in order to incorporate the DLLs that were missing from the previous build.

If you are having installation issues with ValhallaRoom, please fill out a support request:

https://valhalladsp.com/support/

We have a full-on support system nowadays, including searchable FAQ, and additional help from Don Gunn in solving support issues.

ValhallaRoom not loading in Windows 10 x64