Well Support old version instead using newer version Will not go forever... And someday I will have to leave my old 10.x system, and install w.11
Good bye to one of the best Operating Systems and the most beautiful Microsoft OS ever created. Thanks to MDL, all the Engineers at Microsoft who designed it and to Simplix for keeping this OS updated for us, the legendary Windows 7 (2009-2023) Will be installing the most updated version soon on my new machine to keep me fond of it's memories.
If there's a way to keep Windows 7 alive after 01-10-2023, I'm confident that someone will submit the procedure after the next "patch Tuesday" on 02-14-2023.
Spoiler: Usage translation to English The system should have at least 10GB of free disk space and preferably at least 1GB of free RAM. You can drag and drop a clean ISO distribution to UpdatePack7R2 and get a ready to use updated ISO image. You can use the following options and their combinations for a flexible installation: /Reboot to automatically reboot if needed. /S option for a completely silent installation without windows or messages. It's case sensitive. /Silent for a passive installation - you can see the progress dialog, but the installation is fully automatic. /Temp= allows you to specify a temporary working directory. It doesn't have to be empty, but it must exist. /NoSpace allows you to skip checking for free space on the system partition, it is not recommended. /FixOn turns on protection against Meltdown and Spectre, while the /FixOff turns it off. Without the option, protection is disabled for Windows 7, and enabled for Win2008R2. Examples: Need to automatically install all the updates, IE11 and reboot the computer: UpdatePack7R2.exe /silent /reboot You need to quietly install all the updates for existing products and not to reboot the computer: UpdatePack7R2.exe /S The following options are designed to integrate updates into the distribution: /WimFile= specify the location of the WIM file, you must specify an absolute path. /Index= specify the system index in the WIM file, it is necessary to perform the integration again for each index. /Index=* allows to integrate updates into all the WIM indexes in turn. /Boot= specify the boot.wim location for integrating NVMe and USB3 support. /Optimize allows to optimize the size of the WIM file after updates have been integrated. /Optimize=esd converts the WIM file to ESD after updates have been integrated. /NoUSB cancels the integration of the generic USB3 driver from daniel_k. Notes: It is useful to run the command before specifying the index: Dism /Get-WimInfo /WimFile:C:\install.wim (replace the path with your own). When upgrading boot.wim you need to copy new files from the sources folder to the distribution according to the instructions. Examples: Need to integrate IE11 and all the updates into index 1: UpdatePack7R2.exe /WimFile=C:\install.wim /Index=1 IE11 and all updates should be integrated into all the indexes: UpdatePack7R2.exe /WimFile=C:\install.wim /Index=* If the integration is successful, the Windows 7 distribution, Server 2008 R2 or the working system will be updated to the current state and the following can be seen on the screen: Additional features: It is possible to automatically install SP1 if it is not installed on the system. To do that, put the Windows6.1-KB976932-X86.exe and Windows6.1-KB976932-X64.exe files in the same directory as the kit. If there is UpdatePack7R2Start.cmd in the same directory - it will be executed before installing updates, UpdatePack7R2Finish.cmd - after installation, UpdatePack7R2Wim.cmd - after updates integration. By default, the console windows will be shown. To hide them, the first line in the cmd file must start with ":hide" (without quotes). The update set keeps track of the exit code of the cmd files, in case you need to reboot. This code is 3010 (command exit 3010). If you want to apply your tweaks after installing Internet Explorer 11 on the working system, place the file ie11.reg in the folder with the update kit and it will be imported automatically. Some of the keys can be replaced by renaming the update kit file itself. For example, you can add "--" anywhere in the update kit filename for automatic rebooting and "++" for passive installation. Supported installation and integration of addons: SmartFix, DirectX, .NET Framework, Visual C++. Addon files need to be placed in the same folder as UpdatePack7R2. Examples: You need to automatically install the update kit on the working system along with IE11 and reboot the computer: Rename UpdatePack7R2.exe to UpdatePack7R2--++.exe This would be exactly like using the following options: UpdatePack7R2.exe /silent /reboot Notes The size of the distribution (WIM file) will be increased by the size of the installed updates. Integrated updates can be removed after the system is installed. It is recommended that the running antivirus is paused for the duration of the update to speed up the process. The detailed log of the updates installation can be found in the file %WinDir%\UpdatePack7.log. The installation on the working system will be done in several stages with reboots. To install and boot the system on new UEFI devices there is a project called UefiSeven.
I am completely out there a year ago once built a version with Simplix. If I would now build an Enterprise version, is the update capable, with the ESU patch from Abbodie
It will be updated with the latest and most likely last ESU updates but if you want you can install ESU Bypass by @abbodi1406 manually.
I would write the bypass of Abbodie into the stupcomplete anyway. My question was actually only about whether the updates work with the ESU patch from Abbodie. hope my english is not too bad *g mean the monthly updates whether they would then still work with the patch from Abbodie