Hi,
I’m not aware of any issue. But it’s definitely better to use a proper Audio Device with own ASIO driver. The only way, how to know, if there is any issue with your specific system, is to download Cubase 15 Trial.
On Windows, it’s the Steinberg built-in ASIO Driver.
It has never been officially tested in this combination. Therefore no one know.
Hi,
Thank you for the information you sent me.
This may not be the issue here, but just noting it in case.
In Cubase 15, when using the Steinberg generic ASIO driver, if you plug in the headphones, you need to make changes in two places.
I ran into that at SuperBooth and the Steinberg team helped me out 
Pete
Microsoft
Thank you very much for the information. I have no plans to upgrade to Cubase 15 Pro at the moment, but if I do decide to upgrade, I’ll try the trial version first to see if everything works well.
If you use the Steinberg built-in ASIO driver, selecting the “headphones” box in the ASIO driver control panel and then selecting the headphones output in the Studio > Audio Connections menu produces headphones output in my case, that is, in Cubase 12/Windows 11 and a Realtek internal sound card in a notebook.
However, simply removing the headphone jack from the PC blocks the audio, instead of outputting the PC speakers by switching, and no audio is output even when the headphone jack is reinserted. To restore the headphone audio, you need to reset Cubase 12 to its factory settings.
If you remove the headphones, you have to go back through the steps I mentioned, only selecting the built-in speakers instead of the headphones.
Pete
Microsoft
Hi,
I tested the drivers and found that:
- The “Generic Low Latency ASIO Driver” only selects the internal speaker output ports (it does not detect the headphone output ports);
- The “ASIO4ALL v.2” driver, on the contrary, select only selects the headphone output ports (it does not detect the internal speaker output port).Furthermore, because it detects many Intel Smart Sound ports and other special ports, it tends to get stuck during ports selection. To unlock the PC, you need to restart it and relaunch Cubase 12 with factory settings.
- The “Steinberg built-in ASIO driver” makes what you describe possible, as follows:
To select the Headphones output:
1. Studio → Studio Setup → Audio System = Steinberg built-in Asio driver → Control Panel:
2. Check the “headphones” boxes in the ASIO driver Control Panel
3. Studio → Audio Connections (Output) menu:
4. Change Audio Device selection from “Not connected” → Steinberg built-in ASIO Driver (Device name = Headphone).
To select the PC Speakers output:
1. Studio → Studio Setup → Audio System = Steinberg built-in Asio driver → Control Panel:
2. Check the “Speakers” boxes in the ASIO driver Control Panel.
3. Check that in Studio → Studio Setup → Audio System = Steinberg built-in Asio driver → Ports (output) = Speakers;
4. Studio → Audio Connections (Output) menu:
5. Change Audio Device selection from “Not connected” → “Steinberg built-in ASIO Driver” (Device port = Speaker).
I have definitively set the “Steinberg built-in Asio driver” as the driver for my Cubase 12, but I remain very perplexed when I note that in my other Netbook with Windows 10 with Cubase 12 and in my other DAWs with Windows 11 the Headphones/Speakers output of the PC is switched simply by inserting/uninserting the Headphones jack, while in this case I am forced to repeat the series of steps mentioned above.
Thank you for your help.
From my experience that has rather something to do with the maker of the computer and Realtek and not with Cubase.
Hello,
With Cubase software on Mac operating systems, you can directly specify which input and output ports are actually active, while on Windows operating systems, you must use a suitable ASIO interface driver to select ports. ASIO drivers must be updated and optimized for new generations of Windows and PCs as they are released (in my case, the notebook is an HP with a 14th-generation Intel Core ULTRA 7 with 16 cores + IA CPU). I don’t think HP can be considered an unreliable maker of the computers.
According to Microsoft, the transition from Windows 10 to Windows 11 is carried out without any particular problems, as if it were an upgrade, but from direct experience I have been able to ascertain that some software encounters difficulties when switching to the newer OS due to certain choices made by Microsoft and in these cases it is necessary to intervene with appropriate choices or by updating the drivers to resolve these problems.
I’ve been a Cubase user since 2001 (Cubase VST 32), and recently I temporarily installed and used that software with MIDI files on a Windows 10 PC, with no problems: fantastic!!!
I think Cubase is among the best DAW software, especially for working with MIDI files.
From what I’ve learned, the “Steinberg built-in ASIO driver” takes into account newer generations of PCs and Realtek HD cards and is certainly an improved driver compared to the “Generic Low Latency ASIO Driver” (default for Cubase 12 – Windows 10), but it’s not completely up to par with Windows 11.
That’s why I’m still very perplexed…
Maybe you can switch the behaviour of the output:
Hi,
Thank you, but your suggestion cannot be implemented because my Windows 11 PC doesn’t have the Realtek app with the corresponding “Realtek Audio Console,” and there’s no way to fix it. The integrated Realtek sound card works perfectly, has the latest driver, and can be accessed from the following path:
Control Panel->Hardware and Sound->Device Manager->Sound, video, and game controllers->Realtek(R) Audio.
You can also get to device manager by right-clicking the Windows logo on the taskbar and choosing your localized equivalent to “Device Manager”
Pete
Microsoft
Hi,
In "Device Manager," I found the "Audio Input and Output" section, where Windows 11 manages the three ports on the PC's internal sound card. These ports correspond to those found in Cubase using the "Steinberg built-in ASIO Driver" in the ASIO Driver Control Panel, namely:
1. Microphone Array (Intel Smart Sound Technology for Digital Microphones)
2. Headphone (Realtek(R) Audio)
3. Speaker (Realtek(R) Audio)
In the “Events” menu for the Headphones and Speakers ports, I found the following message regarding Windows 11 loading on a new PC:
“16.04.2026: Device settings were not migrated for SWD\MMDEVAPI\{0.0.0.00000000}.{49244445-9349-4663-a79a-d41e7ab2d2a7} from the previous operating system installation due to a partial or ambiguous device match.ID last resort device: SWD\MMDEVAPI\{0.0.0.00000000}.{239b03b6-a268-44c9-b04c-20efd5d9373d}
GUID classe: {c166523c-fe0c-4a94-a586-f1a80cfbbf3e}
Path:
Migration classification: 0xF00000000000F120
Present: state true : 0xC0000719”
Maybe it's nothing important and I shouldn't take the report into consideration, but can you tell me something about it?
Hi,
Post Scriptum: I forgot to say that in the “Events” and “Driver” menus of the Headphones and Speakers ports, after the report, various updates are registered and that they currently appear to be working regularly.
After the report, various updates are recorded and that now the outputs are functioning regularly.
Please don’t put posts inside code blocks. They are nearly impossible to read when you do that.
Pete
Microsoft
I would like to thank the users who contributed to the Forum, thanks to whom I learned the solution to my problems:
1. To use Cubase 12 with Windows 11, it is better to use the “Steinberg built-in ASIO driver” (the default driver for Cubase 15, provided free of charge by Steinberg) rather than the “Generic Low Latency ASIO Driver” (the default driver for Cubase 12 – Windows 10);
2. To select the audio ports for the Headphones or Speakers Output (“Steinberg built-in ASIO driver” does not detect both audio ports simultaneously), you can follow the instructions provided by Psychlist1972 (Pete – Microsoft):
and then:
Cubase 12 now works fine with Windows 11 and the internal Realtek card, except that plugging/unplugging the headphone jack into the PC doesn’t switch the output between the two devices (headphones/speakers) as expected.
But for me, this isn’t a problem; it’s an acceptable, minor issue.
