Feature update to Windows 10, version 1803

- Had to reinstall Audio Driver on my Zoom uac-8 audio interface
- Re-register Addictive Drums 2
- Re-register Addictive Trigger
- Re-register Spectrasonics Keyscape, Omnisphere, Trillian, Stylus
- Re-register RC-20 Retro Color

Everything else seems to work fine, those issues mention can of course be a issues just for me

By the way I regularly do disk cleanup and now it's almost 30 GB previous windows installations, so this is a serious update. I will not cleanup before I have tested the system a week or so, so I can do a system restore if necessary

 

Last edited: May 6, 2018

Most things seem to work, But my version of Slylenth crashes Studio One 3 the only way out is to close via task manager, which is a shame really as I quite like Slylenth. If anyone knows a workaround????

 

On my Windwos 10 it is always a 50/50 chance that it will destroy itself and endup in a infinite update loop. Is is so sad that there are so many updates but non adress the actual windows flaws.

 

One more reason to stick with or "downgrade" to Windows 7.

 

sound like you either have to reinstall Slylenth or Studio One. Is that Sylenth a plugin?... if so can you give me a link to you're version so I can test it out. I have both Ableton and Studio One on my pc

 

Agree totally, My main studio runs Windoze 7, but I use a Windoze 10 on my domestic machine, and only use it for small projects and learning... but I shall miss using Slylenth on it

 

my windows solution was to install the LTSR iso of windows 10....never let the DAW online and install all my software and studio one as admin....runs like a dream

 

Yes that is probably smart, but I cloned my whole system a month ago so I can take chances.

 

sylenth 1 don´t work after win 10 update i use fl studio 12
any solutions?

 

Yes Same here. Win 10 still in evaluation mode on my pc on a dual boot PC. I did lose my BFD registration after a update which took for ever to download and install. Win 10 acts like it's a miracle just to do update, win 7 is way faster. I did read and article the other day that MS is working on the horrible win 10 updates though.

 

My brother do not tell me that you believe anything that MS says. That is their SOP "we are working on it". Before they come out with a fix, MS will have a new OS and once again the cycle will repeat itself: updates to fix updates that were supposed to fix some problems and MS telling its customers "we are working on it".

 

One of my clients had her mouse stop working after an update. No matter what I did, I couldn't make it work again, so I installed W7 and she actually wanted back to W7 anyway, since her other audio PC with W7 works great. The thing is, she bought this laptop with pre-installed W10 so she thought "oh well, it should be alright... Windows is Windows". She was wrong. Now she's a happy camper.

Besides, when I saw what pile of crap came pre-installed with it, it made me queasy...

 

Last edited: May 7, 2018

Only the 64bit version locks up (on every host afaik) on 1803, use the bridged 32bit version until there's a fix (sylenth doesn't really gain much from 64bit unlike something like kontakt, anyway)

 

64bit sylenth1 works fine on my win10 laptop. Cubase 8.

 

, I have this copy of Slylenth and the R2R version of S1, tried everything, so I'm assuming that its Win 10 update

 

and then here I am, deciding whether to upgrade my PC from MacOS 10.11.6 to 10.13.6 (once it releases and becomes tested) xD
speaking of Windows 10, I'll probably settle down on latest W10 Enterprise LTSB modded "Lite" version in summer, nothing useful added since july 2016 in W10 imo

 

What?? You mean you don't want windows bothering you with a notification to tell you that it's detected a full screen app and thus it won't bother you with notifications while you're playing a game?

(Thanks MS, that's a great new feature)

 

same here W10 x64, I made a roll back then blocked updates for 1 month. now sylenth re-works

 

Never had a problem with Windows updates (And I have WiBu and iLok2)... Normally the issue is on the other side of the keyboard

 

In any other circumstance I would completely agree, but this is W10 we're talking about, mate. It's got a mind of its own.