Bypass Windows 7 Extended Security Updates Eligibility

You say that as if some underground hacker group produced and distributed these updates on behalf of Microsoft. What is so shocking about Microsoft's "2024-02 Security Monthly Quality Rollup for Server 2008 R2" update working on Microsoft's Server 2008 R2? The question here has always been how do we get these updates. We already know they work.

- Not an "urgent security fix". This has never been true.
Microsoft always sits on rollups for a month before bestowing them upon their public at their discretion. Your machine with the Feb 13th 2024 rollup installed is running a version of Windows that M$ built on January 8th 2024 and hoarded until Feb 13th. Your machine is always at least one month out of date. Actual component based servicing died years ago.

- Not "forced to release" this update. This has never been true.
Software monopolies this massive are never "forced to release" updates (forced by what, hm? there are no regulations, no threatening bigger fish). Every action they take on their products & services has been planned many years in advance, especially when there are hundreds of billions of dollars riding on those actions ($211,900,000,000 publicly in msft's case).
Microsoft sold agreements to update NT 6 until at least January 2026. The revenue from that (which is beyond simple dollars) has funded, is funding, and will fund their operations. Microsoft intends to collect this revenue, and so they will fulfill their contract. They were never "forced" to do this. They voluntarily chose to create & sell the Premium Assurance program to chase the money they smelled, and they will continue to execute it so long as it is profitable.

- "Microsoft doesn't say" anything about <abc> or <xyz> or whatever. This has always been true.
Yes, they are great at lying by omission and are also great at normal lying as well. In both cases this means you need to observe their actions, not their words.
M$ will tell you whatever scary words it takes to get you to loosen up your wallet for them. "No more ESU! It's over! There's no Year 5! We never sold Premium Assurance! Server 2008 is dead! Buy Bugcrash 11 today or else!" Its centuries old business propaganda, and it still fools the unwashed masses so very well. Were you convinced?

I'll direct you and all the other Microsoft/megacorp novices to some posts I made last year on these topics. They may answer some of the questions you have.
Regarding NT 6 update policy: https://forums.mydigitallife.net/th...dates-eligibility.80606/page-356#post-1778169
Regarding Years 5 & 6 literature policy: https://forums.mydigitallife.net/threads/bypass-windows-7-extended-security-updates-eligibility.80606/page-380#post-1806858

Lastly, I will say please don't feel singled out by this post. We periodically get people here who are very confused/misled about these matters, but not everyone bothers to post their thoughts. There are many silent lurkers with the same thoughts as you who will benefit from having those misconceptions dispelled. Those who do post, however, sometimes come back bitter and personally offended when they are educated, hence this last little paragraph here.

 

You need to login to view this posts content.

 

They are not going to listen to you!! There may need to be some suspensions.

 

Just remove the browser themed comments to your posted link. That is how I learned to pay attention when warned that I was bringing in subject matter that should be discussed elsewhere. ;>)

 

I am clean installing Win7 Sp1. With an ISO that has all "public" updates until the "end" of Win7 in 2019.

1. Can I do ALL updates until today, with ESU 12?

2. Are there complete downloads for all updates (cumulative, I believe is the english word?) ? I use a stand alone, one user, desktop?
I would really be grateful if someone would give me the KBs, if possible, so I can get them from the MIcrosoft Update Catalog.

If there is already a similar post to this (I could not find one) please, also let me know.

Thank you

 

A basic question:

I downloaded the ESU12 from post one.
Is ESU 12 good for all updates since the official stop, or do I also an older one for the early ones?
I think that was in 2019? (I am doing a clean install of an Win7 Sp1, with only "public" updates)

Thank you

 

Thank you, yes, I thought I read about the pre-requesites. I will go step by step and do the install on an old 100Gb SSD... and then use Macrium once it works properly.

 

why im getting this update ? it popped up today. im using win7pro with all updates installed including bypasstool v12

 

If you question it run "check for Updates" & see if it pops up again. If it does then update. If it does not then problem solved. ;>)

 

YES !!!! Thank you, gamazet, abbodi and Enthousiast.
Exactly what I was looking for.

One more: "(normally Pack should be placed in appropriate Disk or Folder)", which folder would that be?

I do need to install ESU12 before installing the updates?

 

SIMPLIX can be run from anywhere when updating a LIVE System. When I build Win07 Systems, I use SIMPLIX to update a 2011 RTM version of Win07 Enterprise, and when done, it has every needed update to date.

This should be taken out of this thread, BTW

 

I have a problem with KB5022338, maybe related, definitely strange.
I use abbodi1406 w7esui script (thank you, thank you so much abbodi1406) to install KB5022338, which of course worked perfectly,
it was listed nicely in the Installed Updates, next day I did install KB5029296 (with KB5028264 servicing stack update)
and to my surprise KB5022338 disappeared... Neither Installed Updates nor wmic qfe list show KB5022338 as installed.
More or less same happens when using wkeller's integrate7 script (dism installs the update but it is then not listed)
OS is Win7 Pro 64bit. Anybody had the same issue, please? Or I am doing something terribly wrong?

 

Any installed package can be marked as invisible in registry, there should be a bug that add needed key. Of course I have not tested it. Just side note information. In my own solution I mark all installed updates as invisible as I’m removing updates backup in Syspreped images. There is no need to be able to list them in DISM or WMIC, Windows / Microsoft update will be clear and of course no need to revert to old update backup when deploying stable Syspreped images. Image build is always updated with latest updates and that should be enough to identify latest installed updates

 

Although a little late, I found this

NT 6.0 (Vista) and 6.1 (Win7) will continue to be supported until 2026-01/13
NT6.2 (Win8) and NT6.3 (Win8.1) will continue to be supported until 2029-01/09
Build 14393 (Win10 Ver.1607) will continue to be supported until 2033-01/11
Don't bother with POSReady at all