Windows now selects the device-specific driver instead of the default USB audio 2.0 driver. You can do this by using the appropriate installer for the device. If the device is not yet connected, install the device-specific driver first. The problem may not occur if the device is connected to a different USB port. Method 2Ĭonnect the device to a different USB port. In step 2, don't select the Delete the driver software for this device check box.
To fix this problem, use one of the following methods. Because the new driver does not support the WaveRT port, the system cannot access the driver. Therefore, the operating system assumes that the new driver also supports the WaveRT port. When the device-specific driver replaces the default driver, the device interface that is created by usbaudio2.sys is still used because the reference strings overlap. However, both drivers use the "wave" reference string when the device interface is registered. This "audio not playing" problem occurs because the default USB audio 2.0 driver (usbaudio2.sys) uses the WaveRT port for operation but the device-specific driver does not. Both the Windows Audio and the Windows Audio End Point Builder services must be running for audio to work correctly. When you select the icon, you receive the following message:Īudio services not responding.
The speaker icon on the task bar is marked with an X mark. In this scenario, the device cannot be used, and the computer does not have sound. The downloaded device driver replaces the usbaudio2.sys driver.Windows then downloads the device-specific driver from Windows Update.The operating system detects the device and loads the standard USB audio 2.0 driver (usbaudio2.sys).You connect a Universal Serial Bus (USB) audio device, such as an audio adapter or USB digital-to-analog converter (DAC), to a Windows 10 Version 1703-based computer for the first time.USB Audio Not Playing (KB 4045958) "Audio services not responding" error and USB audio device does not work in Windows 10 version 1703
0 kommentar(er)
