What are the "ERROR: Access is denied." in the log below? Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Check Build ============================================================ CurrentBuild is: 26100 ============================================================ Remove Microsoft-Copilot & UserExperience-Recall Packages ============================================================ ERROR: Access is denied. ERROR: Access is denied. ERROR: Access is denied. ERROR: Access is denied. Removing: Microsoft-Copilot-Package~31bf3856ad364e35~amd64~~10.0.26100.1301 Removing: UserExperience-Recall-Package~31bf3856ad364e35~amd64~~10.0.26100.1591 ============================================================ Remove Edge.Webview2.Platform ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.2454 Image Version: 10.0.26100.1742 [==========================100.0%==========================] The operation completed successfully. ============================================================ Downloading missing Windows 11 Updates... ============================================================ Done.
Please check if you are using script 26H1_Creator_1.8 to edit a 26100 image. This script is specific to the 28000 image. For the 26100 image, use script 2xH2_Creator_16.3. I hope this helps. Best regards
After the main script finishes executing, a log file with the same name as the main script is automatically created, for example 2xH2_Creator_16.3.log. This is the file I need to examine to see how you performed the process.
I just ran a new test here in VirtualBox, with Windows 11 as the host. Everything went smoothly. See the attached log file as an example. Attention: The first time you run the 2xH2_Creator_16.3_Start.cmd script, a PowerRun warning will appear, asking you to enable command line commands. To do this, go to the tools folder and run the PowerRun_x64.exe file. In the window that opens, go to the Files tab and click "Allow command line". That's it. Now everything will run without problems.
@hoak - Please stick to the subject of this topic, let's not derail it too much. It's Slimdown, not a general news topic.
========================= 2xH2_Creator_16.4 ========================= Updated to 26x00.8524 https://forums.mydigitallife.net/th...to-classic-legacy-windows.90039/#post-1872013 Enjoy
Sometimes small details can make a difference. I got a warning, but I was not aware that PowerRun_x64.exe is in the tools folder. It was already in a different folder and even if "Allow command line" was enabled, I would still get a warning. I had to launch command prompt from PowerRun_x64.exe and run the script to avoid it. In _HowToUse.txt I still read about 2xH2_Creator_Start_Nsudo.cmd, which does not seem to be included. Doesn't the script create an ISO or do I have to copy the contents of the DVD folder to a USB drive?
In the new version, several things have been adjusted. Regarding PowerRun, I always do it this way: run it and, in files, select "Allow command line". Regarding ISO creation, there's a script for that in the package. I adopted this method because many users, like me, make new personal adjustments before creating the final ISO. If you want to create the ISO, run the script "_CreateISO.cmd". The image will be created based on the existing files in the DVD folder.