This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Windows 10 no sound for 2nd user to log in

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by rob-j

rob-j
rob-j
more options

User 1 logs in to Windows, runs Firefox, does not log out, locks Windows. User 2 logs in to Windows. Windows sound does not work in ANY application *except* for the sample played when changing the volume. No sound is available through the HDMI port, or the onboard sound chip. User 1 unlocks session and closes Firefox, then locks again. User 2 unlocks session and sound is working normally on all devices and applications.

This scenario happens regularly but not all the time. I believe Firefox is using hardware acceleration and might not be releasing its sound resources.

Latest Windows 10 version updated the Realtek driver, but the driver only affects the Realtek outputs, not HDMI which is also affected.

User 1 logs in to Windows, runs Firefox, does not log out, locks Windows. User 2 logs in to Windows. Windows sound does not work in ANY application *except* for the sample played when changing the volume. No sound is available through the HDMI port, or the onboard sound chip. User 1 unlocks session and closes Firefox, then locks again. User 2 unlocks session and sound is working normally on all devices and applications. This scenario happens regularly but not all the time. I believe Firefox is using hardware acceleration and might not be releasing its sound resources. Latest Windows 10 version updated the Realtek driver, but the driver only affects the Realtek outputs, not HDMI which is also affected.

Chosen solution

Thanks, yes it's definitely hardware related, and it's possible with software (e.g. a web browser that plays sounds) to control the hardware. It may be coincidence that Firefox happens to be the trigger, so will close it. Life's too short.

Your answer is not clear in a couple of places: 1. browser is software, not sure what 'software issue isn't a Browser problem' means. 2. Rebooting Windows (in any mode) automatically fixes the problem 100% of the time.

I believe it's possible when the PC wakes from sleep, Firefox might be locking a device in a disconnected session - of course it could be the OS and Firefox is doing nothing wrong - closing Firefox in the other session solves it, but I'm not getting many opportunities to prove it or try other solutions.

Therefore the issue is closed.

Update: Problem is with Windows 10's latest update, not Firefox. Just switching from one user profile to another solves the problem, Firefox involvement was just a coincidence.

Read this answer in context 👍 0

All Replies (2)

WestEnd
WestEnd
more options

Sounds hardware or software issue isn't a Browser problem but software install or corruption. Did you boot Windows into "Safe mode with Networking" to verify the problem wasn't the O/S itself? When there is no sounds that is hardware issue or software driver problem.

rob-j
rob-j Question owner
more options

Chosen Solution

Thanks, yes it's definitely hardware related, and it's possible with software (e.g. a web browser that plays sounds) to control the hardware. It may be coincidence that Firefox happens to be the trigger, so will close it. Life's too short.

Your answer is not clear in a couple of places: 1. browser is software, not sure what 'software issue isn't a Browser problem' means. 2. Rebooting Windows (in any mode) automatically fixes the problem 100% of the time.

I believe it's possible when the PC wakes from sleep, Firefox might be locking a device in a disconnected session - of course it could be the OS and Firefox is doing nothing wrong - closing Firefox in the other session solves it, but I'm not getting many opportunities to prove it or try other solutions.

Therefore the issue is closed.

Update: Problem is with Windows 10's latest update, not Firefox. Just switching from one user profile to another solves the problem, Firefox involvement was just a coincidence.

Modified by rob-j