Solved Realtek Audio Manager not opening

[JtLK]

Thanks to these forums I got the drivers up to date (realtek HD audio driver) and finally the Realtek Audio Manager appeared on the control panel.
I thought my problem was solved but when I click that shortcut it runs RtHDVCpl.exe but the manager doesn't open.
The process is running but no window opens.

Any idea why that's happening?
Or how I can access the darn thing?

I'm afraid I've gone as far as my searching ability can take me

 

[Yard Dog]

Hello, are you using an Admin account ? If so, make a new one and try that one , also, are you right clicking it ?

 

[JtLK]

Only have one user account on my pc, I think it counts as an admin account since I can run things as admin and acess pretty much anything on the pc

Figured it out
Kind of weird
The process that shortcut runs is the file RtHDVCpl.exe in the Windows folder (clicked open file location in the task manager). And that file was an outdated one, replaced it with the new file from C:\Program Files\Realtek\Audio\HDA and it works now

Now I just have to deal with the crushing despair from finding out the Realtek Audio Manager doesn't see anything but the HDMI output, guess it's more google on that.

Guess I should mark this as solved

 

[Yard Dog]

Well, glad you figured this out , strange that your file was outdated tho . As far as the rest of the issue, it is a matter of opening the Sound Manager and peeking around in there. Good luck .

 

[JtLK]

Quite strange indeed. You'd think the new driver would overwrite it.

As for the rest of my issue it was a matter of going into the setup and setting the onboard audio something to "Enable" instead of "Auto".
My new graphic card was responsible for setting it to HDMI only, with Enable on all other options popped back on the Audio Manager.
My dad figured it out, handy to have a family member with a background in electronics. Guess I really should know more about the setup options though, even if it's outside of civil engineering.

 

[Yard Dog]

Ahhh, okay, yeah, that makes sense, thanks for posting that, as not all users have the hardware for that driver , so, if this pops up again, other users will see what was done to sort it out.