Noel Borthwick Posted December 23, 2024 Author Share Posted December 23, 2024 Its literally explained in the first post on this thread. Generally if running the latest redist installer didn't resolve your issue then you have some other issue. Are you using an ASIO driver like ASIO4All or a variant of that? If so that is likely the cause for your hang. Link to comment Share on other sites More sharing options...
ZincT Posted July 2 Share Posted July 2 (edited) Thanks @Noel Borthwick Noel - this was my problem and it is fixed now. 👍🏻 In case anyone else has this, I noticed it was when I removed the older 2008 VC++ redists that the problem went away. I also noticed a couple of the uninstallers for the 2008 redists were in Russian, possibly installed by Ilya Efimov libraries IDK. Anyway, Sonar is now running 😃 EDIT: Scrub that, it's gone back to exiting when I click the "continue evaluation" button. 😕 In more detail, here's what happens... - I double click on Sonar icon and see the startup/loading window - Next I momentarily see the Sonar UI flash up which then disappears, leaving the "continue evaluation" window displayed - I wait 15 seconds and then click "continue evaluation" which then exits and leaves nothing running I don't see why it would run once after I had removed all VC++ Redists and Re-installed (via Sonar installation), but not run again afterwards? I'm not running ASIO4All or similar and I have also removed the Steinberg Generic ASIO drivers which seem to keep getting installed. Here are the VC++ Redists that are currently installed.. Edited July 2 by ZincT Link to comment Share on other sites More sharing options...
Noel Borthwick Posted July 2 Author Share Posted July 2 This is unlikely to be a redist issue. The membership screen should always be shown only when the app is visible in the background. Start a new thread and attach a video to show the problem. Link to comment Share on other sites More sharing options...
ZincT Posted July 2 Share Posted July 2 2 hours ago, Noel Borthwick said: This is unlikely to be a redist issue. The membership screen should always be shown only when the app is visible in the background. Start a new thread and attach a video to show the problem. Okay, thanks Noel. I have started a new thread here. Link to comment Share on other sites More sharing options...
Michael Stolze-Hölzber Posted July 4 Share Posted July 4 As a professional software developer with over 30 years of experience, I’m honestly stunned by the current state of Cakewalk Sonar’s ASIO implementation. I’ve tested the latest version of Sonar on a clean system, with all third-party VSTs removed from their default paths to eliminate plugin-related interference. Despite this, the application consistently crashes or disappears as soon as I attempt to switch to any ASIO driver — including well-maintained ones from major vendors and even ASIO4ALL, which used to work flawlessly for years. In some configurations, simply selecting an audio driver leads to an immediate Blue Screen of Death — something that should never happen in any user-mode application, let alone in a production-grade DAW. Most concerning, however, is this: Sonar's current installer actively reinstalls the Microsoft Visual C++ 2005 Redistributable, specifically version 8.0.59192. This happens even if you’ve already removed older runtime versions and have the latest 2015–2022 VC++ redistributables installed. If the software is so dependent on a 20-year-old runtime that it reintroduces it silently, then something is very wrong with the deployment model. Telling users to "just uninstall all old redistributables" while your own installer injects legacy binaries back into the system — potentially destabilizing audio subsystems — is not a viable support strategy. I strongly suggest the development team revisit the runtime dependencies and ASIO handling logic. What you have now may technically boot up on some machines, but from a system integrity and reliability perspective, it's broken — and that’s putting it politely. Link to comment Share on other sites More sharing options...
Colin Nicholls Posted July 4 Share Posted July 4 3 hours ago, Michael Stolze-Hölzber said: As a professional software developer with over 30 years of experience, Welcome to the forum. It sucks you're experiencing the behavior you describe. It's definitely not typical. I hope you get to the bottom of it. 2 Link to comment Share on other sites More sharing options...
dtrebel Posted Thursday at 08:25 PM Share Posted Thursday at 08:25 PM I'm disappointed too! New Cakewalk Sonar free-trial - great! load projects impressed! after update cannot even load a FX Vst from Cakewalk (LP Multiband) without crash/hang. I was ready to make the jump to the membership, (already a customer) but now I'll be very impaient, like the rest of the 100m members, waiting for a true fix and a solid version... UGH! Link to comment Share on other sites More sharing options...
Jonathan Sasor Posted yesterday at 06:10 PM Share Posted yesterday at 06:10 PM 21 hours ago, dtrebel said: I'm disappointed too! New Cakewalk Sonar free-trial - great! load projects impressed! after update cannot even load a FX Vst from Cakewalk (LP Multiband) without crash/hang. I was ready to make the jump to the membership, (already a customer) but now I'll be very impaient, like the rest of the 100m members, waiting for a true fix and a solid version... UGH! Which version of the LP Multiband is crashing for you? Can you provide a crash dump for the crash so we can investigate? Details on that here: Link to comment Share on other sites More sharing options...
Jeremy Oakes Posted 21 hours ago Share Posted 21 hours ago On 7/4/2025 at 10:38 PM, Michael Stolze-Hölzber said: As a professional software developer with over 30 years of experience, I’m honestly stunned by the current state of Cakewalk Sonar’s ASIO implementation. I’ve tested the latest version of Sonar on a clean system, with all third-party VSTs removed from their default paths to eliminate plugin-related interference. Despite this, the application consistently crashes or disappears as soon as I attempt to switch to any ASIO driver — including well-maintained ones from major vendors and even ASIO4ALL, which used to work flawlessly for years. In some configurations, simply selecting an audio driver leads to an immediate Blue Screen of Death — something that should never happen in any user-mode application, let alone in a production-grade DAW. Most concerning, however, is this: Sonar's current installer actively reinstalls the Microsoft Visual C++ 2005 Redistributable, specifically version 8.0.59192. This happens even if you’ve already removed older runtime versions and have the latest 2015–2022 VC++ redistributables installed. If the software is so dependent on a 20-year-old runtime that it reintroduces it silently, then something is very wrong with the deployment model. Telling users to "just uninstall all old redistributables" while your own installer injects legacy binaries back into the system — potentially destabilizing audio subsystems — is not a viable support strategy. I strongly suggest the development team revisit the runtime dependencies and ASIO handling logic. What you have now may technically boot up on some machines, but from a system integrity and reliability perspective, it's broken — and that’s putting it politely. As a software developer you certainly know that the most BSOD’s are driver based. You don’t say which audio device you’re running - are its drivers up to date ? Asio4All isn’t the best of asio solutions albeit does work for certain on board cards. Personally i would uninstall it and any generic Asio drivers that other DAW’s may have installed. And this also in the registry. The last time i had a BSOD was a dodgy/corrupt Focusrite driver (it said so on the dreaded screen) i simply re-installed my drivers and all was good. I’ll think you’ll find the greater majority of users are experiencing little or no issues. However, YMMV Try it J Link to comment Share on other sites More sharing options...
dtrebel Posted 7 hours ago Share Posted 7 hours ago 17 hours ago, Jonathan Sasor said: Which version of the LP Multiband is crashing for you? Can you provide a crash dump for the crash so we can investigate? Details on that here: sent, thanks for the response _07082025_170007.dmp _07082025_170007.txt Link to comment Share on other sites More sharing options...
dtrebel Posted 7 hours ago Share Posted 7 hours ago lastest from july 12 All VST-2 from Cakewalk load except the LP multiband and EQ regards Untitled_07122025_073825.dmp Untitled_07122025_073825.txt Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now