Have you been experiencing issues recently where Sonar crashes and your ASIO device vanishes from your DAW ?  (No crash log sent to Sonar, no attempted recovery save, all work since last save lost.  Have to restart your computer to get ASIO device back)
 
Have you been getting frequent audio drop outs when using pro- channel ?
 
Have your projects started to take up to 8 minutes to load ?
 
It seems that others have been seeing these issues and I am wondering how wide spread.  My OCTAcapture was rock solid for years, however recently it has become very unreliable.  Not sure if this is a Windows 10 or Sonar issue ?
 
I do know that I have never had a crash using standalone VST instruments from Toontrack or NI, only seems to happen with Sonar. And my older version of reaper that I use to test with, seems to not have any issues.
 
Add on to this thread if you have seen this and any thing you have done to mitigate.
 
JR

Well I have the Studio Capture at my studio. I must say that I have similar issues on my home setup where I have no audio interface so... I started having issues on my home rig 2 or 3 days ago and similar issues when I went to the studio yesterday. Ca-2a crashes both computers on insertion. Home computer seems to load a project with ca-2a without crashing. Studio computer sure won't load much - can start a new project and loads one project, all midi, that I managed to start on my home computer being sure to avoid ca-2a. However if I insert ca-2a in it it crashes. Ca-2a definitely has issues - sure seems like a section of it's code didn't like December too much. It is acting like they gave it to us for a limited time and now that time is up (I know that is not the case).
Now at the studio yesterday Sonar would start up fine yet crash upon loading almost any project. One exception was a new project, all midi, I just started at home while avoiding ca-2a. But when I loaded any other project Sonar crashed and upon restarting with no reboot, Sonar told me I had no audio devices and didn't "see" the Roland anymore. 
This is very mystifying and seems more related to Sonar than Roland since I'm having such similar issues at home with no interface. Particularly the ca-2a which I feel is the root of all this somehow. I might go up there and try to load some old project that predates ca-2a today. See if the Roland behaves.
 
In summary it would seem pretty obvious at the studio that inserting ca-2a in a prochannel or fx bin crashes Sonar and somehow consequently makes Sonar lose its communication with the Roland or not see it anymore, hmmmm...
 
[edit] - I haven't been getting slow loading(positive) or dropouts(pretty sure)
 

Inserting Rapture Session also crashes the home computer

I have had no problems with Roland's Octa-Capture, that is no drop outs, no lost drivers etc.  Note that I am knocking as hard as I can on wood!
 
Ca-2a is also working here with no problems.
 
Because if this and all of the  reported problems with the latest update for the first time ever I have not updated Sonar Platinum.  Hopefully the bakers will get this straightened out.
 
I should also note that I have my Win 10 Pro set not to update so I do not have the anniversary update on this machine.  I am also off line and I do not have Defender or anything else running in the background.

If you are crashing and losing the ASIO driver try these :
(Found this on a PT forum where people were having similar issues, so may be a Roland driver issue after all and not Sonar or Windows ???)
 
1) If you're using the ASIO driver in your DAW, then you should disable the device in Windows' audio properties (manage audio devices - select all Octa capture ins and outs to "disable") This way you don't have two different drivers trying to access the interface. Of course this means that you cannot watch a move or listen to MP3s on your DAW.  But as an experiment I am trying this and it does seems to be much more stable.  I have not had a problem with CA2A, but I added it to a project and opened and closed it a bunch of times.
 
2) Go into Windows' power profiles, click 'advanced settings' and turn off "USB Selective Suspend". This is a power saving feature that turns off power to the USB port if the device isn't doing anything.
Unfortunately audio interfaces tend not to play well with this.  (not sure if this is an issue or not, but when plugged in I disabled USB selective suspend)
 
On the Roland web page it says that Intel USB chip set is best, not sure if there is anything you can do about this, but this will be something I check if problem persists.
 
JR

No problem with my Quad Capture.

I should add that I have upgraded Windows 10 pretty consistently, including the anniversary update.  And I have upgraded SPLAT to 2016.11.
 
Still playing with Sonar with all my Windows octa capture sound drivers disabled and solid as a rock...hmmmm
 
JR

i have experienced the lost ASIO driver syndrome on Windows 10 x64 w/ SPLAT several times.  but i am using AMD, not Intel.  i know Roland is recommending Intel for the new drivers, but what the heck are AMD users supposed to rely on?

My Studio-Captures have had this problem since late X2 updates!!! I have posted here many times for help and I hope that this thread has better results! I am comforted by auto_da_fe's post above and will try these immediately!!

auto_da_fe
If you are crashing and losing the ASIO driver try these :
(Found this on a PT forum where people were having similar issues, so may be a Roland driver issue after all and not Sonar or Windows ???)
 
1) If you're using the ASIO driver in your DAW, then you should disable the device in Windows' audio properties (manage audio devices - select all Octa capture ins and outs to "disable") This way you don't have two different drivers trying to access the interface. Of course this means that you cannot watch a move or listen to MP3s on your DAW.  But as an experiment I am trying this and it does seems to be much more stable.  I have not had a problem with CA2A, but I added it to a project and opened and closed it a bunch of times.
 
2) Go into Windows' power profiles, click 'advanced settings' and turn off "USB Selective Suspend". This is a power saving feature that turns off power to the USB port if the device isn't doing anything.
Unfortunately audio interfaces tend not to play well with this.  (not sure if this is an issue or not, but when plugged in I disabled USB selective suspend)
 
On the Roland web page it says that Intel USB chip set is best, not sure if there is anything you can do about this, but this will be something I check if problem persists.
 
JR

I'm pretty much having the same issue on my home rig and I don't even have a dedicated audio interface, just realtek for output (I don't record at home). No Roland products at home so it is definitely not a Roland issue.