I created a UEFI Image in VMware for Win 10 1803 using the KACE guide. The capture went without a hitch.The deployment also went smooth outside of the prompt to choose which Windows 10 volume to boot to on each restart or fresh boot.I've been able to remedy this on a per system basis by going to msconfig > Boot > Deleting additional volume.My question is what causes this?Here are the details:The source VM does not have multiple volumes listed in msconfig.The UEFI deployment guide linked above was used for the entire process.My pre-install tasks match that of the guide minus the logic to detect BIOS/UEFI.I feel like this has something to do with the pre or mid level tasks, but can't quite put my finger on it.Any thoughts?Volume Prompt:BIOS Settings:

Scripting : Multiple Windows 10 Volumes Created with K2000 Image

Multiple Windows 10 Volumes Created with K2000 Image

I created a UEFI Image in VMware for Win 10 1803 using the KACE guide. The capture went without a hitch.

The deployment also went smooth outside of the prompt to choose which Windows 10 volume to boot to on each restart or fresh boot.

I've been able to remedy this on a per system basis by going to msconfig > Boot > Deleting additional volume.

My question is what causes this?

Here are the details:

The source VM does not have multiple volumes listed in msconfig.
The UEFI deployment guide linked above was used for the entire process.
My pre-install tasks match that of the guide minus the logic to detect BIOS/UEFI.

I feel like this has something to do with the pre or mid level tasks, but can't quite put my finger on it.

Any thoughts?

Volume Prompt:

BIOS Settings:

4 Comments [ + ] Show comments

If your end goal is UEFI, make sure your are booting from a true UEFI source.

(look at the KBE footer before starting the deployment, somewhere down there it should say Boot Mode: UEFI.)

Make sure you are using these tasks, please don't edit them, just copy paste:

https://www.itninja.com/blog/view/bios-uefi-combined-tasks

Might be a formatting issue, please use CMD from the KBE and try to

SEL DISK 0
CLEAN

And see if the hard drive is truly empty.... if not, might be a drivers issue - Channeler 5 years ago
- Thank you for the link. I was able to see that my K2000 includes these tasks built in as of the latest update.
  
  I removed both of the manual tasks and added the built in tasks listed in the article you linked.
  
  I also verified that the source KBE is UEFI as notated in the footer.
  
  Additionally, I launched a cmd and cleaned the disk and verified that disk 0 was the only disk with no volumes prior to imaging.
  
  I am still receiving the multiple volumes prompt.
  
  A side note is that this occurs on machines with NVMe and 2.5" SATA SSDs.
  
  As far as a driver issue, I'm not sure where to start. Windows loads without issue and all drivers appear installed. No blue screens. This behavior occurs on both models I've tested the OptiPlex 5050 MFF and 5040 SFF. - robertsj 5 years ago
  - I know this might be too 101, but could you add a picture to the original question, showing up
    
    -BIOS setup in regards Boot options and Modes
    
    -A picture showing the multiple boot Volumes after POST.
    
    And make sure we are not dealing with some kind of RAID 1.... what is not enabled. - Channeler 5 years ago
I've updated the post to include a picture of the prompt as well as the BIOS settings. I have no doubt that whatever the issue is will be a simple one.

A few things to note:

The BIOS settings were taken after an install where the multiple volumes are present.

I have tried imaging using AHCI just to see and I am receiving the same results. - robertsj 5 years ago
multiple boot managers....

I would delete them from the BIOS. all of them.

Switch to AHCI

and try to image again.

Question, Are you PXE booting or booting with a USB KBE? - Channeler 5 years ago
- I deleted all boot managers, switched to AHCI, did a manual cleaning of disk 0. Still received the volume prompt. We are using PXE. - robertsj 5 years ago
  - What partitions where captured for this Image?
    
    Is the KBE confirming you are booting in UEFI Mode?
    
    (before starting to Image, check the footer, it has several details, check the Boot Mode: UEFI, if it says legacy is not going to work.
    
    Make sure you do not have any other device plugged via USB.
    
    Are you sure this is not one of those precision devices with a PERC and two physical hard drives?
    
    Make sure the RAID is enabled, the KBE must see only one logical drive. - Channeler 5 years ago
  - Sorry to keep replying to old replies, I can’t seem to reply to you after a certain point in the tree.
    
    In regards to the UEFI combined tasks, my understanding is that the tasks auto detect BIOS/UEFI, set and apply the parititions properly based on the detection. In the article, it looks like starting with the latest version of the K2000 software, these tasks are available by default. I have a pre install and mid level task that both detect the machine type and set partitions based on the detection.
    
    My logic is that I can capture an EFI VM (c and s) partitions, then rely on these scripts to detect UEFI and appropriate format the disk to accept the captured partitions. Am I misunderstanding something?
    
    Your post got me thinking, it may be a good idea for me to create UEFI only pre and mid level tasks to take the auto detect logic out of the equation. My end goal here is to deploy Win 10 in our environment with UEFI across the board. - robertsj 5 years ago
  - those tasks do all that, and yes they are built-in... you are right, but ONLY if the C is captured, alone.
    
    If you have C and S captured, those tasks will fail big time.(like it's currently happening).
    
    Take them out, use Create UEFI Partitions as PRE Level task
    Use Apply UEFI Partitions as MID level task.
    
    Same image, and tell me how it goes.
    
    If it fails with error --Unknown Error: 4294967295--, read this:
    
    https://support.quest.com/kace-systems-deployment-appliance/kb/226039/unable-to-deploy-uefi-image-with-unknown-error-4294967295 - Channeler 5 years ago
- Confirmed that UEFI mode is the selected boot mode. Using WinPE version :10 (1803).
  
  Checked diskpart > list disk to verify only one physical drive is selected. The physical drive is an m.2 NVMe SSD.
  
  From the VM, I captured the C and S partitions as instructed in the UEFI guide.
  
  Here are some interesting oddities. I can choose either partition and boot into Win 10. I can also delete one or the other to no ill effect. Also, I've noticed that the files that are on the local admin desktop (not public desktop), show up on every new account's desktop that logs in.
  
  We've deployed a few of these machines and haven't noticed any issues with the images themselves, but I'm almost at the point of deleting the VM and starting from scratch. - robertsj 5 years ago
  - I think there is a huge misunderstanding here.
    
    In a previous post, you said:
    "I am using the ones built into the K2000. They appear to be the ones from this post here.
    --https://www.itninja.com/blog/view/bios-uefi-combined-tasks--"
    
    If that is true, your image needs to be captured from a LEGACY VM, not an EFI VM, and it needs to have C: as the ONLY captured partition.
    
    If you captured C: and S:, those tasks will cause issues.
    
    For C: and S: images, your pre install task should be:
    Create UEFI Partitions
    and your mid level task should be
    Apply UEFI Partitions
    
    These are the original UEFI deployment tasks, designed to work with C: and S: combo for Images - Channeler 5 years ago
- That was it! The pre and mid install tasks needed to be the UEFI specific tasks as opposed to the combined tasks. I totally missed that line in the BIOS/UEFI combined tasks. How do I mark your comment as the answer? - robertsj 5 years ago
whats your diskpart script for create UEFI Partitions - Ozhunna 5 years ago
- I am using the ones built into the K2000. They appear to be the ones from this post here. https://www.itninja.com/blog/view/bios-uefi-combined-tasks - robertsj 5 years ago