05-25-2024 09:54 PM - edited 06-29-2024 08:24 PM
Dear Support,
CURRENT STATUS WITH ALL ISSUES IS IN
I am owner of ASUS ROG MAXIMUS Z790 DARK HERO motherboard. I have the latest v6.3.9600.2368 drivers installed. I have been having the following issues with this driver:
@Echo Install Realtek Audio Driver Please Wait ...
@Echo on
@Echo dism online install DTS Sound Unbound appx files
%~d0
cd %~dp0
REG ADD "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell" /f /v "ExecutionPolicy" /d "RemoteSigned" /t REG_SZ
powershell -executionpolicy bypass -File .\remove_and_install_DTSSUWP.ps1
REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell" /v "ExecutionPolicy" /f
@Ping 127.0.0.1 -n 12 -w 1000 > nul
dism.exe /online /Add-ProvisionedAppxPackage /PackagePath:"77ebcb3cc75d4261bade64b63bb84bf9.appxbundle" /LicensePath:"77ebcb3cc75d4261bade64b63bb84bf9_License1.xml" /DependencyPackagePath:"Microsoft.NET.Native.Framework.2.2_2.2.29512.0_x64__8wekyb3d8bbwe.appx" /DependencyPackagePath:"Microsoft.NET.Native.Runtime.2.2_2.2.28604.0_x64__8wekyb3d8bbwe.appx" /DependencyPackagePath:"Microsoft.VCLibs.140.00_14.0.30704.0_x64__8wekyb3d8bbwe.appx"
@Ping 127.0.0.1 -n 12 -w 1000 > nul
cd ..
@Echo Done
exit /b
BONGIOVI DRIVER ISSUES
I am sure by now you would have seen numerous people complaining about loud pops with these APOs which is why I have tried to uninstall them. They are not easy to uninstall also.
-Amit
Tagging #ROG, #Motherboard, #Z790, #Z790 Dark Hero
05-27-2024 07:12 PM
REGARDING TOPIC No. 7 (quote for quick reference)
The officially published driver on the ASUS Support downloads has couple of mistakes or issues.
What type of recording or screenshots do you need? I already shared the issue. The problem here is that DTS SoundUnbound App is NOT installed and the Realtek Audio Control App is NOT PINNED to the Start Menu. Here is my attempt to show you the original vs fix.
I have already shared the fixed install.bat file in my very first post. See the file difference between the original vs the fixed installer. LEFT side is original. RIGHT side is fixed. This can be seen the screenshot of the folder names being compared towards the top.
This screenshot shows the missing file that has to be manually copied. I have highlighted the RUN folder on the LEFT which is missing the file shown in PURPLE on right that I copied. There are couple of copies of this file in the ZIP file. Since they are all the same it does not matter which one gets copied to this RUN folder.
Here' the fixed install.bat file which is shown in RED. I have already provided this fixed install file as text in my first post for anyone else to easy copy around.
On the LEFT is the original. Here you can see that the DTS SoundUnound App is first installed on line no 8. Then on line no 13 it is being removed. It is best to remove any installation first and then do a fresh install. Which is what I have changed on the right side. I added the delays assuming that is what is needed and how your development and QA team in ASUS is building these installers. This worked for me.
05-27-2024 08:03 PM - edited 05-27-2024 08:08 PM
REGARDING Bongiovi APO Drivers (Refer to Topic No 4 above, part a that talks about installation problems with getting these drivers installed correctly)
Multiple posts on this forum about Bongiovi drivers causing issues. Some of which have been solved other resulted towards uninstalling these drivers.
First, I also uninstalled these drivers using the following commands with "Command Prompt" running as administrator.
%windir%/system32/pnputil /delete-driver %_OEMFILE% /uninstall /force
I run the above command TWICE to remove both the INF files installed. For details, please see Re: ROG Maximus Z790 Dark Hero Low Microphone Volu... - Republic of Gamers Forum - 1019225 (asus.com...
When I uninstalled these drivers, while the driver files were deleted, not everything about Bongiovi got removed as it left behind files (see Solved: Re: Bongiovi Acoustics/audio enhancements causes p... - Page 10 - Republic of Gamers Forum -...)
In my constant attempt to find a proper uninstaller, I was finally able to figure out that the MbLedSDK version 3.0.25 file contains the installation of these drivers. I uninstalled Armoury Crate (which has now left my Armoury Crate to get into a constant spinner with loading; so a new problem has shown up), I was able to use debugging tools to find the following:
Here's the defect. I still don't understand what causes it. The files copied to "C:\Program Files\BongioviMBApp" folder are for some reason X86 versions and not the X64 version of the files. Somehow, the Bongiovi SDK file copied to "C:\Windows\System32\Bongiovi\MB" folder is the correct X64 version that goes with the INF files. Since the files in the application folder at "C:\Program Files\BongioviMBApp" are the wrong X86 version, the Windows Startup Application named "RoutingService" is now running with X86 version. I believe it loads the wrong X86 versions of the files including the X86 version of the SDK. This X86 version is not able to work with the X64 version of the BongioviAPO.dll from the Windows System folder at "C:\Windows\System32\Bongiovi\MB" which got correctly installed.
So, my theory is that the installer mixed up things on this motherboard as part of the MbLedSDK version 3.00.25 and this is causing all sorts of issues for people.
To show these wrong versions, here's a screenshot.
This first screenshot is showing on LEFT the folder I dumped and backed up after a fresh clean install. The RIGHT side is the dump of files used by the installer inside the MbLedSDK v3.00.25. As you can see everything is matching to the X86 version except APO dll which is shown in RED.
Here's another screenshot showing LEFT side with files installed by the installer and RIGHT side now using X64 versions.
Everything is now RED and nothing is matching as expected since they all matched to the X86 versions.
NOTE: I have not shared these installer files because I am not sure if my analysis is correct. I am still testing things out but installing the correct files have definitely starting to solve few problems for me i.e. my Microphone Volume is now normal rather than being extremely low.
REQUEST TO ASUS DEVELOPMENT TEAM
I love the fact that you are now using Windows Batch files and Powershell scripts. This helps people like me in the community to solve the issues quickly together. Can you please make these installers accessible easily? There is no easy way to download and save Armoury Crate files. Can you please add an option to "Save and Download Only" but not install? Also, the MbLedSDK is a native InstallShield installer. This makes it really hard for armatures like me to extract and investigate what it is doing. Maybe you can think about converting this installer to script based installer because it took me 4 days just to figure out how I can get access to these files for simple comparison.
Lastly, the MbLedSDK does not perform force installation i.e. if I uninstall Armoury Crate, these Bongiovi stuff is not uninstalled. Similarly, when I reinstall, there is no reinstallation happening. What I have observed is that the installer checks something in the registry or some file that is left behind by the Armoury Crate and does not even attempt to run the Bongiovi Installation again. Only time it works is on a fresh installation of Windows 11.
05-28-2024 02:33 AM
Hello, @achugh
Thank you for providing comprehensive information and corresponding explanations.
I have compiled the seven questions and related discussions and submitted them to the relevant team, and I believe that you would understand that verifying these issues may take some time.
If there are any responses or further inquiries to confirm, I will update this thread promptly.
Kindly feel free to supplement any additional information to this discussion at any time as well.
Thank you in advance for your patience.
05-28-2024 06:33 PM
Hi @Jiaszzz_ROG ,
I understand it will take time for the team to look into these issues and request. In order to troubleshoot and find the installation issue with MbLedSDK v3.00.25 I tried to uninstall and reinstall Armoury Crate. While that did not help as the installation does not uninstall or perform a force installation of Bongiovi Drivers, I created a new problem that now my Armoury Crate Motherboard device is no longer showing. It simply shows LOADING message. I have uninstalled and reinstalled Armoury Crate multiple times but have not figured out what is failing.
Can you please suggest what should I do at this time short of formatting Windows all over and starting fresh?
-Amit
06-05-2024 02:41 AM
Hello, @achugh
Apologies for the delayed response.
We have investigated the first issue you raised:
Our relevant department confirmed that after installing the official website drivers, there is a noticeable change in the Amplify level when adjusted in the Realtek Audio Console UWP, as shown in the link provided.
***Due to the unclear audio changes in the video, additional recordings were made.
Through screenshots of the recorded audio signal, you can observe the sound changes, contrary to what you described as ineffective.
If you are still experiencing this issue, we recommend recording a video of the complete installation and testing steps for further analysis.
Regarding the loading circle in the Armoury Crate, is this something that has been happening consistently since installation, and if you reboot the system and wait for a while (for example, half an hour or an hour), does it still spin without accessing the interface?
Could you please provide screenshots or more detailed descriptions of the situation, such as where you downloaded the Armoury Crate from and what version you installed?
You may also consider testing it on a fresh or restored system configuration.
Thank you.
06-02-2024 10:05 PM
I returned to the default driver of ASUS I did not use those of the forum, the Z790 has behavioral problems, while Antens used the Z790hero with the driver of the forum everything was going very well.
Podrías experimentar esto en tu configuración, si usas salida óptica, solo busca un video con un sonido codificado o una película de alta calidad ya que vienen con sonidos codificados, y si la cosa te pasa como el video que comparto el problema va Be at the Board Z790 Dark Hero. Viene con problemas de firma.
06-05-2024 10:24 AM
Hi @Jiaszzz_ROG thank for you sharing this update. I downloaded the file from your development team and did hear a difference like it is shown in the waveform as well.
I believe the test done by your team is not the same as my problem. My understanding is the ASUS team tested the sound connecting an external speaker and then recording the sound using a different device like a phone or another computer to show the volume difference. I would love to know where did the ASUS team connect these speakers? To the Front Panel connector or the REAR PANEL connector? If it is the REAR PANEL, which COLOR connector was used for sound output to the speaker?
To reproduce my issue, the ASUS team would need to connect a HEADSET in the front panel connector. As a reminder, a header is the used for phones which comes with a headphone a microphone all in one device and has a 3 PIN connector that goes properly into the ASUS PROART PA602 front panel audio connector on the case.
Because I am listening on the headset, I get NO CHANGE in volume using the AMPLIFY LEVEL at all. Can your team confirm that the volume changes are not observed when using headset? FYI, I also have the DTS SoundUnbound app installed and activated in case DTS Headphone portion of the audio chain is breaking this setting? Here's how the Windows SOUND SETTINGS look like for me at the moment.
I have tried everything including the official 6.3.9600.2368 version of the drivers and there is no difference in the headset volume. I have even tried to disable spatial sound OFF to disable DTS and that does not help. In fact as @Warryor3D reported above, spatial sounds are not making a difference at all. Now changing the headset I am using inside the DTS SoundUnbound App does make a difference in the sound profile i.e. it affects the way low frequencies in DTS SoundUnbound test clip sound. So I can confirm that DTS SoundUnbound is able to change and affect the sound however, Realtek console is not able to make any changes.
Since there are no audible changes observed in the headset, I am not sure what exactly is needed by your team. If you can get me specifics, I would be more than happy to comply and provide the needed information.
06-05-2024 11:17 AM
Hi @Jiaszzz_ROG I also wanted to share that I have completely formatted my Windows machine (not reinstalled keeping original files but actually formatting the drive losing every file on the drive and doing a proper fresh install). When I did the most recent fresh installed I used the Windows 11 Pro 23H2 ISO file while staying 100% disconnected from the network. Here are my findings from this fully clean install:
I disabled Armourmy Crate and MyASUS installation in BIOS so that when the Windows installation is finished, nothing is injected into Windows and I can start fully fresh.
Why do I care about this microphone loud pop and low volume?
I cannot game at all since the microphone sends these loud pops only. Other than the pops, no one is able to hear me at all hence I am looking for a solution instead of spending for another USB Audio hardware when my premium motherboard already should be able to do bare minimum needs of basic audio in today's world.
06-05-2024 01:37 PM
Hi @Jiaszzz_ROG , I can also confirm that if I simply plug in my headset into the REAR GREEN connector labeled "Front Speaker Out" then the AMPLIFY LEVEL is working. See screenshot of Realtek Audio Control showing in WHITE where I plugged in my headset below. The unused connectors are showing in GREY color including the Front Panel as there is nothing connected in this test.
In this configuration of using a REAR OUT (FRONT SPEAKER OUT) connector with the following Speaker Configuration of STEREO, I can confirm the AMPLIFY LEVEL does work which like I said in my previous post is NOT my setup. I am trying to use HEADPHONES from the front panel where this AMPLIFY LEVEL is not working.
Here you can also notice that the LEFT side of the MENU shows SPEAKERS (SELECTED AND HIGHTED WITH RED BAR IN THE MENU AREA) and NO MICROPHONE because I am using the REAR Speaker Out.
When I connect my headset to the Front Panel this same screen shows like below
If you notice above, the device has changed from SPEAKERS to HEADPHONES and Microphone has also shown up as a device. In this configuration, the AMPLIFY LEVEL does nothing or does not work.
Now my device information is shown below. See FRONT PANEL GREEN connector is highlighted in WHITE color and everything else is shown in GREY color. I have selected MIC IN as the input level for my microphone for my headset when windows notification pops up asking what type of device have I connected to the front panel connector.
I believe the Realtek Drivers have the DEVICE routing messed up for HEADPHONE device. I am referring to RtDUsbAD_asus.inf and ExtRtXUsb_Asus_BJ_RTK.inf file which I believe has the Windows configuration mistake causing Headphones to not work properly.
I do not understand Windows Device Driver development to exactly point out the mistake so this is my best guess that these two files require some adjustment.
NOTE: I have done this test on a freshly cleaned machine with no Armoury Crate or Bongiovi Drivers installed. Hence, this issue is in the BASE Realtek Driver package as I mentioned in my very first thread with all the issues in the base driver package that needs help.
REQUEST TO ASUS DEVELOPMENT TESTING TEAM
Can your team, attach the same speakers they connected in the rear to the front panel and confirm if they hear the volume increase? When they do connect the speakers in the front panel, please FIRST MAKE SURE in Realtek Audio Console the speaker is listed as HEADPHONE and not as a SPEAKER. The routing mistake is for the device type HEADPHONE.
Looking forward to the next update from your team.
06-07-2024 03:58 AM
How to get the Realtek audio control screen?
In my case, it is not shown, it is always damaged.