Dell Command | Update fails to install updates during OSD after v5.6.0
Unable to run updates in Dell Command
MDT : Application Dell Command Update 4.7.1 returned an unexpected code 2
Dell Command Update Application Error
We utilize PatchMyPC and this morning, it updated "Dell Command | Update" to v5.6.0. Our OSD task sequences install DCU, apply a config file for DCU, then invoke the CLI to apply any driver/firmware updates it finds. For us, this is simpler than updating the driver packages for each model all the time and ensures that a system is running the latest patches and is ready for use as soon as the task sequence completes.
I tested an OSD task sequence on a Dell workstation to validate the new version. DCU installs successfully, I'm able to apply the config file, but when it runs the "dcu-cli.exe" command, it fails immediately and returns 3006. That specific return code is not documented, but 3000-3005 all indicate issues with the Dell Client Management Service. Looking into the logs, I can see smsts.log showing the following output from dcu-cli.exe:
Currently the system is in Windows Out of Box Experience (OOBE) State. Please try again after sometime.
Applying Dell updates via DCU at this stage of OS provisioning has never given us problems before, so I can only assume it's something that changed in this update. To confirm, I rolled back the version of DCU used in the task sequence to 5.5.0 and observed the failure was no longer present.
Not sure if this issue is expected going forward and is the "new normal" (which would be disappointing) or if it's unintentional. Regardless, I figured I'd share here in case anyone else was experiencing this and had any suggestions.
Hello there,
The Return code of 2 generally means that a file was not found. As the Dell command update has passed through may be this might a different error message meaning in your scenario. Can you see any other Event ID being generated to narrow down the issue?
Check the bdd.log file and see what it says. Per my personal experience, unexpected code 2 usually means file not found, incorrect file path, or permissions.
The below thread discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue.
https://social.technet.microsoft.com/Forums/en-US/12faf5f9-0c1a-4922-9fdf-b249ed4588fa/unexpected-return-code-2-when-installing-applications?forum=mdt
https://learn.microsoft.com/en-us/answers/questions/355159/mdt-the-application-returned-an-unexpected-code-2.html
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer–
I was getting the same error code on my installation, but finding that the application was installed. After searching I found that Error Code 2 for Dell Command Update indicates that a reboot is required.
[https://blog.loftinnc.com/dell-update-package-command-line-reference-and-exit-codes
I wish there was some uniformity between vendors when it comes to error codes.