The .wim+tweak I made with stageSxS-principalis is almost close to the normal install.wim, which should not be the same as unstaged.
I have seen in the installation log of Panther, the installer will distinguish between install.wim is Stage or Foundation This should be used to make normal install.wim. Spoiler
Unstaged = install.wim (Users & Windows & Packages & Language pack) Normal = install.wim (full image) Same install.wim; different structures. DO, not GUESS. owouwu's two scripts create "Users" and "Windows". You have to prepare esds and make "Packages" yourself.
(I don't use it, so I say) Maybe it lets you apply Pro packages to make "Packages". I mod and use its script to create Unstaged in official way. Unstaged-wim-Creation-repack.7z Z:\Unstaged-wim-Creation-repack\sources Code: C:\windows\system32>dir /b Z:\Unstaged-wim-Creation-repack\sources microsoft-windows-client-desktop-required-package.esd microsoft-windows-client-desktop-required-wow64-package.esd microsoft-windows-client-features-package.esd microsoft-windows-client-features-wow64-package.esd microsoft-windows-editionpack-core-package.esd microsoft-windows-editionpack-core-wow64-package.esd microsoft-windows-editionpack-ppipro-package.esd microsoft-windows-editionpack-ppipro-wow64-package.esd microsoft-windows-editionspecific-core-package.esd microsoft-windows-editionspecific-corecountryspecific-package.esd microsoft-windows-editionspecific-coren-package.esd microsoft-windows-editionspecific-enterpriseg-package.esd microsoft-windows-editionspecific-enterprises-package.esd microsoft-windows-editionspecific-ppipro-package.esd microsoft-windows-editionspecific-ppipro-wow64-package.esd microsoft-windows-editionspecific-professional-package.esd microsoft-windows-editionspecific-professional-wow64-package.esd microsoft-windows-editionspecific-professionaln-package.esd microsoft-windows-foundation-package.esd microsoft-windows-not-supported-on-ltsb-package.esd microsoft-windows-not-supported-on-ltsb-wow64-package.esd microsoft-windows-regulatedpackages-package.esd microsoft-windows-regulatedpackages-wow64-package.esd microsoft-windows-required-shellexperiences-desktop-package.esd microsoft-windows-required-shellexperiences-desktop-wow64-package.esd C:\windows\system32> Code: ========================================================================== Creating 19041.1 Unstaged install.wim amd64 ========================================================================== ------------------------------------------------------------ Preparing sources ------------------------------------------------------------ Extracting microsoft-windows-client-desktop-required-package.esd Creating files: 18034 of 18034 (100%) done Extracting file data: 340 MiB of 2453 MiB (13%) done Z:\Unstaged-wim-Creation-repack\temp\mount Packages Users Windows Then captured to install.wim. Code: temp\mount\Packages\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.19041.1_none_f1842539350f99e4\API-MS-Win-Eventing-Provider-L1-1-0.dll temp\mount\Packages\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.19041.1_none_f1842539350f99e4\API-MS-Win-EventLog-Legacy-L1-1-0.dll temp\mount\Packages\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.19041.1_none_f1842539350f99e4\API-MS-Win-Security-Lsalookup-L2-1-0.dll temp\mount\Packages\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.19041.1_none_f1842539350f99e4\API-MS-Win-Security-Lsalookup-L2-1-1.dll temp\mount\Packages\amd64_microsoft-windows-m..namespace-downlevel_31bf3856ad364e35_10.0.19041.1_none_f1842539350f99e4\API-MS-Win-security-provider-L1-1-0.dll 已複製 30 個檔案 temp\mount\Packages\amd64_microsoft-windows-o..namespace-downlevel_31bf3856ad364e35_10.0.19041.1_none_f70e304c2189961c\api-ms-win-shcore-stream-l1-1-0.dll 已複製 1 個檔案 請按任意鍵繼續 . . . ------------------------------------------------------------ Capturing image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.746 Saving image [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------ Exporting image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.746 Exporting image [==========================100.0%==========================] The operation completed successfully. ========================================================================== 19041.1 Unstaged install.wim amd64 has been successfully created. ========================================================================== Mission took 0:4:38.58 (278.58s total) 請按任意鍵繼續 . . . Z:\Unstaged-wim-Creation-repack\install.wim\ Packages Users Windows Unstaged, not normal.
I do not share any more. You have to prepare "Packages" for the script to make "Users" and "Windows".
The earliest used is the script of owouwu. Also did as he said. Several recent scripts can be understood, but it is more laborious to change the path. Without the script you sent before, the path setting is clear at a glance. It's time to rest, try again another day, good night.
You can replace modded Professional.mum with original one by RunOnce registry or SetupComplete.cmd. As for Store or App dependencies, maybe SetupComplete.cmd. (Place App packages in ISO\support)
Q: How to integrate gailium119's tweak in owouwu's registry? Oh, no. Don't! It will ruin the install.
If you're saying to apply it after first boot, than probably no. If you're saying to apply it after ISO-boot to install and before first boot, than probably yes.
I tried to integrate your tweak directly into owouwu's SOFTWARE and SYSTEM while making the wim. Then applied the wim to a partition and installed. [Before] make wim + load hive add your tweak unload hive = OK [After] make wim with your tweak = NOT OK
Here's your REG_MULTI_SZ /d "setupcl.exe" Code: [HKEY_LOCAL_MACHINE\SYSTEM1\ControlSet001\Control\Session Manager] "setupexecute"=hex(7):73,00,65,00,74,00,75,00,70,00,63,00,6c,00,2e,00,65,00,78,\ 00,65,00,00,00,00,00 Q: How to make it in Code: SYSTEM ControlSet001 Control Session Manager setupexecute = REG_MULTI_SZ xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx = ? setupexecute = REG_MULTI_SZ setupcl.exe --> blank
That's not for my question. I want owouwu's registry script to create your "setupexecute" registry, so I do not need to add or import it afterwards.
Why does the script create the registry everytime anyway? Just make 3 sets of registry for x86,amd64 and arm64, and copy them to destination every time instead of fresh create.