Forum Discussion
Reinstate audio function without reinstalling Windows?
- Aug 02, 2021
1. Run the audio troubleshooter.
This is the easiest thing you can try. If your audio issue is deeply rooted, it will probably not be very helpful to run the audio troubleshooter. It can only fix the simplest possible non-issues such as if you have accidentally muted your speakers and you're unaware of it. In that case, this tool can unmute it for you.
I did not make this tool, so I don't know all of its capabilities. It could for example be able to restart and enable audio related Windows services, and that alone would make it worth a try.
Run control from the Run prompt to open the Control Panel.
Now follow this path.
Control Panel\All Control Panel Items\Troubleshooting\Hardware and Sound
Click on the item that says "Playing Audio" and follow the instructions.
2. Ensure that audio related Windows services are running.Run services.msc from the Run prompt and locate the following two services.
- Windows Audio
- Windows Audio Endpoint Builder
Make sure their Status is "Running" and their Startup Type is set to "Automatic".
3. Reinstall audio device and device drivers.Open the Device Manager and locate the "Sound, video and game controllers" category and expand it to view audio controllers. Right click on each of them and then click "Uninstall device". If you get the optional check box "Delete the driver software for this device" be sure to check it before you click on Uninstall.
Note: You will have to download and reinstall the audio drivers, especially if you have selected to "delete the driver software for this device".
Go to Action menu, then select "Scan for hardware changes" to re-enable your audio device(s). You may need to reboot the PC, especially if you have selected to delete the device drivers in the previous step.
4. Restore system configuration using a System Restore point.Run sysdm.cpl from the Run prompt to open System Properties and click on "System Protection" tab. Then click on System Restore, select "Choose a different restore point" and click Next. Then select a restore point whose creation date and time predates the audio issue you're experiencing. Don't select one that's too far back in the past as it could undo more system changes than you would want to.
5. Attempt to manually repair the Windows registry.Have a look at one of these locations.
- C:\Windows\System32\config\repair
- C:\Windows\System32\config\RegBack
See if you have some files in there with names such as "SAM", "SECURITY", "SOFTWARE", etc. These are your registry hive files. These files contain all the important system configuration parameters and allow Windows to boot correctly, recognize and initialize your system devices. You can use these files in an attempt to repair your Windows registry using various tools Microsoft has released over the years, including RegEdit.
Note: The hive files your system is currently using are stored one level up in the System32\config folder.
Note: This is a very advanced topic, and I would advice against using these techniques if you don't feel comfortable with it. I would not only advice against it because it's an advanced topic, but because the chances of success are slim and you may be wasting your time on this. There is no single tool (to my knowledge) that Microsoft has released that can reliably repair a corrupted Windows registry. The best I know of is RegEdit, but you need to be running it on the system you are trying to repair, or know how to load and unload registry hives offline and make changes that way. It can get really tricky and it's a dirty solution.
Note: Starting with Windows 10 version 1803, Windows no longer uses the RegBack folder to store backup copies of its important registry hive files. This feature has been deprecated and this folder is no longer used.
Note: Don't fool yourself with registry repair tools. They don't do anything useful but make you feel good about your PC, making you think that you're doing something good for your PC. They belong in the same category as "PC Performance Boost" type of applications. There are dozens of these registry repair and cleaning tools on the web, and all they do is remove registry keys and values that are not of any concern to begin with. You can end up screwing up a perfectly healthy Windows installation by using these tools.
6. Do a so called "in-place upgrade".This works by migrating the old Windows registry and all the registered devices and their drivers to a new Windows registry. The chances of a successful repair are higher here than doing manual registry labor. It depends largely on the state of the current registry and how badly it is corrupted.
7. Restore your system from a system backup.If you have one, restoring your system state from a backup could be your first and last step you would need to do to recover from this kind of audio issue. If you don't have a backup solution already, you should invest some time in sourcing a backup solution that can create disk images or system images. I personally have a very good one, but this event with Windows Update and audio issues was set too far back in time for me to revert the changes using my system image, and I didn't attend to the problem at hand before it was too late.
8. Reinstall Windows.As the last resort, if everything else fails, you can be sure that reinstalling Windows will most certainly resolve the issue. This too could be your first and last step you would need to do. The cost of reinstalling Windows is that you would have to restore all your files and applications. As I pointed out previously, your files should not be stored and living on your Windows partition in any case. Make it a habit to store your files elsewhere. The same goes for applications and configuration files. If you can install them elsewhere, do so. This will make you much better prepared to reinstall Windows whenever you run into some issue that you can't resolve. Reinstalling Windows fixes 99.99% of all issues with Windows.
Following articles discuss how to repair Windows registry hives.
https://www.kuhnline.com/repair-corrupted-registry-hive/
https://www.css-networks.com/2010/12/recovering-from-windows-registry-hive-corruption-the-clever-or-smart-way/
It's surprising to see that the first author (first link) came to the same conclusion as I have: the first thing you want to try when a registry hive has been corrupted is to use the Last Known Good Configuration. Followed by using a restore point in System Restore, followed by offline loading the hive in Registry Editor. In that order.
Then I found a second article, from a different author (second link) that suggests offline loading the hive in Registry Editor immediately (same as the other author), without testing any of the other method. He describes this as "the smart way" of recovering from registry hive corruption.
So all I really need now is a good copy of my SYSTEM hive to attempt to repair this "No Audio" issue offline in a second computer. It would seem reasonable to think that this might actually do the job.
Sadly I don't have a good copy of these files. My system image backups are not old enough to retrieve copies of these files that predate this issue with audio devices. Otherwise I have not had any major issues with this computer, not a single crash, not until I got KB5003345.
I may still be able to repair the SYSTEM file that I have, using that extra stuff (LOG1, LOG2, BLF, REGTRANS-MS). But it seems like a long shot, and will require opening my computer and disconnecting my M.2 disk, which may be problematic to install on the second computer since it's not a regular SATA HDD or SSD disk. If I knew it would work I would do it... I may still do it, I just need to convince myself it's worth the hassle. At least I have a fresh backup in True Image to fall back on should something go wrong. I will think about it.
I wish I knew what I know now. But wishing is not going to help me...
Also, I will add that I just learned that as of Windows 10, Windows no longer makes backup copies of these hive files as of version 1803. See for yourself, the Microsoft Docs link is below.
https://docs.microsoft.com/en-us/troubleshoot/windows-client/deployment/system-registry-no-backed-up-regback-folder
Since at least Windows 2000, there was this folder:
C:\Windows\System32\config\RegBack
Windows used to make its own backup copies of the registry to this folder. But starting with Windows 10 version 1803 it no longer does that. It would have been so convenient if it did.
This change is by design, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you use a system restore point.
Actually, I am using the very latest Windows 10 evaluation copy (build 21390.2025) on the Dev channel and I can still see this folder, but it's empty (screenshot below).
This article is not very helpful but it supports what I said earlier about how the KB5003345 update is to blame that I'm in this situation now, because it triggered a GSOD loop and power loss.
https://docs.microsoft.com/en-US/troubleshoot/windows-server/performance/registry-troubleshooting-advanced-users
A power failure or some other unexpected shutdown event may cause a corrupted registry hive. To determine whether this is the cause of the issue, look for event ID 6008 entries. Event ID 6008 entries indicate that there was an unexpected shutdown. In this case, some process may have been modifying part of the registry hive, and the computer lost power before that change could be completed. This leaves the registry hive in an inconsistent state.
So basically it's Windows that broke Windows. I am only guilty of testing unstable Windows versions. 🤪