8 replies to this topic

[noel]

hello,

Because my english is so poor, i prefere write a long explanation with short sentences.

 

I create a VM (generation2 with UEFI) in HyperV.
I disable snapshots ( too many issues with the differential file )
I create a VHDX file (fixed size, GPT/UEFI)
I create the two partitions ( ESR fat32 and System ntfs )
I create the BCD for UEFI
I expand my "customised" winpe in the "system" partition with dism /apply....
So, in the VHDX file, i get a winpe in Flat mode.
Start is OK.

Now i install an application which modifies "files, system hive, software hive".
Because Flat mode, files are ok for the next boot.
System hive is easy to backup and to modify for the next boot.
Software hive is easy to backup for the next boot. No possibility to recopy it at this time because the file is locked

Now i need to boot on a second "small" winpe in the same VHDX file for recopying the two saved hives.
I create a new directory "x:\newWinpe" and expand a second small winpe.
I create a new entry in the BCD file for this second small winpe.
After boot, i can choose between the two "Flat" winpe.
I choose the second small winpe.
I can recopy the two hives in the first big winpe.
And now, when i boot on this first winpe, i retrieve the "new" application. And it works well.

 

My question : for the second "small" winpe, i want to use a boot.wim (not expanded) file. How can i modify the BCD file for that?

Thank you to give me some ideas.

[cdob]

You have to add the file boot.sdi too.
This can be different locations, UEFI ESR, \boot\boot.sdi.
Or at the boot.wim folder.

http://diddy.boot-la...#ramdiskoptions

Copy boot.sdi and boot.wim first.
Adjust ramdisksdidevice and ramdisksdipath to existing file layout next.

[wimb]

 

My question : for the second "small" winpe, i want to use a boot.wim (not expanded) file. How can i modify the BCD file for that?

Thank you to give me some ideas.

 

If your FAT32 partition has sufficient size to accomodate your boot.wim file Then

- In Win10 x64 OS mount your VHDX file using double click

- Use UEFI MULTI to make boot entry for boot.wim and boot\boot.sdi file added to FAT32 Boot drive

 

Else

- you can use BOOTICE to make New WIM Boot entry for boot.wim + boot.sdi located in folder on NTFS partition

 

More Info:

[noel]

Thank you for your quick answers. Links are very helpfull.

 

Because of my very poor English, I did not write down all my research or report what I have been manipulating fairly regularly in the last few years. And I understand that they are very difficult for you to invent.

I am familiar with WinPE that I use in various contexts, ISO, Flat, CD/DVD (Ramdisk), USB key/pen, VHD, Hard disk, VM or not....
But this is the first time that I do not find the right solution with this very particular context, VHDX (UEFI/GPT) in a VM with 2 WinPE (one in Flat mode and the other in mode  "boot. wim".

I know how to stay humble and recognize that I don't know much, WinPE is too big a topic for me.

I still have to say that the language barrier is such an obstacle to me that what appears to you simple and obvious is to me as an Egyptian text. That's why I use very little software like grub4dos or others. Please do not hold it against me.

As soon as I can restart my tests (2-3 days), I will post a link here to make available the various bcdedit commands and the associated contents of BCD. Maybe you'll see my mistake?

See you soon

[cdob]

Please, can you post a 'dir boot.sdi' and 'dir boot.wim' ? The result should include boot.sdi and boot.wim.
Is boot.sdi located at the EFI ESR partion, or at another partition?
And post a 'bcdedit.exe /store bcd /enum all' ? (change directory to the bcd file first)

Given that information, it's possible to make a specific suggestion.

[noel]

While I was collecting the information requested by CDOB, I realized that I had renamed  "boot.wim" file to "small-boot.wim".
I'm ashamed not to have checked properly before asking a question.   
 

You found my mistake.  
Thank you for taking time to think and solve my problem.

[sebus]

Just wonder why to go to all these hassle, instead of just mounting vhdx in any available OS (host or attached to another VM)?

Surely would be way easier? Just to copy a single file...

[noel]

Hi Sebus,

last year, I wanted to automate the copying of 2 files in a winpe (the 2 hives system and software). Winpe does not allow the memorization of hives. It's a safety of MS (like restarting after 72 hours). And precisely, I didn't want to use another physical medium to do this copy. Other utilities (modification of ProductOptions, it seems to me but I can not remember the name of the software) uses the same mechanism.
I abandoned this mechanism because the duration of the restarts is too long. And it is true that such complexity can surprise.

Sorry for my poor English ( i use a translator  but sometime it changes the meaning of my point)

[sebus]

You do over-complicate something that is easy