Apollo Twin USB duo Daw connection HELP!

Man u guys sound like you know what your saying, but im worried about deleting files that I dont know much about. I hate to ask, but it would be better for me to to chat one on one.  If its possible, I would really appreciate it.  Im spending more time fighting with this than I would like.  I just hate to mess something up with my pc ignorance.  If you can chat via phone, my email is [link=mailto:detectivefontenot@yahoo.com,]detectivefontenot@yahoo.com,[/link] or facebook, Rocky Fontenot (Kinder, La), to let me know.  Thanks again, but I really dont want to start deleting things unless someone could walk me through.  Sorry about that.

Do you think I should delete the m-audio file, its in the same location and was using the asio4all driver to operate in my DAW?
 

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

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. 
 
 

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.

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.