Anyone know why the self-installing format ( .exe ) version dont have audio driver ( IntcDAud.inf ) and the manual installation format ( .zip ) yes?
Thank you for joining this community.
I understand that you noticed that the latest Intel® Graphics Driver for Windows® 10 (Version: 188.8.131.5236)
Based on the release notes of the Driver, the content of both packages .exe and.zip are:
Intel® Graphics Driver
Intel® Display Audio Driver (10.25.00.8)
Intel® Media SDK Runtime
Intel® OpenCL* Driver
Intel® Graphics Control Panel
Vulkan* Runtime Installer (184.108.40.206
As you can see both files share the latest Intel® Display Audio Driver (10.25.00.8), however; these may appear with different names or containers, as one will be an executable file and the other a compressed file.
You can check the release notes of the driver here:
We are pretty interested in your post, so please tell us how you determined that the format .exe does not have the audio driver named IntcDAud.inf?
I hope to hear from you soon.
After running win64_220.127.116.1136.exe, the video driver was installed correctly, but the audio driver did not. I had to install it manually looking for the dirver in the file win64_18.104.22.16836.zip
You can use programs like https://rarlab.com/ WinRAR to see the contents of the EXE file, inside the Graphics folder, you will only find the igdlh64.inf driver, when in the ZIP version, inside the same folder it will be find both igdlh64.inf and IntcDAud.inf.
You can also see inside the contents of the previous version win64_22.214.171.12494.exe and you will see that both drivers are inside the Graphics folder.
Thank you for your response, we really appreciate it.
All the information provided by you is extremely helpful.
We are currently performing further research regarding the issue that you exposed to us.
This may cause a brief delay in our answers; however we will contact you back as soon as we have an answer.
I hope this helps.
Thank you for your patience.
We reported your feedback and took actions regarding the missing driver that you exposed through your thread.
Pease take a look to the new Driver Version that we released back in 7/11/18:
Hope this helps, please let us know if you have any other question or concern.
We just wanted to double check if you still need further assistance.
Please do not hesitate on contacting us back.