This answer applied only to windows - if you are using Unix you would need to use different commands
After quick search in launcher logs you would notice this:
12:45:23 dgr Thread-2 info Initializing No Sound
12:45:23 dgr Thread-2 info (Silent Mode)
12:45:23 dgr Thread-2 info OpenAL initialized.
This is mostly caused by OpenAL loading error. Detailed error would be shown in actual game logs witch should be included in such situtations.
But why this happens ? OpenAL could error while loading due to multiple issues:
- Mojang shipped wrong OpenAL library - they did it in past, they could do it now.
- Mismatch between in java version that are used by game or launcher - launcher downloads binaries based on its java, not one that is used to start-up game ( Depends on launcher version - Notch's old launcher uses same java instance to launch game )
- Another OpenAL.dll library somewhere in java's libpath. This case is pretty rare but can happen with some software that uses java "in wrong way"
First case isn't applicable for you as sound does work with
java.exe , but doesn't with
As for second one - you reinstalling java doesn't do much! Your old version is still there and it could be defined in %PATH%! This is why
where.exe comes in play:
- Open up any command prompt that you like.
- Type in
where.exe java and
.exe part is required if you are using PowerShell!
- Compare output of both commands - it should be semi-equal
Also including game logs could help finding issue as there are many more OpenAL errors that can happen.