I have tracked down that the issue on my system is not the entire driver package, but one. I have had my Inspirion notebook for about four years, and never encountered a block before – much less for something as common as a sound driver from a mainstream provider used on 100s of thousands (if not more) systems. Not brand-spanking new, but these are not ancient drivers from 10 years ago. My Conexant drivers from Dell are dated March 2019. Respectfully, I disagree that Microsoft is ‘innocent’ in this issue. This reply was modified 1 year, 2 months ago by Alex5723. They didn’t because they don’t want to invest time and money. The hardware OEMs has enough beta testing time to test and update drivers. Microsoft hasn’t caused the incompatibly issues. If you insist on updating to 2004/20H2 Microsoft has a workaround by unblocking any blocks. if you cant fix it maybe find another job at McDonalds and leave your positions to other more skillful programmers that MS could hire.
They are working on a fix from May and it is December. Connexant, Synaptics and laptop makers are unacceptable for not supporting their products… but Microsoft caused this issue.
I have a Spectre laptop of 2017 and cant update. No new audio drivers are available from Dell, and talking with their support folks was sadly/predictable, not productive. In device manager, the device is listed as ‘Conexant SmartAudio HD.’ Via device manager, Windows says I have the best drivers for my system installed. I have considered trying to force the update via the online update tool/media creation tool … but also not necessarily looking to tempt fate with a BSOD.ĭoes anyone here have insights as to why this block has not been resolved since May? Any thoughts on how one might proceed? Looking at threads such as this > … it’s pretty clear I am not alone, but there is no word on a resolution.Īs I use the more advanced audio features the Dell has provided (INS 7353), I would rather not hack the block by installing generic drivers etc., but I am getting concerned I could run into a situation where my system will not be upgraded, ever … which does carry security and EOL issues. Well … I suspect the reason I have yet to be offered the update is some combination of these blocks:īoth these blocks show up in the notes for both 2004 and 20H2. Since July (or perhaps even earlier), Windows update has been warning/teasing me that the May Update is on the way, and will be downloaded when it’s ready for my system.
0 kommentar(er)
