is possible to boot from .AVHD?

#1
Hello folks. I have a question: is there a new version of easybcd letting add a boot entry from a .AVHD file? :scared: cause I did create a VHD, but in order to deploy the image, I need to run sysprep, but if I do so directly from the VHD file, I'd do a virtual machine each time.
Thanks for your help.
Have a good day. :happy:
 
Last edited:

mqudsi

Mostly Harmless
Staff member
#2
Yes. EasyBCD | Add Entry | VHD
 
#3
I can't boot from an AVHD file... just from VHD

Thanks for your answer Computer Guru, but when I try to add a new entry, the only type of file I can use is .VHD and not .AVHD (differential VHD)...
Cuold you help me with this please?... If you have 2 files, a VHD and an AVHD, the only file you can add as an entry is the VHD, but i ran sysprep on the AVHD, in order to deploy it....
:??
 

mqudsi

Mostly Harmless
Staff member
#4
Can you try manually entering the path to the avhd file in the Add Entry section, and see if it works?
 
#5
it doesn't work.. snif snif

:frowning: Hello Computer Guru, Unfortunately it didn't work.

here i'll write the message I got and the settings I have in the bcdedit:

The windows Boot Configuration Data (BCD) store file contains some invalid information

objet GUID {581e1c4c-3ea1-11e0-************-b8ac6f418f27}
Status: 0xc03a000d
Info: The configuration for an element within the object is invalid in the bot configuration data store.

The associated windows Boot loader entry may not be available for selection until the problem is rectified by an administrator.


Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device boot
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {581e1c4b-3ea1-11e0-881a-b8ac6f418f27}
resumeobject {1f8184a2-14de-11df-9734-f08c6d8c50b0}
displayorder {581e1c4b-3ea1-11e0-881a-b8ac6f418f27}
{581e1c4c-3ea1-11e0-881a-b8ac6f418f27}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 10
displaybootmenu Yes
Windows Boot Loader
-------------------
identifier {581e1c4b-3ea1-11e0-881a-b8ac6f418f27}
device partition=C:
path \Windows\system32\winload.exe
description Microsoft Windows 7
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {a650b2e3-3ea4-11e0-908f-806e6f6e6963}
Windows Boot Loader
-------------------
identifier {581e1c4c-3ea1-11e0-881a-b8ac6f418f27}
device vhd=[C:]\disque\T-Images_E1966931-ED28-4A5F-83B5-2F79C3AFEA78.avhd,locate=custom:12000002
path \Windows\system32\winload.exe
description test
locale en-US
osdevice vhd=[C:]\disque\T-Images_E1966931-ED28-4A5F-83B5-2F79C3AFEA78.avhd,locate=custom:22000002
systemroot \Windows
detecthal Yes

thanks for all your help.
have a good day.
 

mqudsi

Mostly Harmless
Staff member
#6
Interesting. Let me look into this and get back to you.