EDIT: I might be barking up the wrong tree here. I see that I have gotten off track again and confused you with WIMB. I remember now that it was WIMB That came up with the VHD_WIMBOOT package...so maybe I should be asking him instead? I apologize... I lost track of who was who. I have had some starts and stops in working on this with some time elapsed in between.
alacran: Would you help me consider a slight variation and how to handle it?
I already have an existing VHD that I boot up into Hyper V. It has all the customizations (and it has SVBUS installed with the test mode signing / disable integrity checks, disabled pagefile / disabled hiberfile already built into it). I was able to mount it and I have completed the first capture of the capt_f.wim file from this VHD. It is a fresh install of Windows 10 that is fully updated. This is the same VHD that I use as part of a Windows 10 RAM Boot. So, my goal here is to take an existing ram bootable image and wanting to convert it into a VHD + WIM RAM Bootable.
As I am working through the VHD_WIMBOOT.pdf I am at the step where I use my captured .wim file from the full Windows 10 Install. I'll be feeding that WIM file into WinNTSetup to install this customized version to a new 2GB file with wimboot enabled. Here is where I have a problem I'd like help with: I believe the WinNTSetup wants to modify my boot loader under "Select location of the Boot drive". I don't want to modify the bootloader of my computer. I already have an external drive that is setup with Grub4DOS. So, once I get a VHD and WIM "set" I should be able to add it to my existing Grub4DOS bootable drive.
My ultimate goal is to end up with a VHD file that I can ram boot from the Grub4DOS bootloader that referemces the wimboot file. So my goal is similar to yours, but I am trying to get there through a path that doesn't involve me changing the bootloader on my existing computer.
To boot up the 2GB VHD file and complete the setup, I should already have SVBUS baked into it...so I should be able to boot it as the FileDisk straight from the Grub4DOS external drive.
Do you mind helping me work through this variation? I know it is a deviation from the way you presented it, but I think it has value. At the end of this, if successful, I should be able to provide some useful input on how to do all of this through HyperV. It may or may not be clear what the benefit of this would be, so let me just add that by using HyperV to create all of this it makes testing changes to the image / adding updates and much more far easier. I've already been testing a SVBUS RAM Disk bootable image from HyperV quite a bit and have had a great time working with it. The revision process is far easier this way and if I break my image, I can easily restore a previous version with a single file copy operation or extraction from an archive.
EDIT #2: I went ahead and went to the next Setup screen after selecting my local boot drive and tried choosing "do nothing" from the drop down list. I really don't want to mess with my running system. I'd like to get it all booting under HyperV and/or the Grub4DOS disk. I hope I am on the right track.
Edited by quarky42, A week ago.