Systems Management Question

No USB support after creating new KBE

03/04/2016 1885 views
Greetings All,

Hoping that you can help me out, I've added some drivers to our K2 and went through the adding drivers process; add the drivers manually, re-cache the drivers on the K2, then create a new KBE. The problem that I'm having is that the new KBE is not loading the driver(s) necessary for USB functionality. Let me clarify;

The machine that I'm trying image is an Optiplex 5040 desktop.

Step 1: F12 to PXE boot the machine
Step 2: Choose which KBE you want to boot to K/M still working
Step 3: Next screen 'Starting Windows', this is where the USB keyboard and mouse go dead sequentially there's no cursor
Step 4: The main menu now appears, but you can't choose anything as the KB & M are not working.

I've tried adding the USB 3.0 hub driver to the \\\drivers folder and going through the above process, but no love. What's odd to me is that I have a KBE on the K2 that I created 6 months or so ago and that one gives me USB functionality but does not have the NIC driver in it, so if I use that one the machine can't connect to the K2 to get imaged. The one that I'm trying to use has the NIC driver in it and it loads where it's supposed to, thus getting me to the main menu.

I feel like I've missed something.

Any help would be greatly appreciated!

- JZ
0 Comments   [ + ] Show comments


  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.

All Answers

Hi JZ,

Just as a guess at this point without looking into more depth it would appear there is a driver conflict occurring which is preventing the mouse/keyboard from functioning correctly.

Is there only one driver pack installed with the added network driver (WINPE), my current recommendation is to use WINPE5 (Driver Pack 5 and Windows 8.1 ADK) as this can be used for Windows 8.1 or Windows 7 imaging.

Verify that no other drivers are being loading into the KBE image, sometimes there will be a feed folder or other drivers in the OS Specific driver folders. These are rarely used for the normal process and should be empty, compressing them to a .ZIP file or removing them completely before the driver re-cache and building the KBE.

Answered 03/07/2016 by: TheAustinDave
Brown Belt

  • Hi AustinDave!

    Thanks for your response! I'm circling back around to this and am going to try what you've recommended. I'll keep you posted.

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