Windows 10 Feature update (to 2004) Conexant driver Issue

My 2014 lenovo laptop has conexant audio, so guess I was unlucky

Yeah quite amusing, Conexant is not better, looks like a very horrible company, I will not buy anything with their components inside, that is for sure!

Conexant went out of business in 2014.

This post is a rant and it does not contain useful info, since the issue is just nit resolved

It has now been 6 months since the release, and even the October update is out, but still there is nothing from windows or synaptics, just “update is on the way!”. As a windows pc owner, i think that i shouldn’t be treated as a nobody cares about you customer, i don’t know on which side the issue is, Ms or synaptics, but i do think that a driver issue should have been resolved in 6 months. In 6 months you could have even written a driver from scratch. I am still on 1909, which is a year and 2 months old now. And i cant update. ( well technically i can but but Ms says that i shouldn’t because of the driver issue.) 

This post is indeed a rant toward those who (MS, Synaptics, and device manufacturers) are responsible and have the resources to solve the issue but somehow chose not to. Initially, this post was made in a desperate move to draw some attention to the ones that are responsible, knowing well that this is not a place to ask for solutions from MS. This is just a discussion among the sufferer and sharing their experiences and possible workaround of the problem.

Before even making this post, I directly contacted MS support staff asking what is MS doing resolving the issue and found out that MS is not feeling responsible when it comes to fixing this issue. 

I totally understand the sheer frustration of being the sufferer or should I say "Victim of such negligence", as I happened to go through the same exact situation only to take matters into my own hand rather than waiting for it to be resolved and eventually succeeding.

Although it's unfortunate enough and not the way to solving such an issue, it seems acting on your own and trying to find a workaround for the issue is the only way right now given how long it has been left unsolved.

I tried to update and it halted me - even thoug my driver is from June 2020.

Thanks for the suggestion. This does not show up for me on the HP Updater, Window update or Intel's update service. My driver shows June 6, 2020 which is after the issue was reported with 2020 04 Update, but still won't work with that or the current 2020 H2 update.