Using Display Driver Uninstaller (DDU) Silently During SCCM Task Sequence Imaging
Posted: Sun Oct 19, 2025 10:57 pm
Hi everyone,
First off, a big thank you to the developers of this program — it quickly solved an issue I’d been struggling with for days! I’ve already sent over a small donation in appreciation.
I wanted to ask if anyone has successfully used Display Driver Uninstaller (DDU) as part of a task sequence in SCCM during the imaging process. I found documentation in the forums about running DDU silently using command-line options, but I’m curious if anyone has implemented this specifically during imaging.
Here’s the command line I’m looking to use:
"Display Driver Uninstaller.exe" -logging -silent -removemonitors -cleanintel -restart
Here’s my situation: I spent a week building a fairly complex image for a new class of hardware. It worked perfectly for its intended systems. However, my management later decided they wanted this same image to be backward compatible with all our older hardware models as well.
That wasn’t too bad — I packaged and integrated the appropriate driver sets, and most systems worked fine. But two of the older models, which use integrated Intel graphics, are giving me trouble. After imaging, they only show up in Device Manager as a generic VGA adapter. Installing the official OEM driver packages or Intel’s reference drivers doesn’t fix it — until DDU is run manually, which resolves the issue instantly.
Before I go through the effort of loading the full image into a VM, running DDU, and recapturing, I’d like to try deploying DDU silently as an SCCM package and then applying the drivers right after that step.
Has anyone attempted something like this or have tips for integrating DDU into a task sequence workflow?
Thanks in advance for any insights!
First off, a big thank you to the developers of this program — it quickly solved an issue I’d been struggling with for days! I’ve already sent over a small donation in appreciation.
I wanted to ask if anyone has successfully used Display Driver Uninstaller (DDU) as part of a task sequence in SCCM during the imaging process. I found documentation in the forums about running DDU silently using command-line options, but I’m curious if anyone has implemented this specifically during imaging.
Here’s the command line I’m looking to use:
"Display Driver Uninstaller.exe" -logging -silent -removemonitors -cleanintel -restart
Here’s my situation: I spent a week building a fairly complex image for a new class of hardware. It worked perfectly for its intended systems. However, my management later decided they wanted this same image to be backward compatible with all our older hardware models as well.
That wasn’t too bad — I packaged and integrated the appropriate driver sets, and most systems worked fine. But two of the older models, which use integrated Intel graphics, are giving me trouble. After imaging, they only show up in Device Manager as a generic VGA adapter. Installing the official OEM driver packages or Intel’s reference drivers doesn’t fix it — until DDU is run manually, which resolves the issue instantly.
Before I go through the effort of loading the full image into a VM, running DDU, and recapturing, I’d like to try deploying DDU silently as an SCCM package and then applying the drivers right after that step.
Has anyone attempted something like this or have tips for integrating DDU into a task sequence workflow?
Thanks in advance for any insights!