Oh, I use one 20348.51 Editions package in 20348.1 ServerTurbine reconstruction which is accepted by Windows Update, without the need to use baseless LCU. Hint: In sxs of the script, I removed f\n\r folders from all binary folders.
Q: What is the difference between inside and outside reconstruction? Driver and Mechanic? Patient and Doctor? User and Inventor? Q: How did you do that? Could you share the Dedup packages with me? A: Here you go: BlaBlaBla. Q: How to make it working on 22000? A: Here you go: BlaBlaBla. Q: How to make it working on 22463? A: Here you go: BlaBlaBla. Same question, same answer, endless. Fact: Windows is made of package, aka module. A: Knowing package is Insider, Outsider on the contrary. Win32Calc for example. Outsider: 1. Copy win32calc.exe to C:\Windows\System32. 2. Copy win32calc.exe.mui to C:\Windows\System32\xx-XX. Insider: 1. Extract Win32Calc packages. 2. Install Win32Calc packages. Therefore, you want to do reconstruction? Learn to extract and install package.
Is it possible to obtain Windows 7 SKUs in Windows 8/8.1/10 via this project? Or we'll fail due to version incompatiblity?
SPP service won't support, I think. e.g. 17763.1 does not support 19041.1 IoTEnterpriseS. BTW, 14393.0 supports Starter, but not 10240.16384. Fact about working Windows 10 Starter: 14393.0 15063.0 16299.15 17134.1
Even so, is the tutorial same with other tutorials? I wanna see if there're how many bugs will happen.
I meant Windows 7 SKUs in Windows 8/8.1/10 (same with Server counterparts or reversed) For example: Code: Windows 10 Starter Windows 8.1 Ultimate Windows 8 Home Premium Windows 7 Core Windows Server 2022 Web Server Windows Server 2016 Enterprise Server Windows Server 2012 R2 Small Business Server Windows Server 2008 R2 Foundation I'm planning to create a giant ISO with Official and Homemade SKUs.
"I'm planning to create a giant ISO with Official and Homemade SKUs." Sorry, this is off-topic, I can't help.