I have had, the past 2 months, two scripted installations on my K2 - One x86 & one x64, Win 7, SP1, Ent, OS ONLY.  Both have been used many times and worked fine when installing legacy boot.  I even duplicated the x64 installation and created a UEFI installation that works fine as well.  

Yesterday I tried to perform a scripted installation (legacy boot) and I get "Windows cannot locate the disk and partition specified in the unattend answer file's setting.  Make sure the setting references a valid partition and restart the installation."  I'm using the same KBE as before to boot and it works fine as well.  I have changed nothing in the Wizard created answer file in the installations.  They are as they have always been.

I've created a NEW scripted installation (to legacy boot) from the same OS source and it fails.  I tested the UEFI boot installation and it worked fine.  The only difference in legacy & UEFI installations is the Pre-Install / Mid-Install tasks????

The only thing I have done to the K2000 in the past few weeks is upgrade to 3.7.113224 from 3.7.110084 or something around that number.

Did the upgrade change something?

1 Comment   [ - ] Hide Comment


  • Last week I had one of two new 3.0 USB drives become corrupted after each use on a Dell E5450. I setup the drive three times for UEFI and after one use the drive was toast. The other drive works fine and the corrupt drive works fine for storage - just not KBE. If it can happen - it will. Test everything.
Please log in to comment

Answer this question or Comment on this question for clarity



After 15 hours of troubleshooting, support tickets and trial & error I figured out the problem. The brand/model of USB drive.  I've seen this before in older versions of Kace but figured the brands/types of USB flash drives wouldn't matter anymore since it has been a few years. 

I have the KBE installed on a Silicon Power 16GB 3.0 flash drive that is formatted NTFS.  Everything boots fine and I get the K2000.  I select the Scripted Install and it kicks off fine then fails when trying to install the OS.

I installed the KBE onto a generic company branded 80 cent USB flash drive, booted to it, kicked in the scripted install and off it went without a hitch.  I had changed the flash drives after getting some new ones and didn't give that a thought - till now.

Anyone know WHY one flash drive works and the other doesn't?


Answered 05/04/2015 by: rjobe
Fourth Degree Green Belt

  • The quality of USB drives varies enormously, and it is not uncommon for the first blocks of a USB flash device to use fast memory and the rest to be slower memory.
  • Yup, just got the disk partition error while using a new Kanguru FlashBlu 3.0. Our older usb sticks work fine on the same computer.
  • Your post here led me to my "solution".

    I had built a scripted image which worked fine on a standard Dell laptop we use on-campus, and I thought I was finished with the image.

    But then when I tried to install it on another Dell laptop, which we acquired as an evaluation unit rather than a standard-use laptop, the image I had built kept failing, with the Windows install complaining that the disk/partition specified in the unattended file could not be found (if I used /IMAGE/INDEX) or that the drive was in GPT mode (if I used /IMAGE/NAME), neither error message giving me the info I needed to solve the issue.

    Your post made me realize that perhaps it's some incompatibility with the SSD in this non-campus-standard laptop, so I tried it on a campus-standard Dell desktop, and the image works fine.

    There's some incompatibility with this non-standard laptop and K2 imaging and/or Windows unattended setup.

    Okay, so maybe not an entire "solution", but at least now I know it's not a problem with my image, per se. Thanks for your post, which helped me get to this position!
Please log in to comment