Windows 10: Errors or issues during or after updating devices with Conexant ISST audio drivers

Errors or issues during or after updating devices with Conexant ISST audio drivers
[COLOR=rgba23, 23, 23, 1]Devices with affected Conexant ISST audio drivers might receive an error or have issues with Windows 10, version 2004[/COLOR]


[COLOR=rgba23, 23, 23, 1]It's almost been a GD year, when is this going to be fixed? ...[/COLOR]

:)

 

Conexant ISST audio drivers uninstall after updates to Windows 10

Hi,

I have a 3 month old HP Spectre x360 that came with Windows 10. Every time there is an update which requires a restart (for Windows 10, iTunes or what have you), my audio drivers (Conexant ISST audio) are uninstalled. I have to manually go into Device Manager,
update driver, and choose from a driver installed on my computer to get the driver to work again (after yet another restart). I have tried uninstalling the driver and then restarting the computer, but this (like the device manager option) is only a temporary
fix. Every new update and restart uninstalls the audio drivers again. While the temporary fix has worked every time (so far) it is getting annoying and I would greatly appreciate some advice on a permanent fix.

 

MicTray64 keylogger issue fixed in latest Conexant ISST Audio drivers?

Does anyone know if the latest Conexant ISST Audio Driver, created 25 Jan 2019 and released by HP 12 Feb 2019 (as well as earlier updates) has REMOVED the accidental keylogger? I just bought a nice used HP Elitebook 840 G3 and downloaded the 12 Feb 2019 driver directly from HP (overwriting whatever was there) and checked that it Is in fact the one now shown in Device Manager, and installed today (Properties).

I checked C:\Users\Public\ and there is NO MicTray.log

Problem or not?

 

Conexant ISST audio drivers uninstall after updates to Windows 10

I got the same issue with the HP Elitepad 1030 G1.

Windows is up to date, as are all the softpaqs.

Every update, the audio drivers stop working (Connexant ISST 9.0.67.0)

Any update to this issue?