Okay, I should have said 'fixed', not 'resolved'. The people here are super bright at finding ways around this problem.
I still don't think that this will be 'properly fixed', i.e. a software change in the conexant driver. The driver now belongs to another company that probably doesn't want to invest time to fix old things. This was discovered in May and is still unresolved. It is listed as an issue with the 20H2 update as well. At some point MSFT will have to do something.