How to fix the no sound issue in Windows 10

23/05/2019 00:30 By Lhyam

Does the sound disappear and then strangely come back normal after a system restart?

I have been seeing this issue crop up a few times now where for no apparent reason, Windows 10 seems to lose all sound. Strangely, in some occasions it comes back if you manually restart the computer.
So what's going on?

It seems Windows is not loading the sound drivers correctly as it resumes, even if you are just starting the system up, but it is forced to do this when you restart the system completely. From what I have noticed, the problem appears to be related to the Windows Fast Start-up Option.

This is a feature that is included in both Windows 8 and Windows 10. It saves your computer a few seconds when starting up by creating a hibernation file, saving information about your system drivers and state. When you turn the system back on, Windows can boot a little bit quicker by not having to load these drivers again by simply using the information it saved previously. Instead, it just refreshes the memory but loads the previous state.

By disabling this setting, you force Windows to load all the system drivers, including the sound driver, on each boot thereby hopefully resolving the issue for good.

It does mean waiting a few extra seconds at start-up though… but that is a trade-off I would consider worthwhile if it means getting sound first time without having to restart always. Hopefully Microsoft will release a fix soon enough to resolve this problem.

Solution: Disable Fast Start-up Option

To do this:

  • Open your Start menu and choose Settings
  • Click in to System and from the left menu, choose Power & sleep
  • Click on Additional power settings
  • A new window will appear and from the left menu, click Choose what the power buttons do
  • Click the option at the top for Change settings that are currently unavailable
  • Uncheck the box Turn on fast startup (recommended)
  • Click Save changes

That should be it

Now, all that is left is to shutdown your system, turn it back on and try it out. Let me know if this helped you. Or perhaps you have found another solution and would like to share it with others in the comments?