Windows will win this fight unless you change the rules. A Realtek audio driver that keeps reinstalling itself after every reboot or Windows Update cycle is not a bug you can patch by clicking “update driver” harder; it is Windows treating a specific driver package as the recommended match for your hardware ID, then quietly restoring it whenever it re-evaluates the device. Pinning a version means breaking that match deliberately and repeatedly.
We have had this happen most on laptops where the OEM ships a customized Realtek package with a vendor control panel baked in, then Windows Update decides a generic Realtek High Definition Audio driver is newer (it is often a different, later-dated build) and swaps it. The control panel vanishes, jack detection breaks, and your headphone port starts behaving oddly. Rolling back buys you a day or two. The fix needs to stop the automatic replacement at the source.
Why the version you install keeps getting replaced
Windows does not track “your preferred driver” the way people assume. It tracks what is installed and compares it against what Windows Update and the local driver store consider best for that hardware. If the package you installed has an older build date than the one Microsoft is offering, Windows has no reason to keep yours. It reinstalls the newer one, you notice the sound is wrong, and the cycle repeats.
Realtek makes this worse because the audio chip is usually identified by a generic hardware ID, and multiple driver packages claim to support it. Your OEM’s package may be signed and correct for your machine, but the store still holds a competing generic entry. Until you remove or block that competing entry, the store can reinstate it. Everything below is about controlling that store, not about the driver itself.
Step one: stop Windows Update from touching drivers
This is the load-bearing step. Skip it and the rest is temporary. On Windows 10 and 11 you can interrupt automatic driver delivery through Settings, and you can also do it more firmly through the system’s device installation settings. The clean approach is to use the Group Policy or registry route that tells Windows not to fetch drivers from Windows Update for any device. Microsoft’s own documentation for device installation settings covers the “Do you want to automatically download manufacturers’ apps and custom icons” toggle, but the stronger control is the policy that blocks driver search on Windows Update entirely.
For a single machine at home, the Device Installation Settings dialog (reachable from System Properties, Hardware tab) lets you set it to not install manufacturer apps automatically. For a work machine or one you care about, the policy route is more reliable because Settings can be reset by a feature update. We pin it before installing anything, then verify after the next cumulative update that it held.
Step two: install the version you actually want, from the right source
Realtek’s own site does publish HD audio codec packages, but the download flow is not friendly and the generic package may not match your OEM port layout. For most laptops and many prebuilt desktops the correct source is the OEM support page for your exact model. Download the Realtek audio package for your Windows version and architecture, and keep the installer file somewhere you will find it later. You will need it again.
Note the version number before you install. You will be checking it repeatedly, and “it looks newer” is not a measurement. Open Device Manager, expand Sound, video and game controllers, right-click the Realtek entry, and read the Driver tab. Write the version and date down.
Step three: install clean, then clear the competing package
If a newer generic driver is already sitting in the store, installing your preferred package on top of it may leave both entries present. We find it cleaner to remove the audio device and let Windows re-detect, then point it at the downloaded package using the “Browse my computer for drivers” option in the Update Driver wizard. Microsoft documents that path, and it does not require the newer package to be absent, only that you select your package explicitly.
- Open Device Manager and remove the Realtek audio device (right-click, Uninstall device). If offered, tick the box to delete the driver software for it.
- Restart. Windows will reinstall something on its own if Update is still allowed to; that is why step one comes first.
- Run the OEM or Realtek installer you downloaded, or use Update Driver and choose Browse my computer for drivers, pointing at the extracted package.
- Restart again and confirm the version in the Driver tab matches what you recorded.
If you cannot select your downloaded driver files because the OEM only supplies a packaged .exe installer, run that installer and let it place the driver itself. Many OEM Realtek packages install silently and register the control panel as part of setup. That is normal, not a sign of anything wrong.
Step four: block the newer package from coming back
With Update blocked and your version installed, the remaining risk is the driver store still holding the competing package and a future servicing operation choosing it. Windows has a built-in mechanism for this: the “Show or hide updates” troubleshooter (Microsoft’s wushowhide.diagcab) lets you hide a specific driver update so Windows Update stops offering it. Run it, let it scan, and hide the Realtek HD Audio entry that keeps reappearing. This is the piece most guides skip, and it is what converts a temporary rollback into a pinned version.
On Windows 11 the same principle applies; the troubleshooter is old but still functions on current builds for hiding driver updates. If it will not run, the policy route from step one is your fallback, because a blocked Windows Update driver search leaves nothing to hide.
We also recommend keeping a copy of the working installer and a short note of the version and date. A system restore point before each install is cheap insurance, and a record of what worked is the thing you will actually want six months from now when a feature update resets half your settings. The rollback path Microsoft documents (the Roll Back Driver button on the Driver tab) only works when Windows has stored a previous version, so it is not a plan on its own; it is a fallback when the store happens to have kept one.
When the cycle still will not stop
If the driver returns even with Windows Update driver search off and the update hidden, look at whether your OEM’s management software (the vendor update utility that ships with many laptops) is reinstalling it. Those tools run their own update checks and can override Windows settings. Disable or uninstall the vendor update agent, then recheck. In rare cases the Windows Update policy is being reset by a management tool; Event Viewer will usually show a driver installation event around the moment the version changes, which tells you what triggered it.
The reason this problem is so persistent is that people treat it as an audio issue. It is a driver-installation policy issue. Pin the policy, pin the package, hide the competing update, and the reinstalls stop.