🌐
Dell
dell.com › support › manuals › en-us › command-update › dcu_ug › update-history
Dell Command | Update Version 5.x User's Guide | Dell US
You can view the details of previously installed updates on the system in the Update History screen. The details include the update name, update type, date of the update was last installed, and the version of the update installed on the system.
🌐
Dell
dell.com › support › kbdoc › en-us › 000177325 › dell-command-update
Dell Command | Update | Dell US
May 27, 2026 - Note: To know which version is installed on the computer, go to Control Panel > Programs > Programs and Features: If Dell Command | Update Windows Universal Application is listed, then it is the Universal Windows Application (UWP) variant.
Discussions

Dell Command | Update - Archives?
Why do you want them? Many of these versions have various vulnerabilities that you won't want around. Ideally you should be using the most recent version that will successfully install on the device. I've been able to install 5.4 on devices going back to 2012? or so (Latitude e6410), though the only thing it tends to pick up are really old BIOS updates (because the OS install typically includes the requisite drivers for stuff that old). More on reddit.com
🌐 r/Dell
6
1
October 4, 2024
Those of you using Dell Command Update, how current are the BIOS versions?
What I've seen: website is most current, SupportAssist gets it shortly after, DCU gets it after SupportAssist. I'm not sure it's true, but I've always thought DCU was more enterprise focused and that Dell slow rolls the updates as a way to test them. At very least you could consider it different speed update channels and choose accordingly. More on reddit.com
🌐 r/SCCM
5
1
August 20, 2025
Dell Command Update Classic/Universal GPO support? v5.5/5.6 or 5.7?
We've got version 5.6.0 of Dell Command | Update (Universal) installed on 212 of our 630 or so Dells (Primarily Latitude 7420 and 7440s) with the rest running version 5.5.0 or 5.4.0 (all deployed via SCCM) and I can't say I've noticed 5.6.0 being any less stable than the prior versions, but your milage may vary, as we only use it for ad-hoc interactive patching with the aim to eventually use the CLI to do background updates once I've got buy-in. I personally decided to go with the universal version due to also seeing that the classic version was to be retired at some point. (Although as you say, they've been saying that for years, but you can only make decisions based on what you know at the time!) We successfully use the ADMX templates deployed via group policy with the universal version of DCU, so I can confirm that works. Regarding different versions being installed manually, we had the opposite problem to you in that some machines previously had the classic version, but I was pleasantly surprised that I was able to just chuck the universal version at said machines and it sorted itself out without any intervention. You're definitely right in deploying .NET Desktop Runtime 8 separately before installing DCU though, as it likes to install older versions of .NET Desktop Runtime 8 if you don't. (Last time I checked it would install 8.0.10) Just make sure your detection rule for the .NET install is happy with the current version or newer versions, as .NET will happily install older versions alongside newer versions which is a pain. More on reddit.com
🌐 r/sysadmin
12
17
March 5, 2026
Automating Dell Command Update

I run this as an application towards the end of the TS then reboot with MDT and run it again followed by another reboot before finishing up the whole TS.

@echo off
TITLE Running DELL Command Update...
REM Checks for updated DELL Drivers using DELL Command Update CLI

"C:\Program Files\Dell\CommandUpdate\dcu-cli.exe" /configure -silent -autoSuspendBitLocker=enable -userConsent=disable
"C:\Program Files\Dell\CommandUpdate\dcu-cli.exe" /scan -outputLog=C:\dell\logs\scan.log
"C:\Program Files\Dell\CommandUpdate\dcu-cli.exe" /applyUpdates -reboot=disable -outputLog=C:\dell\logs\applyUpdates.log        

It's pretty self explanatory but it configures it first, does a scan, then applies the updates and disables reboot so that MDT can do it instead. I run this against DCU 4.1.

I don't recommend silencing the Apply Updates stage (it isn't in that script above) because sometimes it can take a little while and not being able to see what it's doing can be nerve racking.

More on reddit.com
🌐 r/MDT
27
12
March 12, 2021
🌐
Dell
dell.com › home › support home › product support › manuals
Dell Command | Update Version 3.1 User's Guide | Dell US
You can view the details of previously installed updates on the system in the Update History screen. The details include the update name, update type, the date of the update was last installed, and the version of this update that was installed on the system.
🌐
Dell
dell.com › support › manuals › en-us › command-update-v2.4 › dcu_ug_v2.4 › update-history
Dell Command | Update Version 2.4 User's Guide | Dell US
You can view the details of the previously installed updates on the system on the Update History screen. The details include the name of the component, type of the component, date when it was updated, and the current or latest version of the component available on the system.
Find elsewhere
🌐
Dell
dl.dell.com › topicspdf › command-update-v24_users-guide_en-us.pdf pdf
Dell Command | Update Version 2.4 User's Guide
You can view the details of the previously installed updates on the system on the Update History screen. The details include the name of · the component, type of the component, date when it was updated, and the current or latest version of the component available on the · system.
🌐
Dell
dell.com › support › manuals › en-us › command-update-v3.0 › dcu_rn_win10_v3.0
Dell Command | Update Version 3.0 Release Notes | Dell US
Dell Command | Update is installed as a standalone application on a business client supported platform to provide updates for systems software released by Dell. This application is installed locally on the target systems and simplifies BIOS, firmware, drivers, and application update experience ...
🌐
Dell
dell.com › support › manuals › en-us › command-update › dcu_rn › release-summary
Dell Command | Update 5.x Release Notes | Dell US
Dell Command | Update is installed as a one-to-one stand-alone application on a business client supported platform to provide updates for system software released by Dell Command | Update . This application is installed locally on the target systems and simplifies the BIOS, firmware, driver, ...
🌐
Dell
dl.dell.com › topicspdf › command-update_Users-Guide2_en-us.pdf pdf
Dell Command | Update Version 3.1.1 User's Guide February 2020 Rev. A00
The Update History screen is located on the left pane of the main screen. ... On the Welcome screen, click System Information. The System Information screen is displayed with system details such as the name, description, version of the operating ... The activity log feature helps you to view ...
🌐
Reddit
reddit.com › r/dell › dell command | update - archives?
r/Dell on Reddit: Dell Command | Update - Archives?
October 4, 2024 -

Hi guys as the title suggests does anyone have archives of DCU for old versions prior to v4?

Reason why I ask is from the screenshot below we have various versions of DCU on the estate.

I have managed to get hold of legacy MSI installers for versions older than v5 but anything older than v4 I have come unstuck. Dell search is not great, if anyone has any sites that I can use that would be great as I am in the process of standardising old versions of DCU for a client they have over 40+ versions on their estate. Using MSI installers I have managed to uninstall some of the older versions but getting hold of later versions is a pain. I have tried using scripts but some of the scripts have borked the uninstalls where remnants of DCU have been left behind and it has corrupted the installation voiding being able to install newer versions.

Below is the various versions of DCU we have on our estate

  • DCU | Windows 10

  • DCU | Update

  • DCU | Update Windows Universal

🌐
Dell
dell.com › support › kbdoc › en-us › 000108963 › how-to-use-and-troubleshoot-dell-command-update-to-update-all-drivers-bios-and-firmware-for-your-system
How to Use Dell Command Update to Update All Drivers, BIOS, and Firmware For Your Computer | Dell US
The CAB file can be loaded to baseline ... a complete report of all current drivers, firmware, and BIOS versions by selecting System Information on the left side of the main screen, then selecting Export....
🌐
Dell
dell.com › home › support home › product support › driver details
Dell Command | Update Application | Driver Details | Dell US
This package contains the Dell Command | Update application. Dell Command Update is a stand-alone application for client systems, that provides updates for system software that is released by Dell. This application simplifies the BIOS, firmware, driver, and application update experience for Dell client hardware.
🌐
Reddit
reddit.com › r/sccm › those of you using dell command update, how current are the bios versions?
r/SCCM on Reddit: Those of you using Dell Command Update, how current are the BIOS versions?
August 20, 2025 -

We currently use OSDCloud for OSD and it has a piece that updates the BIOS. It works okay but it's generally kind of far behind. For example, the Dell Pro Max Tower T2 is like three versions behind. I notice the msendpointmgr tool is also not current with what's on Dell's website. From what I can tell they seem to use some version of an XML, from Dell, to get the download links for BIOS and driver packs.

That's probably okay, but I was looking into Dell Command Update and was curious if it's going to return the same versions that are in the XML. If it doesn't show a BIOS version that was released last week then I am fine with that. I just wanted to know if it's going to be any more up-to-date compared to other tools out there.

🌐
Reddit
reddit.com › r/sysadmin › dell command update classic/universal gpo support? v5.5/5.6 or 5.7?
r/sysadmin on Reddit: Dell Command Update Classic/Universal GPO support? v5.5/5.6 or 5.7?
March 5, 2026 -

Hello,

I am currently quite confused about the situation with Dell Command Update. I would like to introduce it in our company to manage driver and BIOS updates.

Initially, I created a package that installs .NET Desktop Runtime 8 first and then Dell Command Update Classic, because I read that this version supports CLI usage and GPO management via an ADMX template.

However, I noticed that some users already have Dell Command Update installed by a colleague, but in this case it is the Universal version that was installed manually.

After taking a closer look at the Universal version, I also found ADMX templates included. Does this mean the Universal version also supports GPO-based management?

While researching further, I came across additional confusing information. I read that Dell planned to discontinue the Classic version about three years ago, but it still seems to exist. I also saw references to version 5.7, but now I only see 5.6 again.

In addition, I found a post from someone who mentioned that they are still using version 5.5, claiming that it is more stable.

Could someone please clarify what the current situation is?
What actually happened with the different versions, and what would be the best and easiest approach for deploying Dell Command Update in a business environment?

Thank you very much for your help.

Top answer
1 of 7
4
We've got version 5.6.0 of Dell Command | Update (Universal) installed on 212 of our 630 or so Dells (Primarily Latitude 7420 and 7440s) with the rest running version 5.5.0 or 5.4.0 (all deployed via SCCM) and I can't say I've noticed 5.6.0 being any less stable than the prior versions, but your milage may vary, as we only use it for ad-hoc interactive patching with the aim to eventually use the CLI to do background updates once I've got buy-in. I personally decided to go with the universal version due to also seeing that the classic version was to be retired at some point. (Although as you say, they've been saying that for years, but you can only make decisions based on what you know at the time!) We successfully use the ADMX templates deployed via group policy with the universal version of DCU, so I can confirm that works. Regarding different versions being installed manually, we had the opposite problem to you in that some machines previously had the classic version, but I was pleasantly surprised that I was able to just chuck the universal version at said machines and it sorted itself out without any intervention. You're definitely right in deploying .NET Desktop Runtime 8 separately before installing DCU though, as it likes to install older versions of .NET Desktop Runtime 8 if you don't. (Last time I checked it would install 8.0.10) Just make sure your detection rule for the .NET install is happy with the current version or newer versions, as .NET will happily install older versions alongside newer versions which is a pain.
2 of 7
4
I think Dell stopped supporting Classic last year and started swapping even their recovery images to pre-install Dell Command Universal. The best is to deploy .Net then Dell Command Universal in a linked relationship then have a policy/config/post install script/Intune remediation run afterwards. Dell Command Universal will fail or install fragmented and non function if it installs before .Net.