Multiboot Collection Full 7.8 (RUS/ENG)

Additional Information:

Initially, this collection was basically aimed at the ability to install any Windows (from 7 to 11) from one bootable media. Gradually, it acquired additional components.
This collection contains the full version of Full with the latest (at the time of distribution) versions of Live builds and a light version of the MInstAll by Andreyonohov & Leha342 Lite program installation collection
If you do not need all this kit contained in this collection, then you can use the designer Lite version of this collection Multiboot Collection Lite (which in essence is the basis of multiboot media) with the choice of filling it with various assemblies of your choice. For convenience and versatility, the collection can be installed on a USB flash drive with any of the three bootloaders to choose from: BOOTMGR or GRUB4DOS (GRLDR) or XORBOOT.
In each of these menus, it is possible to switch from one menu to another:
Screenshots of BCD, GRUB4DOS and XORBOOT menu

In the GRUB4DOS menu, all commands are written in such a way that if one of these folders with the assembly is deleted from the USB flash drive,
then the command to run this assembly will not be displayed in the GRUB menu (menu.lst).
And vice versa, if you add any of these assembly folders to the USB flash drive, then it will automatically appear in the GRUB menu.

Also in the collection there is an "Application startup menu" (Auto_Menu.exe) - for working with a computer from under the "working system"


Structure of folders/files in the collection and their description:

FOLDERS :

_ISO folder

In the _ISO folder you can place and load your images from it, such as (.iso; .iz; .img; .ima; .vhd (fixed size only); .rhd; .bin; .fir; .wbl) of various LiveCDs and etc. (such as anti-virus utility images, etc.)
Image filenames MUST be in English letters and without spaces!
These images are launched from the Grub4Dos menu, from the menu item: "Auto-menu for launching images from the _ISO folder"
When you click on the menu item: "Running images based on the Linux kernel", the 4th partition of the first disk should not be occupied.
(the first disk at boot time is the one you booted from (hd0,0) - that is, the active partition of the bootable media)
The image is mounted as (hd0,3).
This method is great for downloading Linux-based images.

When you click on the menu item: "Launching images based on the WinPE kernel", it does not matter whether you have the 4th partition of the first disk occupied or not.
Here is another download method. The image is mounted using the FiraDisk driver.
This method is great for downloading WinPE-based images.

PS
If an error Error -60 pops up when starting the image, this means that your image is fragmented
and it must be defragmented using, for example, the WinContig program - (present in the "Application Startup Menu" Auto_Menu.exe)

The _ISO folder can be located on any other (separate from the main assembly) partition of the same disk.
You do not need to duplicate this folder on two sections, otherwise the first folder with the name _ISO will be found and images will be searched for in it.


_VHD Folder

We drop our images (*.vhd) into the _VHD folder and launch it from the Grub4Dos menu from the item: "Load images (*.VHD) from the _VHD folder"
Note:

In the menus, the launch is registered in two ways:
- 1st method: Launch images (*VHD) --> VBOOT (for loading WinXP.VHD images)
- 2nd method: Launch images (*VHD) --> NT6.X (for downloading Win7-10.VHD images)
(for universality and selection of the most appropriate method for a particular image (*.vhd), two methods of loading are proposed).

When you click on this item, a menu for loading images (* .vhd) located in the \ _VHD folder will be created

IMPORTANT!!!
1. Image names (*.vhd) must not contain spaces or Cyrillic characters.
2. Images (*.vhd) must be (MANDATORY!!!) previously defragmented on bootable media (for example, using WinContig).
3. The _VHD folder (with the *.vhd images in it) must be located on the NTFS partition of your bootable media.

PS
The WINXP.VHD image currently in the _VHD folder is a dummy image (example only),
you can safely delete it and put your various images (* .vhd) in the _VHD folder.

The _VHD folder can be located on any other (separate from the main assembly) NTFS partition on the same disk.
There is no need to duplicate this folder on two partitions, otherwise the first folder with the name _VHD will be found and images will be searched for in it.


_WIN folder

The _WIN folder is designed to contain various Windows iso images or installation files (install.wim/*.esd/*.swm) from Windows 7-10 (x86-x64) images with subsequent installation of any of these Windows.

Windows installation is performed by direct launch of the menu item from the section, for example: "Windows 10?64 (22H2_19045) 6in1" - performs a direct launch of the Windows installation from install.esd located in the corresponding (menu item name) folder on the media (\_WIN\1064_22H2) :

...or using the 78Setup utility (by conty9)
...or using the Winst utility (by Ander_73)

...or using the WinNTSetup utility

The _WIN folder consists of 11 subfolders for placing installation files (install.wim/*.esd/*.swm) Windows 7/8.1/10/11 (x32/x64) in them:

The composition of the editions and checksums of the install.esd images included in the collection:

_WIN\7?32 - install.esd Windows 7 (x86) 7in1 Starter, Home Basic, Home Premium, Professional, Professional VL, Ultimate, Enterprise (Version 6.1 OS Build 7601.26564)
CRC-32: dd23d9ee
MD5: 6c9bb568173f908206952e7cd841f721
SHA-1: a2dd9ebf1d520fd0bcf1757154adfa2f911e2215
_WIN\7?64 - install.esd Windows 7 (x64) 6in1 Home Basic, Home Premium, Professional, Professional VL, Ultimate, Enterprise (Version 6.1 OS Build 7601.26564)
CRC-32: 636dccb0
MD5: 293c72b245cc952da2c7041ac41c76e0
SHA-1: 06529d1de386cd81f49ce9b22ba131e9baa6f8b6

_WIN\8132 - install.esd Windows 8.1 (x86) 7in1 Core, Single Language, Professional, Professional VL, Enterprise, Embedded Industry Pro, Embedded Industry Enterprise (Version 6.3 OS Build 9600.21013)
CRC32: bd2d84d2
MD5: 32298a537bc5ea7d13a5dafb790e8c05
SHA-1: a222e37249d81b38a82033202c1cdc2c866e9158
_WIN\8164 - install.esd Windows 8.1 (x64) 7in1 Core, Single Language, Professional, Professional VL, Enterprise, Embedded Industry Pro, Embedded Industry Enterprise (Version 6.3 OS Build 9600.21013)
CRC32: 0aca195a
MD5: 599e16d88eba1ff52b9941c6692006ed
SHA-1: c06d033745e3aef87982d908c6b0dcd9daae9b2d

_WIN\1032_22H2 - install.esd Windows 10 (x86) 6in1 Home, Home Single Language, Education, Pro, Enterprise, Enterprise 2021 LTSC (Version 22H2 OS Build 19045.3086)
CRC32: 12d14e06
MD5: 8f1346dd97892400ef280ecb3c4dcbec
SHA-1: b9703f5ffa2167fc6628a8a479898da6cdcf6f78
_WIN\1064_22H2 - install.esd Windows 10 (x64) 6in1 Home, Home Single Language, Education, Pro, Enterprise, Enterprise 2021 LTSC (Version 22H2 OS Build 19045.3086)
CRC32: 20d7105a
MD5: 440f9d15eab35a99b63dd8042858e3d1
SHA-1: c05e9d71e8cc9780e37b1a3cfe835097a570a371

_WIN\1164_22H2 - install.esd Windows 11 (x64) 6in1 Home, Home Single Language, Education, Pro, Enterprise, IoT Enterprise (Version 22H2 OS Build 22621.1848)
CRC32: 5c30122a
MD5: b532dcff1e1df624866cd01fd3705662
SHA-1: 6414a059a9bbe6e2d6816727eb881b6e1c6a2bd0

What are these images?
Install.esd images of Windows 11, Windows 10, Windows 8.1, and Windows 7 with integrated updates.
The original install.wim Russian versions are taken as a basis.
In all editions of all versions of Windows, the Windows Client Language Pack (en-US) is also integrated,
(which makes it possible to install Windows with an English interface).

Integrated into install.esd Windows 7 images:
Pickup MassStorage, NVMe, USB 3.0/3.1 drivers for Windows 7 (launching SDI during the installation phase, before the second reboot. The filter is configured only to install uninstalled drivers. If the corresponding equipment does not require driver installation, then nothing will be installed).
RunOnce (system startup (single launch)) integrates a script for updating root certificates - CertUpd_by_Ander_73
Integrated USB 3/XHCI Universal Host Driver supporting USB Attached SCSI Protocol (UASP) devices
(Supports USB 3/XHCI host controllers from any manufacturer (USB 3.0/3.1/3.2)).
All "core" updates (via the UpdatePack7 project (by Mazahaka_lab))
Then integrated by means of DISM the monthly cumulative update package.
Integrated stubs from unwanted updates (by_Bifido):
List of updates that will be hidden in the "Update Center":
- KB971033 (Windows 7 activation technology (authentication) check)
- KB2952664 (For upgrading to Windows 10)
- KB3021917 (For upgrading to Windows 10)
- KB3068708 (Telemetry Services)
- KB3080149 (Telemetry Services)
- KB3150513 (For upgrading to Windows 10)
- KB4493132 (Windows 7 End of Support Alerts)
- KB4524752 (Windows 7 End of Support Notice)
- All language packs that are offered by the "Update Center" as optional updates.
Disabled fix Specter and Meltdown
A bypass patch has been integrated (ESU Istaller (by Bifido)) that allows you to suppress the system validity check for the ability to install updates using the Extended Security Updates (ESU) program and continue to install updates in Windows 7 in the future.

Integrated into install.esd Windows 8.1 images:
Pickup of NVMe, RST AHCI RAID, USB 3.0/3.1 drivers for Windows 8.1 (starting SDI during installation, before the second reboot. The filter is configured only to install uninstalled drivers. If the corresponding equipment does not require driver installation, then nothing will be installed).
RunOnce (system startup (single launch)) integrates a script for updating root certificates - CertUpd_by_Ander_73
All "core" updates (via the UpdatePack8.1 project (by Mazahaka_lab))
Then integrated by means of DISM the monthly cumulative update package.
Integrated stubs from unwanted updates (by_Bifido):
- KB2976978 (For upgrading to Windows 10)
- KB3044374 (For upgrading to Windows 10)
- KB3080149 (Telemetry Services)
- KB3150513 (For upgrading to Windows 10)
Disabled fix Specter and Meltdown
.NET Framework 3.5 included

Integrated into install.esd Windows 10 images:
Pickup of NVMe, RST AHCI RAID, USB 3.0/3.1 drivers for Windows 10 (starting SDI during installation, before the second reboot. The filter is configured to only install uninstalled drivers. If the corresponding hardware does not require driver installation, then nothing will be installed).
Updates are integrated exclusively by means of DISM.
Disabled fix Specter and Meltdown
.NET Framework 3.5 included

There are no illegal activations and changes.
All operating systems pass a system integrity check (sfc /scannow).
(In fact, these are original images, only with the latest updates integrated into them as of the release date).

The _WIN folder with subfolders 7?32, 7?64, 1032_22H2, 1064_22H2, 1164_22H2, 8132, 8164 and Windows installation files in them can be located at the root of any partition of any disk.
Note:
This does not mean that you can completely delete the _WIN folder from the boot media, but it means that you can create the _WIN folder in the root of any partition and move only the above subfolders with Windows installation files into it. When you click on the menu item of the Windows installation you need, the required installation file will be searched for all disk partitions connected to this computer.
Starting with Multiboot Collection Full v.6.9, Windows OS installation files (_WIN\*\install.esd) have been moved to the Addons directory. The reason for the transfer is described here: => Multiboot Collection Full v.7.7 (Updatable) [Ru/En]

How to replace install.wim/*.esd/*.swm with another ("your own"):
Extract from your image with Windows 7/8.1/10/11 (x32/x64) from the sources folder the install.wim or install.esd or install.swm file to any of these subfolders (according to the version and bitness). Also add here (if present in the image) the $OEM$ folder and (or) the *unattend.xml answer file (relevant for Windows builds). If you have an answer file (*unattend.xml) and/or $OEM$ folder next to install.wim/esd, you will be able to install Windows using:
Manual installation => (answer file unattend.xml and/or $OEM$ folder are ignored during further Windows installation)
Automatic installation => (unattend.xml answer file and (or) $OEM$ folder are "picked up" during further Windows installation)

The collection has the ability to automatically activate (only when installing Windows in the Automatic installation mode ("using" the $OEM$ folder))
Used activation methods:
Windows 7 (all editions except Enterprise) - activation using Windows Loader 2.2.2 by Daz.
Windows 7 Enterprise - activation using ConsoleAct (KMS activator from Ratiborus)
Windows 8.1 (all editions except CoreSingleLanguage) - activation using ConsoleAct (KMS activator from Ratiborus)
Windows 10 (all editions) - Activation with W10 Digital by Ratiborus - HWID Method (Digital License)

If there is no answer file (unattend.xml) and the $OEM$ folder next to install.wim/esd, the Automatic installation item will be dimmed and unavailable, therefore, further Windows installation can only be carried out using Manual installation

(implementation of conty9, for which many thanks to him!!!) If you have "your" subfolders with "your" names in the _WIN folder, then use the 78Setup utility or the WinNTSetup utility to install Windows.
Using these subfolders (7?32, 7?64, 1032_22H2, 1064_22H2, 1164_22H2, 8132, 8164) as an example, you can add your own subfolders (with their own names) under your Windows distributions. After adding the install.wim or install.esd or install.swm installation file to these folders, in the install.wim.txt or install.esd.txt or install.swm.txt text file, write the name of your installation (optional) to display this name in the 78Setup utility window.
Other installation files install.wim or install.esd or install.swm (which, for example, are located in a completely different folder on a completely different partition or disk) can be selected and launched by pressing a button in the "Select archive manually" utility window.
Also, using the 78Setup utility, it is possible to install Windows from image files (.iso). Add your images to the _WIN or _ISO or 2k10\User.Image folder and these images will be displayed in the list in the utility window.
Other images can be selected, mounted and launched by pressing a button in the Select Image Manually utility window.

Starting with Multiboot Collection v.4.0, the PECMD scripts of the Multiboot Manager menu of each WinPE installer (BOOT*.WIM) are now moved to an external folder (\_WIN\MBOOTMGR_*.wcs)
In order to edit the Multiboot Manager menu for yourself, it is now enough just to open \_WIN\MBOOTMGR_*.wcs using any text editor and edit the required menu item.

An example of a menu item with decoding:
ITEM -font: 13 Win10?64_22H2, L555T255W320H25, Windows 10?64 (22H2_19045) 6in1, CALL StartS 1064_22H2, %CurDir%\UTILITES\Icons\SETUPWIN_10.ico

ITEM - button
-font: 13 - font size of the displayed menu item name
Win10?64_22H2 - unique button name (identifier)
L555T255W320H25 - button location and size in the window L (left) T (top) W (button width) H (button height)
Windows 10?64 (22H2_19045) 6in1 - button display name
CALL StartS - call the subroutine StartS (the block of commands in the subroutine starts with _SUB and ends with _END)
1064_22H2 — name of the folder (accepted value of the %MM% variable) in which the installation file will be searched (install.wim/esd, $OEM$, *unattend.xml)
%CurDir%\UTILITES\Icons\SETUPWIN_10.ico - path to the icon displayed in the menu item (\_WIN\UTILITES\Icons\SETUPWIN_10.ico)

Note :
Using the (x86) bootloader, Windows of any bit depth is installed from any subfolder (in Legacy BIOS boot mode)
Using the (x64) bootloader, you can only install (x64)-bit Windows (both in Legacy BIOS boot mode and in EFI / UEFI boot mode)

Windows installations are launched from the BCD menu of the collection


_WINBOOT folder

This folder describes how to install bootloaders (BOOTMGR or GRUB4DOS (GRLDR) or XORBOOT):
In the _WIN\BOOT folder (in each corresponding subfolder) there is a text file READ!!!.txt and screenshots with a detailed description and demonstration of actions.
Also in this folder (_WIN\BOOT) there are "crutches" (2K10.LDR, AWBL.LDR, PASS.LDR, PE10_X1.LDR, SSTR.LDR, etc.) for running these assemblies (MultiBoot 2k10, AntiWinBlock WinPE, BootPass, Win10PE by Xemom1, Boot USB Sergei Strelec, etc.) from the BCD menu of the collection.
The launch of collections is specified in the _WIN\GUEST.INI file, which makes it easy to add/remove menu items to the main BCD menu of the collection.
Unnecessary (unused) items in the BCD menu can be commented out with a semicolon ";" in the GUEST.INI file and after that they will not be displayed in the BCD menu.
As an example, the Win10PE by Xemom1 build line is commented out in GUEST.INI
; C:\_WIN\BOOT\PE10_X1.LDR="Win10PE by Xemom1 (BCD-menu)"
If you uncomment this line (removing the semicolon character; at the beginning of this line, then after that this item will be displayed in the main menu of the collection:

By the same principle (according to the examples in GUEST.INI), you can add your own launch items for various assemblies to the BCD menu of the collection.
"Crutches" for running various assemblies can be easily created using the XB Plus utility (from conty9)
... or create "crutches" based on GRLDR (the method is described in the second post of the topic under the spoiler: An example of creating a "crutch" based on GRLDR)


_WINBOOTDOS folder

This folder contains a set of utilities for working in DOS mode.
These are utilities for working with a hard disk, its recovery, diagnostics, partitioning and formatting,
diagnostic utilities for all computer nodes, file managers, network utilities,
tools for bypassing and unlocking Windows and Linux system passwords, as well as many others.
The launch of DOS utilities is registered in all menus (in Grub4DOS, BCD and in XORBOOT)


_WINXP folder

We drop our Windows XP images into the _WINXP folder and launch it from the Grub4Dos menu item: "Windows XP installation menu from the _WINXP folder".
This item will take you to the Windows XP installation menu from your images (.iso) located in the _WINXP folder.
From the images (.iso) located in the _WINXP folder, an auto-start menu will be created with a choice to install Windows XP from the image you need.
Windows XP is installed in two steps.
We go into the Grub4Dos menu of our flash drive and click on the menu item: "Windows XP installation menu from the _WINXP folder".
Next, click on the menu item: "1. Installing Windows XP from an .ISO image (first stage) "- (click this menu item and select the desired image to install and run it)
More MUST!!! after the first reboot, again go to the Grub4Dos menu of your flash drive, click on the menu item: "Windows XP installation menu from the _WINXP folder".
Next, click on the menu item: "2. Completing the installation of Windows XP (second stage) "- Select the same image as in the first stage of the installation and press Enter.
All! ... we sit, smoke, control the further process of installing Windows.
IMPORTANT!!!
1. The names of images (.iso) should not contain spaces and Cyrillic.
2. Images (*.iso) must be (MANDATORY!!!) previously defragmented on bootable media, for example, using WinContig - (present in the "Autorun Applications Menu" Auto_Menu.exe).
3. The disk partition on which you will install Windows XP must have the "active" status.
4. If Windows XP images are loaded from an external USB-HDD, then it is advisable to pre-integrate the Firadisk driver into Windows XP images using the FiraDisk_integrator.exe script (otherwise, when loading the image, there may be a BSOD), as well as (if necessary) AHCI -driver using MassStor-x86.exe or MassStor-x64.exe script
Read the details in the text file READ!!!.txt in the folder: _WINXP\FiraDisk_integrator.

PS
The WINXP.ISO image currently in the _WINXP folder is a dummy image (example only),
you can safely delete it and put your Windows XP images in the _WINXP folder.

The _WINXP folder can be located on any other (separate from the main assembly) partition of the same disk.
There is no need to duplicate this folder on two partitions, otherwise the first folder with the name _WINXP will be found and images will be searched for in it.


Folder 2k10

The folder is designed to contain the collection 2k10 Live - 2k10 Live 7.40 (official build version)
...or MultiBoot 2k10 Unofficial - MultiBoot 2k10 7.37 Unofficial [Ru/En] (unofficial build version)

In order to use this build (here 2k10 Live [Ru/En])
copy the 2k10 folder from the Addons folder to the root of your flash drive

The launch points for the 2k10 Live assembly are registered both in the main BCD menu, and in the EFI-BCD menu, and in the Grub4Dos menu of the Multiboot Collection.
In order for the menu item to launch the 2k10 Live build to be displayed in the BCD menu of the Multiboot Collection,
open the file \_WIN\GUEST.INI with any text editor and uncomment the line in it:
; C:\_WIN\BOOT\2K10.LDR="MultiBoot 2k10 (BCD-menu)"
or
; C:\2k10\GRUB4DOS\GRLDR="MultiBoot 2k10 (Grub4Dos-menu)"
(that is, remove the semicolon character (;) at the beginning of the line)

In the GRUB4DOS menu, the command to start the assembly is written in such a way that if the folder with the assembly is deleted from the USB flash drive,
then the command to run this assembly will not be displayed in the GRUB menu (menu.lst).
And vice versa, if you add an assembly folder to the USB flash drive, then it will automatically appear in the GRUB menu.

When updating a build on a tracker, all you need to do is:
1. Delete the old version of the assembly on your flash drive (folder 2k10)
2. Download the new build image, open it in UltraISO, and extract only the 2k10 folder to your flash drive
3. Everything is ready!

PS
If you do not need this assembly, you can not download this folder (Addons \ 2k10) from this distribution.


ACRONIS folder

The folder is designed to contain the collection of ACRONIS products.
* To add this compilation to your bootable media:
1. Copy the ACRONIS folder from the Addons folder to the root of your bootable media.

In the GRUB4DOS menu, the command to start the assembly is written in such a way that if the folder with the assembly is deleted from the USB flash drive,
then the command to run this assembly will not be displayed in the GRUB menu (menu.lst).
And vice versa, if you add an assembly folder to the USB flash drive, then it will automatically appear in the GRUB menu.

* To remove any individual product:
1. Delete the folder corresponding to the product (see the folder designations in the text file ACRONIS\READ!!!.txt)
2. Delete the entry corresponding to the product in ACRONIS.LST (this item is optional, but at your discretion, since after deleting any folder with any product, the command to launch this product will not be displayed in the GRUB4DOS menu).
The assembly is started only from the GRUB4DOS menu.
For complete information on the ACRONIS collection, see the text file READ!!!.txt in the \Addons\ACRONIS folder

PS
If you do not need this assembly, you can not download this folder (Addons \ ACRONIS) from this distribution.


EFI folder

The collection has support for booting in EFI / UEFI mode
BCD-EFI-x64-menu:

BCD-EFI-x32-menu:

Starting with version 5.8, the UEFI boot mode has been added as an additional EFI bootloader - rEFInd.
rEFInd-menu:

By default, there is a standard efi bootloader from Microsoft (for seamless use of EFI boot with the Secure Boot option enabled).
To install the rEFInd bootloader, run the \EFI\install_refind.cmd script.
To get back the standard Microsoft efi bootloader, run the \EFI\install_MS_EFI.cmd script.
PS
When using the rEFInd bootloader, you must disable (in the BIOS settings) the Secure Boot option.

Note :
To boot in EFI / UEFI mode, the partition on your flash drive with the EFI folder present on it must be in FAT32 format
To boot WinPE 7?64 in EFI / UEFI mode, disable the Secure Boot option in your BIOS settings (WinPE 7?64 simply will not boot with this option enabled)


Folder My_Files

A folder for the user's personal files and launching some of these programs from the "Application Startup Menu" (Auto_Menu.exe)


SDI_Update folder

Folder for a collection of drivers.
Due to the fact that the developer of the Snappy Driver Installer (SDI) program, BadPointer, has ceased its activities regarding the further development of the program, now other (no less respected) developers support the further development of the program:
- Snappy Driver Installer - (development of the program and driverpacks is supported by SamLab)
.or
- Snappy Driver Installer Origin - (program development supported by Glenn Delahoy, SamLab driver packs)

Starting with Multiboot Collection v.3.0, instead of a lightweight driver collection (as it was in previous versions of Multiboot Collection), there will now be a shell for separate work with any of the two versions of the SDI program with a common set of driver packs, updating the programs themselves, updating drivers and cleaning them.
This version of the shell was provided by a respected wadimus for which many thanks to him !!!
(I slightly edited the shell "for myself", ... but I think he does not mind).

- Run the file drivers.exe - Runs a GUI shell.

- Item "Download / Update Snappy Driver Installer (SDI)" - The software packages of the two editions of SDI (from SamLab and from Glenn Delahoy) will be updated (or downloaded).
- Item "Download / Update driverpacks" - One (for two editions) set of driverpacks (from SamLab) will be loaded into the Drivers directory in the mode of updating driverpacks from the program.
- Item "Delete obsolete driverpacks" - Removes obsolete driverpacks from the Drivers directory if new versions are loaded.
- Item "Snappy Driver Installer (SamLab)" - Launches the Snappy Driver Installer in SamLab edition.
- Item "Snappy Driver Installer Origin (Glenn Delahoy)" - Launches Snappy Driver Installer Origin as revised by Glenn Delahoy.
- Item "Convert SDI to Lite version (Lite)" - Removes 17 driverpacks from the Drivers directory.
(You can see the list of driverpacks that will be removed in the text file \SDI_Update\READ!!!.txt)

Note:
If you already have current driverpacks, you can place them in the Drivers directory (so as not to download them again from the shell itself)
The SDI_Update folder with a collection of drivers can be located at the root of any other disk/partition.
When you start the collection from Auto_Menu, the script is launched and a search is carried out by all letters of the disk partitions for the presence of the SDI_Update folder in the root.
At the first detection, it launches \SDI_Update\drivers.exe in this folder, which launches the collection shell.
The collection is launched from the "Application startup menu" (Auto_Menu.exe):

PS
If you do not need this assembly, you can not download this folder (SDI_Update) from this distribution.


SMBB folder

The folder is designed to contain the collection AllWinUSB by SmokieBlahBlah - AllWinUSB Constructor by SmokieBlahBlah 20.09.2021 [Ru/En]

To use this compilation, download and copy only the SMBB folder (from the Components folder of the AllWinUSB by SmokieBlahBlah compilation) to the root of your bootable media.
The launch items for the Windows collection from SmokieBlahBlah are registered both in the main BCD menu, and in the EFI-BCD menu, and in the Grub4Dos menu of the Multiboot Collection.
In order for the AllWinUSB by SmokieBlahBlah launch menu item to be displayed in the Multiboot Collection BCD menu, open the \_WIN\GUEST.INI file with any text editor and uncomment the line in it:
; C:\_WIN\BOOT\SMBB.LDR="AllWinUSB by SmokieBlahBlah (BCD-menu)"
(that is, remove the semicolon character (;) at the beginning of the line)


Software folder

The folder is intended for placing in it a collection of programs with automatic installation:
— MInstAll by Andreyonohov & Leha342 Lite — https://softpilot.win/viewtopic.php?t=31649 — (lite version)
You can download the full version of this collection here (ISO): MInstAll v.20.02.2022 By Andreyonohov (ISO) [Ru]
or here (Unpacked): MInstAll v.20.02.2022 By Andreyonohov (Unpacked) [Ru]

To use this collection
copy the Software folder from the Addons folder to the root of your flash drive / USB-HDD
The collection is launched from the "Application startup menu" (Auto_Menu.exe)

Note:
The Software folder with a collection of programs in it MInstAll By Andreyonohov & Leha342 can be located at the root of any other disk/partition.
When you start the collection from Auto_Menu, the script is launched and a search is made by all letters of the disk partitions for the presence of the Software folder in the root.
At the first detection, it launches \Software\MInstAll\MInst.exe in this folder, which launches the collection of automatic installation programs.

How to replace this collection of programs with an updated version?
Your actions:
1. Delete the MInstAll folder from the Software folder
2. Download the new collection MInstAll By Andreyonohov & Leha342
3. Open the MInstAll By Andreyonohov & Leha342.iso image (for example, using UltraISO) and extract the MInstAll folder from this image to the Software folder on your flash drive (Actions / Extract)
4. That's it, you can then launch the collection from: "Application startup menu" (Auto_Menu.exe)

PS
If you do not need this assembly, you can not download this folder (Addons\Software) from this distribution.


SSTR folder

The folder is intended for placing the WinPE Sergei Strelec assembly in it - https://sergeistrelec.ru/winpe_10_8/

To use this build,
copy the SSTR folder from the Addons folder to the root of your flash drive

WinPE assembly launch points Sergei Strelec are registered both in the main BCD menu, and in the EFI-BCD menu, and in the Grub4Dos menu of the Multiboot Collection.
In order for the menu item to launch the WinPE assembly Sergei Strelec to be displayed in the BCD menu of the Multiboot Collection,
open the file \_WIN\GUEST.INI with any text editor and uncomment the line in it:
; C:\_WIN\BOOT\SSTR.LDR="WinPE Sergei Strelec (BCD-menu)"
(that is, remove the semicolon character (;) at the beginning of the line)

In the GRUB4DOS menu, the command to start the assembly is written in such a way that if the folder with the assembly is deleted from the USB flash drive,
then the command to run this assembly will not be displayed in the GRUB menu (menu.lst).
And vice versa, if you add an assembly folder to the USB flash drive, then it will automatically appear in the GRUB menu.

When updating a build on a tracker, all you need to do is:
1. Delete the old version of the assembly on your flash drive (SSTR folder)
2. Download the new build image, open it in UltraISO, and extract only the SSTR folder to your flash drive
3. Everything is ready!

PS
If you do not need this assembly, you can not download this folder (Addons \ SSTR) from this distribution.


USER_MENU folder

In the USER_MENU folder, drop your Grub4Dos menus (* .lst)
The encoding of these *.lst must be in UTF-8 (with or without BOM - it doesn't matter)
The list of these *.lst is loaded from the Grub menu, from the item: "Loading "guest" menu.lst from the USER_MENU folder"
(you can then call this item in the root menu.lst, as you prefer, I couldn't think of anything smarter)
For example, I threw it into the USER_MENU --> menu.lst folder from various assemblies and simply renamed them (* .lst) in accordance with the assembly.


FILES :

File Auto_Menu.apm

Editable file "Application autorun menu".
If you need to edit this menu "for yourself" or add / remove applications to launch from this menu, then:
1. Install the AutoPlay Menu Builder program on your computer - AutoPlay Menu Builder Business 8.0 build 2459 (DC 21.08.19) RePack (& ​​Portable) by TryRooM [Multi/Ru]
2. Run the program and open the Auto_Menu.apm file for editing (File / Open)
3. Well, and then, I hope, you will figure it out yourself, ... it's not difficult there. Replace applications, duplicate buttons, add, remove, ... in general, as you please.


Auto_Menu.exe File

Executable file "Application Autorun Menu".


BOOTMGR FILE

BOOTMGR FILE
BOOTMGR Boot File
The BCD menu of this bootloader is located in the _WIN folder
If necessary, you can edit this menu using the BOOTICE program


GRLDR file

GRUB4DOS Boot File
The menu of this bootloader (menu.lst) is located at the root of the flash drive
You can edit this menu by opening it with any text editor (e.g. Notepad, Notepad++ or AkelPad)


File QemuBootTester.exe

QemuBootTester utility (conty9 rebuild)
Program for testing boot disks with x86/x64 UEFI mode support.



How to update from the previous distribution, so as not to download the entire collection again:

1. Stop and remove the previous distribution from your torrent client (only the torrent from the list in the torrent client)
2. Rename the old distribution folder from Multiboot_Collection_Full_v.7.7 to Multiboot_Collection_Full_v.7.8
3. Download a new torrent link, run it and specify the path in the torrent client to the Multiboot_Collection_Full_v.7.8 folder and rehash the distribution.
(only specify in the torrent client the path not to the Multiboot_Collection_Full_v.7.8 folder itself, but to the one in which it lies, otherwise the torrent client will start downloading the Multiboot_Collection_Full_v.7.8 folder to the Multiboot_Collection_Full_v.7.8 folder
4. The torrent client will rehash the distribution and download only the missing or updated files.


How to delete old files left from the previous distribution:

The distribution contains the Clear.exe utility to remove old files / folders from the distribution of folders (from CHDevice)
Instructions for use:
1. After the updated distribution files are downloaded, run the Clear.exe utility and click "Search for extra files".
2. After scanning for extra (old) files / folders from the last distribution, a list of files / folders marked with checkmarks will appear.
Click Remove Selected Files.


IMPORTANT INFORMATION!!! :

· Many of the programs included in the collections have been treated with "drugs".
·Therefore, in order to avoid false positives of antiviruses, it is recommended to disable them while downloading the distribution or add the folder with the distribution to the exceptions of your antivirus.


Burning the collection to media using the BootInst utility (by nikzzzz):

In the distribution there is a folder Recording the collection on a USB flash drive in which the BootInst utility (from nikzzzz) and instructions for use are located.


How to properly place the Multiboot Collection on a two-partition flash drive or USB-HDD:

Often, many people wonder how to properly place the Multiboot Collection on a two-partition flash drive or USB-HDD.
Briefly describe for those who have not yet figured out the structure of the collection or did not understand the description in the header.
Partition the disk into two partitions (MBR partitioning style). Don't worry, it will work in both UEFI boot mode and Legacy BIOS boot mode:
1st - FAT32, bootable (active), no larger than 32 GB.
2nd - NTFS, to all the remaining space.
Copy from the MBUSB directory completely all the contents (in its entirety !!!) to the 1st - FAT32, the boot partition of your disk.
Copy from the Addons directory:
Folder _WIN - on the 2nd - NTFS partition of your disk.
Folder 2K10 - on the 1st - FAT32, the boot partition of your disk.
Folder ACRONIS - on the 1st - FAT32, the boot partition of your disk.
Software folder - on the 2nd - NTFS partition of your disk.
(Also, the SDI_Update folder can be completely moved to the 2nd - NTFS partition of your disk (well, it is not needed in principle on the FAT32 boot partition)).
The SSTR folder - on the 1st - FAT32, the boot partition of your disk.
After placing the collection on your media, go to the 1st - FAT32 partition of your disk to the folder "Activate partition and change bootloader", select the bootloader script and run (I mainly use MBR-(USB-HDD+)_PBR-(BOOTMGR)_Activate. exe)
PS
I recommend repartitioning a flash drive (or USB-HDD) into two partitions using the c2pud.cmd script (from Ander_73) (present in the distribution along the path ".\Create a flash drive with two partitions\Create2-partitionUSB-drive\").


Changes in version 7.8:

• Updated all \_WIN\BOOT*.WIM
• Edited efi-BCD menus in \EFI\boot\SMBB, \EFI\boot\SSTR and \EFI\microsoft\boot
• Updated BootIt Bare Metal (BIBM++ by Ander_73) in \_WIN\BOOT\DOS
• Updated Tweaks in "Useful registry tweaks"
• Updated install.esd image Windows 11 (x64) (Version 22H2 OS build 22621.1848)
• Updated install.esd images for Windows 10 (x86/x64) (Version 22H2 OS Build 19045.3086)
• Updated install.esd images for Windows 8.1 (x86/x64) (Version 6.3 OS Build 9600.21013)
• Updated install.esd images for Windows 7 (x86/x64) (Version 6.1 OS Build 7601.26564)
(All the latest updates for the month of June on the release date of the distribution).
• Starting with Multiboot Collection Full v.6.9, Windows OS installation files (_WIN\*\install.esd) have been moved to the Addons directory
The reason for the transfer is described here: => Multiboot Collection Full v.7.7 (Updatable) [Ru/En]
• In Windows 7 and 8.1, the system startup (single start (RunOnce)) is integrated with the script for updating root certificates - CertUpd_by_Ander_73