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?
Great script. The created shortcutway made by whatever is simply amazing... Made it a little more windows 7 friendly...Seems it's not really tested from a windows 7? Atleast with a couple test runs from windows 7 spotted some small bugs... no pun intended here whatsoever...cuse Enthousiast is a real helpfull human being. Code: :: ===================================================== Modified a little to service flawlessly on Windows 7 :: ===================================================== 1] Added portable DISM Version: 10.0.22621.1 Use Windows 7 default DISM // ADK 8.1,10 if any are installed // Portable Dism Version: 10.0.22621.1 2] Added a SED command to get the correct DISM variable (Portable DISM - ADK 8.1/10 - Windows 7 default DISM) to Cleanup Mountpoints properly /// Written to "W7AIO_Project_CleanUP_Script.cmd" Else it might ERROR while doing a Cleanup-WIM with "DISM /Cleanup-Wim" SET and using Dism from ADK 10 for example... 3] Added double quotation marks to %_wimlib% and %_dism% to escape spaces in the FILE PATH Else the script reports "not found" ERROR and moves on. Same for Dism... 4] Added a DaRT Spyware System Sweeper Definitions updates PART to include latest updates for Boot.wim and WinRE.wim Verify the 2 required updates needed for the definitions to work. Install both if they are missing. Not really needed if one updates all images anyway. It is required for the tool and latest definitions to work. Windows 7 ftw
HP 800 mini G3, shipped with Windows 10. It's Intel skylake CPU (i5-6500T processor 6th generation/Intel HD Graphics 530). I was trying to install Windows 7 x64 on it but got black screen after Windows logo before "Install now". the modded media worked for ASUS skylake CPU PC install but failed to work on HP 800 mini G3.
Sorry in advance, since this doesn't directly pertain to the MDL Win7 Tool for Simplix Update7... I too am getting a blue error screen on startup, halfway through the Win7 boot screen. Using Update7R2-23.4.11 on a clean install of Win7 Professional and Ultimate x64. I posted in further detail here: https://forums.mydigitallife.net/th...win7-distribution.45005/page-228#post-1786361 I might have a go with the update pack from this package instead, since I'm only using Win7 offline and there probably haven't been any updates which would affect performance for gaming since 2022. Thanks for your work on this! Just wanted to mention this in case my issue lines up with the other mention of a blue screen error, using the latest Simplix pack.
Have you tried to disable secure boot & delete all embedded keys or certificates, before starting installation from the simplexed iso on Hp mini pc?
I actually just used UpdatePack7R2-23.4.11 (with the /Silent /Reboot /NoUSB switches) on a live system after a clean install, NOT the MDL Win7 Tool (hence the intro apology...). Using an old Win7 Ult x64 SP1 image. Which may have been a problem somehow or another. But also had the boot loop happen on a previous install of Win7 Pro x64 (which had been used for quite some time) and had the same thing happen. My best guess tells me it was caused by the Nvidia 15.49 drivers I use for my chipset, since only after installing them did I encounter the boot loop. Possibly an update conflicting with my hardware, since there were 51 updates installed after using the Simplix installer, but 49 updates installed after using system restore - after encountering the boot loop. My motherboard is very weird and has some quirks to it when it comes to drivers and Win7, so it wouldn't surprise me if it does have something to do w my hardware. The video and audio drivers install fine on a normal Win7 install, but technically they were programmed for Vista. I'll be trying the MDL Legacy integrator properly here soon. Studying to make sure I get all the steps right. I'll report back when I do. Edit: I will also add that I am on a legacy BIOS only system (no UEFI) and did not have the ADK/dism package installed if that matters. Since you also experienced the bsod at boot with 23.4.11, I wonder if it's something specific to that release. Though iirc the only thing that was changed was the removal of ESU? I could be wrong. Perhaps one or two versions prior to the current release might go through successfully... Getting ready to test the modern MDL Tool results tonight using UpdatePack7R2-23.4.11
I was able to install Win7 via the Modern MDL Tool with the 2022 UpdatePack7 included. Haven't spent much time in Win7 yet at this point. I have noticed my theme keeps getting knocked off of Aero to Basic for some reason, and the system seems a little sluggish compared to my old install updated with WSUS Offline (old update compilation from just before Win7 reached EoL and updates started disappearing or receiving errors trying to download them via WSUS Offline), but everything seems fine other than that. I might try the legacy tool to see if there may be any difference with my very dated hardware. Perhaps by installing drivers manually there are some conflicts somewhere...
So, as far as I can tell, the chipset drivers were the issue on my end. I have a Radeon R7 250 2GB GDDR3 (OEM) for dedicated graphics, which there is no issue with. However, my motherboard has Geforce 6100 onboard graphics and nForce4 chipset. I always had issues installing chipset and graphics drivers for my motherboard, as they are targeted for WinXP and Windows Vista. Windows 7 support was added later, and I suspect they might install using a compatibility layer. (I have 2 nearly identical motherboards with this infernal gpu/chipset combo. The other with Geforce 6150SE/nForce4 instead.) AMD has old legacy nForce4 drivers along with another legacy driver package, the latest version being 15.49. After attempting to install the 15.49 drivers, that's when I experienced the bootloop. I have since used MDL Legacy Tool with both the provided Simplix 2022 update and the most recent 23.4.11 update - omitting installing the 15.49 drivers for my chipset and haven't had any issues so far. Not sure if I needed to, but I even used Windows Update to install a handful of updates without issue. Along with manually installing Radeon GPU and VIA audio drivers. The 3 drivers that 15.49 installs are Away Mode driver, SATA Storage driver (includes RAID stuff), and Nvidia Forceware Network Manager (which is borderline useless), so I'm betting one of those is creating some sort of conflict. Though, I can't imagine how it would create a critical boot error leading to a bootloop. I'm betting that one or more of the drivers that the 15.49 package tries to install are already included with Simplex UpdatePack (DriverPacks maybe in there somewhere?) and some files are overwritten by the installer. Did you ever figure out what was causing your crash?