EDIT : Thank you thank you, thank you! I spent WEEKS trying to get Win7 installed on NVMe, going through the various integrator tools including Integrate7 and had no idea this tool existed at the time. Nothing seemed to recognise the drive. The only 'issue' I had with this tool is that when selecting a hard drive to install to for some reason Windows said my BIOS can't boot from this drive - but it let me go through with the install and everything seems peachy. Got Subscribestar? Oh, thanks. That being the legacy one was not obvious.
The legacy script created ISO, based on win 7, can do inplace upgrades and run on ancient hardware, the modern ones, based on win 10, can't.
Biggest difference: Without the Setup program from Win10, you cannot use INSTALL.ESD (high compression). Legacy Win7 Setup only supports INSTALL.WIM and INSTALL.SWM (split WIM). Edit: Plus what @Enthousiast said above.
I have setup a system created using Legacytool, all is working fine. While going through the settings once again I noticed that the Spectre/Meltdown switch was OFF. Is this still a big of a issue as before?
Newer generations like 6th gen won't be affected that much? I've created this Win7 setup to run in VM.
Intel processors with PCID (Haswell or newer) take only a minimal performance hit from Meltdown mitigations. Older generations are not so lucky. InSpectre can report that, too. Spectre mitigations without big performance hit need eighth generation Core or newer. It's best to simply test it for your special scenarios, if you "feel" the difference in performance, and if you accept it.
I've switched from FixOff to FixON in last line of SiMPLiX.bat and made a new ISO. In InSpectre app it shows Meltdown YES, Spectre as NO.
Oooooohhhhh, it just clicked with me today. I was thinking legacy meant it was an older version of the tool.
UpdatePack7R2-21.7.7.exe https://forums.mydigitallife.net/th...win7-distribution.45005/page-198#post-1672862
I'm surprised to see that 21.7.7 has been released. I wasn't expecting another UpdatePack7R2 update until a few days after July 13th "patch Tuesday". Anyway, it's now in the same folder as the June 8th dotnet and vcredist add-ons.
MSFT released an important (out of band, fix a loophole, iirc) update, so @simplix made an updated pack.
I feel embarrassed for even having to post this. Couldn't sort it out on my own, and after a search around here, still couldn't find anything. Whenever I run one of the batch files to begin the process, I see a command window with "Check for Admin Rights", then it closes and nothing happens. On Windows 10 19043.1083. Have tried running from C:\ and another drive, double clicking, right click .bat -> Run as administrator, Opening command from Search -> Run as administrator and then running .bat from within command. Still can't seem to get it to run. Any help would be greatly appreciated.
The bat file is not the file to run, run the cmd file of your liking and the bat file will be called when it starts using the updatepack to update all. From the OP: