Boot Disk Creator unable to add driver or missing optional components
search cancel

Boot Disk Creator unable to add driver or missing optional components

book

Article ID: 171253

calendar_today

Updated On:

Products

Ghost Solution Suite

Issue/Introduction

While trying to create either a new configuration or creating a new PXE boot option through Boot Disk Creator you notice a couple of different issues.

  1. If you try to add a NIC driver, you receive a message stating that Bootwiz is unable to add the driver
  2. When you're on the Optional Components page you notice that only three options are available instead of the normal 20 to 30 that are normally there

In both situations you are still able to successfully build your boot option.  You'll get an error when trying to add the NIC driver but that doesn't stop the build process from working.

You'll see an error stating that Bootwiz is unable to add the NIC driver if you try to add a driver.  Even though the driver is just fine.  Other than that, the missing optional components section will not give any error.  It will simply be missing nearly all the optional components.

Environment

GSS 3.x

Cause

It has been determined that these issues are caused by remnants of a boot.wim file being mounted or partially mounted on the box.  This is preventing Dism from performing the work it needs to do to build the new configuration.

Resolution

Try running the following commands to determine if this is the case.

  1. Open a command prompt (Run as Administrator)
  2. Run: Dism /get-mountedimageinfo
  3. Run: Dism /get-wiminfo /wimfile:<Install Media Source>\<filename>.wim
  4. Run: Add "/index:X" with X being 1-4 indicating the OS from the output of previous command

If an image is mounted

  1. Run: Dism /unmount-wim /mountdir:<Mount Dir Location> /discard
  2. Verify Status
  3. Run: Dism /get-mountedimageinfo (Only the operation completion message is displayed)

At this point you can try to add a NIC driver or build a new boot option.  The optional components should also be back now.

Other command line arguments that may help with the clean up:

  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /RestoreHealth /Source:<files location of required source> /LimitAccess