I have a new model Dell machine that I am having issues getting to boot into the KBE_x86 environment. I uploaded and built a new KBE with updated drivers using the Driver_Feed_Builder tool (this added 6 more drivers). The issue still existed. I then downloaded the latest driver pack (kbe_driver_pack_3) and created another KBE. There are 46 additional drivers in the newest version of the KBE and it is still not loading correctly (using PXE or USB boot). I am starting to get the feeling it isn't the drivers but something underlying that I cannot pinpoint.


I am getting as far as the "Starting Windows" splash screen and then it just keeps processing.


Any ideas? Thank you,

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0
Hello,

This sounds like you might have multiple sets of WINPE3 versions loaded in the /drivers share. Should only have one version of WINPE3, be sure you don't have WINPE4 or WINPE5 also loaded as this can cause KBE issues.

Most likely the case is the Network driver is not responding as expected, start with just the native WINPE3 pack and build the KBE (be sure to compress/zip and files in the other OS folders which may be causing a conflict).

The Driver_Feed_Builder tool only adds the post-install drivers and would not affect KBE function.

TheAustinDave
Answered 04/15/2015 by: TheAustinDave
Second Degree Blue Belt

  • Thank you for the feedback. Looking in the drivers share, I have multiple directories under the kbe_windows_x86.

    Custom-32
    Dell-winpe3-a15.2
    feed
    kace
    kace-winpe3-k04

    I am going to try to remove and re-cache until I get a successful result. If you have a chance, let me know if there is something else I am missing.

    Thank you,

    Kyle
    • I would start with leaving just the customer_32, Winpe3-A15.2 and Winpe3-K04 in the directory, cache and create a new KBE. (remove the feed and kace folders).

      TheAustinDave
      • Still no dice. I tried a few combinations and have a few more to test. Would it be getting stuck due to a lack of a driver, or is it getting stuck due to the fact it doesn't know what driver to use?

        Kyle
Please log in to comment
Answer this question or Comment on this question for clarity