/build/static/layout/Breadcrumb_cap_w.png

K2000 Apply UEFI Partitions fails with Return Code 1

Hi

 

We have K2000 v3.6 and a Win 7 x64 .WIM image.  The image was taken off a computer with UEFI bios.  

 

The System Image deployment has been set with the followings:

 

Run Preinstallation Tasks:

- Create UEFI Partitions

 

Run Mid-Level Tasks:

- Apply UEFI Partitions

 

 

When we get to run the System Image deployment, the process bombs out at Apply UEFI Partitions with the following error:

 

Task ID: 10

Task Name: Apply UEFI Partitions

Return Code: 1

Error Description: Unknown error.

 

 

 

I have been trying to find out where I can find the error log with more informative message, the System Maintenance log files from K2000 doesn't seem to contain anything related to this error.

 

Where should I look for the debug error file? or does soomeone know how to decrypt this not so useful error message?

 

Thank you

Asked 10 years ago 11354 views
9 Comments   [ + ] Show comments
  • when it bombs one of the choices is to edit the tasks xml file look thru it and find task id 10 and what are the xml lines for this task? - SMal.tmcc 10 years ago
  • you can also open a cmd window and try to run that task manually from the y: drive and see what errors show. - SMal.tmcc 10 years ago
  • thank you, will try this and post back! - cpurn 10 years ago
  • Hi SMal.tmcc

    I have uploaded screenshots below:

    http://imgur.com/wFbo6AX
    http://imgur.com/KK5zXqc
    http://imgur.com/wVM6Wcd

    I'm still researching about the error above.

    thanks! - cpurn 10 years ago
  • Even running bcdedit without any parameters gives the same error message.

    I created a USB boot environment from the image because this is a UEFI image and boot off the USB to apply the image. The USB was formatted with fat32.

    is this an issue related to the usb flashdrive? - cpurn 10 years ago
    • this is correct method to boot uefi, looks like it does not know where the boot store is kept. adding second nic to our k2000 now. I will do some checking when I get this done. - SMal.tmcc 10 years ago
    • used a lifeline and emailed a friend, see answer to see if that helps - SMal.tmcc 10 years ago
  • Thanks SMal.tmcc - I hope you still have many lifeline.

    I will try this and provide feedback here, we have a public holiday on Monday so I will post by Tuesday (AEST). thanks again - cpurn 10 years ago
  • could you help clarifying this?

    --
    assuming c: is windows partition
    and make sure you run that bcdboot cmd from a winpe 5 based KBE or it will fail.
    ---

    winpe5 based KBE - I read this as not to use the current usb flash for UEFI? if I only have Win7 which I understand is NOT winpe5 environment? - cpurn 10 years ago
  • I am receiving this same message after I captured a Windows 7 UEFI 64 bit virtual image. I captured a wim file and selected both the S: and C: drive as part of the image. I am trying to image a Dell Precision 5820.
    I am still very new to how the whole image process works so it be very helpful if you can provide me step by step what to look for. Log files explaining what the program is?
    Thanks. - kkullot 6 years ago
  • Hello, you may refer to this https://support.quest.com/kace-systems-deployment-appliance/kb/226039/unable-to-deploy-uefi-image-with-unknown-error-4294967295 to fix it. - GreenChin 6 years ago
    • Version of my K2000 is 5.1.84 and this says "This is affecting only 4.0.695, 4.1.182 and 4.1.1148 Server Versions."
      Step 2A at the bottom doesn't have a file at the end of document to download that I can see. Any other ideas? - kkullot 6 years ago
      • Hi kkullot, Sorry on the late reply, there are two attachment, S_Capture and S_Not_Capture. Download them and import them as KACE package. - GreenChin 6 years ago

Answers (2)

Posted by: gerald_mack 10 years ago
Orange Belt
1

1. Can you include a screen shot of the drives you captured, either the image file browser if its a k-image or a screenshot of the \\ikbox\peinst\wim\id#\ share, if it was a wim ?

2. It sounds like it failed to edit the bcd file, which may simply be due to the fact that, it doesn't exist, i.e. if -- S: wasn't captured as part of the deployment, then it wasn't restored and \bcd doesnt exist to be edited.

 3. you could try:

bcdboot c:\windows /s s: /f UEFI

assuming c: is windows partition

and make sure you run that bcdboot cmd from a winpe 5 based KBE or it will fail.

then run:

 

bcdedit /store S:\efi\microsoft\boot\bcd /set {bootmgr} device partition=s:bcdedit /store S:\efi\microsoft\boot\bcd /set {memdiag} device partition=s:bcdedit /store S:\efi\microsoft\boot\bcd /set {default} device partition=c:bcdedit /store S:\efi\microsoft\boot\bcd /set {default} osdevice partition=c:Bcdedit /store S:\efi\microsoft\boot\bcd /set {FWbootmgr} displayorder {Bootmgr} /addfirst
Posted by: SITEL 8 years ago
Purple Belt
0

Hi,

I face exactly the same problem. Deployment crashes when I used "Apply UEFI Partitions" post-install task. Is there an answer?

Thanks

 
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