VHD_WIMBOOT - Apply and Capture of WIM Files for OS in VHD

wonko, we r talking megabytes. we do not have such sizes. at least not yet. wimb only wanted to know whether it booted, as little as that.

Sure, I know , but I am looking forward, it was only a preventive Q&A.

Wonko

Happy Easter to u and everyone,

for wimb's info, i use iastor(something.sys), it must be the same as his only my system calls it that. i did not choose the driver, the system did.

Sorry to be changing the subject a little bit, but I am sure this new discovery of mine will certainly interest alacrán. I have just discovered I should be named Mr. Fuffa (wonko knows what I mean), or if our international friends like it better, I will call myself Mr. Fluff. Ya' guys cannot imagine how much fluff I have managed to eliminate from ... Programs and Features in the control panel. I used to enable all the stuff there was. Now I have realized that most of it is unneeded, so this would be good for Alacrán to shrink his vhd's even further. I will surely be able to tell u whether there is a significant gain in booting time as well. But since alacrán set such great store by size, I can tell u I've gotten hold of an executable called compact+lzx.exe, which reduces used space on c:\ (it automatically compacts and compresses c:\ files and folders as soon as u launch it).

nino

You mean this approach?

https://winaero.com/...thm-windows-10/

Now seemingly bettered:

http://forum.noteboo...dows-10.809809/

https://github.com/I...actGUI/releases

It is very Windows-10-only, though some good soul made a version of the command line for 8.x (just in case):

https://wimlib.net/f...topic.php?t=351

Wonko

The Compact (XPRESS 4k is the default) install is available and "exclusive" to 10 since first version, but WinNTSetup let you install in Compact mode XPRESS 4k, XPRESS 8k, XPRESS 16k or LZX from 7 to 10 since long time ago, in fact I have tried it on 7 about 2 years ago.

That tool mentioned by Wonko CompactGUI.exe is only a GUI for Win10 Compact.exe (do not work on previous versions like 8.x or 7), it seems nice but nothing you can't do on a short command line.

No news here.

i mean neither.

i mean neither.

WofCompress tool for Win7 to win10 from JFX:

http://reboot.pro/to...for-win7-win10/

I don't think there is something better and also compatible with WinNTSetup.

alacran

Update VHD_WIMBOOT Version 2.0

- Solution for missing file Boot\bootvhd.dll in case Boot Manager BCD menu was made earlier by MediaCreationTool

File Boot\bootvhd.dll is essential to make the VHD entry appear in BIOS Boot Manager menu.

Download:  VHD_WIMBOOT - Encrypted with password =  bootwimb

Update VHD_WIMBOOT Version 2.1

- VHDX file support useful only for booting as WIMBOOT FILEDISK and Not as RAMDISK, since Grub4dos does not support VHDX files

- Update to wimlib-1.13.1

- Update to grub4dos-0.4.6a-2019-06-17

- Added SVBus signed x64 driver from here made by Yamingw given by tinybit

- Update of VHD_WIMBOOT.pdf Manual with UEFI VHDX WIMBOOT as personalised Standard Operating System

Download:  VHD_WIMBOOT and 

UEFI VHDX WIMBOOT personalised Operating System in 25 GB Fixed VHDX on Internal SSD booting as FILEDISK

==  ==  == 

3.9 GB Expand VHD WIMBOOT on USB Portable SSD for booting from RAMDISK using Grub4dos Menu and SVBus driver

== 

It would be interesting to have a comparison of VHD vs. VHDX format (one made by someone with some common sense, I mean  ).

The web is full (really full) of senseless blogs/posts revolving around this concept:

The new VHDX format is better, really better than the old VHD, it has in fact MANY advantages:
1) Size limit 64 TB instead of only 2 TB
2) 4K block size, which aligns well with modern hard drives (3TB+) which also use 4KB internally
3) Live resize of virtual disks
4) insert here some senseless stuff
5) insert here some more senseless stuff
6) and insert here even more senseless stuff

Now, of the above three non-meaningless features, #2 is pure bullshit, which leaves us with two very meaningful advantages, #1 and #3, none of which applies to VHD_wimbooting AFAICT.

And - just in case someone would come out again (set aside VHD_wimbooting) with dynamic VHD's or VHDX's (and their advantages) - this is recommended reading:

http://hyper-v-backu...dx-performance/

Wonko

It would be interesting to have a comparison of VHD vs. VHDX format (one made by someone with some common sense, I mean  ).

 

Microsoft is giving info about VHDX and Native Boot

Native boot for Windows 10 requires the .vhdx format, not the .vhd format.

Personally I have never experienced any difference in functionality of VHD and VHDX for booting from USB.

But the only limitation is that Grub4dos needs VHD, since Grub4dos does Not support booting with VHDX from RAMDISK

I have used VHDX format for UEFI VHDX WIMBOOT using 25 GB VHDX as personalised OS booting as FILEDISK from Internal SSD (this is my OS now )

And I have used VHD for booting from USB Portable SSD using 3.9 GB VHD booting with Grub4dos from RAMDISK.

You mean that the good MS guys intentionally crippled Windows 10 in such a way that it cannot anymore boot natively from VHD?

(TP could just fine):

https://www.wintelle...iew-from-a-vhd/

Not exactly the people with common sense I had in mind.

Wonko

Personally I have never experienced any difference in functionality of VHD and VHDX for booting from USB.

But the only limitation is that Grub4dos needs VHD, since Grub4dos does Not support booting with VHDX from RAMDISK

 

This was the common sense ....

Also AFAIK size limit for a VHD is 2 TB, so unless you need a virtual disk bigger than 2 TB I don't see any need for a VHDX, wich as already mentioned is not grub4dos compatible.

 

Native boot for Windows 10 requires the .vhdx format, not the .vhd format.

Win10 runs perfectly fine from a VHD, that comment about native boot is just BS.

alacran

This was the common sense ....

Well, no, maybe it is, but it is not clear enough.

Either:

1) windows 10 (current version) can still boot "natively" from VHD  (and the good MS guys are lying)

or

2) it does not (and the good MS guys are telling the truth and intentionally removed the feature)?

As Alacran just confirmed, the 1st one is seemingly correct and you should have thus posted:

 

Microsoft is giving FALSE info about VHDX and Native Boot

 

or maybe alacran is talking of non-native booting?

Wonko

From my statement I think it is clear that Microsoft might have given FALSE info about VHDX as that it should be required for Native Boot ....

This topic proves that Windows 10 Native Boot from VHD is working OK   

Nevertheless I think it is good that VHD_WIMBOOT program is capable to do CAPTURE of VHDX files, since they exist .....

Well this is not the first time we get wrong/false info from MS, I remember when Wimboot just started on Win 8.1 Update 1, MS said it was only possible to make Wimboot installs on SSD or eMMC drives, see:

 

• WIMBoot is available only for UEFI-based PCs running in UEFI mode (legacy BIOS-compatibility mode isn't supported).

• WIMBoot is supported for solid-state drives and eMMC (Windows HCK compliant) drives. WIMBoot isn't supported on traditional drives that contain rotational components, or on hybrid drives that contain both solid-state and rotational drive components. WIMBoot works by taking advantage of the capability of solid-state drives to access different areas of the hard drive quickly.

Source: https://docs.microso...94399(v=win.10)

Actually we already know since the tests we made (erwan.l, misty and myself) on those times (http://reboot.pro/to...e-boot-wimboot/), this is totally wrong/false.

And we can make Wimboot installs on PCs MBR and UEFI and in any internal/external physical mass storage or virtual device capable to support an standard install.

alacran

Hello guys!

I have successfully setup a RAMDISK booting device that works perfectly. GRUB4DOS with menu.lst

My problem is that I need to run this boot sequence without having installed any graphics adapter on my system because it is going to run only as a server.

As soon as the Graphics adapter is installed, everything works fine. Unplugging the graphics adapter leads to halt of the boot sequence.

Has anybody ever anticipated such a need to boot and work without any graphics adapter installed and with a CPU that does not include any graphics subsystem?

Your reply would be very much helpful!

Hello guys!

I have successfully setup a RAMDISK booting device that works perfectly. GRUB4DOS with menu.lst

My problem is that I need to run this boot sequence without having installed any graphics adapter on my system because it is going to run only as a server.

As soon as the Graphics adapter is installed, everything works fine. Unplugging the graphics adapter leads to halt of the boot sequence.

 

Has anybody ever anticipated such a need to boot and work without any graphics adapter installed and with a CPU that does not include any graphics subsystem?

 

Your reply would be very much helpful!

Mind you the following not necessarily applies to Windows 10 (which I presume is the OS you are trying to boot, but - generally speaking - it could be that you installed the OS (on the image) with the graphic adapter actually plugged in and this "triggered" the install of some driver that - when you remove the graphic adapter - "panicks" and creates the issue.

Loosely, you want to make a "headless install" (if you google for it you will find a number of articles related to different OSes/Install methods) and adapt it to your situation.

A couple of examples:

https://migeel.sk/bl...s-installation/

https://blogs.techne...012-essentials/

There are a lot of variables involved (including EXACT OS, booting method and hardware involved), you should start a new thread listing all the needed details, as it is an "edge" case, not really pertaining to VHD_wimboot (this thread).

Wonko

Update VHD_WIMBOOT Version 2.2

- VHDX disabled in Windows 7 OS, since VHDX is Not compatible with Windows 7

- Improved Tool Tips and WARNINGS regarding Windows 7 Limitations, presence of WOF Driver and incompatibilities of VHDX File Type

- Preset for choice of 25 GB Fixed VHD as FILEDISK (preferred) Or 3.9 GB Expandable VHD for booting with Grub4dos and SVBus driver from RAMDISK

- Solved - Failure in Windows PE to create fresh working Boot Manager on empty disk

- Update of VHD_WIMBOOT.pdf Manual

Download:  VHD_WIMBOOT

sorry wimb, 

I tried ur new version, it promises a filedisk/ramdisk alternative, but after trying both, I do not see any difference in menu.lst, so I still do not understand what the difference is about. Is it only a future promise that is not yet implemented?

nino

@antonino61

It  is just a Preset to get desired values for VHD Type(Fixed/Expandable) and Size(25 / 3.9 GB)

For booting as FILEDISK you want a lot of space to accomodate drivers for new hardware, to allow Windows Update and to add Programs.

FILEDISK is needed as first step and preferred is VHD type Fixed with size 25 GB for booting with Boot Manager Menu.

The menu.lst entry for booting from RAMDISK is also made, but most of us will not have enough RAM

Then After Capture and Apply the WIM file is used to make small VHD for booting from RAMDISK using Grub4dos menu.lst and SVBus driver

For booting from RAMDISK you want size half of the available RAM and 3.9 GB is a good compromise.

Expandable VHD allows to load such VHD fast into RAMDISK.

The Boot Manager entry for booting as FILEDISK is also made, but not so useful since there is limited free space, certainly not enough for Windows Update

Update VHD_WIMBOOT Version 2.3

- Solved - Failure in Windows PE to create Boot Manager on empty disk for case of Windows 7 VHD

Download:  VHD_WIMBOOT

bootmgr file of Windows 7 of 2010-11-21 cannot be used for booting VHDX as WIMBOOT

In Boot Manager Menu you get a WARNING as shown below

bootmgr file of Windows 7 of 2010-11-21 cannot be used for booting VHD as WIMBOOT

In Boot Manager Menu you get ERROR as shown below

The problems can be solved by replacing bootmgr of Windows 7 by recent 2019 Windows 10 bootmgr version