I understand that is a suitable process for you and me But if going forward each monthly update after EOS requires manual / forced intervention this is not an ideal solution for people who will either forget to check or just never bother or think about this ? I have had a computer sat for 9 hrs now after TS forge ESU ( activation checks out ok ) I have deliberately witheld from forcing any updates manually after this and no updates are being automatically offered so something is different with the windows update service or process with automated EOS updates ?
This is one of 18 registry edits that I deploy after I install Windows 10 Pro 22H2 64-bit. This is what its contents look like.
It is hard to make sense of that sentence for me, if the updates are offered, whether by pressing the search button manually or waitting till WU finally starts searching for the updates by itself, the ESU stuff works, and that's it.
But thats the point WU is not searching to offer the update ? its only offered if you press the search yourself previously prior to EOS a monthly update would download and be offered at some point automatically The user would then be notified via taskbar prompt to run the monthly update I just feel something now appears different after EOS ?
Again, nobody here will sit and wait for WU to finally start searching, ESU or not, most, if not all, will have pressed the button to death (although the same people blocked auto updates ). I am pretty obsessed with updates and i never seen WU start on itself on my hardware and VM's.
So you have never seen a taskbar message ( windows updates are available ) or the orange dot when you shutdown ( updates are available choose how you want to install ? ) these are always automatic without a manual push for check updates ( I see this on virtually everyone of my clients PCs as very few choose to run or even know about the check for updates option I will leave this computer as it is for testing purposes and we shall see if WU kicks in and notifys about updates available, but so far not looking good here ?
@logicwatch - If you have not intentionally disabled windows updates, perhaps it just requires patience. It seems unlikely that the same automatic updates will roll out simultaneously to everyone everywhere.
On all my machines, where I leave them to auto-update and don't check for updates manually, I find they usually take 24 to 48 hours after Patch Tuesday release to get downloaded, installed, and then prompt for the reboot. Patience is required for those who wait, and for the impatient there is always the check for updates button.
Thanks for all your comments and help guys but I wonder if the answer possibly could be the following ? After using TS Forge ESU I assumed the kb5068781 November update would be offered automatically as I look at the W10 EOS screen in Windows updates ( if I just waited ) My thoughts are this particular update HAS to be manually run after TS Forge ESU is applied kb5068781 is not been offered as an update automatically ( so installing TS forge ESU alone is not enough you then have to manually run the updates check ) After which of course the EOS message is removed and windows update then states You`re up to date So my misunderstanding could be the W10 EOS screen will just sit there until you force this kb5068781 manually Does this make sense guys ? Hopefully next month because we now see a You`re up to date screen next months December update will show up as normal ?
No, you don't need to manually check any scan (scheduled, triggered, manually) will find it if the registry value(s) are correctly set EOS message is removed only after KB5068781 is fully installed (restarted)
I ran TSforge on my Windows 10 Pro computer back in October. My experience yesterday (patch Tuesday) was that KB5068781 was automatically installed without any intervention by me. After reboot, the "end of support" was gone. Again, nothing other than runing TSforge previously was done.
Thank you very much! Can confirm, MAS 3.8 does it - awesome! I was still using MAS 3.7 yesterday and noticed that after TSforge ESU, it was enough to just wait a few minutes. After about 7-10 minutes, both "Win10CommercialKeybasedESUEligible" and "win10ConsumerESUStatus" were automatically set to 1. I was quite surprised - but it was reproducible. I have to disagree there; that’s exactly why I didn’t do anything on my main system except the MAS TSforge ESU. As the "family admin", I just had to know. Today, I got automatically KB5068781 - the OOB (KB5071959) wasn’t installed at all. Spoiler: Not sure if anyone want to, but to avoid installing the 4-6-year ESU... ...it seems sufficient to delete (commenting out does not work) line 5087 from the MAS_AIO.cmd V.3.8. Additionally, in line 5907 (beware that the numbering will change if any previous line(s) are deleted), the 4-6Y Activation ID "0b533b5e-08b6-44f9-b885-c2de291ba456" must be replaced with the last used, e.g. ESU Year3: "83d49986-add3-41d7-ba33-87c7bfb5c0fb" - otherwise ClipESUConsumer.exe or ClipESU.exe will no longer be executed. The text "Windows Update gets 1-3 years of ESU; 4-6 are unofficial but may let you install LTSC updates manually." in the next line can either be ignored or modified. At least, that worked for me - would be great if a pro could take a quick look at it.
Which way do you recommend to get ESU on a Windows 10 installation that is not activated? Is it necessary to activate Windows for the ESU methods to work?