"Unable to Open Audio Playback Device" Win 10 Anniversary?

Hi Larry,
I had the same problem over the weekend.  I just reinstalled the driver for my audio card ( actually a Roland /Cakewalk VS20), and it worked fine. Good luck! 

Thanks, Tim and Craig.
 
I uninstalled Mix Control 1.8 and the Scarlett driver, then reinstalled both. Now when I open a project template and play the guitar, the signal is getting through from the 6i6 to the computer, showing on all the meters and sounding. But when I try to play an existing project I get the same error as before, to wit "Unable to open audio playback device. Device may not support the current project's audio format or may be in use" and the transport won't roll. There is nothing unusual in the project I'm trying to play, and it worked the last time I tried to listen to it -- a few days ago just before my Windows Anniversary update.
 
So I'm still trying to figure this out. Does anyone have an idea?
 
EDITED TO ADD MORE INFO:
1.) The playback problem appears to apply only to one project. It's an old project that was recorded in SONAR 8.5.3. Just by coincidence I chose it to test my system, and assumed the failure would apply to other projects. I've tried two newer projects, and they play fine. This is good news, but still a problem that must be solved, because I have a bunch of stuff from the old days that I want to be able to use.
2.) On the "bad" project, in Preferences|Audio|Driver Settings, bit depth was set to 24 and greyed out -- I could not change it. Later, after I messed around with sample rate & bit depth in Windows Sound control panel, I discovered that SONAR's bit depth had changed to 16, and was still greyed out.
2.) Also on the "bad" project, in Preferences|Audio|Driver Settings, the "Asio panel..." button does not open Mix Control. It doesn't do anything.
 
Thanks for reading. I'll try any ideas you might have.

Check all ins and outs in that project. If it was made with a different audio interface there could be residual outs that are no longer there. Check Preferences to see that you have the right driver loaded.
 
Once done save the project.  
 

Aside from what Bitflipper mentioned, it could be that some other program (e.g., a browser) already grabbed Windows' audio engine.

You got off easy, my DAW will not boot after that big anniversary roll up patch! I rolled it back and got it running again. But, I will need to turn off driver authentication so I can install an unsigned driver I think.

eric_peterson
You got off easy, my DAW will not boot after that big anniversary roll up patch! I rolled it back and got it running again. But, I will need to turn off driver authentication so I can install an unsigned driver I think.

Eric - I feel your pain. I'm not sure a rollback would solve my problem, though, because 1.) I don't know for sure when this started and 2.) I think everything worked briefly after the Anniversary update and then went south. Unfortunately, I was using the DAW only sporadically, so didn't notice what triggered my current dilemma.

Maarkr
check Win Sound... both playback and recording setup... click on properties of your selected interface, then the advanced tab.  Look at the default format like bit flipper said, but also look at the Exclusive mode options which give apps exclusive priority.  Try de-selecting them.

Maarkr - Deselected Exclusive mode, but it didn't help. As I mentioned in red above, I now have only 16 bit format options in Win Sound, and I think this "bad" project was recorded at 24. I don't know how to tell, but that would make it not play, wouldn't it? I used to have 24 bit options with the Scarlett 6i6, but not now.