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.
Or the system repair disk is done at the beginning of use, and then it is forgotten
As for "recovery drive", I don't have that either. Isn't that the Windows equivalent of disk imaging backup system? I may be confusing it with something else. I use Acronis True Image for my system backups.
Sadly I no longer have the system image versions in True Image that predate the audio device problem. Otherwise I would like to have another look at repairing that SYSTEM hive (from backup).
Because, what this "No Audio" issue is, is essentially a Windows Registry corruption, caused by a filesystem error which was inevitable when the computer kept entering the GSOD (green screen of death) loop cycle, triggered by installing KB5001391 (plus some other root cause further down the rabbit hole).
What I do have on this computer is a 99 MB "EFI System Partition" and then another 499 MB for which no description is given in Disk Management. It appears to be the recovery partition, when viewed in Diskpart (as seen below). Then there is a second 555 MB recovery partition at the end for some reason (not sure why there are two of them).
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Reserved 128 MB 17 KB
Partition 2 Recovery 499 MB 129 MB
Partition 3 System 99 MB 628 MB
* Partition 4 Primary 464 GB 727 MB
Partition 5 Recovery 555 MB 465 GB
- SamirGunicJun 16, 2021Brass Contributor
I have this SYSTEM hive file and then some LOG files, plus some more.
SYSTEM SYSTEM.LOG1 SYSTEM.LOG2 SYSTEM{1a3392bd-bad9-11eb-bacb-000d3a964f52}.TM.blf SYSTEM{1a3392bd-bad9-11eb-bacb-000d3a964f52}.TMContainer00000000000000000001.regtrans-ms SYSTEM{1a3392bd-bad9-11eb-bacb-000d3a964f52}.TMContainer00000000000000000002.regtrans-ms
According to online sources, these files can be used to repair a corrupted Windows Registry hives. But it has to be done offline.
Because such registry corruptions are often caused by filesystem errors and corruptions (due to sudden power loss for example caused by a GSOD crash and Windows Update), one of the first suggested remedies is often to run a disk check with CHKDSK or SFC. I have already ran SFC long ago, and done all the servicing commands as prescribed by other people on different web forums. None of that helped. If anything, it helped "fix" some minor filesystem issues (as intended) but did not fix the underlying Windows registry corruption.
What's done is done. A filesystem corruption that causes Windows registry corruption would have to be fixed ahead of time, before propagating to a registry corruption to serve as a fix for the same (it's amusing to think that by running SFC you can achieve a Widows registry repair, but many users online seem to be under that impression).
- DeletedJun 16, 2021https://techcommunity.microsoft.com/t5/windows-it-pro-blog/windows-recovery-environment-explained/ba-p/2273533
Please read this again.- SamirGunicJun 16, 2021Brass Contributor
Can I use WinRE on the same computer to load and unload the SYSTEM hive? As opposed to removing my M.2 disk and placing it in a second computer, this would be much more convenient.
Windows Recovery Environment explained - Microsoft Tech Community
The author writes:
Yes, you can use regedit within Windows RE, but warning: this is a powerful tool that can really mess things up if not used correctly! Keep in mind the X:\ drive is the WinRE OS and has its own registry. C:\ is likely where the Windows 10 registry is.So this seems like a good way forward that doesn't require me to remove the disk.
As for the labeling of recovery partitions he writes:
The WinRE partition can have any volume label or no label, but the most common labels are WinRE tools, WinRE, or Recovery. The label is subject to change upon update. The status could also say OEM Partition or Recovery Partition.So it sure looks like I have two of these recovery partitions for some reason. One with a label, and one without a label. In my experience, Windows tends to create a second recovery partition or move the existing partition to the end of the disk address space (for some reason). It's a really strange behavior I have been witness to in later years with Windows 10 across several computers in regard to these mythical recovery partitions. Well, at least now I know a label-less recovery partition is a real thing not to be surprised about.
- DeletedJun 16, 2021Well, and you tried scanning Defender offline?
- SamirGunicJun 16, 2021Brass ContributorYou mean Windows Defender (a.k.a. Microsoft Defender)? No, I have not.