I can answer that question since SB got back to me with info, after earlier support sessions that were not so good. I'm doing this to help any other hapless person that might get in this situation like I did. I thought that a device had only a single driver for it in the system that was available to run the device. So, I thought the driver had to be installed such that it is the main (and I thought only) thing running the device. I'm not sure if that was true before, but of course it's not true now. When SB Control (and possibly Connect) is loaded, an option to include drivers is presented (it actually says "driver" which adds to confusion). Selecting the option brings in the ASIO driver. However, that driver cannot be found by doing a search in your computer, from what I saw. It also is not the driver loaded to be the operative one in your system. Thus, you have no way of knowing it's in your system. To get use from it, you don't (and cannot I believe) load it as the main operative one. To get use from it for a particular application, you must go into that application and go through menus to find the place where you can choose a driver for audio, and when you do that, the ASIO driver will appear on a list of available drivers. Wow. At least in the end, Creative came through with acceptable help for me.