I don't think the OS is the problem, as I have Session Horns (as part of the Kontakt Komplete pack) on both my Windows 7 laptop and my Windows 10 desktop.

However, Session Horns is just a library used within Kontakt, so if the VSTi scanning is failing, it would seem to be more of a Kontakt issue rather than Session Horns itself, as the DAW scanner doesn't scan the specific libraries loaded by Kontakt, just the Kontakt DLL itself.

I know when you install, it asks where to install the Session Horns (C: drive), the library sound files (which can be a different drive), and the 64-bit and the 32-bit DLL's. I believe if it has been previously installed, it uses those previous paths, but I'm just going from memory here.

That's why I'd first try using the Kontakt stand-alone first.

I can't remember if Session Horns came with the full Kontakt or just the Kontakt player, however. If just the player, you may want to consider upgrading to the full Kontakt.


John

Laptop-HP Omen I7 Win11Pro 32GB 2x2TB, 1x4TB SSD
Desktop-ASUS-I7 Win10Pro 32GB 2x1.5TB, 2x2TB, 1x4TB SATA

BB2025/UMC404HD/Casios/Cakewalk/Reaper/Studio One/MixBus/Notion/Finale/Dorico/Noteworthy/NI/Halion/IK

http://www.sus4chord.com