That is, you mean that this part of the script should look like this: :: Unmounting image "%DISM%" /Unmount-Wim /MountDir:"%BootMount%" /commit :: Export image "%DISM%" /english /export-image /sourceimagefile:"%BootWim%" /sourceindex:2 /destinationimagefile:"%BootWimTmp%" move /y "%BootWimTmp%" "%BootWim%" >nul p.s. Are you sure that here - sourceindex:2 should be 2 and not 1. Let me remind you that in my boot.wim index 1 has been deleted. and only index 2 remained. Now it will be our index 1.
This is possible with the new boot.wim, publish your code and I will fix everything. There is no point in doing any manipulations with your boot.wim. If you are interested? I can publish a new version of the script, without using the script from abbodi1406
Spoiler "test.cmd" Script - Running As Trusted Installer by nSudo. =========================================================== Mounting Image 2 =========================================================== Deployment Image Servicing and Management tool Version: 10.0.26100.1 Details for image : D:\Win\Integrator11\DVD\sources\boot.wim Index : 1 Name : Microsoft Windows PE (amd64) Description : Microsoft Windows PE (amd64) Size : 2 390 249 693 bytes Index : 2 Name : Microsoft Windows Setup (amd64) Description : Microsoft Windows Setup (amd64) Size : 2 492 990 009 bytes The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Mounting image [==========================100.0%==========================] The operation completed successfully. =========================================================== integration Language pack to Image =========================================================== Скопировано файлов: 148. Скопировано файлов: 148. Скопировано файлов: 1. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package Microsoft-Windows-WinPE-LanguagePack-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package WinPE-SRT-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package WinPE-EnhancedStorage-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package WinPE-Scripting-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package WinPE-SecureStartup-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package WinPE-WDS-Tools-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package WinPE-WMI-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package WinPE-Setup-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 Processing 1 of 1 - Adding package WinPE-Setup-Client-Package~31bf3856ad364e35~amd64~ru-RU~10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. =========================================================== Create the file configuration =========================================================== Скопировано файлов: 1. =========================================================== Windows11-bypass =========================================================== Операция успешно завершена. Операция успешно завершена. Операция успешно завершена. Операция успешно завершена. Операция успешно завершена. =========================================================== Copying [Dart-Files] to Windows Setup =========================================================== Deployment Image Servicing and Management tool Version: 10.0.26100.1 Applying image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Applying image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Applying image [==========================100.0%==========================] The operation completed successfully. =========================================================== Extracting Setup Media Update to sources boot.wim =========================================================== ================================================================================ Cleaning up the WinSxS Folder ================================================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.26100.1 [==========================100.0%==========================] The operation completed successfully. =========================================================== Cleaning image =========================================================== Cистема DISM Версия: 10.0.26100.1 Файл образа: D:\Win\Integrator11\DVD\sources\boot.wim Индекс образа: 2 Сохранение образа [==========================100.0%==========================] Отключение образа [==========================100.0%==========================] Операция успешно завершена. Cистема DISM Версия: 10.0.19041.1 Сведения об образе : D:\Win\Integrator11\DVD\sources\install.wim Индекс: 1 Имя : Windows 11 Enterprise LTSC Описание : Windows 11 Enterprise LTSC Размер: 20 098 371 526 байт Операция успешно завершена. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Exporting image [==========================100.0%==========================] The operation completed successfully. =========================================================== Re-Building Source [boot.wim] Image... =========================================================== Using LZX compression with 4 threads Archiving file data: 1202 MiB of 1202 MiB (100%) done
I understand that you are suggesting to simply export index 2 from the boot.wim image. I won’t explain for a long time, but it won’t give anything at all, in my case. It then exports it, but does not delete the Deleted folder from boot.wim (which now contains the deleted first index) and therefore the size of boot.wim does not change, but on the contrary, increases slightly. Okay, no need, проехали ...
Tried this though script exits just after update integration, eg press 9 to exit integrator then press any key to progress, just prior to Removing capabilities.
Script ran without error. Still having the hardware error when testing in the VM I don't have this issue when using win 10.
SD11v202_4.8.26 Updated 2024_10_09 - Updated hfixes files for downloading updates (22621 and 26100) - Improved conditions for correct Build identification and thus facilitate other processes safely - Adjusted conditions for W10UI to process updates correctly - Added OpenShell with the Start Button modified for Windows 11, for optional installation - Other small adjustments https://forums.mydigitallife.net/th...sic-legacy-windows.86552/page-75#post-1851693
Better use 26100.1742 original oem Uup dump must used only for test Search massgrave section https://forums.mydigitallife.net/th...retail-ge-release.88220/page-105#post-1854344
14081 error and the script continue, any idea? host running ltsc 2019 probably because i use en-us_windows_10_consumer_editions_version_22h2_updated_july_2024_x64_dvd_3245b006.iso, will try the default iso
For Windows 10 use this script: https://forums.mydigitallife.net/threads/slimdown10_v2-0-2-continued.88599/ For Windows 11 use this script: https://forums.mydigitallife.net/threads/slimdown10-–-turn-windows-10-22h2-or-ltsc-2021-into-classic-legacy-windows.86552/page-75#post-1851693
Does anyone else find this problem when running a windows eleven image using virtual Box? This error does not appear to be TPM or a Ram requirement issue. I used Rufus to remove those requirements & still receive this, "Install driver to display hardware" I have not used this image on a real PC yet.