K2000 Issue with Dell latitude 3480 audio driver Build 1903

We are just starting to use the K2000, and we ran into an issue with the Dell latitude 3480 audio drivers. Build 1903. Once imaged we could not fix the audio driver no matter what we did.We tried every driver Dell provided and removed and reinstalled but still had issues in the device manager

We used Dism and put the 1809 image onto the same laptop and the Audio works fine. Issue we have over 300 of this model laptop.  We are upgrading the 1809 build to the 1903 to see if it still works,  but i was wondering if anyone else has ran into this issue? if yes what have you done to fix it?

2 Comments   [ + ] Show comments
  • Have you activated the "Dell Driver Feed" for the Latitude 3480 in the KAE SDA Library?

    In addition, the KACE SDA normally sets up all drivers automatically for Dell systems. - Gerhart 1 year ago
  • yes, when we push thru kace 2000 with the 3480 driver feed is when we ran into the issue. Imaging with a jump stick using dism the driver works fine - sscott0420 1 year ago

Answers (2)

Posted by: Ckunik 3 months ago
Yellow Belt

Im having the same issue. IF i use scripting image it work. my image wasnt built using a vm. anyway to remove the drivers 

Posted by: Channeler 1 year ago
Red Belt

The latest enterprise driver pack for that model, is version A11:

That is the same version available in the KACE SDA, and it includes Audio Driver version

Is that the same driver version reported by Device Manager after the Imaging process?

Could be an issue with the driver itself,  Was that Imaged Sysprepped and Captured from a VM? (Virtual machines provide the best Images for mass deployment, as they won't carry any drivers from any previous device).

Also if you download the Audio Driver from Support.Dell.com (the non enterprise page, that usually have the newest but not tested drivers), and manually install it, does that work? (if so, you could setup a Post Install Task Script, to install that audio driver as part of the Imaging process).
If this Image was Sysprepped and Captured from a VM, with a KBE built with ADK 1903, then we can consider this a good image and look somewhere else.

I would suggest checking at the DISM log in Windows, get the dism.log from c:\windows\dism.log, (Not the one from c\windows\logs\dism\dism.log)

That log generated by Windows will tell you what drivers where injected and from where, and if Windows or DISM did not like them.

Also when you say issues with audio....., could your elaborate?


  • The k2000 image we are using was built by quest and is a VM. We loaded the 3480 driver pack and imaged.
    When the machine booted, everything worked but the sound card. We had a unknown device in the Device manager.
    We tried to install the driver manually from Dell but no matter what driver we tried it would fail. We tried many way to fix the issue and could not resolve it.
    To see if it was a K2000 glitch? we used a usb stick and imaged it with version 1809
    this seemed to work with no issues, but we were stuck having to upgrade etc manually. I was
    just wondering if anyone else had ran into this issue before? We are going to bring a few more of the same devices back to the office and try again. - sscott0420 1 year ago
    • We tried to install the driver manually from Dell but no matter what driver we tried it would fail.

      So the wizard to install the driver manually fails with an error message, What does it says?

      To clarify, the Image is a clean image, Sysprepped and No drivers right?

      Is the Same Thing happening when you deploy a scripted install? (Scripted Installs are based on the virgin clean Windows ISO, instead of customized Image). - Channeler 1 year ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ