Windows Audio Device Code 19: Safe Diagnosis, Driver Recovery, and Legacy Migration

A yellow exclamation mark in Device Manager is only a starting point. Open the device’s Properties and confirm on the General tab that the status is actually Code 19, then record the exact device with the error. No speaker output, a wrong endpoint, a stopped service, disconnected hardware, and Code 19 are different faults.

Safety boundary: Do not run a registry cleaner; do not search for and bulk-delete KMIXER, Realtek, UpperFilters, or LowerFilters; do not grant Everyone full control; and do not download packages from driver mirrors. Establish a backup and restore point first, and change only one confirmed device or package at a time.

Scope and Legacy-OS Boundary

The current procedure is for a still-supported Windows 11 release or another Windows edition your organization explicitly supports. Windows XP extended support ended in 2014, and ordinary Windows 10 Home/Pro support ended in October 2025. LTSC, ESU, and managed devices follow their own contracts and lifecycles.

The 2011 article’s Microsoft Kernel Wave Audio Mixer belongs to the Windows XP audio model. Since Windows Vista, Windows Audio Endpoint Builder has enumerated and created user-facing endpoints. Do not expect the same device name or registry layout on modern Windows.

What Code 19 Actually Means

Microsoft’s current explanation is that Windows cannot start the hardware because its registry configuration information is incomplete or damaged. Causes can include multiple services defined for one device, failure to open the service key, or failure to obtain the driver name from that key.

That places the failure in the device-installation/service configuration chain; it does not prove that a registry item containing kmixer or a vendor brand is redundant. A modern audio stack can include:

  • a bus, chipset, or DSP/audio-controller driver;
  • an audio codec, USB, Bluetooth, or HDMI/DisplayPort function driver;
  • upper/lower filter drivers and Audio Processing Objects;
  • Windows Audio and Windows Audio Endpoint Builder services;
  • speaker, headphone, and microphone endpoints.

Deleting the wrong class-wide filter, service, or driver package can break several devices at once.

Establish Recovery Conditions Before Changes

  1. Back up every file you need to keep and verify that the backup is readable.
  2. Open “Create a restore point,” confirm System Protection is enabled, and create a restore point labeled with the date and fault. A restore point is not a personal-file backup.
  3. If the device uses BitLocker, confirm that its recovery key is available; System Restore from Windows Recovery Environment may require it.
  4. Record the Windows release/build, exact machine model, recent Windows/driver/audio-software changes, and the time the fault first appeared.
  5. In Device Manager, record the device name, full device-status message, hardware IDs, driver provider, version, date, digital signer, and Events-tab timeline.

Do not uninstall a driver package or edit the registry without a usable restore point, an OEM driver, and a rollback path.

Collect Reviewable Evidence

Locate the Exact Layer in Device Manager

Expand Sound, video and game controllers; Audio inputs and outputs; and, where relevant, System devices. Do not uninstall every audio item merely because one endpoint is silent.

ObservationMore likely layerNext step
Device explicitly shows Code 19Device-installation, service, or filter configurationPreserve device properties and SetupAPI log; follow the Code 19 path
Devices are healthy but no sound playsOutput selection, mute, enhancement, format, application, or serviceRun the Get Help audio troubleshooter; check output and services
Only an HDMI/USB/Bluetooth endpoint failsMatching graphics, USB, or Bluetooth stackChange only that path’s device and OEM package
Audio controller is completely absentFirmware, chipset, hardware, or busUse OEM diagnostics and firmware documentation; do not clean the registry
Fault began immediately after an updateIncompatible or incomplete new driver/component packagePrefer driver rollback and installation-log review

Record State with Read-Only PowerShell

Run the following in PowerShell. These commands only read device, signed-driver, and service state:

Get-PnpDevice -PresentOnly | Where-Object { $_.Class -in @('MEDIA','AudioEndpoint') } | Format-Table Status,Class,FriendlyName,InstanceId -AutoSize
Get-CimInstance Win32_PnPSignedDriver | Where-Object { $_.DeviceClass -eq 'MEDIA' } | Select-Object DeviceName,DriverProviderName,DriverVersion,DriverDate,Signer
Get-Service Audiosrv,AudioEndpointBuilder | Format-Table Status,Name,DisplayName -AutoSize

InstanceId, machine names, usernames, and some driver paths can be asset information; redact them before submitting evidence to a forum or vendor. Do not upload a complete system inventory publicly.

Inspect Events and the Device-Installation Log

Record the fault time, then inspect adjacent Kernel-PnP, UserPnp, and Service Control Manager events in the System log. Microsoft also documents that setupapi.dev.log records device-installation and signing failures; it is in the Windows INF directory.

Get-WinEvent -LogName System -MaxEvents 300 | Where-Object { $_.ProviderName -match 'Kernel-PnP|UserPnp|Service Control Manager' } | Select-Object TimeCreated,Id,LevelDisplayName,ProviderName,Message
notepad "$env:SystemRoot/INF/setupapi.dev.log"

Anchor the log review on the device instance ID and fault time to identify the INF, service, or signature that actually failed; not every warning is causal. Before sharing an excerpt, redact device instance IDs, user paths, network locations, and organization names.

Safe Repair Order on Current Windows

After each step, restart or rescan as appropriate and verify Code 19, service state, and sound. Stop when successful; do not keep “cleaning.”

1. Exclude Ordinary Output and Connection Problems

Confirm the selected output, volume, mute, audio enhancements, cable/port, and in-app output. On Windows 11, first run the audio troubleshooter in Get Help. It cannot prove that Code 19 is resolved, so return to the device Properties afterward and check the error code.

2. Verify and Restart Audio Services

First confirm the state of Windows Audio and Windows Audio Endpoint Builder. If devices are healthy but a service did not start correctly, follow Microsoft’s audio guidance in Services and restart one audio service at a time, testing after each. Do not change service accounts, dependencies, or startup types, and do not delete service keys.

3. If the Fault Followed an Update, Prefer Driver Rollback

On the exact device’s Properties → Driver page, select Roll Back Driver when the button is available and the timeline matches. Record versions before and after, then restart and verify. Do not use a third-party mirror to obtain an older version.

4. Reinstall Only the Confirmed Device

Microsoft’s current Code 19 resolution is to uninstall and reinstall that device:

  1. Confirm that Windows Update or the OEM provides a signed driver for the exact model, Windows release, and architecture.
  2. In Device Manager, select only the device with Code 19 and choose Uninstall device.
  3. Do not select an option to remove the driver package unless the exact OEM/Microsoft workflow requires it and a verified replacement is ready.
  4. Use Action → Scan for hardware changes or perform one normal restart to enumerate it again.
  5. Verify provider, version, digital signature, device status, and the new SetupAPI time window.

If the OEM audio package depends on chipset, platform DSP, or graphics-audio components, use the OEM’s model-specific installation order. Do not repeat uninstall across every “sound” device.

5. Use a Restore Point to Undo a Known System Change

If Code 19 began after a driver, software, or configuration change and reinstalling the exact device failed, consider a system restore point from before the fault. Review the affected apps and drivers first. System Restore rolls back system files, registry settings, and installed programs, but does not replace a personal-file backup. After recovery, reinstall current security updates and verify audio.

Driver Provenance and Signatures

Prefer Windows Update, the device manufacturer’s support page for the exact model, and—only when the OEM permits it—the hardware component vendor’s official package. Microsoft explicitly recommends avoiding driver downloads from sites other than the manufacturer’s official site.

Keep the download page, package version, applicable models/hardware IDs, release date, file hash, and digital signer. A signature establishes part of the publisher/integrity chain; it cannot correct a model or Windows-version mismatch.

Do not use:

  • driver aggregators, mirrors, forum attachments, or “universal audio driver” bundles;
  • unknown packages that require disabling driver-signature enforcement or installing a test certificate;
  • .sys, INF, or registry fragments copied from another computer;
  • registry cleaners or driver updaters promising one-click repair.

If only an unsigned XP/Vista-era driver exists, migrating the hardware or OS is usually the correct conclusion—not weakening the current system’s security policy.

Registry, Service, and Filter Boundaries

Windows PnP filters can attach above or below a function driver; INF/installers maintain the corresponding lists. An orphaned or misordered filter can cause a device-configuration failure, but UpperFilters and LowerFilters are structures, not garbage to delete on sight.

Use these boundaries:

  1. First use the SetupAPI log and device events to identify the specific package or service that failed.
  2. Prefer Settings → Apps, Device Manager, or the vendor uninstaller to remove the responsible audio-enhancement, virtual-audio, capture, or old-driver software.
  3. Install a corrected package from the same publisher or the OEM, verifying its signature and scope.
  4. Only when Microsoft/OEM support gives written instructions for the exact device and value should an administrator export the exact key, change one named value, restart, verify, and retain an immediate restoration path.

Do not keyword-delete an entire class key, grant Everyone full control, take ownership of system keys, delete unknown services, or apply a CD/DVD “UpperFilters/LowerFilters fix” to audio devices. If a value cannot be mapped to a known signed driver or uninstall entry, stop and escalate to vendor support.

Safe Migration for XP-Era Hardware

Windows XP SP3 is out of support. The historical article’s UAA patches, bulk KMIXER deletion, and permission takeover are not current paths for an Internet-connected production device.

  • First determine whether the hardware vendor provides drivers and firmware for a supported Windows release; if not, treat that as a migration constraint.
  • Prefer replacing the audio interface or computer with one having current signed drivers rather than preserving an unsupported kernel driver.
  • If an old application/device must temporarily remain, isolate its network, restrict data transfer, make a recoverable full-disk image, and document legitimate media and licenses. This limits risk; it does not restore XP support.
  • Virtualization may preserve an old application but does not guarantee specialized PCI/audio hardware, timing, or drivers. Test a copy first and do not bypass software licensing.
  • Migrate user data, project files, and configuration documentation—not unknown driver binaries, activation material, or the whole old registry.

Verification and Rollback Matrix

ChangeSuccess evidenceStop conditionRollback
Get Help/output settingCorrect endpoint plays and device status is healthyCode 19 remainsPreserve setting evidence and enter device path
Restart audio servicesBoth audio services run and playback/recording returnsService stops again or reports dependency failureRestart Windows, preserve events, and escalate
Roll back exact device driverCode 19 clears and version matches expectationMore devices fail or a signature error appearsUse Update driver to restore the OEM/Windows Update release
Uninstall and re-enumerate exact deviceDevice rebuilds with a signed driver and survives restartNo replacement driver or error spreadsRestore through the restore point or OEM package
System RestoreAffected items were reviewed; device and services recoverRestore point too old, BitLocker key unavailable, impact unacceptableCancel and use Microsoft/OEM support path
Vendor-directed single-value repairLogged fault clears and remains clear after restartTarget/value ambiguous or no exported backupImmediately import the exact backup or use System Restore

Finally test built-in speakers, headphones, microphone, and every HDMI/USB/Bluetooth path you actually use; then test restart, sleep/resume, and startup after one Windows update. Confirm that Device Manager has no Code 19, services remain running, and the event log no longer repeats the same installation failure.

When to Stop and Escalate

  • The device belongs to a company/school and drivers, BitLocker, or security policy are managed.
  • Code 19 affects several device classes, or the system also has boot, signature, or filesystem errors.
  • SetupAPI identifies an unknown/unsigned filter, possible malware, or unverifiable legacy security software.
  • The only driver requires disabling security features, or the OEM explicitly does not support the current system.
  • There is no backup, restore point, BitLocker recovery key, or verified replacement driver.

Preserve redacted device properties, the relevant log time window, and attempted steps for the device OEM, Microsoft Support, or organizational IT. Do not expand the registry-deletion scope until something happens to work.

Current Official References

Historical Source Archive (2011, for Provenance Only)

Warning and archive note: The following is the complete visible source_export body with trailing whitespace normalized and four unique dead HTTP image targets (eight URL occurrences) replaced by labeled placeholders. It contains high-risk XP-era advice to bulk-delete registry data, take permissions on protected keys, and grant Everyone full control. The plain-text fence keeps it from becoming the current operational guide. Nothing else was omitted or rewritten; the original URLs remain in source_export/Git provenance.

解决：microsoft kernel wave audio mixer 显示黄色感叹号，错误代码code 19

Table of Contents

Toggle

- [问题描述](https://blog.lazying.art/en/html/computer_internet/488/%e8%a7%a3%e5%86%b3%ef%bc%9amicrosoft-kernel-wave-audio-mixer-%e6%98%be%e7%a4%ba%e9%bb%84%e8%89%b2%e6%84%9f%e5%8f%b9%e5%8f%b7%ef%bc%8c%e9%94%99%e8%af%af%e4%bb%a3%e7%a0%81code-19.html/#%E9%97%AE%E9%A2%98%E6%8F%8F%E8%BF%B0)
- [原因分析](https://blog.lazying.art/en/html/computer_internet/488/%e8%a7%a3%e5%86%b3%ef%bc%9amicrosoft-kernel-wave-audio-mixer-%e6%98%be%e7%a4%ba%e9%bb%84%e8%89%b2%e6%84%9f%e5%8f%b9%e5%8f%b7%ef%bc%8c%e9%94%99%e8%af%af%e4%bb%a3%e7%a0%81code-19.html/#%E5%8E%9F%E5%9B%A0%E5%88%86%E6%9E%90)
- [解决方案](https://blog.lazying.art/en/html/computer_internet/488/%e8%a7%a3%e5%86%b3%ef%bc%9amicrosoft-kernel-wave-audio-mixer-%e6%98%be%e7%a4%ba%e9%bb%84%e8%89%b2%e6%84%9f%e5%8f%b9%e5%8f%b7%ef%bc%8c%e9%94%99%e8%af%af%e4%bb%a3%e7%a0%81code-19.html/#%E8%A7%A3%E5%86%B3%E6%96%B9%E6%A1%88)
- [后记](https://blog.lazying.art/en/html/computer_internet/488/%e8%a7%a3%e5%86%b3%ef%bc%9amicrosoft-kernel-wave-audio-mixer-%e6%98%be%e7%a4%ba%e9%bb%84%e8%89%b2%e6%84%9f%e5%8f%b9%e5%8f%b7%ef%bc%8c%e9%94%99%e8%af%af%e4%bb%a3%e7%a0%81code-19.html/#%E5%90%8E%E8%AE%B0)

## 问题描述

ThinkPad T400新装的正版 XP SP3, 在正确安装了官方驱动后有声音，但重启后就没有声音，进入设备管理器发现microsoft kernel wave audio mixer 显示黄色感叹号，错误代码code 19，开始几次只要更新驱动后就有声音，但后来更新驱动也没有声音了。

网上有说安装UAA补丁及更新驱动的方法，都不行！

## 原因分析

故障肯定来自于那些包含 KMIXER、Microsoft Kernel Wave Audio Mixer、Realtek 的注册表项。这些注册表里肯定有错误的设置。

## 解决方案

我删除了 KMIXER、Microsoft Kernel Wave Audio Mixer、Realtek 在注册表中的相关内容，但是我没有在注册表中搜索到Realtek High Definition Audio。

删除后，我直接重启电脑，发现Microsoft Kernel Wave Audio Mixer依然被自动安装上去，并且正常工作。接着，我重启两次后发现该驱动都被正常安装了。这个问题终于解决了！

**友情提示1：**
 我第一次只删除了包含kmixer的项、包含kmixer（***kmixer***）的“值”和包含kmixer（***kmixer***）的数据的值，重启依旧不行。说明删除得不彻底。

**友情提示2：**
 我当时删除包含 kmixer 的项、值、数据时，直接搜索 Microsoft Kernel Wave Audio Mixer 没有结果。

我发现 Microsoft Kernel Wave Audio Mixer 和 Kmixer(***kmixer***) 在同一个项里。所以我把只要包含kmixer(***kmixer***)的“项”全删除了。

[![]([REDACTED: dead insecure image URL])]([REDACTED: dead insecure image URL])
[![]([REDACTED: dead insecure image URL])]([REDACTED: dead insecure image URL])

第一次失败，因为我犯了两个错误：

1、删除得不彻底，只删除了kmixer项和包含kmixer的值，应该删除kmixer项和包含kmixer值的项，如下图所示，不仅要删除2和3，**应该删除1**。

2、遇到没有权限的项、值数据便跳过，我觉得其实最关键的就是那几个提示你没有权限的

例如：

我开始删除“项”{9B365890-165F-11D0-A195-0020AFD156E4}时，提示没有权限
[![]([REDACTED: dead insecure image URL])]([REDACTED: dead insecure image URL])
 应该右键“项”{9B365890-165F-11D0-A195-0020AFD156E4}，给“Everyone”添加权限“完全控制”
[![]([REDACTED: dead insecure image URL])]([REDACTED: dead insecure image URL])

## 后记

如果我没有记错的话，这问题确实从一开始安装XP时，就存在的。按道理说，系统的算法应该没有问题。我也是按照操作流程一步一步来的。居然会发生注册表信息写入不正确。难道说电脑也会偶尔出错？即便算法正确，用户输入的也相同？

因为声卡依赖的驱动是 Realtek 的驱动，Windows 本身并未提供 Realtek 驱动，只提供 Microsoft Kernel Wave Audio Mixer。

第一次配置声卡驱动时，Windows 由于上述原因按照错误的设置自动安装检测到的声卡，而只有一个 KMIXER 是不能完全驱动此声卡的。此错误的配置又反而影响了正确的声卡驱动的安装。问题估计就是这么阴差阳错引起的。

Leave a Reply