From an online review of the card in question:

"This card doesn’t have ASIO drivers so those eight channels can’t be addressed by any music software you may be running."

Read more at http://www.trustedreviews...-2#6u6Hi1uK4RWpIxm3.99

Grum.

sock monkey
I see back in December you were shopping for a sound card and said this was for playback only. 
I'm not sure why you bought a 3rd party sound card when all you really need for playback and editing is the on board audio and WASAPI. Asio4all works too, but is no longer really needed now Sonar supports Waspai. 
I use on board on a W7 laptop running WASAPI exclusive day in day out with no real issues. Of couse not all on board cards are created equal but these day's on board video and sound have come a long ways and there's not much need to use 3rd party any more. 

He's running X3.  I don't believe it has WASAPI capability.

X3 has 4 driver modes, WASAPI, WDM/KS, ASIO or MME but lacks the Win10 WASAPI optimizations added after X3 (see http://www.cakewalk.com/Documentation?product=SONAR%20X3&language=3&help=0x22B19 )
 
If it is the case the DAW is for playback only as long as the mode support the desired sample rate and bit depth the choice of driver mode is not critical. The OP may want to try them all.

Yes I know he's using X3, And so do I on that Laptop as well as Home Studio. 

Ah, didn't ever try WASAPI on X3 because it wasn't well executed between Sonar and Windows.

Wrongnoterod
 nothing works.
 
re-installed from their latest update.
 
I can select WDM but then it changes the driver to "headphone" and while there is action in the master bus, no sound comes out of the speakers.
 
I knew this would happen, you cant buy any kind of a soundcard under 500 bucks that has actual ASIO drivers, can you? This was my last shot

https://www.sweetwater.co...--USB_Audio_Interfaces

dwardzala
Ah, didn't ever try WASAPI on X3 because it wasn't well executed between Sonar and Windows.

I was using WASAPI with a UA-101 interface and (I think) Sonar X1. Certainly pre-Platinum anyway. Wasapi fixed a looping bug that only affected some ASIO drivers where when loop recording each successive loop got shortened by the milliseconds set in the audio buffer. So loop 1 would be fine, second pass would replace the last 10ms of the loop with silence, 3rd pass replace the last 30ms with silence and so on.

The bug got fixed in an update, but as I recall WASAPI was pretty much identical in performance terms to ASIO, at least with that particular interface.