any help wouldbe appreiciated,i emailed cakewalk,but under technical support sonar wasnt listed

You'll need to provide a lot more information. We have no clue how , why or when your trying this. 
 
You don't even state which version or Sonar, your OS version, your audio interface etc etc. 

Cactus Music
You'll need to provide a lot more information. We have no clue how , why or when your trying this. 
 
You don't even state which version or Sonar, your OS version, your audio interface etc etc. 

I'm sorry ,I should have explained it better.
I'm using an  HP Spectre x360 Convertible laptop,I have sonar platinum(the manchester 21.12.0.36)
When I switch the audio driver to wasapi i get an audio driver error that says "the following either do not support the current audio format,or are in use by another application,then it wants me to choose disable or use anyways.I choose use anyways but there is no audio.
I dont have any applications open except google chrome
I own a focusrote 2i2 but I am trying to be able to minimize latency just using the laptops audio drivers for when I want to sit in my living room and make music,when I use the virtual keys to play soft synths there is latency that makes it difficult form to be creative.
I wouldreally appreciate any help

Cactus Music
You'll need to provide a lot more information. We have no clue how , why or when your trying this. 
 
You don't even state which version or Sonar, your OS version, your audio interface etc etc. 

I apologize for posting only one line,I got distracted by my wife and hot post,I should have waited till I gave more info

not totally sure, but won't you have to be on 2016.11 or latter to take advantage of the wasapi stuff?
 
http://www.cakewalk.com/S...Fixes-and-Enhancements
 
manchester is way back there

I'm also using the hp spectre 360 although the build may vary. Interface is Scarlett 18i20 2nd gen. Running SPLAT from a March update. Choose not to do the Win Anniversary update yet. I'm using ASIO.

To give a little history on the HP....the spectre so far is running things nicely for last six months. Although a November update made transport start/stop erratic but December update fixed. *Or it was another two month period last few months.

All the others here know a lot more on your subject than I do...... just throwing couple comments on the spectre out there.

The Grim
not totally sure, but won't you have to be on 2016.11 or latter to take advantage of the wasapi stuff?
 
http://www.cakewalk.com/S...Fixes-and-Enhancements
 
manchester is way back there

Wasapi has always worked in Sonar - particularly well under win 10. It was wasapi exclusive mode that was introduced in 2016-11. Ironically it has been less successful than the old wasapi driver on some of my gear.
 
 
To the OP - did you try closing and restarting Sonar after changing the driver to wasapi?
 
 

he is probably on Manchester update because subscription ended (hence: Sonar is not listed under tech support)
I would try opening and closing Sonar as Bruce suggested. WASAPI was updated a few months ago in conjunction with windows 10 but others (like Bruce) have had good results using WASAPI even before that update.
If worse comes to worse and WASAPI wont work, use MME. Its not great and has some latency but it will still play and editing can be done. I've used it in a pinch (on the road with laptop).
 
Best,
Chuck

chuckebaby
If worse comes to worse and WASAPI wont work, use MME.Its not great and has some latency but it will still play and editing can be done. I've used it in a pinch (on the road with laptop).

you may want to (should!) consider asio4all (a wdm wrapper that tricks the host into thinking it's asio) before giving up and using mme, mme is the worst option, see here http://steamcommunity.com...80/#developer_response
or here http://steamcommunity.com/app/380080/discussions/2/365172547941995969/ for example
 
you should avoid mme if at all possible (it's designed for consumer playback of audio/video)

May want to review the driver bit depth and record bit depth settings. I believe this error is thrown when the driver bit depth is set too high. There is no reason to set the record bit depth higher than the driver bit depth.