Audio always zeros down, no fix found / Audio resettet sich immer auf 0

[RPWolf]

Hi,
[in German down below)
I rly hope you can help me. My notebook is the HP Envy X360 13ag0001ng.
The issue:
My audio volume is always zeroing down. The speakers do work. I can pull the volume bar up, but it goes straight back to zero. The audio works perfectly fine in the HP audio test (before BIOS and OS).
So the error occurs only after the BIOS.
The notebooks also freezes sometimes.

What I have tried so far:
-reset Windows 10
-secure boot
-format drive and reinstall Windows
-installing Linux Ubuntu
-deactivated FN-keys
-BIOS update
-different drivers (Windows and HP homepage)

I am out of ideas, but I haven't opened it up yet.

/
Ich hoffe, ihr könnt mir helfen, ich weiß nicht mehr weiter.
Ich habe ein HP Envy X360 13ag0001ng.
Das Problem:
Der Sound geht immer auf 0 zurück. Ich kann dagegenhalten und es kommt auch ton raus, aber der Balken geht immer wieder auf Null zurück.
In der HP Systemsoftware und im BIOS geht alles. Erst beim Laden eines Betriebssystem tritt der Fehler auf. 
Das Gerät stürzt auch teilweise nach wenigen Minuten ab.

Was ich bisher probiert habe:
-Windows zurücksetzen
-abgesicherter Modus 
-Windows komplett neu aufsetzen
-Linux Ubuntu installieren
-Versch. Treiberversionen installieren (wd Windows)

-BIOS-Update
-FN-Keys aus

Ich weiß wirklich nicht mehr weiter.

[The_Fossette]

@RPWolf

I reviewed your post and I understand that you are facing issues with the audio on the computer.

Don’t worry, I assure you I will try my best to get this sorted.

What is the Windows version you are using?

I recommend you download and install the audio driver from the below link and check whether the issue is resolved.

https://ftp.hp.com/pub/softpaq/sp110001-110500/sp110379.exe

Let me know how it goes and you have a great day!

P.S: Welcome to the HP Support Community 😊

If you wish to show appreciation for my efforts, mark my post as Accept as Solution. Your feedback counts!

Cheers!

Stay Home – Stay Safe

[RPWolf]

I have tried both Windows 10 20H2 and 2004 each two times.

For some reason the second installation of 2004 has fixed it just now.
I dont know how.

But thanks for your help. I will leave this thread open until this weekend in case the issue occurs again.

[The_Fossette]

@RPWolf

Perfect, I am really glad to hear that!

If any other questions arise, please feel free to write back to me.

Cheers!