KACE Product Support Question

Windows 10

08/07/2017 1876 views
I am having the hardest time imaging windows 10. I created a image and uploaded it into kace2000 when I go to deploy it works just fine. After the deployment when trying to boot the machine up I get an error stating "no boot device found". Using a brand new SSD in a micro 7050 what am I doing wrong here? 

2 Comments   [ + ] Show comments


  • Need more info...

    UEFI or Legacy?
    What partitions were harvested?
    What Tasks are you using to partition and set the MBR?
    • Harvested from D
      Create UEFI Partitions Assign D
      Select disk 0
      Convert gpt
      Create partition efi size=200
      Assign letter=s
      Format quick fs=FAT32
      Create partition msr size=128
      Create partition primary
      Assign letter=d
      Format quick fs=NTFS

      Format D as NTFS
      format /q /y /s:enable /fs:ntfs d:

      Install WinQO MBR (on D)
      bootsect.exe /NT60 d:

      That's as far as my "Pre-Installation Task".
      • So when you harvested the image you did not harvest the S partition?

        Please verify if this is UEFI or Legacy. You have some mis-matched commands going on right now.
  • There was no S partition?
    • Ok, Was there a C and D drive?
      • Yes the k-img was harvested from D.

All Answers

Ok then you are using a Legacy image.

The Below link will show you how to set up the partitions for a C/D configuration:

If I were you, I would look into altering your image so that the MBR resides on the Main (C) partition. But that is up to you.

Answered 08/07/2017 by: Desktop Jockey
Second Degree Green Belt

  • thanks i'll give that a try.
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