After Windows 10 update, some VSTs not working...?

Author
Post
Essentials Only Full Version
MrBansaw
Max Output Level: -90 dBFS
  • Total Posts : 45
  • Joined: 2015/11/02 17:25:46
  • Status: offline
2017/07/26 12:22:52 (permalink)

After Windows 10 update, some VSTs not working...?

I finally updated my Win10 to Win10 Creators edition, and just after doing that a handful of my VSTs stopped working.
Notably, MOTU Ethno and Symphonic.  Other small VSTs continued to work fine.
When I try and add the VST it just spins and hangs up.  
I reinstalled the MOTU stuff and now they will invoke as a standalone, but not when they are added as a VST.
 
Has anyone had issues with Win10 creator update, and how did yo solve them?
 
(I already contacted MOTU, and they weren't much help.)
 

Sonar Home 6XL 64bit (and Reaper), i7-770k 16GB Win10,  & Toshiba Sat L500 INTEL I5-430M 2.26-2.53GHZ, Win7, 4GB, 1TB, Albion One, Avenger, Motu Ethno, Studiologic 990Xp 88-key
#1

8 Replies Related Threads
    ronboy1952
    Max Output Level: -90 dBFS
    • Total Posts : 45
    • Joined: 2014/12/15 12:51:11
    • Status: offline
    Re: After Windows 10 update, some VSTs not working...? 2017/08/01 23:19:30 (permalink)
    I do believe it's a problem with Sonar and not Windows! I have the same problem but in Cubase and Reaper they work just fine. Run Sonar in Administrative mode and your plugins should work!
    #2
    noynekker
    Max Output Level: -66 dBFS
    • Total Posts : 1235
    • Joined: 2012/01/12 01:09:45
    • Location: POCO, by the river, Canada
    • Status: offline
    Re: After Windows 10 update, some VSTs not working...? 2017/08/02 00:16:34 (permalink)
     . . . after my Windows Creators update , a whole host of issues, mostly device related . . . as far as VST's, mine all seem to work the same, so far, except Spectrasonics Omnisphere. Every time there's a major OS update, I have to rummage through my papers to find the login and password to re-authorize Omnisphere . . . thankfully, I don't have to re-install it . . . so just wondering if this is what you're up against with MOTU ?

    Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.

     
    #3
    MrBansaw
    Max Output Level: -90 dBFS
    • Total Posts : 45
    • Joined: 2015/11/02 17:25:46
    • Status: offline
    Re: After Windows 10 update, some VSTs not working...? 2017/08/02 00:31:20 (permalink)
    With MOTU I think it got messy.  Because I used to run Sonar Home 6XL and installed MOTU for that.   I then fell in love with Reaper (I disliked Sonar so much. :s  ) and just linked the MOTU stuff in.  When I upgraded from Win7 to Win10, there were absolutely no problems.  Its just this Creators update thats knocked a few things off.
    Not just MOTU but a handful of other VSTs as well.  The others seem solvable by a reinstall or reauthorisation,  but MOTU hasnt.
    I tried running as Admin, and even installing as Admin with compatibility modes etc.  No joy.  

    Sonar Home 6XL 64bit (and Reaper), i7-770k 16GB Win10,  & Toshiba Sat L500 INTEL I5-430M 2.26-2.53GHZ, Win7, 4GB, 1TB, Albion One, Avenger, Motu Ethno, Studiologic 990Xp 88-key
    #4
    noynekker
    Max Output Level: -66 dBFS
    • Total Posts : 1235
    • Joined: 2012/01/12 01:09:45
    • Location: POCO, by the river, Canada
    • Status: offline
    Re: After Windows 10 update, some VSTs not working...? 2017/08/02 00:41:00 (permalink)
    Have you tried turning off "Game Mode", as suggested in the Cakewalk sticky above ?
     

    Cakewalk by Bandlab, Cubase, RME Babyface Pro, Intel i7 3770K @3.5Ghz, Asus P8Z77-VPro/Thunderbolt, 32GB DDR3 RAM, GeForce GTX 660 Ti, 250 GB OS SSD, 2TB HDD samples, Win 10 Pro 64 bit, backed up by Macrium Reflect, Novation Impulse 61 Midi Key Controller, Tannoy Active Near Field Monitors, Guitars by Vantage, Gibson, Yamaki and Ovation.

     
    #5
    MrBansaw
    Max Output Level: -90 dBFS
    • Total Posts : 45
    • Joined: 2015/11/02 17:25:46
    • Status: offline
    Re: After Windows 10 update, some VSTs not working...? 2017/08/02 01:04:57 (permalink)
    Just turned Game mode off globally, rebooted, still same issue.
     

    Sonar Home 6XL 64bit (and Reaper), i7-770k 16GB Win10,  & Toshiba Sat L500 INTEL I5-430M 2.26-2.53GHZ, Win7, 4GB, 1TB, Albion One, Avenger, Motu Ethno, Studiologic 990Xp 88-key
    #6
    rmfegley
    Max Output Level: -88 dBFS
    • Total Posts : 114
    • Joined: 2014/12/24 14:57:07
    • Status: offline
    Re: After Windows 10 update, some VSTs not working...? 2017/08/02 01:16:06 (permalink)
    I had the same problems with a couple of NI products, Komplete Kontrol and Maschine, after installing Creators update. It was both as standalones and plugin versions, and in multiple hosts, not just Sonar. Standalone versions wouldn't open, attempting to add them as plugins would crash the host. Updating my GPU drivers fixed it. Seemed random, but it worked.

    Sonar Platinum latest update
    Windows 10 Home
    i7-4790 CPU
    ASRock Z97 Pro4 MB
    16 GB RAM
    Nvidia GTX 960
    Focusrite Scarlett 6i6 
    Alesis VI49 Keyboard/controller
    Native Instruments Komplete Kontrol S49 keyboard/controller
    Native Instruments Maschine Mk3
    Native Instruments Maschine Jam
    Native Instruments Komplete 10
    Various other commercial and free plugins
    &
    #7
    werewindle
    Max Output Level: -86 dBFS
    • Total Posts : 214
    • Joined: 2015/01/21 07:53:04
    • Status: offline
    Re: After Windows 10 update, some VSTs not working...? 2017/08/03 11:52:34 (permalink)
    There is also a new restriction on driver installation unless they have a Microsoft certified digital signature they now won't install properly.
    This explains the workaround https://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
     

    Sonar: Platinum & Studio One 3
    Production PC: Intel i7-6950x 10 cores (20 processors) CPU @ 3.00GHz (with overclock to 3.60GHz), RAM 64GB, Windows 10 - 64 bit, Sound Blaster ZxR Pro, Dual Nvidia GTX1080 with 2 widescreen Monitors
    MIDI: Akai Advance 49, Roland A-500Pro, Akai MPD230, Softube Console 1, Akai EWI USB, Roli Seaboard 25
    Instruments: Martin D12X1AE Dreadnought - 12 string, Martin Ed Sheeran X Signature Edition, Fender Standard Precision-Bass Black MN, Gibson Custom Shop EDS-1275 Cherry (12 & 6 string dual)
    #8
    elsongs
    Max Output Level: -84 dBFS
    • Total Posts : 306
    • Joined: 2010/03/02 16:16:02
    • Location: Los Angeles, CA
    • Status: offline
    Re: After Windows 10 update, some VSTs not working...? 2017/08/05 10:10:01 (permalink)
    My XLN plugins showed that they weren't registered. Apparently it thinks its a new computer now. I re-registered my computer using the XLN Registration program and it's all fine now. So far my other plugins seem to load fine.

    Elson Trinidad Los Angeles, CA, USA
    Web: www.elsongs.com
    Twitter: twitter.com/elsongs

    DAWs: Cakewalk by Bandlab, Cakewalk Sonar Platinum x64, Propellerhead Reason 9, Presonus Studio One v3
    OS: Windows 10 Professional 
    CPU: Intel i7 3820 3.6MHz 
    MB: ASRock X79 Xtreme4
    RAM: Corsair Vengeance 16GB DDR3
    Audio: Focusrite Scarlett 18i20 2nd Generation
    MIDI: MOTU Microlite & Novation Impulse 61
    #9
    Jump to:
    © 2024 APG vNext Commercial Version 5.1