what's the most meaningful way to go with boot and recovery images? What should/shouldn't one integrate/remove there?

[AlterNate37]

Hi, I'm wondering, because I see that other programs have tools specifically designed to more quickly copy to boot and recovery images the changes made to install.wim
But I don't get it.
Recovery, it kind of makes sense that it also contains the exact same removals and integrations than install.wim, so if something get corrupted later you can reset well.
But boot? Why drivers there? Maybe some specific one for specific cases, but would it make sense to integrate all drivers there too?
If I integrate BT driver in boot.wim do I get BT connectivity for the mouse while installing?
What about updates? Why in the boot?
I don't even understand how's that even possible, afaik they are there only to make the install.wim do its magic.
It's boot. Why would you want to copy the configuration of the removal of services and components in the boot.wim too?

Thanks

[CodingWonders]

But boot? Why drivers there? Maybe some specific one for specific cases, but would it make sense to integrate all drivers there too?
If I integrate BT driver in boot.wim do I get BT connectivity for the mouse while installing?

This is important in the case of third-party disk controllers (aka, those that rely on Intel Rapid Storage Technology (RST) or VMD). That will let you see your disks from within the boot image (Windows PE).

When you install drivers in Windows PE, they are not automatically installed in the installation image. The installer will do the job after you apply it. This is because applying drivers before installing the image involves the following process:

1. Mount the install image
2. Add the drivers
3. Unmount the install image saving changes

Since the Preinstallation Environment is loaded to a RAM disk, this procedure is not very resource-efficient, especially if your computer has low memory (ie, 1 or 2 GB). Sure, you can use a temporary directory on a local disk, but what if it isn't formatted? Or what if the user doesn't want to make changes to their disks? For reasons like those, drivers are only added to the install image after applying it to a disk the user chose.

What about updates? Why in the boot?
I don't even understand how's that even possible, afaik they are there only to make the install.wim do its magic.
It's boot. Why would you want to copy the configuration of the removal of services and components in the boot.wim too?

After applying the installation image, you can keep making changes to it. It's not the most recommended thing, but you can still do it. I would recommend making those changes before installing Windows.

[AlterNate37]

Thanks!

So, if I have 16GB ram, would there be any advantage/benefit in loading all drivers (which I loaded in the install.wim) in the boot.wim?
And, to summarize and be sure that I got you right: there is no advantage whatsoever in integrating updates into the boot.wim, or in applying to boot.wim the same tweaks (removals of components, features etc) done to install.wim?
But it does make sense doing all that to recovery image, because it's what you need to get back to your ground 0 in case of issues, right?
(unless the issues come from some of these tweaks or updates, of course)

[CodingWonders]

So, if I have 16GB ram, would there be any advantage/benefit in loading all drivers (which I loaded in the install.wim) in the boot.wim?

If your computer uses RST or VMD, unless you've disabled it, there will be advantages. Those drivers are more critical than, let's say, a webcam or a printer. Do you need to take photos with your PC in WinPE? No. Do you need to print stuff there? Also no.

And, to summarize and be sure that I got you right: there is no advantage whatsoever in integrating updates into the boot.wim, or in applying to boot.wim the same tweaks (removals of components, features etc) done to install.wim?

You got it right. The other thing is that the Preinstallation Environment works with a different set of packages, which are included in the Windows PE add-on of the Assessment and Deployment Kit (ADK), as part of the Optional Components (OCs). Regular OS updates can still be installed.

But it does make sense doing all that to recovery image, because it's what you need to get back to your ground 0 in case of issues, right?
(unless the issues come from some of these tweaks or updates, of course)

The Recovery Environment (Windows RE) generally stays up to date with the installation image, and generally has the same basic hardware support as the full installation.

[AlterNate37]

Ahhhhh, ok, I think I get it.
So, you say that we only need to integrate in the boot.wim the drivers which are needed for the boot phase.
Which makes sense and I also thought that, but, whatever. I guess I overthought.
I do not use RST. It would be nice to be able to have faster processing but atm I don't even really need it, while I do need separate partitions.
And the only virtual things I have a use for is the Disk Management utility which I've discovered it needs the service Virtual Disk.
I am still trying to understand if the Memory Integrity option in Defender is worth the extra usage of resources. It's basically the only virtual thing running on my OS afaik. But I do disable all "not VBS related" Hyper-V options, as also UE-V, App-V etc.

I will have to ask the NTLite guys why they offer the possibility to clone onto WinRE all the changes made to install.wim if like you said it's done automatically anyway.
But what happens if I do it? If FOMO takes over and I check all those little tempting boxes and copy to WinRE all what I did to install.wim?

Regular OS updates can still be installed.

And what is the advantage of integrating regular OS updates to the Windows PE and/or Windows Setup boot images instead of only to install.wim?

[AlterNate37]

I don't find the new release.
I see that you did something 2 hours ago but I only find a release of 2 weeks ago in the downloads.
Sorry, I get a bit confused with the UI/UX of Github, it's very, hmmm, IT :)

And if you answer my last reply to that other discussion, I can complete the ISO and install Windows and try DISMTool on a fresh installation without whatever I did wrong in this one.

While you take your time I have a look at the packages thing.

[CodingWonders]

It will come tomorrow. FYI, write replies instead of answers

[AlterNate37]

I don't know if you noticed my now deleted reply, but sorry, I got confused, I thought we were in the other thread about the bug!
That's why I said "I don't find the new release".

What did YOU mean with tomorrow? The release that you wanted me to try?
Or your answer here?

So, tbc, when I wrote "if you answer my last reply to that other discussion" I actually meant THIS discussion, because I thought we were in the other one :D

And I refer to the (I promise, LAST) questions:

• why would someone offer the possibility to clone onto WinRE all the changes made to install.wim if like you said it's done automatically anyway.
• what happens if I do it? If FOMO takes over and I check all those little tempting boxes and copy to WinRE all what I did to install.wim?
• -what is the advantage of integrating regular OS updates to the Windows PE and/or Windows Setup boot images instead of only to install.wim?

[CodingWonders]

What did YOU mean with tomorrow? The release that you wanted me to try?

The release (Preview 4).

why would someone offer the possibility to clone onto WinRE all the changes made to install.wim if like you said it's done automatically anyway.

No idea

what happens if I do it? If FOMO takes over and I check all those little tempting boxes and copy to WinRE all what I did to install.wim?

Same as the previous question.

what is the advantage of integrating regular OS updates to the Windows PE and/or Windows Setup boot images instead of only to install.wim?

You could provide your WinPE image with security fixes.

[AlterNate37]

NOTE: I'm NOT asking "and why do I even need security fixes during the installation?".
I am NOT asking it because:

• I said that those were my last questions
• I realize that in MY case (single PC, at home, personal use, no networking, no dev stuff) it seems useless because I install Windows offline (I select Rufus' option to skip the online OOBE thing, and I only go online after I check that all is how I wanted), but maybe other people who install the OS while connected to a network might need security fixes in the boot images.

I'll live with the mystery, despite my need to make sense of everything.
Cheers, thanks.