After the last update my Sylenth1 does not work anymore because of the "craked" license, I've always used it like that ... But after the big update of Windows 10 1803. It says that the plugin has been disabled during the process due to an error. If I remove the license license, return demo but it works. Has anyone had the same problem?

 

NEVER USE WIN10 for DAW os

 

You can use the 32 bit version, i use jbridge and it works on cubase.

 

[QUOTE = "je5009, post: 330678, membro: 35151"] Puoi usare la versione a 32 bit, io uso jbridge e funziona su cubase. [/ CITAZIONE]

I used the 64 version, for a similar problem on the Windows FCU, putting the 32 version back on everything works

 

Last edited: May 1, 2018

Fixed by putting the 32-bit version

 

I've had the same issue after updating w10 and sylenth running demo mode.

i just reloaded the reg file and it worked again.

 

It seems to be the update of Windows 10 to 1803. With 1709 it works. So I would suggest to revert to the prior version and wait for fixes before updating again.
The update creates a backup of the old system so you can easily go back to 1709.

Oh. if it works for you the solution @reliefsan has is best.

But nontheless I would suggest to always wait some weeks before updating on a production system.

 

Last edited: May 1, 2018

i own sylenth and have no issues on win 10 1803 64bit

 

Ragazzi è stato sufficiente per sostituire la versione a 64 bit con la versione a 32 bit.

P I use Fl Studio 12.5.165.

 

just downgrade to win7x64 --- thats the only what helps

 

I've never had this problems on Windows 95.

 

I get the same problem. even if I try to bridge them it doesn't work. I dont even think I have a 32bit version. its a AON product.

 

[QUOTE = "JynetiksMusic, post: 330747, membro: 38291"] Ottengo lo stesso problema. anche se provo a collegarli, non funziona. Non penso nemmeno di avere una versione a 32 bit. è un prodotto AON. [/ QUOTE]
The 32bit version can be found on the web or on various torrent sites

 

I actually did have a 32 bit copy. I just didn't realize it. but none the less I get the same thing. I even tried to refresh my Reg file like posted above. bridged it the whole 9. I'm starting to think that the copy of Sylenth that i got is no longer a working copy. it's Sylenth 2.2. at this point I don't expect to see a Sylenth 3.0 anytime soon specially since they have this anti-pirated software supposedly in the 3.0 build. They do have a payment plan. so i might just fork out the 9.99 a month till it's paid off. Other than that I don't see what else I could be doing wrong. Other than I just ended up with a not so great copy.

I'm also wary about googling Sylenth crack cause my AVG ends up finding a virus either in the exe or the keygen itself and deletes it. If someone is willing so send me there working copy of Sylenth that'll be dope but I wont hold my breathe for that. lol

 

[QUOTE = "JynetiksMusic, post: 330787, membro: 38291"] In realtà avevo una copia a 32 bit. Non me ne sono reso conto. ma nondimeno ottengo la stessa cosa Ho anche provato ad aggiornare il mio file Reg come pubblicato sopra. l'ho completato tutto 9. Sto iniziando a pensare che la copia di Sylenth che ho ricevuto non sia più una copia funzionante. è Sylenth 2.2. a questo punto non mi aspetto di vedere un Sylenth 3.0 in qualunque momento presto, visto che hanno questo software anti-pirata presumibilmente nella versione 3.0. Hanno un piano di pagamento. quindi potrei sborsare i 9.99 al mese fino a quando non verrà pagato. A parte questo, non vedo cos'altro potrei fare male. Oltre a quello che ho appena finito con una copia non così grande.

Sono anche cauto nel cercare su Google Sylenth crack perché il mio AVG finisce per trovare un virus nell'exe o nel keygen stesso e lo elimina. Se qualcuno è disposto, mandami la copia funzionante di Sylenth che sarà stupida, ma non terrei il mio respiro per quello. lol [/ QUOTE]
è necessario disabilitare l'antivirus per aprire il keygen

 

Any workarounds whatsoever? I've removed previous build and there is no way I'm going to reinstall the OS with the 1703 build where it worked properly.

 

I just started my monthly Sylenth1 v3 installment few days ago because of the update.
and the v3 so far runs great.

I'll try this and let see if I'm gonna continue the installment for next month or not :D

 

yeah i feel the pain youre going thru. i hope you survive another month

 

I installed 1803 today. No issues with legit Version of sylenth1. So I would suspect Windows changed begaviour e.g. Blocking sylenth's phoning home method.

 

My installers have 32bit version in them. Win10 is a strange fish. The updates haven't caused me any problems (64bit version running in cubase pro 8). It seems that the updates only cause problems on SOME pc's. Which is peculiar.