Dell Command Update 3.1 return/exit code wrong

Question

I have updated to Command update 3.1 from 2.4 since command line support has now been added.  Now I have noticed I no longer get a return code showing a reboot is required. For example this is part of output from an update log after running using command line: Downloaded updates (4 of 4)., 330.5 MB of 330.5 MB transferred (100.00%)...Installing updates (1 of 4). Update Name: Intel Management Engine Components InstallerInstalling updates (2 of 4). Update Name: Intel Chipset Device SoftwareInstalling updates (3 of 4). Update Name: Intel HD, HD 4200/4400/4600/5000/5100/5200//5300/5500 graphics driverInstalling updates (4 of 4). Update Name: Intel PCIe Ethernet Controller DriverExecution completed.Program exited with return code: 0 3 out of the 4 above drivers require a reboot and I get a return code of 1(reboot) in 2.4 but not in 3.1.  Even a BIOS update returns a 0.  I know the return codes partially work as I get 500 if no updates were required which is correct.  I use the exit code in our management software to execute reboots and rescans so this messes up stuff that happens after the update runs. Exit codes referenced 0 Command execution was successful NA 1 A reboot was required from the execution of an operation Reboot the system to complete the operation. 500 No updates were found for the system when a scan operation was executed The system is up to date or no updates were found for the provided filters. Modify the filters and re-run the commands.

Jim Koerner · Answer

Pulled an update log from a different machine that had a BIOS update to show the same return code of 0 where it should be 1.

Creating system restore point...
Downloaded updates (0 of 0)., 41.3 MB of 41.3 MB transferred (100.00%)...
Installing updates (1 of 2). Update Name: Intel 9x60, 826x, 7265, 3165, and 7260 Bluetooth Legacy Driver
Installing updates (2 of 2). Update Name: Dell Latitude E7450 System BIOS
Execution completed.
Program exited with return code: 0

tkernick · Answer

I have the exact same issue.   The reboot flag also does nothing.

Jim Koerner · Answer

I have been working with Dell support on this since I posted here. They got back to me the other day that there is a bug causing this issue and it slated to be fixed in the next release but no scheduled release date at this time.

Jim

Enterprise Client

Was this post helpful?