KB4023057 was just pushed again yesterday or today which is meant to pave the way for those stuck on 1909 build but it still doesn't offer 2004 build for me so I think I must still be held up by the Conexant driver issue.
This update keeps failing for me, with ESET constantly reminding me that my system needs critical Windows Updates installing.KB4023057 was just pushed again yesterday or today which is meant to pave the way for those stuck on 1909 build but it still doesn't offer 2004 build for me so I think I must still be held up by the Conexant driver issue.
KB4023057 was just pushed again yesterday or today which is meant to pave the way for those stuck on 1909 build but it still doesn't offer 2004 build for me so I think I must still be held up by the Conexant driver issue.
Shouldn't be long before 20H2 is released. 13th of October I believe.![]()
Shouldn't be long before 20H2 is released. 13th of October I believe.![]()
I think we've been forgotten!But will it include us Conexant outcasts!
if you check for updates it probably appears as an install now update.Still on 1909. My update screen doesn't mention any other update nor tell me that I'm not compatible. Do all versions of Windows update to new versions or are some manual only?
Got fed up waiting - used the Microsoft "Windows update assistant". Only 1 pc had updated.
With the update assistant 2 Intel home-builts (i920, i5) updated; Asus Eee slowly updated. Not tried the Lenovo laptop yet as that has a Conexant sound driver which frequently causes blue screens and is not always easily recoverable from.
So that is 4 out of 5 on 20H2 and 1/5 on 1909 - blocked by Microsoft from going to 2004 because of sound driver.
Mel