Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Dell Update Universal

Description: This package contains the Dell Command | Update Windows Universal application. Dell Command Update is a stand-alone application for 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.


License: The Software may include Open Source Software (OSS) licensed pursuant to OSS license agreement(s) identified in the OSS comments in the applicable source code file(s) or file header(s) provided with or otherwise associated with the Software. Neither You nor any OEM, ODM, customer, or distributor may subject any proprietary portion of the Software to any OSS license obligations including, without limitation, combining or distributing the Software with OSS in a manner that subjects Intel, the Software or any portion thereof to any OSS license obligation. Nothing in this Agreement limits any rights under, or grants rights that supersede, the terms of any applicable OSS license.

Application Version:  5.0.0 64-bit


Download link:

Silent install: msi (via C:\Windows post initial install on test system)

Thanks for considering this request.



Date Votes
  • Hi Emtsu, 

    Thank you for the inquiry. I have a ticket to look into this. While historically, we have tried to stay hardware agnostic in our Package Library offerings, but we are interested in looking into these types of utilities for the major three vendors (Dell, HP, Lenovo). Going beyond the initial install, what is your plan or how do you recommend that Admins silently interact with the agent using PDQ? is there a command line reference that you would periodically push out for agents to update drivers? Are updates set to automatically install once the agent is installed? Is the user prompted and must take action? How are you currently using this?

  • Control of Command Update can be done through command line scripts, which is currently how I use it.

    Adding support for utilities such as this, along with scripts to manage them, would prove to be very useful for many admins, especially with more firmware and CPU vulnerabilities being discovered and needing patches.

    I would actually like to see support for Command Update and the comparable HP and Lenovo tools be expanded to include the deployment of firmware and driver libraries.  I can't answer for HP and Lenovo, but Dell doesn't make it and easy as it should to house local repositories of drivers for system fleets.  WSUS has certainly proved to no be a good fallback option.