No audio following the PC upgrade or modification...
No audio following the PC upgrade or modification...
I completed two upgrades on both my PCs—partially. I’m holding off on new CPUs but have swapped the cases, changed the GPU, and done some maintenance. My PC is running smoothly, though it’s using an M.2 drive for the OS. My sister’s experience has been quite unpredictable. The hardware installation went well overall; even improved cable management helped. However, when I attempted to boot, I encountered a “boot disk not found” error—possibly because of misplaced SATA cables during the swap. I found a guide on MBR repair and managed to fix it after several tries.
Now, regarding the sound issue: my system is silent despite the volume icon showing an X. It seems the Windows Sound service wasn’t started, and even trying to launch it caused errors. After some research, I learned to set Windows Sound to “Local User” settings, which resolved the problem and let me see all playback devices. Plugging in headphones connected to the front panel audio worked, and switching the device detected it. But still no sound.
It might be a software issue, possibly linked to the SATA port swap or a corrupted Windows installation. I’ve tried reinstalling drivers, testing with different headphones, running Windows troubleshooter, disconnecting the HD audio header, and even reinstalling Windows itself. My sister doesn’t want me to do that.
I’m considering creating an Ubuntu USB drive to test if booting Ubuntu produces sound. If that fails, I might have to format or reinstall Windows. My PC specs include an Asrock B450 Steel Legend, Ryzen 3600, 64 GB RAM, RTX 3070, multiple SSDs and fans, Wi-Fi card—all functioning properly before the case and GPU changes.
All audio outputs function with Ubuntu, indicating the issue lies in the software rather than Windows.
Restarting the windows fixed the sound problems and other issues. It looks like some window conflicts were blocking files from being accessed by Windows, which resolved the matter. Probably there were internal window hiccups affecting file availability. All set!