i know if you have shared some script tools they will work fine but its our fault we do not understand the correct way to use it thus results in error at our end thatswhy i quoted his post with no comments. "Happy Mery XMAS"
Hardly that's an unsolvable problem Basically there's no point in doing that, given 16299 reached the end of life. Just cleanup the enterprise image from the crap, and you're fine If you still want to make it use the 1607 certs to get Ent S 16299, or 1809 certs to get Ent S 17134 On 17134 use the branding from 1607 to have the "Enterprise S" branding, or from 1809 to have the "LTSC" branding[/QUOTE]
I will try to build from scratch 16299.2166 as a Core Standalone removing all the crap and i will see how it is working ..and i will try to see if i can add net framework 4.8 and use this for my low laptop ... if not i will stay with 19041.1415 CORE as LTSC 2021 which so far is the best and fast build i managed to create ...
use CMD, not Powershell. Put install.wim from ESD above to the folder with script. ESD needs to be decrypted by another script. Run as admin
@iamaHUN, I've discovered that; if the process fails, you're going to get an unusable Windows Server 2008. It can't boot due to a BSOD with code 0x000021a. Also Windows can't even boot into safe mode.
Please to avoid confusion use the proper terminology What you mean is that the driver is INCLUDED in 2021, and while it's AVAILABLE for other OSes it doesn't work on your specific scenario. Which is way different than what you said before. P.S. did you try the w81 driver? did you try the one included in 2021?
i try all the drivers available for this type c and i said it is available as a driver updated in 2021 DriverVer = 07/10/2018,1.3.5.0 DriverVer = 12/26/2018,1.5.0.0 DriverVer = 06/19/2019,1.7.0.2 DriverVer = 01/25/2021,1.8.1.0 The same error code in all the drivers installed and same yellow mark , It is the first time for me this kind of error using 14393 LTSB 2016 SAME ERROR IN 15063 ...
To reconstruct EnterpriseS: 1. Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~x86~~10.0.19041.1.cat Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~x86~~10.0.19041.1.mum 2. Microsoft-Windows-EditionSpecific-EnterpriseS-Package~31bf3856ad364e35~x86~~10.0.19041.1 package Hint: No need for whole EditionSpecific package, just the different ones are enough: 1. Microsoft-Windows-Branding-EnterpriseS-Package 2. Microsoft-Windows-Editions-EnterpriseS-Package 3. Microsoft-Windows-EnterpriseS-SPP-Components-Package 4. Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy-Package 5. Microsoft-Windows-win32calc-Package
Q: How to make 19041.1 Starter with 15063.0 packages, yet, with 19041.1 pkeyconfig.xrm-ms? A: Microsoft-Windows-Security-SPP-Component-SKU-Starter-Package~31bf3856ad364e35~amd64~~10.0.19041.1.mum Before Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Starter-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <package identifier="Microsoft-Windows-Security-SPP-Component-SKU-Starter-Package" releaseType="Feature Pack"> <update name="Microsoft-Windows-Security-SPP-Component-SKU-Starter-License-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Starter-License-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </package> </update> <update name="Microsoft-Windows-Security-SPP-Component-SKU-Starter-Default-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Starter-Default-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </package> </update> </package> </update> </package> </assembly> After Code: <?xml version="1.0" encoding="utf-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Starter-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <package identifier="Microsoft-Windows-Security-SPP-Component-SKU-Starter-Package" releaseType="Feature Pack"> <update name="Microsoft-Windows-Security-SPP-Component-SKU-Starter-License-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Starter-License-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </package> </update> <update name="Microsoft-Windows-Security-SPP-Component-SKU-Starter-Default-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Starter-Default-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </package> </update> <update name="Microsoft-Windows-Security-SPP-Component-SKU-Core-License-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Security-SPP-Component-SKU-Core-License-Package" version="10.0.19041.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> </package> </update> </package> </assembly>
Q: In build.cmd of Abbody's script, what's the difference between them? Load --> Modify --> Save to a new file --> Unload --> Replace the old file with the new file Code: set "key=HKLM:\offSOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" reg load HKLM\offSOFTWARE mount\Windows\System32\Config\SOFTWARE powershell -nop -c "SP -Path '%key%\*EnterpriseS*' -Name Trusted -Value 1; SP -Path '%key%\*OEMDefaultAssociations*' -Name Trusted -Value 1" reg save HKLM\offSOFTWARE mount\Windows\System32\Config\SOFTWAR2 reg unload HKLM\offSOFTWARE move /y mount\Windows\System32\Config\SOFTWAR2 mount\Windows\System32\Config\SOFTWARE Load --> Modify --> Unload Code: set "key=HKLM:\offSOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages" reg load HKLM\offSOFTWARE mount\Windows\System32\Config\SOFTWARE powershell -nop -c "SP -Path '%key%\*EnterpriseS*' -Name Trusted -Value 1; SP -Path '%key%\*OEMDefaultAssociations*' -Name Trusted -Value 1" reg unload HKLM\offSOFTWARE Why this modification in registry? I have no idea. But as huynhlam2 said: "That is Great packages, all .1". https://forums.mydigitallife.net/th...struction-project.80939/page-296#post-1713129
@xinso On Windows x86 Host OS, big SOFTWARE hive will fail to flush and unload correctly without saving first https://forums.mydigitallife.net/posts/1568960/ https://forums.mydigitallife.net/posts/1568995/
Oh, I use amd64 only, no wonder I don't know about it. Thanks. BTW: Why not try your scripts with one xml? Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="sxs\Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.19041.1.mum" /> </package> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.19041.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend> From Code: dism /english /logpath:logs\1.log /scratchdir:"%~dp0temp" /image:mount /apply-unattend:1.xml || exit /b 1 dism /english /logpath:logs\2.log /scratchdir:"%~dp0temp" /image:mount /apply-unattend:2.xml || exit /b 1 dism /english /logpath:logs\2.log /scratchdir:"%~dp0temp" /image:mount /add-package /packagepath:lp\update.mum || exit /b 1 dism /english /logpath:logs\3.log /scratchdir:"%~dp0temp" /image:mount /apply-unattend:3.xml || exit /b 1 To Code: dism /english /logpath:logs\1.log /scratchdir:"%~dp0temp" /image:mount /apply-unattend:1.xml || exit /b 1 dism /english /logpath:logs\2.log /scratchdir:"%~dp0temp" /image:mount /add-package /packagepath:lp\update.mum || exit /b 1 And in full_build.cmd, From Code: install_wim_done.cmd || exit /b 1 To Code: call install_wim_done.cmd || exit /b 1 Code: Z:\EnterpriseS-19041.1-x64_rev>call install_wim_done.cmd || exit /b 1 Z:\EnterpriseS-19041.1-x64_rev>set wlexe=bin\wimlib-imagex.exe Z:\EnterpriseS-19041.1-x64_rev>if /I "AMD64" == "x86" if "" == "" set wlexe=bin\86\wimlib-imagex.exe Z:\EnterpriseS-19041.1-x64_rev>bin\wimlib-imagex.exe info install.wim 1 "Windows 10 Enterprise LTSC 2021" "Windows 10 Enterprise LTSC 2021" --image-property FLAGS="EnterpriseS" --image-property DISPLAYNAME="Windows 10 Enterprise LTSC" --image-property DISPLAYDESCRIPTION="Windows 10 Enterprise LTSC" Setting the FLAGS property of image 1 to "EnterpriseS". Setting the DISPLAYNAME property of image 1 to "Windows 10 Enterprise LTSC". Setting the DISPLAYDESCRIPTION property of image 1 to "Windows 10 Enterprise LTSC". Setting the NAME property of image 1 to "Windows 10 Enterprise LTSC 2021". Setting the DESCRIPTION property of image 1 to "Windows 10 Enterprise LTSC 2021". Z:\EnterpriseS-19041.1-x64_rev>bin\wimlib-imagex.exe optimize install.wim "install.wim" original size: 3451945 KiB Using LZX compression with 12 threads Archiving file data: 6262 MiB of 6262 MiB (100%) done "install.wim" optimized size: 2895378 KiB Space saved: 556566 KiB Z:\EnterpriseS-19041.1-x64_rev>bin\wimlib-imagex.exe info install.wim WIM Information: ---------------- Path: install.wim GUID: 0x55c7adc24dca57fe0f13b4972d7990dd Version: 68864 Image Count: 1 Compression: LZX Chunk Size: 32768 bytes Part Number: 1/1 Boot Index: 0 Size: 2964865364 bytes Attributes: Relative path junction Available Images: ----------------- Index: 1 Name: Windows 10 Enterprise LTSC 2021 Description: Windows 10 Enterprise LTSC 2021 Display Name: Windows 10 Enterprise LTSC Display Description: Windows 10 Enterprise LTSC Directory Count: 17097 File Count: 74608 Total Bytes: 12875182239 Hard Link Bytes: 5746588946 Creation Time: Sat Dec 07 11:20:48 2019 UTC Last Modification Time: Wed Dec 22 15:05:01 2021 UTC Architecture: x86_64 Product Name: Microsoft?Windows?Operating System Edition ID: EnterpriseS Installation Type: Client Product Type: WinNT Product Suite: Terminal Server Languages: en-US Default Language: en-US System Root: WINDOWS Major Version: 10 Minor Version: 0 Build: 19041 Service Pack Build: 1 Service Pack Level: 0 Flags: EnterpriseS WIMBoot compatible: no ERROR: error writing to standard output: No error Z:\EnterpriseS-19041.1-x64_rev> Otherwise, the script flashed away, on my amd64 platform. OK. Thanks for your good stuff.
Fact about update technology since 18362.1: All target initial build will be superceded by LCU update build. i.e. It does not matter at all whether the target initial build is modded or fake, once it is being successfully updated, it turns to be genuine.