I discovered today that version 3.0.1 was released, however there's no details on this version. I've tested it on some systems, but the problem persists.

https://www.dell.com/support/article/us/en/19/sln311129/dell-command-update?lang=en

You should be using version 4 and later for 10.  CCTK is now Dell Command. Dell Command and Configure (DCC, Formerly Client Configuration Toolkit CCTK) & Skylake systems

Dell Command | Configure 4.0 later is for platforms supporting WMI-ACPI BIOS (WINDOWS 10 UEFI)

View the complete list of the Newer and the Older Nomenclature Knowledged Base

Version 4.2 is the 2019 version of Dell Command | Configure.

There is support for this but its not free.

https://www.dell.com/learn/us/en/555/services/support-services-prosupport

Dell ProSupport. Proactive automated detection and alerts on critical issues with Dell SupportAssist technology* 24x7 direct access to highly trained engineers. Same or next business day onsite* repair after remote diagnosis.  Incident-based third-party software assistance*

• Windows download (Released - 04/09/2019)
• Linux downloads (Released - 04/09/2019)
  • RHEL7 64 bit
  • Ubuntu Desktop 16.04 64 bit
  • Ubuntu Desktop 18.04 64 bit
  • Ubuntu Server 18.04 64 bit
• Documentation
• Error Codes

My post is regarding Command Update, not Command Configure. There hasn't been a new version for a year now.

https://www.dell.com/support/article/us/en/04/sln311129/dell-command-update?lang=en

Dell Command | Update replaces DCSU and is a part of the Dell Client Command Suite

https://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverid=y2kwd

Add awareness of Dell Command | Update 3.0 architecture. Windows 10 64-Bit LTSC 2019 required

https://downloads.dell.com/FOLDER05312739M/1/Dell-Command-Update_Y2KWD_WIN_3.0.1_A00.EXE

This UWP package provides the Dell Command | Update Application and is supported on OptiPlex, Venue Pro Tablet, Precision, XPS Notebook and Latitude models that are running the following Windows operating system: Windows 10 Version 1607 (RS1 Build 14393) systems or later.

If your system does not support windows 10 this will not work.

As noted in my original post, we are running Windows 10 1703 (now 1809).

We discovered the root cause to this issue and are now using a workaround. For organizations that use a Powershell Execution Policy that requires Powershell scripts to be signed (i.e. "Allsigned") DCU will not work. To workaround the issue we temporarily change the Powershell Execution Policy registry value to "Bypass".

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\PowerShell\ExecutionPolicy

We attempted to automate the process using a script to change the registry value and then launch DCU, but were unsuccessful in getting the app to launch. Reference: https://www.mrlacey.com/2017/01/launch-store-installed-app-from-command.html 

Having to change the registry value manually before we use the product is not ideal, but at least it works now.

This issue seems to have persisted into 3.1 with the CLI feature and it's causing havok in our environment, did you ever discover a workaround that may encompass the CLI method? I've got 3020s on old BIOS versions that SHOULD be on A20 but DCU is reporting there are "No updates Available. Exit Code 500"

Dell Command | Update 3.1 (released November 2019)

There are two downloads available for Dell Command | Update:

• Universal Windows Platform version supported only on Windows 10 Redstone 1 v1607, build 14393 or above for 64-bit operating system

• Windows 32 and 64-bit version for Microsoft Windows 7, 8, 8.1 and 10

Version 3.1.1 is out.

https://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverid=ph01c&oscode=wt64a&produc...

https://dl.dell.com/FOLDER06095696M/1/Dell-Command-Update-Win-32_PH01C_WIN_3.1.1_A00.EXE

Did anyone ever find a solution for this?  We are using v3.1.3 and it is not finding updates for some of our Optiplex systems.