Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modern Driver Management 4.2.1 not installing audio drivers #358

Open
dsraa opened this issue May 24, 2023 · 1 comment
Open

Modern Driver Management 4.2.1 not installing audio drivers #358

dsraa opened this issue May 24, 2023 · 1 comment

Comments

@dsraa
Copy link

dsraa commented May 24, 2023

Hi All,
I've been using MDM 4.2.1 for about 6 months, previous versions seem to work better, but I don't want to roll back if I don't have to. We have all Dell Models in our environment, and lately on the last few models, the Audio Drivers don't seem to install correctly or at all. The MDM apply drivers step finishes fine, and the laptop does finish the image, but upon login no audio driver is install, or audio just doesn't work, and I have to re-install the audio driver manually which usually fixes it. This seems to happen on Dell Latitude 7430, and 9430, and also on Microsoft Surface.

The only error in the apply driver log is - - An error occurred while installing drivers. Continuing with warning code: 2. See DISM.log for more details.

  • Successfully downloaded package content with PackageID: *****
  • Driver package content files was successfully downloaded to: C:_SMSTaskSequence\DriverPackage******
    [DriverPackageDownload]: Completed driver package download phase
    [DriverPackageInstall]: Starting driver package install phase
  • Attempting to apply drivers using dism.exe located in: C:_SMSTaskSequence\DriverPackage*******
  • DriverInstallMode is currently set to: Recurse
  • An error occurred while installing drivers. Continuing with warning code: 2. See DISM.log for more details
    [DriverPackageInstall]: Completed driver package install phase

I've tried several driver package versions downloaded through the automation tool, and it identifies the packages correctly, downloads them, and the above is the only error I get on almost all models. I reviewed the dism log, but an unable to find the issue.

Any ideas?

Thanks

@merlinfrombelgium
Copy link
Contributor

Looks like whatever is going wrong, happens in the dism process, so outside the scope or control of the script. Without seeing your dism.log I can't really help on that. Maybe these drivers don't like being installed using the recurse option. Also note that some drivers are just better off when installed as an application, not through injection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants