I will send you the link the ISO I try to convert..can you check if it do the same?? W10 or W11, or both??
Hi @rayman95, Thanks for the detailed logs! There are two distinct issues happening here due to environment restrictions, but the good news is that they are already addressed in the upcoming core rewrite. Here is what's causing this on your machine: 1. The DISM "Error: 2" (System cannot find the file specified) In version 2.0.5, the script maps the paths inside variables, but under certain multi-lingual hosts or custom directory paths (like running straight from the Desktop), native Windows PowerShell StrictMode loses track of the environment paths mapping if dism.exe tries to look for its core binaries or folders. The script throws Error: 2 during manifest indexing and mounting stages, which causes DISM to bypass mounting completely. Because nothing was actually mounted to Data\Mount, the servicing engine down the pipeline fails. 2. The W10UI Critical Crash (Exit Code: 255 / Le handle n’a pas pu être ouvert) Look at this specific line in your French Windows environment log: "Le handle n’a pas pu être ouvert lors de la redirection du handle 1." (The handle could not be opened during redirection of handle 1). This happens because the background cmd.exe process call for W10UI.cmd uses raw standard input/output stream redirection to run quietly. In localized French/non-English Windows builds, when StrictMode encounters empty variables due to the mounting failure mentioned above, the command shell tries to redirect a non-existent file stream descriptor. This breaks the console handle architecture completely, throwing code 255 and crashing the entire integration process. Summary / Solution: Since the Data\Mount workspace was empty from the start due to the pathing error, W10UI had no target image filesystem to inject updates into. We are currently finalizing WimDirector v3.0, which introduces a completely modified engineering backend: - Total retirement of W10UI.cmd — all cumulative updates and .NET components are now handled natively inside PowerShell via thread-safe Add-WindowsPackage pipelines with real-time graphical progress bars. No more command shell console handle crashes or localized redirection failures! - Robust Path Sanitization — path scopes are completely isolated to guarantee flawless cross-locale execution even when running from deep directory nodes like the User Desktop. Stay tuned for the v3.0 update, it will completely bypass these console stream limitations on your machine!
I'm running actually again the script, but I put the folder in C: and tried with a 26100.1742 stock with french only include...got still errors and fc, but later... Spoiler ========================================================== WimDirector_2.0.5 ========================================================== [*] Logging engine activated: logs\WimOptimizer_Session.log [*] Checking and flushing old build outputs... [PASS] Core servicing environment initialized cleanly. ---------------------------------------------------------- [sub_Mount] Initializing target acquisition sequence... [*] Discovered original storage target: 26100.1742.240906-0558.GE_RELEASE_SVC_PROD1_CLIENT_X64FRE_EN-US_FR-FR.iso [*] Extracting original bootable container contents... [!] Purging original ISO asset out of root storage space... [*] Querying single-edition manifests via local servicing engine... Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Details for image : C:\WimDirector_2.0.5\Data\Temp\ExtractedISO\sources\install.wim Index : 1 Name : Windows 11 IoT Enterprise LTSC Description : Windows 11 IoT Enterprise LTSC Size : 18 740 054 060 bytes The operation completed successfully. Enter the Image Index to extract [Default 1]: 2 [*] Isolating index 2 into workspace pool... Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Error: 87 An error occurred while processing the command. Ensure that the command-line arguments are valid. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log [*] Expanding isolated install.wim layout onto Mount workspace... Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Error: 2 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log [*] Inspecting mounted image internal registry architecture... [*] Launching advanced deployment configurator matrix... [*] Selected Servicing Strategy: Option 1 [*] Configuring deployment repo transitions via TRN storage... [TRN Bypass] Baseline Windows 11 scenario active. No transitions required. ---------------------------------------------------------- ---------------------------------------------------------- [sub_Boot] Initializing advanced boot.wim total rebuild sequence... [*] Extracting WinPE image (Index 2) directly via local wimlib layer... Applying image 2 ("Microsoft Windows Setup (amd64)") from "C:\WimDirector_2.0.5\Data\Temp\boot.wim" to directory "C:\WimDirector_2.0.5\Data\Temp\BootWorkspace" Creating files: 25242 of 25242 (100%) done Extracting file data: 1241 MiB of 1241 MiB (100%) done Applying metadata to files: 25242 of 25242 (100%) done Done applying WIM image. [*] Starting surgical elimination of SysWOW64 and staging layers... [International Guard] Purging folder: SysWOW64 [*] Executing deep language localization alignment sweeper... [Language Guard] Shielding critical deployment assets for: en-US, fr-FR, and en-US [Language Purge] Erased 223 obsolete localization asset directories. [*] Packaging clean workspace layout into an ultra-compressed solid container... Scanning "C:\WimDirector_2.0.5\Data\Temp\BootWorkspace" 1241 MiB scanned (19210 files, 4790 directories) Setting the DESCRIPTION property of image 1 to "Microsoft Windows Setup". Using LZMS compression with 12 threads Archiving file data: 1208 MiB of 1208 MiB (100%) done Calculating integrity table for WIM: 342 MiB of 342 MiB (100%) done [PASS] boot.wim rebuilt. Final single-index solid container weight: 342.17 MB ---------------------------------------------------------- ---------------------------------------------------------- [sub_Updates] Initializing Microsoft cumulative update stage... [*] Synchronizing W10UI configuration parameters... [*] Scanning active update repository: C:\WimDirector_2.0.5\Data\UUP [!] Note: No .msu or .cab servicing packages found inside Data\uup folder. [!] Skipping servicing stage. Proceeding with clean baseline image state. ---------------------------------------------------------- ---------------------------------------------------------- [sub_Matrix] Launching aggressive servicing pipeline... [*] Saving original features, capabilities, and AppX inventory tables... [*] Processing Windows Defender extraction pipeline... Error: 2 Unable to access the image. Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder. [*] Removing Microsoft Edge core packages and DevTools layouts... [*] Executing mass AppX debloat matrix from AppxList.txt... ![PIPELINE CRITICAL CRASH]: Une erreur s’est produite. Aucune opération n’a été effectuée. Assurez-vous que DISM est correctement installé dans l’image, puis recommencez l’opération. To finish, press Enter...:
f...k.. it reboot directly on recovery with blue screen and winload.efi error.... EDIT : So I put a functional install.esd in the created iso and got same error. I get the install.esd from the generated iso and put in functional ISO and it's installing... the error come from WimDirector_v2.0.5_Custom.iso Edit 2 : install stop with this message windows cannot finish the install
Since this is the Slimdown11 thread, please continue discussion of CloudRecovery tool in this new thread. https://forums.mydigitallife.net/threads/cloudrecoverytool.90615/
its difficult to find the culprit, because the install stop. I put the install.esd obtained with the wimdirector 2.0.5 custom iso in a functional ISO, but got error during install..so in theory boot.wim is not the problem..or boot wim and install esd doesn't match..
Actually, here's why I removed it from distribution: everything works fine on my server, but others are experiencing various issues. That's why I removed the tool from distribution until I can figure out what's causing the problems for others. I'm currently working on a new version of the tool, in which I'll try to address all the feedback I've received.
got same problem on VMWare "system32/winload/efi" maybe I got problem with the iso I choose... which one should I try LTSC 26100.1???
I take the US ISO 1742 and made an US/FR LTSC and use this one.. maybe it doesn't like 2 languages in one ISO
so wimoptimizer is in long holiday now, friend? the chief of executive handle by wimdirector, nice.. it's saturday night in my area, so the night is still young. Let us play with the new director. Cheers