Still going on about cars and hills, Carles? You sound very angry by the way, probably about the Cubase issues you're having and I sincerely empathise with you - but taking it out on me isn't going to help.... So I'm going to ignore your insults - and (deliberately?) misconstruing my words/statements (but calling me a fanboy for saying Cubase is working okay for me, really???) - and offer some advice instead. 1 Have you checked the registry for any issues (don't ask me what you should be looking for, it'll have to be researched independently or referenced to Steinberg)? 2 Have you tried a clean install with nothing else on the PC except Cubase and plug-ins? This probably won't get around registry issues though so registry would be the best first place to check/fix. 3 Have you installed the latest Kontakt and are you on the latest Cubase update? 4 You mentioned that Cubase started to play up after you installed Kontakt plug-ins - have you tried to isolate if a particular plug-in, or Kontakt itself, might be causing the shut down delay? 5 Are you running Cubase as administrator? 6 What version of Windows are you on and have you run a compatibility test? 7 Are you using identical graphics cards on both PCs and would it be causing any issues? 8 How old are the plug-ins you're using? 9 Have you updated graphics drivers and disabled any sort of virtual desktop or otherwise possible disruptive visual tools? 10 On a Cubase-related note, have you compared closing times for Cubase with ASIO Guard enabled, and then also disabled? 11 Have you tried disabling Steinberg Hub? 12 What anti-virus are you using? I'm guessing you've tried all of the above since you've spent hours/years trying to fix the problem. The fact you mentioned earlier issues with malware is disconcerting. I would never use a DAW PC for buggy web-browsing.... I'm a little surprised that you're using your DAW PC for "whatever" and expect it to behave perfectly. My advice would be to never install third-party freeware/spyware on a DAW PC.... I'm going to repeat that Cubase is working fine over here - and I do that again (for the third time) in order to try to help people complaining here to also look outside of Cubase for any issues affecting performance. It's low that you could think that I posted that earlier in order to selfishly show-off.... Seriously, really low. What you did is take a harmless comment and assigned a negative connotation to it. I'll keep posting on this forum if I think it can help people though, despite some people trying to read negatives where there are none. The rather simple point I had to repeat at the outset was that, if Cubase works fine for me but not for you, how can it be Cubase - it's the same code we're both using...? The point you're making about Steinberg not caring is invalid. As you have experience with beta-testing, you will know that if the problem can't be replicated, then it can't be fixed. I'm fairly confident that the devs might be scratching their heads saying "what the hell are these people on about, it closes first time for us" ... probably on their clean PCs too I might add. I know from experience that devs might also say "we have no control over how people use their PCs, what other software they have installed affecting performance, or what dodgy website they might be visiting". Or are you saying that Cubase devs know about the problem, that it's affecting them and they are ignoring it? You make the point about business interests - do you honestly think Steinberg would deliberately peev off it's customer-base in the interests of looking for profits elsewhere? I'd agree with you if Steinberg had sold an update to fix this problem. Have they?