Windows 10 not booting after deployment - schema file related



  • I have created an image and uploaded to the server, once I tried to deploy the image, windows 10 was not booting. Upon checking the schema file on the server, comparing to the working image, I found that there was a slight difference.

    Not working schema has this line which appears the \EFI... twice in the line.
    [code]"efibootloader":"\EFI\Microsoft\Boot\bootmgfw.efi EFI\Microsoft\Boot\bootmgfw.efi","volumegroup": { }[/code]

    Comparing to the working schema file, the \EFI.. line only once, so I deleted the second part of it as it becomes like this:
    [code]"efibootloader":"\EFI\Microsoft\Boot\bootmgfw.efi","volumegroup": { }[/code]

    Then redeploy the image, results that Windows 10 was booting ok. Attached is the non working schema file.

    It puzzles me that the schema file was created during the upload process, but why does it make the \EFI.. appears twice, and deleting the second part makes it work.

    Your help needed. Thank you.



  • What version are you using? Can you attach the entire upload log?



  • I am using CloneDeploy 1.2.0, installed on a windows 10 machine as the server. Client boot method using USB. Image environment Linux and type was Block.

    Thank you.



  • I have reviewed your log and discovered the issue. There are 3 nvram entries pointing to the same guid.
    [code]Windows Boot Manager HD(2,GPT,bd008587-c373-462c-bb50-bd0742da0e26,0xe1800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................

    Windows Boot Manager HD(2,GPT,bd008587-c373-462c-bb50-bd0742da0e26,0xe1800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................

    UEFI: Hard Drive, Partition 2 HD(2,GPT,bd008587-c373-462c-bb50-bd0742da0e26,0xe1800,0x32000)/File(EFI\Microsoft\Boot\bootmgfw.efi)..BO[/code]

    You can see that there are 2 entries with \EFI\Microsoft\Boot\bootmgfw.efi but then there is also a 3rd with EFI\Microsoft\Boot\bootmgfw.efi, this entry is missing the first . Since the first two are identical clonedeploy only selects 1, but since the 3rd is slightly different it throws everything off. I will release a patch to address this.



  • Was this fixed in 1.2.1? I am having the same problem. Thanks in advance!



  • No this was just discovered. Will be in 1.2.2