If you’re still running Windows 10 1909, you’re probably receiving a notification that your OS is about to reach the end of its life. Many are confused by the message because the Windows 10 platform is not losing support; instead, the feature release for Windows 10 Professional will be more than likely closing in May.

Windows message out of dateMicrosoft

Windows 10 out of date?

First, check the Windows 10 feature release version you have. Click on Start, Settings, System, scroll down to the bottom, and choose About. If you scroll down to the Windows specifications section, you can see what version of Windows 10 you use. If it shows version 1909, you need to investigate why your machine has not yet received Windows 10 2004 or 20H1.

If you go to Start, Settings, Update and Security, Windows Update — and it indicates your system is still not ready for Windows 10 2004 — you may need to investigate why 2004 (or 20H2) isn’t being installed.

We already know one reason 1909 can’t get 20H2: the infamous Conexant audio driver problem. Windows 10 computers affected by this known issue come with Conexant ISST Audio or Conexant HDAudio drivers (shown under “Sound, video and game controllers” in Device Manager). The blocking drivers have numbered filenames from uci64a96.dll through uci64a231.dll and a file version of 7.231.3.0 or lower.

For some systems, Conexant has offered up the updated driver and the system can install 20H2; for others, the new drivers haven’t been released. For these systems, you need to type “device manager” in the search box. Scroll down to the Sound, video and Game controller section and click on the Conexant audio. Now right-mouse click and uninstall the audio driver. Go to the Windows 10 software download location and click on Update now. Once 20H2 is installed, it will find the Conexant audio driver again and complete the update.

Win 10 2004 blockMicrosoft

Windows 10 2004 blocked.

But what if you don’t have a Conexant audio driver — how can you determine the problem? With Windows 10 2004, you can use Setupdiag. Download the tool and run it by double-clicking the SetupDiag file. By reviewing the resulting log files, you may be able to decipher the blocking condition. (If you downloaded the setupdiag file to run, the log files will be in the download folder.)

Copyright © 2021 IDG Communications, Inc.