Seems like last windows updates fixed the issue where you had to use jbridge to use Sylenth1 2.2.1.x on win10 x64 (v1803).
( to be confirmed - it works for me ! )
Cheers |!

 

Last edited: Mar 5, 2019

What version are you talking about exactly? Would be nice to know.

To get the exact version, you can open regedit and go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
or you copy & save this text into a *.bat or *.cmd file and run it:

Code:

@echo off
REG ADD "HKCU\Software\Microsoft\Windows\CurrentVersion\Applets\Regedit" /v "LastKey" /d "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /f
start /B regedit.exe

It will add that key/path as the last opened key and then regedit automatically opens up at the specified key.

You can read the version then at the value "BuildLabEx"

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\BuildLabEx :
[ 17134.1.amd64fre.rs4_release.180410-1804 ]
In windows update, last updates are labeled as :
[ version 1803 ]

 

Hm but the last updates were build 1809/rs5.
Will check that in a virtual machine.

 

Because i use the Semi-Annual Channel instead of the Semi-Annual Channel (Targeted) in windows update settings.

 

I just tested it. and it works fine now. tnx for the info

 

It works without any problems on windows 10 19h1 update that is coming on april of this year.

 

Hahahah yeah I was thinking the same after I loadout one of my old project and sylenth was working perfect! But I don't wont to use this shitty synth anymore, if happened again in a future win update my "future" project get fucked. I prefer to stick with other synth just in case and to be honest… there is better synth on the market, the old shitty noise vibe of sylenth isn't worth the price of losing a project.