I have two questions: Where do I put the file Autounattend.xml (It needs to be at the root of the iso to works) ? Hwo can I enable Meltdown fix but keep Spectre fix off ?
Again... Tried today using the Single Index x86, all ok but Batch Error when Simplix Pack need to do his job And the ISO I done some days ago still missing "compbatt.sys" file... What's wrong with me ?? The OS i'm using is Windows 10 Pro 2004 (19041.630) 64bit The original ISOes i'm using are: - W7_it_windows_7_ultimate_with_sp1_x86_dvd_u_677443.iso SHA1: 3378d4bfdbab850407ab6047b68fa9cbb2275b75 SHA256: dac1af059bc4ec5b2592eb43ae70ca0936ae524807d5e34a40b775b8776e8440 - W7_it_windows_7_ultimate_with_sp1_x64_dvd_u_677356.iso SHA1: 9af84e5a557c30f9d0c10bdc5fed339a7159f830 SHA256: 2ea42c7c7cd72cebd73eb240d681b499b7d2b18cf94fa3de2071d3707804ce6e - Win10_20H2_v2_Italian_x32.iso SHA1: 2ac20b990088f552cb62407ed3f29351ced7bb60 SHA256: 6d4a4aed64dbf6fc2677d097df4328d1eac9852ed0c8dc431129057a86e40dbe - Win10_20H2_v2_Italian_x64.iso SHA1: e38c45f292267fa11632f41936dd63966409f5aa SHA256: ededea10c1b7d0e664994b8d909530bab3e5c8ac11178c75b0e0236a0e112156 The UpdatePack hash is: - UpdatePack7R2-21.1.15.exe SHA1: 1624d38f2f41f114ede6ca4108e6884bfacec700 SHA256: a61630bcb257a32bcc62018ae70cc0fd4d86ffde585bb3bd6745885bf8731622
You could start everything from the beginning, namely: 1 - Unzip the tool to a short path, for example: E:\SiMPLiXAiO 2 - Use only original Windows 7 ISO's, which know all the index. (Enthousiast posted the download link on the front pages) For Windows 7, i use: - pt_windows_7_ultimate_with_sp1_x64_dvd_u_677358.iso - pt_windows_7_ultimate_with_sp1_x86_dvd_u_677457.iso 3 - For Windows 10, i use: - pt_windows_10_enterprise_ltsc_2019_x64_dvd_3e7f778a.iso - pt_windows_10_enterprise_ltsc_2019_x86_dvd_193e121c.iso Try using this version or earlier 4 - Check and update the remaining folders: Addons, EXE, SMARTFIX and OEM NOTE: Remember that folders must contain only one executable, for example: Addons_x64_x86: DirectX_June2010_x64.WA, dotNetFx48_20210117_x64.WA, dotNetFx48LP_x64_PTB.WA and vcredist_x64_Win7_20210117.WA EXE: UpdatePack7R2-21.1.15.exe 5 - Before running "W7_x64_AiO_New_2.3.cmd" disable your antivirus 6 - Run the tool as an administrator Try and see if it works for you ... If errors occur again, before closing the command prompt, copy and paste the content for review. possible failures. Good luck!
That error is on the updatepack part, i get it too lately, rebooting the host and re-running the script works for me in all tests. example: Code: The installation log of UpdatePack 7 / 2008 R2 / 21.1.15 Installation start time - 14:29:39 18.01.2021 Operating system - Windows 7 Starter SP1 x64 UpdRoots - Integration of the update has been successfully completed KB917607 - Integration of the update has been successfully completed KB2533552 - Integration of the update has been successfully completed KB2545698 - Integration of the update has been successfully completed KB2547666 - Integration of the update has been successfully completed KB2574819-v2 - Integration of the update has been successfully completed KB2592687 - An advanced installer failed during setup or servicing. KB2603229 - The return code is 0x800F0830 KB2667402-v2 - The return code is 0x800F0830 Installation finish time - 14:49:13 18.01.2021 The number of installed updates - 6 Total installation time of UpdatePack - 19:34 Updates installation was interrupted
Thanks but... THAT IS what i done If you read my message you see i used original Microsoft ISOes, checking also the hash for each Oh... so why you never had this error before?? I saw many logs of your integration, recently, all of them good.
oh... so there is something with my Windows 10 Pro system... I rebooted many and many times thanks Enthousiast
Hi @Enthousiast can we keep use default windows 7 boot.wim? i'm only need integrate update and drivers. Thanks
@Enthousiast is there a reason why in the AiO x86 version the command: %_wimlib% optimize "WIM\aio.install.wim" is after the SKUs creation, and in the AiO x64 version is even before the Simplix Pack integration? Thanks Oh, for "my problem" i reinstalled Windows 10, then run your tool and the integration was done without errors
Because for x64 starter needs to be created first to serve as base and i optimize it after it's created (not really needed but it's in). x86 has starter available from the used iso.
So what does this exactly do? Create some kind of hybrid Frankenstein between Windows 7 and Windows 10? What are the advantages, and could there be any conflicts that arise from such an operation?
I've had great success using this script until the latest release (SiMPLiX_AiO_ISO_Bare_Tool_2_3_21.01.15_NEW) with latest simplix.exe and clean verified Win 7 x54, x32 and Win 10 x64 (ultimate) iso's. I've tried twice now on a Win 10 PC (cleanly unzipped to a newly created folder such that the contents are in short folder such as c:\1 and it starts ok and then complains about files not being found (sorry for not being more accurate of having logs) This is running the W7_x64_AiO_New_2.3.cmd batch file. A clean up, reboot, try again fails in the same way. All logged on as admin and running the batch file with admin rights (should inherit but hey . . .) Using the previous bare script expanded into a clean new subfolder, i,e delete all the old ones and make a new '..\1' for example, adding back simplix exe and three iso's, it works and completes perfectly every time. Not a big deal for me as only making a new up to date AIO iso with those few newer addons for the sake of it. I see others have had strange issues of late, but mine failed with slightly different error's than I have seen posted here. Do not believe it's anything with the boot OS nor the master iso's or simplix.exe as it works with Enthusiasts earlier script. Just surprised it's not failing for everyone otherwise there may have been some bug introduced with the new script, but again, that does not seem to be the case. Don't worry about investigating, just mentioning seeing this wierdness but only if attempting to use the latest script (bare tool) - every other supplied source file and freshly booted Win 10 host PC the same. Thanks for all the hard work - always appreciated. .