I tried the procedures to no avail.  I had a Cakewalk technician look through my pc and try to figure out the problem.  He tried different things but could not get Sonar to recognize the twin.  I have sent a request to UAD for support, but havent heard anything yet.  I eve called the support line but I was on hold for so long, I ended up leaving my phone number for them to call me.  I just dont understand how the console is working hand in hand with the twin, but Sonar is not.  If there are any other suggestions, Im open, but am getting so discouraged at this point.  I wish Platinum had a search for device function, maybe that would have done it for me.  Thanks again Jim and Bill  

UAD support, Daniel, called me.  Upon his investigation, he found my 3.0 SS USB port needed updated (last update 10/25/15).  Without the USB port update at HP.com, my pc was making errors with the Apollo and causing Sonar not have access to my driver info.  After a few adjustments and getting my pc to recognize Apollo in the sound control panel, I uninstalled software, and reinstalled it.  Opened Sonar and re set the ASIO driver mode.  Everything was there relating to Apollo.  And for Jim and Bill, I have "0" ASIO4all in my pc now, and it is running very nicely.  Thanks to both of you.  God Bless.   Rocky Fontenot

I've had an Apollo Twin Due since December and it's been nothing but trouble. I'm getting rid of it.

Glad you got that, I was going to say in the past Asio4all often caused conflicts and it has a large hate group amoung forum members. 
I would never recommend installing it if your vendor has proper ASIO drivers. Where it is useful is with using on board sound or with a product that came with no drivers like a USB mike. 
 
I have a DAW set up in my office at work where I run Home Studio and just edit midi into backing tracks to use here for sing a longs. I was using WASAPI without issue but this thing about asio4all came up on the forum (again)  and I thought, what the heck, lets see if this is all true or BS. So I downloaded Asio4all and ran a few tests. It outperforms WASAPI no questions. It is like having a real ASIO driver, at least on this laptop. Might not work on all systems. Lower latency and reported accurately so the offset loopback test scored 100% in sync. WASAPI is out of sync for overdubs. 
 
The other thing it gets bashed for is conflicting with real ASIO drivers. So I brought in my Scarlett 6i6, installed the drivers and had no issue what so ever. I could easily switch between asio4all or the Scarlett ASIO. It worked but with limitations. Under asio4all I lost my 3/4 and SPDIF in/outs. But  I think I could have gone in and configured this. 
 
 So my take- Asio4all is actually good software and does what it does. It is like most software under constant updates so the asio4all we all hated 5 years ago has improved and seems to be mature and stable. 
 
 

My Apollo Twin USB worked right outta the box, I have a Dell XPS about 1 year old with two USB 3 ports .
 
I love the fact you can process a few of the UAD preamps through the hardware, I just wish they would allow more of them.
 
Now every once in a blue moon the detecting apollo hardware and connection dialog dont invoke, but a reboot of the machine takes care of that. It ususally connects in about one minute of  signing into win10 and opening to the desktop

Well, I just read what I had posted last December, and boy was I frustrated.  But all is well now, and I really love my Apollo Twin Duo.  Everything works very well, and I guess, I just had to get the kinks out.  Not long after I posted this, I was contacted by a representative Tech, and he walked me through everything until all was good.  It was great to finally get the Apollo running like I knew it could have.  If my memory serves me right, my main problem was that my USB 3 port needed to be updated and then everything fell into place.  Thanks again for all the feedback, and Im kinda embarrassed by how my post sounded so angry.  I guess I was so frustrated, I dont even remember posting it in that way.  Thumbs up for this site and all who participate.

detrocky
If my memory serves me right, my main problem was that my USB 3 port needed to be updated and then everything fell into place.  

From my experience having a compatible USB3 port is the main issue most folks have when first using an Apollo USB.
Not only do you need a working USB3 port, but a compatible one as well. There are some USB3 chipsets that don't play well with the Apollo USB and will never work as expected. Sometimes, all it takes is to upgrade the USB3 drivers for the motherboard. Sometimes you need to downgrade and use an older USB3 driver. ASIO4ALL is not compatible should never be used with the Apollo USB. The Apollo is not only an audio device but a DSP device as well. The audio & DSP work hand in hand.
I've had my Apollo USB for about 14 months now. It worked right out of the box with my self-built DAW. For kicks, I even tried it on an old Dell i5 D630 laptop running Win 7 and it worked there as well. Although it did take a long time to finalize the UAD install (about 40 minutes) that I almost gave up on it. I had no intention of using it with the laptop, but I was curious if it would even work on an older laptop running Win 7. 
I have since acquired a Satellite OCTO USB for extra DSP and have both the Apollo & Satellite running off of the same pair of USB3 ports on the back of my i7 4770k/Win 10 x64 Pro DAW without any issues.
 
Cheers,
 
Billy Buck

I would like to get an Apollo unit as it will allow me to have a good external sound device and the ability to use UAD plug-ins at the same time.