Hi Guys,

I have recently updated my KBE Manipulator to the latest version ( from and noticed the Driver Feed Advisor running on the new KBE.  I've read the documentation I could find on this application but I'm still not sure what it's for and why it's needed when imaging via the K2000.

The documentation suggests that it reads the OS version from the currently installed OS on the local hard drive but I don't see why this is needed or what it uses this information for as the K2000 already has a script for discovering the OS, make and model for driver installs.

Obviously I can disable this in the KBE Manipulator but what functionality would this disable if any?



1 Comment   [ - ] Hide Comment


  • Brilliant, thanks for your comments guys.

    If that's the only function it has I think I'll disable it going forward.

Please log in to comment

Answer this question or Comment on this question for clarity


Here is information on Driver Feed Advisor: http://www.itninja.com/blog/view/driver-feed-advisor

It is added in and run in as a way to help troubleshoot driver injection issues.  Disabling it from running is fine.  If I'm not mistaken, the app is still there so that it can be run manually if needed.

Answered 08/09/2016 by: cserrins
Red Belt

Please log in to comment
The DF advisor is just that an advisor.  It displays in the command startnet.cmd window at the end where the drivers would need to be on the kbox and does the directory currently exist.  You can disable it to save boot a little boot time (10sec)

In this example it's telling me I do not have the proper drivers available if I were to deploy win10 to this 7020 I am booting to the K2.

Answered 08/09/2016 by: SMal.tmcc
Red Belt

Please log in to comment