Then you can generate a PNP file (containing information on your installed devices) for Microsoft developer team and attach it to your e-mail.ġ- run the command prompt in administrator mode.Ģ- type: pnputil.exe /export-pnpstate myfile.pnp /force (the export process can take a minute).ģ- get back the pnp file (that should be created in the current directory) to attach it to your e-mail (might be zipped first)ĭirect Email: Microsoft Report Procedure explained by Matthew van Eerde: You may report the problem to Microsoft with the title: "Windows Update cannot re-install non-PNP Audio driver correctly" and precise your specific problem in the body: something like: "after WIN10 update sound is not stable anymore" or "impossible to select a given device " or "this device does not work anymore".
THIS PROBLEM IS EXPECTED TO HAVE BEEN FIXED WITH WINDOWS BUILD 19500 (to be validated). The problem is there since VISTA, this is why we ask to our users to REBOOT after installation and REBOOT after de-installation - to let the system finalize the process correctly) but WIN10/11 automatic update, can re-install audio driver at once, and create a complete mess in the audio stack. The driver installation procedure is not using the driver Hardware ID as unique identifier in the installation process, and consequently is merging driver properties and pins with possible previous installed drivers (USB devices are not impacted). The problem has been recently fully identified: Windows Update is not able to re-install NON-PNP Audio Drivers correctly (since 1998 - by design). We talk about this audio driver installation problem with Microsoft guys since years: our last discussion about this. In fact all the audio stack can be impacted by a WIN10 update and make you PC totally unusable from a day to another. In some cases, WIN10 or WIN11 update can bring some problems and disturb audio driver installation.
0 kommentar(er)
