Bedi.cmd Code: echo: echo Lite Options: echo ------------- echo 20. !_store! Windows Store 23. !_helospeech! HelloFace and Speech echo 21. !_defender! Defender,VBS,Bitlocker24. !_winre! Windows Recovery echo 22. !_msedge! Microsoft Edge25. !_wifirtl! Realtek Wifi Driver ---> 25. !_wifirtl! Realtek Wifi Driver
Thank you very much. P.S. My lo Log of Bedi's scrip is exactly the same exclude Bedi.ini. I'm trying it right now. Thank you again. P.P.S. I use 19041.1.191206-1406.VB_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO
The 19041.1.191206-1406.VB_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO is OEMRET. You must change OEM or Retail to Volume in EI.CFG as followings (because Bedi_v7.44 uses Volume key). 19041.1.191206-1406.VB_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO\sources\EI.CFG Code: [Channel] volume [VL] 1
Hello everyone! I reviewed the Bedi v7.44 script for modifying Windows images. Sharing my findings because the script doesn't have a proper ReadMe file. Script functions: • Supports Windows 10/11 builds: 17763 (10.1809) ... 28000+ (11.26H1). • Converts Professional to EnterpriseS, EnterpriseG, WNC, and Starter. • Converts Server Datacenter to EnterpriseS and EnterpriseG. • Allows removal of some components: Defender, Edge, Store, WinRE, and drivers. Target editions: • EnterpriseG: purest edition, for the Chinese sector, without telemetry and with new cryptographic algorithms. • EnterpriseS: minimalist edition, without the Store, Cortana, and pre-installed UWP apps. • WNC (Windows Team): not for PCs, as it is designed for Surface Hub devices and interactive panels. • Starter: not for regular users, due to many limitations (you can't change wallpapers, themes, etc.). Limitations: 1. Doesn't download source files (install.wim and language packs). It could use ready-made links and uup-converter-wimlib. But now you have to search for all components yourself on MDL, Archive.org, tb.rg-adguard.net, and Telegram.2. Uses archived builds that have been removed from the servers. Insider builds live on the servers for ~30–60 days. When trying to download 28000.1 via UUP Dump: "Unable to retrieve data from Windows Update servers. Reason: EMPTY_FILELIST".3. EnterpriseG is English-only. This limitation can apparently be circumvented, but now is confirmed by the code (Bedi.cmd, line 94): Code: if /i %_targSKU% == EnterpriseG ( if /i not %_lang% == en-us ( Call :_Warn "Language Pack not supported for %_targSKU%. Only en-US" ) ) 4. No convenient task scheduling. Cleanup and shutdown are available only after the build. If the process is long (30–90 minutes), you'll have to wait at the console.5. No logging or file integrity checking. Only DISM commands are logged — if the script crashes, it's difficult to understand at what stage and why. Also, the script doesn't validate SHA-256 hashes — there's a risk of using or receiving a corrupted file. In short, Bedi is a tool for users capable of improving the code and searching for packages. Can anyone share a more handy Windows 10–11 reconstruction script? Maybe @DichVAN or someone will respond?
[Test Reconstruct 14393.0 Windows Server 2016 Standard (Desktop Experience) amd64 zh-TW with official zh-TW ServerStandardNano image] Code: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Convert ServerStandardNano to ServerStandard :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.14393.0 Removing package Microsoft-Windows-ServerStandardNanoEdition~31bf3856ad364e35~amd64~~10.0.14393.0 Removing package Microsoft-Windows-ServerStandardNanoEdition~31bf3856ad364e35~amd64~~10.0.14393.0 [==========================100.0%==========================] Error: 14099 An advanced installer failed during setup or servicing. The DISM log file can be found at C:\windows\Logs\DISM\dism.log ContainerOSPLus, WinVOS, etc. are different to regular Windows Editions. It's impossible to construct\reconstruct them for lacking "InternalBuildPackage-ServicingStack-OneCore-InstallOptions-Package". ServerStandardNano? It is one of them.
[19044.7184 Windows 10 Enterprise LTSC amd64 en-US with official SSU] Code: ------------------------------------------------------------ Add Servicing Stack update to EnterpriseS image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_7183~31bf3856ad364e35~amd64~~19041.7183.1.10 [==========================100.0%==========================] The operation completed successfully. Code: ------------------------------------------------------------ Set EnterpriseS key ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19044.7184 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : EnterpriseS (Volume) ============================================================ [19044.7184 Windows 10 Enterprise N LTSC amd64 en-US with official SSU] Code: ------------------------------------------------------------ Add Servicing Stack update to EnterpriseSN image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_7183~31bf3856ad364e35~amd64~~19041.7183.1.10 [==========================100.0%==========================] The operation completed successfully. Code: ------------------------------------------------------------ Set EnterpriseSN key ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19044.7184 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : EnterpriseSN (Volume) ============================================================ [19044.7184 Windows 10 Enterprise G amd64 en-US with official SSU] Code: ------------------------------------------------------------ Add Servicing Stack update to EnterpriseG image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_7183~31bf3856ad364e35~amd64~~19041.7183.1.10 [==========================100.0%==========================] The operation completed successfully. Code: ------------------------------------------------------------ Set EnterpriseG key ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19044.7184 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : EnterpriseG (Volume) ============================================================ [Credits] pp03 @ #4934
afaik from .7184 esu tweak not required official info from msft: [Licensing] Improved: This update addresses an issue that affects Long-Term Servicing Channel (LTSC) image creation using Deployment Image Servicing and Management (DISM). DISM offline operations on the below editions could not apply security updates because of limits in licensing enforcement. Now, you can use DISM to add security packages during offline image creation for LTSC. Windows 10 IoT Enterprise LTSC 2021 Windows 10 Enterprise G SKU Windows 10 Enterprise N LTSC
When Dism++ was under development, the author once said that he\she does not use Dism. Instead, he\she uses the lowest level of Cbs. Q: What is the lowest level of Cbs?
I don't know how the Bedi script is being rebuilt... I'm sorry... Perhaps the problem with license.rtf is because the corresponding folders are missing... Make sure the license.rtf files are inside the install.wim file.
construcdtion 22000.1 WindowsOnOneCore-Package successful Code: @echo off pushd "%~dp0" mkdir mount set MT=mount mkdir update set ua=update echo. echo ============================================================ echo Mount image echo ============================================================ echo. dism /mount-wim /wimfile:winpe.wim /index:1 /mountdir:%MT% dism /image:%MT% /apply-unattend:sxs\22000.1.xml dism /image:%MT% /apply-unattend:sxs\0b.xml dism /image:%MT% /apply-unattend:sxs\0blp.xml dism /english /image:%MT% /cleanup-image /startcomponentcleanup /resetbase dism /english /unmount-wim /mountdir:%MT% /commit echo dism /english /export-image /sourceimagefile:winpe.wim /sourceindex:1 /destinationimagefile:coreos.wim /Compress:max /CheckIntegrity echo. pause exit