Driver Feed Discovery Tool MIA

Can anyone tell me the commands of the Driver Feed Discovery Tool.vbs script? I upgraded to 9.0.144 and it seems that file disappeared entirely. I can't find a download of it and a 6 year old post for its download location has expired. I'm also wondering if I'm missing anything else in this folder?

K2000 SDA



2 Comments   [ + ] Show comments
  • Thank you Nico! That solves the riddle. - RyanRusty37 3 months ago
  • Excuse the ignorance as I'm new to this. But I have trued running the copy_drivers_debug.vbs on the target machine and it just returns "No registry entry found" thoughts? - BigfootIsReal 2 months ago

Answers (7)

Answer Summary:
Posted by: Nico_K 3 months ago
Red Belt

with 9.0 the driver feed has been changed.
the popup etc is now in the copy_drivers_debug-.vbs

Posted by: MarkRMonaco 3 days ago
Yellow Belt

Not to hijack this post, but does anyone know if they still support us manually adding drivers under 9.1 (that are not Dell, HP, or Lenovo)?  We just recently upgraded our SDA and previously had drivers for Microsoft Surface Tablets and Intel NUCs in our "drivers_postinstall" folder (under the original 8.x structure).

Ideally, I would like to move them into that new "windows" folder that was automatically created, but I do know the correct hex codes for those models. - I would also like to avoid having to re-run the driver feed builder tool (which is still present under 9.x), if possible.

Posted by: TimHR 3 months ago
Second Degree Blue Belt

I am having a bunch of issues with the driver feed when I upgraded to the 9.0.144.



My folders are all weird names now  where they used to say the name of the Computer.

Has anyone else had this issue?

Also since two days ago now my folders are duplicating over and over again.


Just makes the folder over and over again.

  • Those are the Model IDs from DELL's Enterprise Catalog.

    The driver feed used to be a manual repository where each driver had to be added\profiled\updated, 8.2 and older versions were maintained by Quest.

    KACE SDA 9.0 and onwards are pulling driver packs directly from the manufacturers repositories:

    From the release notes:

    Driver Feed for Dell is now automated using Dell Driver Pack Catalog.

    Driver Feed for Lenovo is now available.

    Driver Feed for HP is now available.

    This is why HP, Lenovo driver packs were added(more brands to come in the future), because now the process is automated. (this was a dauting task with the old manual naming convention process).

    The folder names are automatically generated from the XML file supplied by the OEM itself. - Channeler 3 months ago
Posted by: RyanRusty37 3 months ago
White Belt

Mine have also renamed themselves, i don't have nearly as many as you but the ones i see are following the same naming convention as you have posted. I've seen this # referenced during the Copy drivers task during imaging, the 4 digit code you see is referenced once the discovery tool identifies the machine you are working on. For example yesterday the HP Prodesk 700 was identified as 8148. I think this is a cleaner way for kace to identify a machine, instead of HP Probook 17 G6 etc etc etc. I just cant figure out how we as techs identify the computer's driver folder outside of selecting it in Driver Feed. Unsure if it matters if we do or not. 

Im unsure of the duplication problem you're facing. 

Posted by: TimHR 3 months ago
Second Degree Blue Belt

One of the problems when it keeps adding another folder and you image that computer that uses those drivers you get like 4,134+ drivers to install. To fix the folder I have to know what computer model to find then unistall the package then reinstall the drivers and it is fixed, except it keeps that four digit name. 

I am trying to figure out why/how it is duplicating the folders.

  • Yes, a known issue with 9.0
    The "nested folders" issues.
    Please keep in mind this is NOT eating up space, the file you are seeing is a symbolic link pointing to itself.
    (this allows you to double click it an infinite amount of time, creating a huge path in Windows Explorer with just the Folder ID) - Channeler 3 months ago
Posted by: TimHR 3 months ago
Second Degree Blue Belt

But it does cause the imaging process to slow down because it (the one I saw) has over 4000 drivers to install, which now takes a longer time to image.  What is also weird looking in the samba some folders are ok .

I updated the K2000 with the hotfix 9.0.146  .

Posted by: RD94 2 months ago
Senior Yellow Belt

But it DOES seem to eat up space.  I just did a WinDirStat on \\drivers_postinstall, and some of my "nested folders" were over 50GB, and one even >100GB, then, when I delete them manually through File Explorer, it certainly seems to be deleting that much data.

If this "hex code" is going to be the new way models are identified, in the Driver Feed Library that code should be displayed.  Somewhere.

The hotfix seems to resolve the issue, however, it doesn't go back and fix what was already "nested."  I was able to determine this error by it taking a VERY long time to copy drivers during imaging for a particular model, in my case, a Optiplex 5090.

I highly recommend you do the same with WinDirStat or some similar tool, and then uninstall/reinstall from the Driver Feed those that seem to have this "nested folders" issue.

Don't be a Stranger!

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

Sign up! or login

View more:


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