https://0patch.com/index.html
Hey I just read this 1st time last week but this was out there in Oct 22' mostly unconfirmed now official.
BWHUAHAHAHAHAHA!! Screw OTT streaming, more subscriptions, skull raping ads and mouth breathin marketeers collecting m'data!!
7MCE will never effing die! lol Win8 users tho... sorry man
2 MORE YEARS of Win 7 security patches
Forum rules
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
★ Download the latest EPG123 here: https://garyan2.github.io/ <> Setup guide here: https://garyan2.github.io/install.html ★
-
mustpushbuttons
- Posts: 52
- Joined: Tue Dec 31, 2019 6:20 pm
- Location:
-
HTPC Specs:
-
mustpushbuttons
- Posts: 52
- Joined: Tue Dec 31, 2019 6:20 pm
- Location:
-
HTPC Specs:
OK looks like 0patch in memory hack may work but I'm not using it for now. Below is very well written summary of win7 support (through 2026?) from mydigitallife thread on win7 esu bypass. carry on.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
""Microsoft will be updating the NT 6.x codebase (Vista, 7, 8, and 8.1) until at least 2026, due to the "Premium Assurance" sales that they made to enterprise customers. This means that all of these versions of Windows continue to receive updates from Microsoft, despite the various lies and propaganda that Microsoft peddles to the public. The problem is that Microsoft will stop releasing these updates for their Windows products after the stated EOL date for that product. This is accomplished by placing artificial locks in the update files and in the Windows Update service that prevents the updates from being installed on versions of Windows that are no longer "in support". This is the problem that we play a cat and mouse game with.
Jan 2020 to Jan 2023
Microsoft's stated EOL date for consumer Windows 7 clients was Jan 2020. When Feb 2020 rolled around, Microsoft was still producing NT 6.1 updates, but they stopped making them available to Windows 7 clients. These updates were only available for Windows 7 ESU, Windows Embedded Standard 7, Server 2008 R2 ESU, etc.
"Windows 7 ESU" is a different logical entity than "Windows 7". Same OS and same core files, but different SKU and therefore different business & support agreements. Starting Feb 2020, the MSU update packages for NT 6.1 included artificial locks that prevented them from being installed on a "Windows 7" client.
Enter abbodi's ESU Bypass. By installing Microsoft's ESU preparation updates as well as abbodi's ESU Bypass on a "Windows 7" client, you change your "Windows 7" client into a "Windows 7 ESU" client. Now when you try to install the MSU package, the artificial lock does not trigger, because your computer is now "Windows 7 ESU" and not "Windows 7" anymore. "Windows 7 ESU" is still supported by these updates; "Windows 7" is not. Same OS and same core files, but different SKU. Same updates, but different EOL date and support timeline from Microsoft.
Feb 2023 to Oct 2023
Microsoft's stated EOL date for "Windows 7 ESU" was Jan 2023. Now that Feb 2023's Update Tuesday has come, Microsoft is still producing NT 6.1 updates, but they have stopped making them available to "Windows 7 ESU" clients. These updates are now only available for WES7 ESU, Server 2008 R2 ESU, etc.
"Windows Embedded Standard 7 ESU" is a different logical entity than "Windows 7 ESU" and "Windows 7". Again, same OS and same core files, but different SKU and therefore different business & support agreements. Starting Feb 2023, the MSU update packages for NT 6.1 now have a new artificial lock that prevents them from being installed on a "Windows 7 ESU" client. For those counting, the SKUs that are blacklisted from accepting NT 6.1 updates now include "Windows 7", "Windows 7 ESU", and "Windows Embedded Standard 7". The SKUs that do not have artificial locks yet include "Windows Embedded Standard 7 ESU" and "Server 2008 R2 ESU".
Enter v12 of abbodi's ESU bypass. It tricks our "Windows 7 ESU" clients into bypassing the new artificial lock. Now when you try to install a "WES7 ESU" or "Server 2008 R2 ESU" update MSU package, the artificial lock does not trigger, and the update can be installed successfully. WES7 ESU is the same OS as WES7 and Windows 7 and Windows 7 ESU and Server 2008 R2 and Server 2008 R2 ESU. Same core files, but different SKUs. Same updates, but different EOL dates and support timelines from Microsoft.
Nov 2023 to ???
Microsoft's stated EOL date for "WES7 ESU" is Oct 2023. When the Nov 2023 Update Tuesday comes, Microsoft will still be producing NT 6.1 updates, but they will stop making them available to "WES7 ESU" clients. These updates will become only available for Server 2008 R2 ESU. (edit: and still available for POSReady 7, too, but I don't know if POSReady 7 is functionally equivalent to the mainline NT 6.1 SKUs so I can't say for certain if updates for POSReady 7 will work as intended on Windows 7).
"Server 2008 R2 ESU" is a different logical entity than "WES7" and "WES7 ESU" and "Windows 7 ESU" and "Windows 7". Again, same OS and same core files, but different SKU and therefore different business & support agreements. Now you can probably see where this is going... Starting Nov 2023, the MSU update packages for NT 6.1 will have yet another new artifical lock that will prevent them from being installed on a "WES7 ESU" client (in addition to all the other SKUs that have already been locked out).
When this day comes, Microsoft will only be releasing NT 6.1 updates for the "Server 2008 R2 ESU" SKU. All other SKUs will be blacklisted by the artificial locks. abbodi will most likely update his ESU Bypass tool again and provide us with new instructions for tricking Windows Update into bypassing the new locks and allowing us to install the Server 2008 R2 ESU update MSU packages on our Windows 7 clients. Same OS and same core files, but different SKUs. Same updates, but different EOL dates and support timelines from Microsoft.
This is the cat and mouse game that Microsoft plays. It only exists because of negotiated support contracts with customers and the desire to rake in billions. It has nothing to do with the technical resources required to update NT 6.x, which are a drop in the bucket anyways.
You can verify everything I've said by going to the Microsoft update catalog, picking any monthly rollup KB from the last 8 years, and inspecting the version for "Windows 7" vs "WES7" vs "Server 2008 R2". April 2016 rollup? The MSUs for 7, WES7, and Server are identical. November 2017 rollup? The MSUs for 7, WES7, and Server are identical. December 2019 rollup? The MSUs for 7, WES7, and Server are identical. They all are.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
""Microsoft will be updating the NT 6.x codebase (Vista, 7, 8, and 8.1) until at least 2026, due to the "Premium Assurance" sales that they made to enterprise customers. This means that all of these versions of Windows continue to receive updates from Microsoft, despite the various lies and propaganda that Microsoft peddles to the public. The problem is that Microsoft will stop releasing these updates for their Windows products after the stated EOL date for that product. This is accomplished by placing artificial locks in the update files and in the Windows Update service that prevents the updates from being installed on versions of Windows that are no longer "in support". This is the problem that we play a cat and mouse game with.
Jan 2020 to Jan 2023
Microsoft's stated EOL date for consumer Windows 7 clients was Jan 2020. When Feb 2020 rolled around, Microsoft was still producing NT 6.1 updates, but they stopped making them available to Windows 7 clients. These updates were only available for Windows 7 ESU, Windows Embedded Standard 7, Server 2008 R2 ESU, etc.
"Windows 7 ESU" is a different logical entity than "Windows 7". Same OS and same core files, but different SKU and therefore different business & support agreements. Starting Feb 2020, the MSU update packages for NT 6.1 included artificial locks that prevented them from being installed on a "Windows 7" client.
Enter abbodi's ESU Bypass. By installing Microsoft's ESU preparation updates as well as abbodi's ESU Bypass on a "Windows 7" client, you change your "Windows 7" client into a "Windows 7 ESU" client. Now when you try to install the MSU package, the artificial lock does not trigger, because your computer is now "Windows 7 ESU" and not "Windows 7" anymore. "Windows 7 ESU" is still supported by these updates; "Windows 7" is not. Same OS and same core files, but different SKU. Same updates, but different EOL date and support timeline from Microsoft.
Feb 2023 to Oct 2023
Microsoft's stated EOL date for "Windows 7 ESU" was Jan 2023. Now that Feb 2023's Update Tuesday has come, Microsoft is still producing NT 6.1 updates, but they have stopped making them available to "Windows 7 ESU" clients. These updates are now only available for WES7 ESU, Server 2008 R2 ESU, etc.
"Windows Embedded Standard 7 ESU" is a different logical entity than "Windows 7 ESU" and "Windows 7". Again, same OS and same core files, but different SKU and therefore different business & support agreements. Starting Feb 2023, the MSU update packages for NT 6.1 now have a new artificial lock that prevents them from being installed on a "Windows 7 ESU" client. For those counting, the SKUs that are blacklisted from accepting NT 6.1 updates now include "Windows 7", "Windows 7 ESU", and "Windows Embedded Standard 7". The SKUs that do not have artificial locks yet include "Windows Embedded Standard 7 ESU" and "Server 2008 R2 ESU".
Enter v12 of abbodi's ESU bypass. It tricks our "Windows 7 ESU" clients into bypassing the new artificial lock. Now when you try to install a "WES7 ESU" or "Server 2008 R2 ESU" update MSU package, the artificial lock does not trigger, and the update can be installed successfully. WES7 ESU is the same OS as WES7 and Windows 7 and Windows 7 ESU and Server 2008 R2 and Server 2008 R2 ESU. Same core files, but different SKUs. Same updates, but different EOL dates and support timelines from Microsoft.
Nov 2023 to ???
Microsoft's stated EOL date for "WES7 ESU" is Oct 2023. When the Nov 2023 Update Tuesday comes, Microsoft will still be producing NT 6.1 updates, but they will stop making them available to "WES7 ESU" clients. These updates will become only available for Server 2008 R2 ESU. (edit: and still available for POSReady 7, too, but I don't know if POSReady 7 is functionally equivalent to the mainline NT 6.1 SKUs so I can't say for certain if updates for POSReady 7 will work as intended on Windows 7).
"Server 2008 R2 ESU" is a different logical entity than "WES7" and "WES7 ESU" and "Windows 7 ESU" and "Windows 7". Again, same OS and same core files, but different SKU and therefore different business & support agreements. Now you can probably see where this is going... Starting Nov 2023, the MSU update packages for NT 6.1 will have yet another new artifical lock that will prevent them from being installed on a "WES7 ESU" client (in addition to all the other SKUs that have already been locked out).
When this day comes, Microsoft will only be releasing NT 6.1 updates for the "Server 2008 R2 ESU" SKU. All other SKUs will be blacklisted by the artificial locks. abbodi will most likely update his ESU Bypass tool again and provide us with new instructions for tricking Windows Update into bypassing the new locks and allowing us to install the Server 2008 R2 ESU update MSU packages on our Windows 7 clients. Same OS and same core files, but different SKUs. Same updates, but different EOL dates and support timelines from Microsoft.
This is the cat and mouse game that Microsoft plays. It only exists because of negotiated support contracts with customers and the desire to rake in billions. It has nothing to do with the technical resources required to update NT 6.x, which are a drop in the bucket anyways.
You can verify everything I've said by going to the Microsoft update catalog, picking any monthly rollup KB from the last 8 years, and inspecting the version for "Windows 7" vs "WES7" vs "Server 2008 R2". April 2016 rollup? The MSUs for 7, WES7, and Server are identical. November 2017 rollup? The MSUs for 7, WES7, and Server are identical. December 2019 rollup? The MSUs for 7, WES7, and Server are identical. They all are.