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.
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.
@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).
RealestSwissJay
2 Posts
0
October 20th, 2022 07:00
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
2 Intern
•
162 Posts
0
October 28th, 2022 00:00
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
2 Intern
•
185 Posts
0
July 6th, 2023 03:00
4.5 does not work either
SPGS
1 Rookie
•
22 Posts
0
January 19th, 2025 13:40
Current 5.4.0 in 2025 still does not work!
BrokenHinge
1 Rookie
•
3 Posts
1
April 15th, 2025 19:17
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
1 Rookie
•
2 Posts
0
July 23rd, 2025 21:36
@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).