I am a software developer, so spare me "tech police" routine.
 
The fact that SONAR is popping a dialog for a driver that is greyed out and not even selected is a BUG.  At the very least it is an undocumented feature.   There may be some way external to the software to workaround this bug.
 
This driver does not show up in any other audio programs.  Cubase, Samplitude, Ableton, Studio One have worked fine.
 
RME drivers are solid, this was a minor release with 3 tiny unrelated features addressed.  There is a .0001% chance it is the driver, but since last release of SONAR was prior to latest RME patch,  very very unlikely.
 
Another RME user in this thread reported getting this same problem, for which he came up with a workaround he cant remember, but it did not involve an RME patch.  Most likely explanation a SONAR bug.  Its possible to modify the system to avoid getting the bug, which is what you are suggesting.  That is called a workaround.
 
In software world, finding bugs is a good thing.  Acknowledging them instead of dismissing the user is the way they get fixed.

If you are a developer I would hate to use anything you developed if this is how you troubleshoot.. Sonar has plenty of bugs..all software does but so far you have not described anythong that sounds like bug. You would think a developer would know better.

Cakewalk has a site for submitting repeatable problems or bugs. They also have a support line. Call support and get some help is my suggestion. Personally, I'm betting it's related to software you installed.

I have to agree with dubdisciple.

I'm a developer as well. Sorry no, ABSOLUTELY NOT a Sonar bug. This is an issue with drivers on your machine and/or conflicting software. Your debugging skills should have worked that one out by now. You should be able to trace this issue and search the right areas within windows if you have the expertise. You also seem to be the only person complaining about this problem since Sonar was released. Sorry you are talking a load of baloney and by the way you write I don't see any form of a qualified developer mentality, hunches and hearsay is not how you go about things when debugging these sort of issues.

If you were a half decent software developer you would give exact steps to repro the issue so that everybody else could reproduce it before you proclaimed it as a bug. As a software developer you should know a bug that isn't reproducible does not get fixed.

To add why don't you remove this driver? With your skill set you should be able to work out where it is and how to uninstall or forceably remove it. Or you could locate the issue by process of elimination. And update your drivers and firmware as others have said.

Anderton
.FWIW I've never been able to get the Generic ASIO driver that Cubase installed off my system, and believe me, I've tried because it wants to take over if I boot any program without remembering to turn on an audio interface first.

Craig I experienced identical issues with JRiver software, the solution was to (in explorer) rename the files needed for the driver, or rename the folder if they are contained within a dedicated folder. So maybe look within the cubase application folder for these.

Also here is a link that could help (removal via registry):
http://www.kvraudio.com/f...iewtopic.php?p=5629592

May also be of help to the OP after he updates his drivers.

Ta

Teal
Another RME user in this thread reported getting this same problem, for which he came up with a workaround he cant remember, but it did not involve an RME patch.  Most likely explanation a SONAR bug.  Its possible to modify the system to avoid getting the bug, which is what you are suggesting.  That is called a workaround.

 
Unless there's some other post you're referring to I don't think you have your facts straight. He remembered what caused the problem, and it didn't involve Sonar:
 
"I have the RME unit and I have come across the problem you describe. I was able to chase it down to a MIDI device (Fishman Triple Play) in standalone mode. However I don't believe I ever came across it while utilizing the device while I was in Sonar."
 
The only other post with someone having problems with RME related to his specific computer, with the computer manufacturer blaming RME and RME blaming the computer manufacturer. Again, not a Sonar problem.
 

In software world, finding bugs is a good thing.  Acknowledging them instead of dismissing the user is the way they get fixed.

Finding bugs is good, but there's zero evidence you've actually found a bug in Sonar as opposed to one that's system-specific. Sonar exposing a bug is different compared to Sonar having a bug. You haven't provided any steps to reproduce, and no other RME user has the same problem with Sonar. Unless you can figure out how to reproduce it, or someone else encounters it, you're the only person who can find out what's wrong with your system. You haven't given any information the community (especially RME owners) can use to help you find out what's wrong.
 
What do RME and the RME forums have to say about this? By definition they're almost all RME users, and some are bound to use Sonar, so you might have a better chance of finding out if anyone else has experienced this issue in a context other than running Fishman's TriplePlay in standalone mode. But just the very fact that the same problem occurs with a program that's NOT Sonar pretty much indicates the problem lies outside of Sonar.

I'll toss in here that I think the demo is actually the original X3,,, It does not have updates applied.  Is this correct? I'm thinking this because when you purchase and download X3 you have to then download the "e" patch afterwards. Small chance this  could make a difference but worth a mention. 
 
 I've seen a few good ideas here and I don't see that you have tried them. 
 I'm sure your issue is related to mucking around too much with an audio computer and now you've got an issue where they normally wouldn't be one. 
 

It's X3D I think unless they did another build since.

fwiw, it's not the first time sonar has had trubs with particular drivers, unless everyone has forgotten the x1/lynx hoo-ha that prompted a hotfix