The new updates are ESU stage updates. This project is used for being able to have them pre-integrated/installed: Bypass Windows 7 Extended Security Updates Eligibility
I just did a clean install of Windows 7 Professional SP1 64-bit and installed the necessary device drivers and activated it. I'm now putting version 20.6.11 of the Simplix Update Pack to use. I'll post the results after I'm completely done.
I just finished putting Simplix Update Pack 20.6.11 to use after doing a clean install of Windows 7 Professional SP1 64-bit and installing its drivers and activating it. ----------------------------------- These are the steps I went through while using it: 1. The 1st scan displayed and installed 45 updates. 2. The 2nd scan displayed and installed 2 updates. 3. The 3rd scan displayed and installed 4 updates. 4. Disk Cleanup loaded and ran. 5. Windows 7 loaded. ----------------------------------- These are the steps I went through after using it: 1. Windows Update checked for updates the 1st time. These updates were displayed and installed: Internet Explorer 11 Microsoft .NET Framework 4.8 (KB4503548) 2. Windows Update checked for updates the 2nd time. These updates were displayed and installed: 2020-01 Microsoft .NET Framework 4.8 update (KB4535102) 2020-06 Security Monthly Quality Rollup (KB4561643) 3. BypassESU-v7 was run and option #7 was selected. 4. Windows Update checked for updates the 3rd time. This update was displayed and installed: 2020-05 Microsoft .NET Framework 4.8 update (KB4556399) Note: KB4556399 displayed a failure code 643 and would not install until the bypass tool was put to use first. -----------------------------------
You could have just downloaded abbodi's addons and put them in the same folder as the updatepack.exe and you'd have DirectX 9.0 update, .NET 4.8 installed and updated, Visual C++ runtime libs installed.
@simplix and anyone else with experience for that matter During offline integration, does the updatepack mount winre.wim from within the mounted install.wim index? In my experience, mounting/servicing/unmounting(commit) winre.wim this way makes the final install.wim size larger than it's supposed to be. Like there's some left-over bloat. Copying winre.wim to an outside folder first, servicing it there and then copying it back into the mounted install.wim actually keeps the final install.wim size down, or so I've observed when servicing windows 10 images. I'm not really sure about all of this, I may very well be completely wrong, but I can't really test it on my own. ================================ On a side note, I just tested 20.6.11 in a virtual machine. - clean sp1 media refresh iso with just a language pack - made a new folder in the iso, put in the updatepack.exe and abbodi's DX/NETFX/VC++ addons, saved the changes *when performing an actual install on a physical machine, for example form a usb flash drive, it's enough to just make a folder on the usb drive and put the mentioned files in it, no modifications of windows iso are actually required 1. Installed windows 7 (optional! not necessary if using external storage as install media)1.5. Copied the updatepack folder FROM the iso TO \Downloads folder on the virtual pc 2. Renamed the updatepack to UpdatePack7R2--ie11.exe and ran it as admin 3. After a few restarts for updates, the updatepack installed the addons as well, then it ran Disk Cleanup 4. End result - 7 professional sp1 x86 fully up-to-date, system partition size - ~11.5GB(may vary with actual physical machines due to drivers/other software)
To automatically install updates on a working system together with IE11 and reboot: Rename Pack to UpdatePack7R2--ie11++.exe
you people just dont read the instructions!!!!!! because if that,i suggest the aythors already rename the simplix file,so it automatically updates ie11 etc...
I have no problem with installing IE11 and MNF 4.8 after the Simplix tool is finished. It only takes a few extra minutes.
@shhnedo as long as install.wim is rebuilt (exprted) at the end, the left-over bloat will be left out however, it's faster to service winre.wim from phusical location (i.e. outside install.wim) instead mounted directory
KB4561603 Cumulative update for IE11 June 9, 2020 Greetings all, Not having any success installing KB4561603. It doesn't appear on WU, but KB4561643 was offered. Running the latest simplix update pack with the ie11 switch doesn't seem to do anything as well. Test system was created using the May simplix pack. Code: UpdatePack7R2-20.6.11.exe /ie11 Many thanks and best regards,
@shhnedo I'm not sure that I understood the question correctly, but I will try to answer. In my case, the original winRE.wim from Win7x86rus takes up 143.61 MB and after integrating updates to support NVMe it becomes 144.57 MB. Install.wim itself is not optimized by default because it takes time, but you can use the key /Optimize or /Optimize=esd. @jusilusi KB4561643 already contains KB4561603.
Thanks for the kind reply, simplix. A couple fo quick questions; 1. Does this mean running UpdatePack7R2-20.6.11.exe without the ie11 switch will also install the latest ie11 update? 2. Out of curiosity, I downloaded and ran KB4561603 on a system that has KB4561643 installed. Was expecting a message saying updated already installed, but installation proceeded and was completed successfully after a few minutes. Checking Program and Features' installed updates reveals a new entry created for KB4561603. What do you make of this? 3. Thank you for creating and sharing this splendid tool. A most brilliant piece of work.
@simplix Basically my question is which one of the two methods are you using: Code: 1. dism /mount-image /imagefile:d:\win7\sources\install.wim /index:1 /mountdir:d:\mount_install 2. dism /mount-image /imagefile:d:\mount_install\Windows\System32\Recovery\winre.wim /index:1 /mountdir:d:\mount_winre 3. service the mounted install.wim and winre.wim 4. dism /unmount-image /mountdir:d:\mount_winre /commit 5. dism /unmount-image /mountdir:d:\mount_install /commit or Code: 1. dism /mount-image /imagefile:d:\win7\sources\install.wim /index:1 /mountdir:d:\mount_install 2. copy d:\mount_install\Windows\System32\Recovery\winre.wim d:\win7\sources\winre.wim 3. dism /mount-image /imagefile:d:\win7\sources\winre.wim /index:1 /mountdir:d:\mount_winre 4. service the mounted install.wim and winre.wim 5. dism /unmount-image /mountdir:d:\mount_winre /commit 6. copy d:\win7\sources\winre.wim d:\mount_install\Windows\System32\Recovery\winre.wim /y 7. dism /unmount-image /mountdir:d:\mount_install /commit When you're mounting winre.wim, what is the /imagefile path: is it inside the mounted install.wim index folder(in my example mount_install), or is it outside(in my example, next to the install.wim file)? And does THAT by itself affect the final install.wim size(regardless of optimization)?