Sulfur spikes don't have sounds

Thank you for helping us improve Minecraft! We saved your files:

Does this issue require any additional setup that is not listed in the description? I was unable to reproduce the issue myself in snapshot 6, as all the correct audio played.

No, this issue doesn’t require any additional setup, I just normally started 26.2 Snapshot 6. However, these lines appear in the logs when starting the game:

[15:36:33] [Render thread] [net.minecraft.client.sounds.SoundEngine/WARN]: Missing sound for event: minecraft:block.sulfur_spike.break
[15:36:33] [Render thread] [net.minecraft.client.sounds.SoundEngine/WARN]: Missing sound for event: minecraft:block.sulfur_spike.step
[15:36:33] [Render thread] [net.minecraft.client.sounds.SoundEngine/WARN]: Missing sound for event: minecraft:block.sulfur_spike.place
[15:36:33] [Render thread] [net.minecraft.client.sounds.SoundEngine/WARN]: Missing sound for event: minecraft:block.sulfur_spike.hit
[15:36:33] [Render thread] [net.minecraft.client.sounds.SoundEngine/WARN]: Missing sound for event: minecraft:block.sulfur_spike.fall
[15:36:33] [Render thread] [net.minecraft.client.sounds.SoundEngine/WARN]: Missing sound for event: minecraft:block.sulfur_spike.land
[15:36:33] [Render thread] [net.minecraft.client.sounds.SoundEngine/WARN]: Missing sound for event: minecraft:block.potent_sulfur.geyser_eruption
[15:36:33] [Render thread] [net.minecraft.client.sounds.SoundEngine/WARN]: Missing sound for event: minecraft:block.potent_sulfur.geyser_eruption_active

It appears your asset index has not updated properly. Are you using a modified launcher? Does this occur when using the official launcher?

_{This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.}

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

It seems it really was due to the launcher, even though I launched a vanilla instance. That definitely won't happen again, sorry. The issue can be closed now.