Dell Command Update in Windows 10 Audit Mode

Question

In Windows 10 (21H2) audit mode Dell Command Update does not run. But it runs fine when its not in audit/oobe mode. See below for what I am trying when in audit mode.

dcu-cli.exe /applyupdates -outputlog=C:\dcu.log

The Dell Client Management Service is starting.

Checking for updates...

Apply updates action ended due to an unknown error..

Execution completed.

The program exited with return code: 2

C:\dcu.log

[2022-03-09 01:36:39] : The computer manufacturer is 'Dell'
[2022-03-09 01:36:39] : Checking for updates...
[2022-03-09 01:36:39] : One or more errors occurred.
System.AggregateException: One or more errors occurred. ---> FrameworkCore.ServiceBlockedException: Operation ID 67bcd2d0-a040-4ba2-9eaa-5feff9ac7b41. The service is blocked.
at UpdateClient.ExecutionMonitor.d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UpdateClient.UpdateClient.d__32`1.MoveNext()
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at System.Threading.Tasks.Task`1.get_Result()
at Dell.DCU.CLI.Operations.UpdateCliModel.<>c__DisplayClass75_0.b__1(UpdateClient T)
at Dell.App.Core.ServiceAccessor.InstanceHandler.<>c__DisplayClass11_0.b__0()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Dell.App.Core.ServiceAccessor.InstanceHandler.d__11.MoveNext()
---> (Inner Exception #0) FrameworkCore.ServiceBlockedException: Operation ID 67bcd2d0-a040-4ba2-9eaa-5feff9ac7b41. The service is blocked.
at UpdateClient.ExecutionMonitor.d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UpdateClient.UpdateClient.d__32`1.MoveNext()<---

[2022-03-09 01:36:39] : Apply updates action ended due to an unknown error..
[2022-03-09 01:36:41] : Execution completed.
[2022-03-09 01:36:41] : The program exited with return code: 2
[2022-03-09 01:36:41] : State monitoring instance total elapsed time = 00:00:12.1639597, Execution time = 7mS, Overhead = 0.061405168910581%
[2022-03-09 01:36:41] : State monitoring disposed for application domain dcu-cli.exe

RealestSwissJay · Answer

Any chance you are doing this with DCU v4.6? If so, try it with v4.5. I just battled the same issue for a couple days and it turns out that Dell did something to v4.6 that breaks this. Went back to v4.5 and it runs just fine during a task sequence or in audit mode, even on Windows 11 22H2.

RachelGomez · Answer

Use Windows Updates to get the latest Windows updates.
Right-click Start and click Settings.
In the Settings panel, click Update & Security.
On the left panel, select Windows Update.
On the right panel, click Check for updates.
Restart the computer when prompted.

Regards,

Rachel Gomez

spgsit · Answer

4.5 does not work either

SPGS · Answer

Current 5.4.0 in 2025 still does not work!

BrokenHinge · Answer

DCU doesn't like running when OOBE hasn't been completed.

To temporarily work around this, open Regedit, go to HKLM\System\Setup and change OOBEInProgress from 1 to 0

I found that DCU would then work normally.
When finished, don't forget to switch OOBEInProgress back to 1

Baalp · Answer

@BrokenHinge​  I tried setting this in a (SYSTEM-level) PS script that runs during the OOBE state (sysprepped images we deploy on thousands of PCs at once) and it did not work, dell still complained. That was with version 5.5 and the recommended 4.5 of 'Dell Command | Update'.  My solution was to create a SYSTEM one-time-only task that runs before a user logs in, right at the domain-joined login/warning screen. So basically after the full OOBE and automation process, when it shows the login prompt it's actually running dell command updates. The script that is called from this task self-deletes the script as well as the task. Mind you my automation script runs Windows Updates and even prior Dell driver injection, but running 'Dell Command | Update' was just to get the latest drivers both of those may miss (and specifically tied to Dell architecture).

Windows General

Dell Command Update in Windows 10 Audit Mode

Was this post helpful?