I think it's also something to do with how well your ASIO drivers for your interface are written too. 
I know many people have issues with on board audio taking over where others do not. 
And the same would go with this issue. Probably lots of people have that driver and without issue as Cubase and Wavelab are popular. 
A good audio driver will manage this and not allow take over. 

Lynx have some of the best drivers in the business. None of my other hosts where affected, only Sonar. All on board audio is always turned off. The Generic ASIO Driver showed up as an option in Sonar, but was never activated. Yet, it seems that the program kept the driver in a kind of "ready state" to where it could be accessed. With drivers being installed by different devices and programs, and Microsoft being hell-bent on taking control away from the user, Sonar would be more future-proof if we were given some kind of driver blacklist. I assumed that's what was happening when drivers were not activated, but it wasn't. A blacklist would keep a driver from affecting Sonar even if it became unknowingly re-enabled. Then the program could concentrate fully on the task at hand.
 
I'm not the only person that's been burned by this :
 
"I think what I learned is this: Drivers ARE a major source of issues."
 
http://forum.cakewalk.com/Troubleshooting-Tip-that-Saved-My-Windows-Sanity-m3654214.aspx
 
I use different programs for different purposes. Sonar has several advantages over other hosts. I just wish it wasn't such a fragile egg sometimes, and I think steps could be taken to shore up stability.

Resonant Serpent
"I think what I learned is this: Drivers ARE a major source of issues."
 
http://forum.cakewalk.com/Troubleshooting-Tip-that-Saved-My-Windows-Sanity-m3654214.aspx
 
I use different programs for different purposes. Sonar has several advantages over other hosts. I just wish it wasn't such a fragile egg sometimes, and I think steps could be taken to shore up stability.

The problem is you can't have access to everything AND have stability. For example I think (not sure) SONAR is still the only DAW that can access the new low-latency WASAPI drivers. This is fantastic is you're using a laptop or doing something like trying to record video of SONAR doing something while you're hearing SONAR, but it adds one more layer to how SONAR interacts with the OS.
 
Maybe a solution would be when Windows 10 installs a Sound, Video, or Game Controller driver during an update, upon rebooting a dialog box could come up asking if you want it enabled Y/N.

Exactly. If a driver was marked "excluded", then it would have zero impact on how Sonar runs no matter the current state of that driver.