As it is single SKU script only, can I join the SKUs manually, in the end? Will the final have an AIO?
Probably but it will be time consuming. This was the first working test script, AiO will most likely be put in too.
7loder ？ ─OEM │ └─$OEM$ │ └─$ │ └─Setup │ └─Scripts │ DeCompile.exe │ OEM's.7z │ OOBE.cmd These are the correct files. Turn off antivirus software. EDIT: DELETE EDIT2:You can also use Windows Loader. exe, put it in the oem folder. Make a SetupComplete.cmd file in "D:\SiMPLiX_AiO_ISO_Full_Tool_2_3_21.2.10\OEM\$OEM$\$$\Setup\Scripts" directory and edit it Code: @ECHO OFF %~dp0"Windows Loader.exe" /silent /preactivate cd %~dp0 attrib -R -A -S -H *.* SHUTDOWN /R /T 5 RMDIR /S /Q "%WINDIR%\Setup\Scripts" exit
Dare i ask what MRP has fixed, considering MRP doesn't contain any activator (i guess 7loader is one), it only activates when a valid slic or msdm is present.
@Enthousiast use W7 x64 Single ESU Index Only New 2.3 b2 Win7 Based ISO BETA Development The created ISO cannot be installed after entering the installation interface. Prompt that a program driver is required.
That's probably because i made the script integrate the 2 nvme supporting updates into boot.wim, you can put :: in front of lines: 469 and 479: Code: ::dism.exe /image:"%SystemDrive%\AiO_Mount" /Add-Package /Packagepath:"Updates_NVME_Boot\x64" I ran a few tests and this solved the problem.
According to your method, the ISO is successfully made and installed successfully, and this is added:: What does it mean?
That means the script skipped that command and didn't integrate the 2 win 7 nvme support updates, they seem to cause this error.