In any case, you're probably right about a VHD/img being a better. And if I'm not mistaken, doesn't Windows To Go (now unsupported) just take an install.wim and make it bootable from external media? And, the name of the wimboot program itself would seem to imply that it's possible to boot an install.wim.Ĭan someone else independently confirm that there either is or isn't an official or unofficial way to boot an install.wim? And I could swear reading elsewhere that W10 actually supports this. I have searched Google and seen reports of people booting an install.wim. I just love it when people make statements but then don't bother providing an explanation to back up their statement.
Msmg toolkit vs ntlite how to#
That's pretty much what I'm aiming at, but I need ideas on how to proceed.Īs to your 1st statement.WHY NOT?.explain. Use an external bootloader like G4D to boot this recovery environment, which is actually a fully installed Windows, but portable and self-contained Capture this VM installation into an ISO/WIM/VHDĥ. Without it being integrated, I can't encrypt/decrypt other volumes.Ĥ.
Msmg toolkit vs ntlite driver#
DiskCryptor, like pretty much every FDE solution out there, requires a disk filter driver to be installed, and this driver needs a reboot to take effect.
Msmg toolkit vs ntlite install#
Install all the essential softwares I would need, to be able to recover my primary Windows installation. Customize a Windows 10 ISO with something like NTLite or MSMG Toolkit, to strip out as much as much unnecessary BS as possibleģ. So the plan is this (not yet finalized and open to revision):ġ. Booting externally from USB is just going to slow down the booting process, they (external HDDs or flash drives) cant compete with an SSD's disk access speed/boot speed. I would want to have this stored in a separate partition on disk for fastest booting, I have 3 NVMe SSDs and 2 SATA SSDs, all internal. Ideally contained within an ISO, WIM file, or VHD/IMG, which I could boot either as a filedisk or ramdisk with G4D/SVBus. It would essentially act as an onboard recovery solution. I've gradually come to the conclusion that having a portable, fully deployed and ready-to-use alternate Windows 10 is the way I want to go. I've considered WinPE, BartPE, WinBuilder, probably I missed something along the way. Getting to it, I now need to devise some kind of personalized recovery solution that I can boot in an emergency. As the old adage goes, anything that can go wrong, eventually will. Without those, you're fucked if and when the shit hits the fan. Anyone that has used an FDE solution in the past, already knows the importance of having a sound backup/recovery strategy. However, I don't want to fully commit to it yet. I just had too much trouble getting a BCVEed Windows 10 to boot within a G4D/SVBus-controlled VHD, and I was never able to get BCVE to stop overwriting GRUB4DOS. Furthermore, it is fully compatible with dualboot scenarios. And it has a fully portable bootloader that doesn't have to reside in any MBR (ISO boot). After years of development inactivity, it has recently been taken over and updated (some months ago) by a guy named David Xanatos, and now it includes full UEFI/GPT support as well, even Secure Boot if you're willing to use a Linux-based intermediary shim loader. I've recently decided to ditch BestCrypt Volume Encryption and return to my old favorite FDE solution, DiskCryptor.
0 kommentar(er)
