I didn't assume any OS was being used to try and build a new Win 7 image, I just pointed out one issue (real time protection) that I know rears it's head on Win 10 and causes issues. But, casio4ever, people are trying to help you so perhaps tone down the hostile replies.
Maybe provide more info like the full progress instead of a small snippet, if you ran it on 10 or on what windows and build you ran it, what ISOs you provided, what exact script did you run, etcetc,,,? Seems there will be errors at an earlier time.
Is that a must-be? frankly, I don't know how to run DISM on Windows 7 (I do on Windows 10/11). I tried some command lines. but not helpful. I need to modify IOS (of Windows 7). adding updates into Windows 7 HP install media. because for HP G3 PC install only takes HP install media/HP_RECOVERY. the mod ISO I learned from here. none worked. HP is unique (In contrast, Dell ASUS MSI, , , no this problem. can take any modded install media)
Here's the complete list, you can ask me if you need something else. Code: Provided ISOs: * en_windows_7_professional_with_sp1_vl_build_x64_dvd_u_677791.iso * 19045.2486.230107-0718.22H2_RELEASE_SVC_REFRESH_CLIENTPROFESSIONALVL_VOL_X64FRE_EN-US.iso Host OS : Windows 8.1 Pro ADK version : 10.1.19041.1 Used script : W7_x64_Single_Index_Only_3.0_Modern.cmd Used tool : SiMPLiX_AiO_ISO_Bare_Tool_4_0_22.12.14.zip
This is not a retail multiple edition ISO (it's a single index Professional VL ISO), use the MSDN multiple edition iso and it will work. The ISO is required to contain x64 HomeBasic or x86 Starter.
Your Test was successful because you are using the old version of the tool (v2.3) which was deleted already by the OP.
you're free to check my trials on pages 105, 106 using v4 releases (dec 2022, apr 2023) respectively and tell me where the problem exists. images used are : 1.en_windows_7_ultimate_with_sp1_x64_dvd_u_677332.iso 2.en-us_windows_10_consumer_editions_versio n_21h2_updated_dec_2021_x64_dvd_a468b4ce.iso ------ ADKs used : 1.Windows 8.1 Adk 6.3.9600 2. Windows 10 Adk 10.0.19041 ------- Host Os : Windows 7 SP1 ultimate retail x64
Sorry, I wish I had time to test. This is the ISO you used before, and it doesn't meet the requirements of the script. Do you still have the same issues with the correct ISO test?
The only one posting in here without reading the answers is you. Where do i blame you for trying to create uefi bootablee ISOs on 7 hosts? 1. I advise to use the legacy script because it works on UEFI and Legacy BIOS too and doesn't need a win 10 source ISO (+ it offers more options). 2. I recreated your scenario on a 7 host using the same ISOs and all ran without any errors. 3. @Gloeyisk uses the wrong win 7 source iso, problem solved. 3. So stop incorrectly blaming us for your local problems.
@jiafei2427 please read my previous posts, i didn't say that i'm using volume media during my trials. i use only retail media of windows 7 ultimate with sp1 & retail media of windows 10 21h2
oh ! really ? why bothering writing error logs then ? you're the one who keep ignoring error messages of your tool, instead you didn't test your code against windows 7, you choose to run it under windows 11 with the skipping of the important step of integrating update pack inside install.wim of windows 7 media, i doubt even if you knew the main goal of your tool is.
@Enthousiast Here Sir : And Here Sir : I'm not asking for gold and diamonds, i'm only asking for only one truthful test of your tool: 1. running single index modern script on windows 7 sp1 ultimate (with no updates after sp1) host os and retail media. 2. with providing of win 10 21h2 adk 19041 media. 3. with providing of consumer win 10 21h2 media. 4. without skipping the integration of updatepack. 5. posting the final log of the whole process.
No, this is not what i mean, update v22.12.14 got extracted and integrated so easily, while v23.04.11 keeps ending with bsod says "a process or thread crucial to system operation has unexpectedly exited or been terminated". i can see that no one is interested to know how my problem with error 577 got resolved without changing the host os or without using the legacy tool realesed in 2019.
I noticed this installation log. The missing log is from 23.4.11. Have you ever tried to update the patch with updatepack7R2 alone?