Second test with10.8 again, Ran the finished image in a VM this time not using an unattended answer file, no images available?
I didn't notice any errors in the log file. This type of error occurs when the Autounattend.xml file doesn't correctly indicate the image being processed. In this case, it was my fault, as I attached the Autounattend.xml I was testing with an Education version. This will conflict with another edition during installation. I'm fixing this in the package as well. Below is an Autounattend.xml that applies to all editions. Please try using the attached Autounattend.xml and see if it works. Please let me know if it went well.
===================== 23H2_Integrator_10.9 ===================== - Updated the 2xH2_Integrator to version 226x1.5840 - add autounattend.xml for use with all editions - add option for remove WinRE.wim in Default mode - Added option to integrate or not with 23H2 Enablement. So you can choose 22621 or 22631 - Updated UUP\all.txt - Updated UUP\Appx - Add my 22H2Tweaks NOTE: If you don't want to apply any or all of the tweaks, simply remove the PersonalTweaks\22H2 folder or remove the tweak(s) you don't want to apply - Windows Update is now disabled during installation. Use ToggleWindowsUpdate to enable Windows Update (Utilities) - Other minor adjustments Test with: 22621.525.220924-1448.NI_RELEASE_SVC_IM_CLIENTBUSINESS_VOL_X64FRE_PT-BR.ISO Please read the README.txt file before doing anything! Good luck! https://forums.mydigitallife.net/th...ic-legacy-windows.86552/page-127#post-1874681
Thank you! I in my scripts and the layout of the tool itself always strive for their usability and transparency for the end user. So that it would be as convenient to use as possible and there would be nothing unnecessary (not clear) for the user on the desktop. That's why I leave open only those folders and files that are really necessary for the unskilled user - everything is extremely simple and clear. But everything I do, I do thanks to what I learned from you Sergey, from SunLion, from comrades from MDL resource. For what all of you thank you very much!
Hi Sainfo! Thank you for your kind words. It's very nice to read that my advice and were useful and helped in your work. You are a great guy for making everything as convenient and understandable as possible for the end user - it's worth a lot! In fact, we all learn from each other, and I also learned a lot from you and other guys from MDL. Therefore, your gratitude is especially valuable to me. I am sure that your tool will turn out even cooler and more in demand! Good luck to you in developing the project, and know - if anything, I am always here, I will help as much as I can.
Does the error look like the one in the attached image? This happened here too. So I switched to using the boot.wim exclusively, without modifications, from the image being modified. After that, I no longer had the problem. Which script are you using?
Did you make any changes to the boot.wim file? Is the error you see the same as the image in my post above?
I didn't make any changes.It's the same as the mistake in the picture. Ah, the ISO I made with dism++ Is this the reason? I'm not sure.
That might be it. I don't use dism++ here, but that's only because I'm not very familiar with it. Try doing it without dism++ and test it out...
========================= 25H2_Integrator_12.8_Lite ========================= Updated to 26200.5074 version - Only the SLIM option was kept in this version - The all.txt file was updated - Enablement 25H2 is already in the package, no download required - Basic apps were added to the Addons\Install folder, which will be copied to the $OEM$ folder to be installed automatically at the end of the process - If you don't want to install any of the apps, simply remove them from the Addons\Install folder - Windows Update is disabled at the end of the installation. If you want to re-enable it, use ToggleWindowsUpdate in the Start Menu\Utilities - The pt-br_windows_11_enterprise_ltsc_2024_x64_dvd_2bb6b75b_2.iso image was used for testing Please read the Changelog.txt and README.txt files before using the script. https://forums.mydigitallife.net/th...ic-legacy-windows.86552/page-120#post-1872013 Enjoy!
Thanks, I am testing whatever 24H2, prefer lite and clean. I did test 24H2 last Oct when it's out.Pretty bad feeling. my python pyautogui couldn't work correctly. had to step back onto Windows 7. but Windows 7 is getting more and more problems.I am cornored. 25H2 is out, hopefully, 24H2 can be improved enough.