Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.microsoft.windows > #2838 > unrolled thread

October 15, 2025 Your version of windows has reached the end of support [19045.6456]

Back to article view | Back to alt.comp.microsoft.windows

Contents

  October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-15 11:06 +0000
    Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] "Joel W. Crump" <joelcrump@gmail.com> - 2025-10-15 07:16 -0400
      Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-15 19:13 +0000
        Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] "Carlos E.R." <robin_listas@es.invalid> - 2025-10-15 23:26 +0200
          Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 06:30 +0000
            Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 09:04 +0000
              Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 10:30 +0000
                Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 13:08 +0000
    Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Steve Hayes <hayesstw@telkomsa.net> - 2025-10-16 03:07 +0200
      Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Paul <nospam@needed.invalid> - 2025-10-15 22:01 -0400
        Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 23:54 +0000
      Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Flash Drive <Flash.Drive@yahoo.com> - 2025-10-16 04:41 +0000
        Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 07:39 +0000
      Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 08:11 +0000
        Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] MikeS <MikeS@fred.com> - 2025-10-16 11:44 +0100
          Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 14:13 +0000
            Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Java Jive <java@evij.com.invalid> - 2025-10-16 23:34 +0100
              Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-17 01:46 +0000
                Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-18 20:21 +0000
                  Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Java Jive <java@evij.com.invalid> - 2025-10-19 02:00 +0100
                    Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-19 02:09 +0000
      Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Frank Slootweg <this@ddress.is.invalid> - 2025-10-16 14:37 +0000
      Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Chris <ithinkiam@gmail.com> - 2025-10-16 15:52 +0000
      Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] pyotr filipivich <phamp@mindspring.com> - 2025-10-20 19:11 -0700
        Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Steve Hayes <hayesstw@telkomsa.net> - 2025-10-22 04:07 +0200
    Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 06:44 +0000
    Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 06:58 +0000
      Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Paul <nospam@needed.invalid> - 2025-10-16 03:35 -0400
        Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 07:58 +0000
    Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 07:22 +0000
    Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-16 22:30 +0000
    Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2025-10-18 00:53 +0800
    Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Fokke Nauta <usenet@solfon.nl> - 2025-10-18 19:49 +0200
      Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-18 22:32 +0000
    Re: October 15, 2025 Your version of windows has reached the end of support [19045.6456] Marion <marionf@fact.com> - 2025-10-19 01:44 +0000

Page 2 of 2 — ← Prev page 1 [2]

#2880

Java Jive wrote:
> I ran the ESU script on the original, and all the PCs, original 
> and clones, are stating that they are enrolled for ESU.

Thanks for that information as we might be able to solve this problem.

I wish I had run the ESU script before the 15th since Microsoft closed the 
loopholes on October 8th, but just in case, I ran this script today.
 <https://github.com/abbodi1406/ConsumerESU/archive/refs/heads/master.zip>

I put the gory details elsewhere in this thread & in the tutorial I wrote.
 <https://i2pn2.pugleaf.net/groups/alt.comp.os.windows-10/articles/191468>

Then I ran my checker (which I wrote to check if the proxy was working to 
hide my IP address from Microsoft) and it seems that the update failed.

Yet, like your PCs, my Windows 10 PC states that it's enrolled for ESU.
 C:\> reg.exe query "HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\ConsumerESU"
       HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\ConsumerESU
        ESUEligibility    REG_DWORD    0x2
        ESUEligibilityResult    REG_DWORD    0x1
  ESUEligibility = 0x2 This is the eligibility state flag.
   0x0 -> Not eligible
   0x1 -> Eligible but not yet enrolled
   0x2 -> Eligible and enrollment attempted/active

I wrote a script to run the update and check things:
 PS\> Get-WindowsUpdateLog
 C:\> gvim %USERPROFILE%\Desktop\WindowsUpdate.log

It's a huge file, with the latest date at the bottom.
But I think I need to wait until there's an update to be had.

Does anyone know if there's a Win10 update already since the 15th?

[toc] | [prev] | [next] | [standalone]

#2858

In alt.comp.os.windows-11 Steve Hayes <hayesstw@telkomsa.net> wrote:
> On Wed, 15 Oct 2025 11:06:50 -0000 (UTC), Marion <marionf@fact.com>
> wrote:
> 
> >Today, October 15th, 2025, I am no longer getting Windows 10 updates. 
> >
> >Any ideas for me, and for anyone in the same situation who does NOT wish to
> >create a privacy-robbing MSA account, or, if it's a must, then how best to
> >creatre that privacy-robbing MSA account with the least loss of privacy?
> 
> While I'm not so concerned with privacy, I do have some questions
> about Microsoft accounts, which seem to be compulsory with the latest
> versions of Windows 11.

  It is still possible to have a local account on Windows 11. The tricks
to get one change over time. *If* Microsoft ever closes all doors, you
can install Windows 11 with a Microsoft Account and after installation
convert that account back to a local account.

  Bottom line: No problem.

> I am wary about backing up stuff on OneDrive, because of Microsofts
> predilection for making new versions incompatible with older ones. If
> I back up on OneDrive, who's to say a future update won't make it
> inaccessible to me?

  Then don't backup to OneDrive. I don't. Anyway, the default free
OneDrive is only 5GB, way too little for most people.

> That happened with DropBox, Sounded like a good idea, so I started
> using it to sync files between my desktop and my laptop and my wife's
> laptop. But then along came an update, and it stopped working on my
> desktop. For a while I got around that by syncing using a flash drive,
> and backing up to dropbox from the laptop. But another update might
> knock that out too. 
> 
> And if it happens with DropBox, it's also likely to happen with
> OneDrive and GoogleDrive and so on. 
> 
> And there's this story that you've got to be online to install Windows
> 11 properly.

  See above. Mostly FUD, but if you don't want to use the tricks, yes
you need to be online during install (unless you have Windows Pro).

>	       Does that mean you always have to be online to use it? If
> I take my laptop to the archives to record my research, and they don't
> have public wi-fi, does that mean I won't be able to use my laptop at
> all?

  No of course you don't have to be online to use it (Windows 11). FYI,
I use my Windows 11 laptop in outback Australia where there *is no*
Internet, full stop (except pay-through-the-nose satellite Internet).
That's the whole point of a laptop, that you can use it everywhere, with
or without Internet.

[More of the same deleted.]

> To put it simply and broadly, does having a Microsoft account in
> effect turn your computer into a dumb terminal rather than a PC?

  No, it doesn't. It basically doesn't change much, but it's of course
easier for Microsoft to get information about/from you, especially if
you answer yes to all the questions you get and will get.

  Bottom line: Don't worry about a Microsoft Account. If you don't mind
or want one, fine. If you (like me) don't want one, fine as well.

[toc] | [prev] | [next] | [standalone]

#2859

Steve Hayes <hayesstw@telkomsa.net> wrote:
> On Wed, 15 Oct 2025 11:06:50 -0000 (UTC), Marion <marionf@fact.com>
> wrote:
> 
>> Today, October 15th, 2025, I am no longer getting Windows 10 updates. 
>> 
>> Any ideas for me, and for anyone in the same situation who does NOT wish to
>> create a privacy-robbing MSA account, or, if it's a must, then how best to
>> creatre that privacy-robbing MSA account with the least loss of privacy?
> 
> While I'm not so concerned with privacy, I do have some questions
> about Microsoft accounts, which seem to be compulsory with the latest
> versions of Windows 11.
> 
> I am wary about backing up stuff on OneDrive, because of Microsofts
> predilection for making new versions incompatible with older ones. If
> I back up on OneDrive, who's to say a future update won't make it
> inaccessible to me?

OneDrive is integrated into Windows so as long as you have an up-to-date
Windows you'll be fine. 

> That happened with DropBox, Sounded like a good idea, so I started
> using it to sync files between my desktop and my laptop and my wife's
> laptop. But then along came an update, and it stopped working on my
> desktop. For a while I got around that by syncing using a flash drive,
> and backing up to dropbox from the laptop. But another update might
> knock that out too. 

I'm surprised to read this. I've had dropbox for at least 10 years over
multiple systems. Never had this issue. 

> And if it happens with DropBox, it's also likely to happen with
> OneDrive and GoogleDrive and so on. 
> 
> And there's this story that you've got to be online to install Windows
> 11 properly. Does that mean you always have to be online to use it? If
> I take my laptop to the archives to record my research, and they don't
> have public wi-fi, does that mean I won't be able to use my laptop at
> all?
> 
> And what happens if the power goes off?
> 
> I have a laptop because it has a battery and I can use it away from
> mains electricity, or when there's a power failure. But if it won't
> work when it's not online, there's not much point, is there?
> 
> To put it simply and broadly, does having a Microsoft account in
> effect turn your computer into a dumb terminal rather than a PC?

Not an issue. A requirement for being always online would fail in so many
scenarios - including your suggestions - that it can't happen. 

[toc] | [prev] | [next] | [standalone]

#2901

Steve Hayes <hayesstw@telkomsa.net> on Thu, 16 Oct 2025 03:07:13 +0200
typed in alt.comp.os.windows-11  the following:
>
>And there's this story that you've got to be online to install Windows
>11 properly.
	Yes you do.
> Does that mean you always have to be online to use it? 

	So far, the answer is no.


> If I take my laptop to the archives to record my research, and they don't
>have public wi-fi, does that mean I won't be able to use my laptop at
>all?
-- 
pyotr filipivich
This Week's Panel:  Us & Them - Eliminating Them.
Next Month's Panel: Having eliminated the old Them(tm) 
     Selecting who insufficiently Woke(tm) as to serve as the new Them(tm)

[toc] | [prev] | [next] | [standalone]

#2903

On Mon, 20 Oct 2025 19:11:22 -0700, pyotr filipivich
<phamp@mindspring.com> wrote:

>Steve Hayes <hayesstw@telkomsa.net> on Thu, 16 Oct 2025 03:07:13 +0200
>typed in alt.comp.os.windows-11  the following:
>>
>>And there's this story that you've got to be online to install Windows
>>11 properly.
>	Yes you do.
>> Does that mean you always have to be online to use it? 
>
>	So far, the answer is no.

Thanks. 

I'm not planning to to use it yet, but my wife has it on her laptop.


-- 
Steve Hayes from Tshwane, South Africa
Web:  http://www.khanya.org.za/stevesig.htm
Blog: http://khanya.wordpress.com
E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk

[toc] | [prev] | [next] | [standalone]

#2846

Hank Rogers wrote:
>>> Any ideas for me, and for anyone in the same situation who does NOT wish to
>>> create a privacy-robbing MSA account, or, if it's a must, then how best to
>>> creatre that privacy-robbing MSA account with the least loss of privacy?
>> 
>> This has been discussed here for months, with solution posted and
>> discussed -- "here" meaning in the Windows 10 group, not the
>> irrelevant one and the nonexistent one you crossposted to. I don't
>> fault you for waiting till past the last minute, but you're supposed
>> to check in a newsgroup _before_ you post, to see if your question
>> has already been answered.
>> 
>> Here is the solution I mentioned, and yes I posted to say I had
>> success. As of today, Settings ť Update and Security ť Windows Update
>> Still confirms "Your PC is enrolled to get Extended Security
>> Updates."
>> 
> 
> I'm so happy for you.  Damn, you're really on the ball.

This is in response to Stan who apparently accidentally missed the point.

Actually, I think he missed a few points, but I can forgive him because
most people have no idea what it takes to be private on the Internet.

Given I've already proxied all (most/some?) of the Microsoft Update
activities such that Microsoft does not know my real IP address....

What I need (and we need!) is a known good working way to create an email
address which is also not tied to our IP address or to our phones.

I create those email addresses on TOR, of course, but if Stan (or anyone
else reading this) has never done that, they might not know most mail
servers (e.g., GMail) won't let you use Tor to set up an email sans phone
verification. Almost all will require phone or a second email if you try to
set it up on Tor. You can set up some (e.g., GMX) on VPN though, but most
mail servers will not allow you to set up the email on VPN either.

So you need an email server for your MSA that...
1. Allows creation via TOR
2. Without asking for a second email or a phone number
3. That will accept a registration verification request from Microsoft

My goto email server for that type of process used to be ProtonMail, 
but when I tried it, it permanently banned me from ever receiving
registration emails because I tried too soon, so you have to wait.

In the past you only had to wait 24 hours, but now you have to wait longer,
and, you have to impersonate a real email account by sending & receiving
emails, which, in and of itself is problematic in terms of privacy.

In summary, in terms of PRIVACY, the problem isn't as simple as Stan (and
many others) may think it is but I understand that most people don't try to
be private on the Internet so they won't be able to help us in this quest.

However... if you know which private email address Microsoft will accept
and which mail server will accept TOR registration emails after creation,
THAT is what this question is after.

Once we find that out, everyone will benefit who cares about privacy and
who wants to do the least possible to garner the extended Win10 support!

Thanks for all your help in this privacy quest.

[toc] | [prev] | [next] | [standalone]

#2847

Alan K. wrote:
>> This has been discussed here for months, with solution posted and
>> discussed -- "here" meaning in the Windows 10 group, not the
>> irrelevant one and the nonexistent one you crossposted to. I don't
>> fault you for waiting till past the last minute, but you're supposed
>> to check in a newsgroup _before_ you post, to see if your question
>> has already been answered.

I'm all about adding value... that is saved forever... for others... so... 
to make sure what Stan thinks isn't what everyone else thinks, I add... 

Just to be clear. the newsgroups alt.comp.microsoft.windows has existed
forever, so, if I were to be cheeky, I'd suggest Stan look first. :)
 <https://groups.google.com/forum/#!forum/alt.comp.microsoft.windows>

But I don't fault Stan for not knowing that alt.comp.microsoft.windows
exists, as a lot of people aren't aware of all the Windows-related ngs.
  <https://groups.google.com/g/alt.comp.microsoft.windows>

But I mention it here BECAUSE everyone on these newsgroups should know.
 https://i2pn2.pugleaf.net/groups/alt.comp.microsoft.windows>

In fact, for years, Google wouldn't archive the Windows 10 newsgroup.
When I finally discussed that fact with the relevant folks in Palo Alto
about that, which is no small feat mind you, they said that the only
official Windows newsgroup was, in fact, alt.comp.microsoft.windows
 <https://newsgrouper.org/alt.comp.microsoft.windows>

So I think it's kind'a funny that people think it doesn't exist. 
Nonetheless, I do agree that most people post to the version-specific ngs.
 <https://alt.comp.microsoft.windows.narkive.com/>
-- 
Part of the reason I document in detail is for others to benefit who don't
even use Usenet since my threads are often the first hits on Google search.

[toc] | [prev] | [next] | [standalone]

#2849

On Thu, 10/16/2025 2:58 AM, Marion wrote:
> Alan K. wrote:
>>> This has been discussed here for months, with solution posted and
>>> discussed -- "here" meaning in the Windows 10 group, not the
>>> irrelevant one and the nonexistent one you crossposted to. I don't
>>> fault you for waiting till past the last minute, but you're supposed
>>> to check in a newsgroup _before_ you post, to see if your question
>>> has already been answered.
> 
> I'm all about adding value... that is saved forever... for others... so... 
> to make sure what Stan thinks isn't what everyone else thinks, I add... 
> 
> Just to be clear. the newsgroups alt.comp.microsoft.windows has existed
> forever, so, if I were to be cheeky, I'd suggest Stan look first. :)
>  <https://groups.google.com/forum/#!forum/alt.comp.microsoft.windows>
> 
> But I don't fault Stan for not knowing that alt.comp.microsoft.windows
> exists, as a lot of people aren't aware of all the Windows-related ngs.
>   <https://groups.google.com/g/alt.comp.microsoft.windows>
> 
> But I mention it here BECAUSE everyone on these newsgroups should know.
>  https://i2pn2.pugleaf.net/groups/alt.comp.microsoft.windows>
> 
> In fact, for years, Google wouldn't archive the Windows 10 newsgroup.
> When I finally discussed that fact with the relevant folks in Palo Alto
> about that, which is no small feat mind you, they said that the only
> official Windows newsgroup was, in fact, alt.comp.microsoft.windows
>  <https://newsgrouper.org/alt.comp.microsoft.windows>
> 
> So I think it's kind'a funny that people think it doesn't exist. 
> Nonetheless, I do agree that most people post to the version-specific ngs.
>  <https://alt.comp.microsoft.windows.narkive.com/>
> 

And you would have to understand the history of alt.*
to know how it got the way it is today.

https://en.wikipedia.org/wiki/Alt.*_hierarchy

   "Unlike most of the other hierarchies, there is no centralized control
    of the hierarchy and anyone who is technically capable of creating a newsgroup
    can do so. [That used to be true. Less so now.]

    In practice, however, most newsgroups follow an informal procedure involving
    a public discussion in alt.config before being created. This procedure is
    designed to help the potential creator better understand what factors
    contribute to a newsgroup's success.

    It is up to each individual news administrator whether to add a new newsgroup,
    and some will not do so if the group has not been discussed in alt.config.
   "

At one time, the creation of alt.* newsgroups got out of control. Vanity
groups would be created, like someone would make a

    alt.greg.sucks.donkey.balls

in other words, tit-for-tat sniping using newsgroups as "toys".
Eventually, there were around 100,000 alt.* newsgroups.
Something had to be done.

Administrators first tightened the creation process.
I believe there might be a queue on the server, attempts
to create go in there, there could be "signing" used to indicate
semi-legit attempts at group creation. The administrator processes
these manually (after a fashion).

Then, the alt.* cesspit was cleaned out. Groups with
low traffic (like only two spam posts in two years), would
get removed. The number of alt groups today is smaller.

There is no guarantee that two servers carry exactly
the same alt.* set. Alt.* has been through a lot over
the years. And that's the result.

Even the alt.comp.os.windows-10 and alt.comp.os.windows-11
are not necessarily on all the hobby servers. And Google
Groups would not have added them either, as a number of
alt.* groups are missing on Google (a temporal cutoff, Google
stopped adding alt.* at some point, some Linux ones are missing).

   Paul

[toc] | [prev] | [next] | [standalone]

#2851

Paul wrote:
>> So I think it's kind'a funny that people think it doesn't exist. 
>> Nonetheless, I do agree that most people post to the version-specific ngs.
>>  <https://alt.comp.microsoft.windows.narkive.com/>
>> 
> 
> And you would have to understand the history of alt.*
> to know how it got the way it is today.

Thanks Paul, for explaining the reason that Google refused to archive the
Windows 10 newsgroup when I literally drove to Palo Alto to talk to them.

All I could accomplish was I was able to get them to *change* the URL from
 <https://groups.google.com/forum/#!forum/alt.comp.microsoft.windows>
to
 <https://groups.google.com/g/alt.comp.microsoft.windows>
for all Usenet newsgroups (not just for the Windows newsgroup).

Once they did that, I no longer needed to create the tinyurl shortcuts
which I created to make the Usenet search simple for non-NNTP users.

> Even the alt.comp.os.windows-10 and alt.comp.os.windows-11
> are not necessarily on all the hobby servers. And Google
> Groups would not have added them either, as a number of
> alt.* groups are missing on Google (a temporal cutoff, Google
> stopped adding alt.* at some point, some Linux ones are missing).

As you probably can recall, I was able to work with the NovaBBS admin
(RetroGuy) to archive all the Windows newsgroups for non-NNTP users but he
died recently so I worked with the pugleaf folks a little bit to port it
(which they did). 

As you probably also recall, I worked with the admin for Narkive (Davide
Cavion) who responded by email to me and to news.admin.peering that he just
didn't have the time to maintain that server well.

And pcbanter seems to have died long ago, so this link I created is 404:
 <https://tinyurl.com/alt-comp-os-windows-10>

I've probably done more than anyone other than those admins for making sure
the archives are available to everyone, where I find most of my Usenet
articles from those servers (or from a Google search for my own threads).

The archives are great because one, five, ten, twenty or more years from
now, people can make use of all the information we've kind heartedly added.

BTW, I haven't responded to your msedge/copilot post but I read it, but I
haven't been able to resolve the problem yet so I was waiting for more data
(which I don't have yet - but I do appreciate the kind hearted help you
provided, as copilot seems to have many shape shifting forms I didn't know
of, so when I say copilot it might not be what you mean when you say it).
-- 
The whole point of Usenet is for intelligent people to help each other, 
& for the results to be archived so that anyone can access our knowledge.

[toc] | [prev] | [next] | [standalone]

#2848

John K.Eason wrote:
> In article <10cp84m$3tkqq$2@dont-email.me>, alan@invalid.com (Alan K.) wrote:
> 
>> The OP also states he's on 22H2 which is 2 versions back.  I would 
>> think he's want to be on 24H2.
> 
> The final major release version of Windows 10 is 22H2 so I don't know where you
> got 24H2 from!

I don't fault Alan K for thinking the version would be different, but as
John K.Easton observed, indeed, the version is 22H2 for Windows 10 (AFAIK).

As for Stan Brown's assertion that creating a private email address has
nothing to do with Windows 11, I disagree. People have MSA's on Win11 also.

In fact, I think there may be a few people on Windows 11 who had to create
an MSA just to use it, and therefore, the topic of how best to create a
private email address that Microsoft will accept as a verification email
(and that will accept the Microsoft verification email) is apropos to both
newsgroups.

In summary, I think a private email is de rigueur for both Windows 10 & 11.

Note also that, to Carlos' point, if you haven't proxied your Microsoft
Updates, then Microsoft will know your "real" IP address unless you've
taken other measures. Windows Update on both Windows 10 and 11 typically
connects directly to Microsoft servers using system-level networking.

Updates bypass browser-level proxies like SOCKS5 or HTTP proxies unless
those proxies are configured system-wide although VPNs, when active,
reroute all traffic, but you have to configure such things to kick in upon
reboot.

Browsers and most apps use WinINET settings.
Windows Update and other system-level services use WinHTTP settings.

Therefore the key step is to copy WinINET proxy settings into WinHTTP.
 netsh winhttp import proxy source=ie

Although, I just checked my proxy settings and I found a minor hiccup,
where not all the Windows Update was going through the proxy. 

That is, if we want Windows Update to go through the proxy, we need to
expose an HTTP/HTTPS proxy endpoint (not just SOCKS) where we then
configure the WinHTTP (which is what Windows Update uses!) via
 netsh winhttp set proxy 127.0.0.1:port

In short, I'm happy this issue came up by Carlos and others that supposedly
Microsoft knows your IP address, because when I doublechecked my scripts, I
realized since WinHTTP doesn't process PACs or SOCKS, Windows Update will
always bypass it unless we give it a plain HTTP proxy address.

Thanks to Stan, Carlos, John K.Easton & Alan K. for bringing this up, as
everyone who wants privacy needs to do at least two things with the MSA:
 1. Make sure the MSA account is private, and, 
 2. Make sure Windows Update doesn't use your real IP address.
-- 
As always, posted to add value to the permanent Usenet record for all to
benefit from, out of the goodness of my heart and from that of others.

[toc] | [prev] | [next] | [standalone]

#2860

Paul wrote:
>> Install a Linux OS?
> 
> "Ah, Linux"  <Stares dreamily out the window>  :-)
> "Young man, staring dreamily out the window won't install that OS"
> You can install Linux besides Windows, without breaking anything.

Just to be clear, I am an old geezer, so of course I started with computers
in the days a decade before when you flipped the DIP switches on the PDP 11
base to set the boot address. Think paper tape. Punched cards were new.

IBM Selectric boat-anchor green domed-ball typewriters were all the rage.

So of course I have decades of experience with the various Unix flavors,
including dual-boot to RedHat in commercial engineering environments.

Once I retired, I naturally went to CentOS dual boot, and then to Ubuntu.
Point being I'm familiar with (and still have) grub on my Windows 10 boxes.

In the olden days (of a few decades ago), I was sure that Linux would wipe
out Microsoft given it's just as good and free but, alas, not on desktops.

Something about Microsoft Office being what everyone uses stopped that. :)

But back to the point about privacy, it seems the best way to get privacy
now that I'm forced to set up an MSA just to get a "free" year of support
is to do two things which most people who are slaves won't be doing:

1. I ensure that the MSA account never uses my real IP address at any time
2. I ensure that Microsoft Update never again gets a hold of my real IP

My "plan" so far, unless someone has a better idea, is the following:
A. Use my protonmail account on Tor for about a month to establish it
B. Then, in a month, use that account for the MSA registration email
C. Meanwhile, keep the PC always on proxy (which is much faster than VPN)

My main question to the team was WHICH PRIVATE EMAIL did most people use?

[toc] | [prev] | [next] | [standalone]

#2869

On 15/10/2025 7:06 pm, Marion wrote:
> Today, October 15th, 2025, I am no longer getting Windows 10 updates.
> 
> Any ideas for me, and for anyone in the same situation who does NOT wish to
> create a privacy-robbing MSA account, or, if it's a must, then how best to
> creatre that privacy-robbing MSA account with the least loss of privacy?
> 


Let's wait and see what the crowd out there choose... :)

-- 
   @~@   Simplicity is Beauty! Remain silent! Drink, Blink, Stretch!
  / v \  May the Force and farces be with you! Live long and prosper!!
/( _ )\ https://sites.google.com/site/changmw/
   ^ ^   https://github.com/changmw/changmw

[toc] | [prev] | [next] | [standalone]

#2871

Op 15/10/2025 om 13:06 schreef Marion:
> Today, October 15th, 2025, I am no longer getting Windows 10 updates.
> 
> Any ideas for me, and for anyone in the same situation who does NOT wish to
> create a privacy-robbing MSA account, or, if it's a must, then how best to
> creatre that privacy-robbing MSA account with the least loss of privacy?
> 
> This is now the last updated version of Windows 10 Pro that I am aware of
> for those of us who never created the MSA (for obvious privacy reasons).
>   C:\> ver
>        Microsoft Windows [Version 10.0.19045.6456]
>   C:\> winver
>        Version 22H2 (OS Build 19045.6456) Windows 10 Pro
> 
>   Runbox > control update > Update & security > Windows Update
>    Your version of windows has reached the end of support
>    Look for the banner or message that says
>     "Your version of Windows has reached end of support".
>    Enroll in Extended Security Updates
>     "Enroll now"
>    Sign in with your Microsoft account.
>    Choose a plan:
>     Free option (requires backing up your data to MS OneDrive)
>     Paid option ($30/year)
> 
> Unfortunately for me...
>   1. I don't have an MSA (for privacy reasons!)
>   2. I don't back up data on the net (for privacy reasons!)
>   3. I don't pay for anything on the net (for privacy reasons!)
>   4. If I do create an MSA, I'll use protonmail or tutanoa to do that.
>   5. What matters now is figuring out the LEAST to back up to MS OneDrive.
> 
> Any ideas for extended support that preserve some semblance of privacy?
> 
> The best "plan" can come up with on my own, without your help yet, is:
>   1. Create a protonmail email address a month ago
>      Each day, send an innocuous email & respond to any replies.
>   2. Press the "Create the MSA" button in the form that shows up above.
>   3. After signing in, go to Settings > Privacy
>   4. Turn off everything under "Activity history," "Diagnostics," & "Sync."
> 
> This takes about a month to perform successfully, so it's best to plan
> ahead by creating a Protonmail account and sending/receiving innocuous
> emails for about a month as Protonmail will permanently block the account
> from receiving "registration" emails if you start registering right away.
> (Ask me how I found that out.)
> 
> If we choose the free ESU option, Microsoft requires us to back up some
> data to OneDrive. To meet the minimum requirement while preserving privacy:
> 
>   1. Create a new folder, name it something like "ESU Backup".
>   2. In that folder, create an empty text file, like "placeholder.txt".
>   3. Open Settings > Accounts > Windows Backup.
>   4. Sign in with your Microsoft account (created a month ago).
>   5. Choose to back up only that one folder to OneDrive.
>      This satisfies the backup requirement with zero personal data.
> 
> Is this the easiest/least expensive method to garner extended support?
> 
> Below is what my current hotfix version is, which I suspect is similar for
> anyone on Windows 10 as of today given we had our last midnight update.
> 
> Check Windows Update History
>   C:\> wmic qfe list brief /format:table
>   or
>   PS> Get-HotFix | Sort-Object InstalledOn -Descending
>   As admin:
>   PS> Get-HotFix | Sort-Object InstalledOn -Descending
> 
>   Description   HotFixID InstalledBy     InstalledOn
>   -----------   -------- -----------     -----------
>   Security Update KB5066790 NT AUTHORITY\SYSTEM 10/15/2025 12:00:00 AM
>   Security Update KB5066791 NT AUTHORITY\SYSTEM 10/15/2025 12:00:00 AM
>   UpdateKB Update KB5066130 NT AUTHORITY\SYSTEM 10/14/2025 12:00:00 AM
>   UpdateKB Update KB5063979 NT AUTHORITY\SYSTEM 09/10/2025 12:00:00 AM
>   UpdateKB Update KB5063261 NT AUTHORITY\SYSTEM 07/25/2025 12:00:00 AM
>   Security Update KB5063706 NT AUTHORITY\SYSTEM 07/09/2025 12:00:00 AM
>   UpdateKB Update KB5059504 NT AUTHORITY\SYSTEM 06/11/2025 12:00:00 AM
>   Security Update KB5058526 NT AUTHORITY\SYSTEM 05/14/2025 12:00:00 AM
>   UpdateKB Update KB5054682 NT AUTHORITY\SYSTEM 04/09/2025 12:00:00 AM
>   UpdateKB Update KB5052916 NT AUTHORITY\SYSTEM 03/12/2025 12:00:00 AM
>   UpdateKB Update KB5050111 NT AUTHORITY\SYSTEM 02/12/2025 12:00:00 AM
>   Security Update KB5050388 NT AUTHORITY\SYSTEM 01/15/2025 12:00:00 AM
>   UpdateKB Update KB5046823 NT AUTHORITY\SYSTEM 11/13/2024 12:00:00 AM
>   UpdateKB Update KB5043130 NT AUTHORITY\SYSTEM 10/13/2024 12:00:00 AM
>   Security Update KB5043935 NT AUTHORITY\SYSTEM 09/11/2024 12:00:00 AM
>   Security Update KB5041579 NT AUTHORITY\SYSTEM 08/14/2024 12:00:00 AM
>   UpdateKB Update KB5039336 NT AUTHORITY\SYSTEM 07/10/2024 12:00:00 AM
>   UpdateKB Update KB5037995 NT AUTHORITY\SYSTEM 06/06/2024 12:00:00 AM
>   UpdateKB Update KB5037240 NT AUTHORITY\SYSTEM 05/15/2024 12:00:00 AM
>   Security Update KB5037018 NT AUTHORITY\SYSTEM 04/17/2024 12:00:00 AM
>   UpdateKB Update KB5036447 NT AUTHORITY\SYSTEM 03/13/2024 12:00:00 AM
>   UpdateKB Update KB5034224 NT AUTHORITY\SYSTEM 02/13/2024 12:00:00 AM
>   Security Update KB5034441 NT AUTHORITY\SYSTEM 01/20/2024 12:00:00 AM
>   UpdateKB Update KB5032907 NT AUTHORITY\SYSTEM 12/13/2023 12:00:00 AM
>   UpdateKB Update KB5032392 NT AUTHORITY\SYSTEM 11/14/2023 12:00:00 AM
>   UpdateKB Update KB5031540 NT AUTHORITY\SYSTEM 11/01/2023 12:00:00 AM
>   UpdateKB Update KB5011048 NT AUTHORITY\SYSTEM 10/31/2023 12:00:00 AM
>   UpdateKB Update KB5030841 NT AUTHORITY\SYSTEM 10/31/2023 12:00:00 AM
>   UpdateKB Update KB5031539 NT AUTHORITY\SYSTEM 10/30/2023 12:00:00 AM
>   UpdateKB Update KB5015684 NT AUTHORITY\SYSTEM 10/30/2023 12:00:00 AM
>   UpdateKB Update KB5026879 NT AUTHORITY\SYSTEM 06/15/2023 12:00:00 AM
>   UpdateKB Update KB5025315 NT AUTHORITY\SYSTEM 05/10/2023 12:00:00 AM
>   UpdateKB Update KB5023794 NT AUTHORITY\SYSTEM 04/12/2023 12:00:00 AM
>   UpdateKB Update KB5022924 NT AUTHORITY\SYSTEM 03/15/2023 12:00:00 AM
>   UpdateKB Update KB5020372 NT AUTHORITY\SYSTEM 12/14/2022 12:00:00 AM
>   UpdateKB Update KB5018506 NT AUTHORITY\SYSTEM 11/09/2022 12:00:00 AM
>   UpdateKB Update KB5016705 NT AUTHORITY\SYSTEM 10/22/2022 12:00:00 AM
>   Security Update KB5012170 NT AUTHORITY\SYSTEM 08/09/2022 12:00:00 AM
>   UpdateKB Update KB5015895 NT AUTHORITY\SYSTEM 08/06/2022 12:00:00 AM
>   UpdateKB Update KB5014671 NT AUTHORITY\SYSTEM 07/12/2022 12:00:00 AM
>   UpdateKB Update KB5014035 NT AUTHORITY\SYSTEM 06/15/2022 12:00:00 AM
>   Security Update KB5014032 NT AUTHORITY\SYSTEM 05/11/2022 12:00:00 AM
>   UpdateKB Update KB5003791 NT AUTHORITY\SYSTEM 04/15/2022 12:00:00 AM
>   UpdateKB Update KB5011651 NT AUTHORITY\SYSTEM 04/12/2022 12:00:00 AM
>   Security Update KB5011352 NT AUTHORITY\SYSTEM 02/14/2022 12:00:00 AM
>   UpdateKB Update KB5007273 NT AUTHORITY\SYSTEM 12/17/2021 12:00:00 AM
>   UpdateKB Update KB5006753 NT AUTHORITY\SYSTEM 11/18/2021 12:00:00 AM
>   Security Update KB5005699 NT AUTHORITY\SYSTEM 09/15/2021 12:00:00 AM
>   UpdateKB Update KB4589212 NT AUTHORITY\SYSTEM 03/12/2021 12:00:00 AM
>   UpdateKB Update KB4577586 NT AUTHORITY\SYSTEM 02/17/2021 12:00:00 AM
>   Security Update KB4598481 NT AUTHORITY\SYSTEM 01/13/2021 12:00:00 AM
>   UpdateKB Update KB4562830 NT AUTHORITY\SYSTEM 12/27/2020 12:00:00 AM
>   Security Update KB4593175 NT AUTHORITY\SYSTEM 12/10/2020 12:00:00 AM
>   Security Update KB4586864 NT AUTHORITY\SYSTEM 11/10/2020 12:00:00 AM
>   Security Update KB4580325 NT AUTHORITY\SYSTEM 10/13/2020 12:00:00 AM
>   Security Update KB4577266 NT AUTHORITY\SYSTEM 09/10/2020 12:00:00 AM
>   Security Update KB4570334 NT AUTHORITY\SYSTEM 08/15/2020 12:00:00 AM
>   Security Update KB4561600 NT AUTHORITY\SYSTEM 08/15/2020 12:00:00 AM
>   Security Update KB4557968 NT AUTHORITY\SYSTEM 05/11/2020 12:00:00 AM
>   Security Update KB4537759 NT AUTHORITY\SYSTEM 05/11/2020 12:00:00 AM
> 
> The first three lines above confirm that the Windows 10 Pro system
> received three updates yesterday 2025, including two security updates:
>   KB5066790 (Security Update) - Installed 10/15/2025
>   KB5066791 (Security Update) - Installed 10/15/2025
>   KB5066130 (Update) - Installed 10/14/2025
> 
> These are likely the final cumulative & security patches for Windows 10 now
> that support has ended, unless a privacy-robbing MSA account is created.
> 
> Any ideas for extended support that preserve some semblance of privacy?
> 

Why are you writing this?

Fokke

[toc] | [prev] | [next] | [standalone]

#2876

Fokke Nauta wrote:
> Why are you writing this?

I've written hundreds of tutorials over the decades to add to vast combined
tribal knowledge, & in doing so, I strive to further our team capabilities.

I'm documenting, for all time, in an easily referenced thread, how to get
ESU updates with privacy, which is a topic I believe hasn't been discussed.

As of October 8th, 2025, there is no longer (AFAIK) a script that allows
one to obtain the ESU extension without an MSA account on the device, so it
behooves us to know how to create an MSA with the utmost of privacy.

Most people might use their Gmail email address, which is what slaves do.
The email address must be unique if we are to achieve the privacy goal.

In this thread, I also explained how to tell if your Windows Updates are
betraying your "real" IP address to Microsoft, which is another privacy
issue, which again, people who own a slave mentality, won't need to know.

But if your mentality is NOT that of a slave, then it behooves you to add
value to this thread which shows how (as much as is known) to satisfy the
minimum requirements to obtain another year of ESU updates, with privacy.

Do you have any technical value to add on that immensely important topic?
-- 
The point of Usenet is for smart people to help each other & for results 
to be archived so that anyone can access our immense tribal knowledge.

[toc] | [prev] | [next] | [standalone]

#2879

Carlos E.R. wrote:
>> That's what I have. Windows 10 is running in a VM. This is BIOS, so not
>> upgradable to 11.
> 
> I upgraded a VM (on vmware) with BIOS from W10 to W11, and told about it 
> here. One of the steps was upgrading the virtual hardware to UEFI. The 
> host is Linux.

I'm willing to test my Win10 PC native, without a VM, on these tests.
There seems to be no dearth of programs reputed to ESU enroll sans MSA.

Below is my experience today running what appears to be a canonical one.
 <https://github.com/abbodi1406/ConsumerESU/archive/refs/heads/master.zip>

Of the half-dozen or so presented, this seems to be the most promising.
 *Consumer ESU Enrollment*
 <https://github.com/Toysoft/ConsumerESU>
 "Windows Powershell script to enroll in Windows 10 Consumer 
  Extended Security Updates (ESU) program via the free Backup option, 
  with or without Microsoft Account.
  The free EnrollUsingBackupV1 function does not actually need 
  enabled Backup or online account."
  <https://codeload.github.com/Toysoft/ConsumerESU/zip/refs/heads/master>
  Name: ConsumerESU-master.zip
  Size: 8806 bytes (8 KiB)
  SHA256: 0D695EA85CE6F3C626EA2983A3103124D50C19DF963A4646C328956D5541BB59

The zip consists of four files:
  Consumer_ESU_Enrollment.ps1
  Consumer_ESU_Enrollment_run.cmd
  LICENSE
  README.md

But note that Microsoft is known to have blocked loopholes as of October 8, 
2025; this code hasn't had an update for "2 months" (i.e., prior to that).

Nonetheless, since I'm a risk taker & experimenter, I ran the cmd above.
 C:\> ConsumerESU-master>Consumer_ESU_Enrollment_run.cmd
      Evaluate ESU Eligibility state ...
      Eligibility Status: Eligible
      Eligibility Result: SUCCESS
      Obtain MSA Token ...
      Obtained token for Local user account
      Run Consumer ESU Enrollment ...
      Operation Failed: 0x80080259
      Evaluate ESU Eligibility state ...
      Eligibility Status: Eligible
      Eligibility Result: SUCCESS

Apparently my system passed Eligibility check as it said "Eligible / 
SUCCESS" which means the prerequisites (Windows 10 22H2, correct CU, 
Consumer ESU feature flag) are in place.

The script successfully generated a token for my local account (so the 
"EnrollUsingBackupV1" path is working as intended).

But the failure code 0x80080259 s a deployment/enrollment failure that 
usually indicates the script pretended to enroll but the server-side 
validation blocked it such that the local token was accepted syntactically 
but not honored by the ESU licensing servers, likely because the backend 
service rejected the enrollment request (probably because Microsoft patched 
the loophole on Oct 8, 2025).

This verifies the eligibility key.
 C:\> reg.exe query "HKCU\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\ConsumerESU"
       HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\ConsumerESU
        ESUEligibility    REG_DWORD    0x2
        ESUEligibilityResult    REG_DWORD    0x1
  ESUEligibility = 0x2 This is the eligibility state flag.
   0x0 -> Not eligible
   0x1 -> Eligible but not yet enrolled
   0x2 -> Eligible and enrollment attempted/active

Locally, Windows now believes my PC is eligible & enrolled for Consumer ESU.
However, the backend rejected the enrollment request (0x80080259).

Delving deeper, this sets the hidden Consumer ESU feature override.
 C:\> reg.exe add "HKLM\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides" /v 4011992206 /t REG_DWORD /d 2 /f
      The operation completed successfully.

This script reputedly forces Windows to reconcile the new feature flag.
 $TN = "ReconcileFeatures"; $TP = "\Microsoft\Windows\Flighting\FeatureConfig\"
 $null = Enable-ScheduledTask $TN $TP
 Start-ScheduledTask $TN $TP
 while ( (Get-ScheduledTask $TN $TP).State.value__ -eq 4) {Start-Sleep -Seconds 1}
 "Task Completed"
 
 $TN = "UsageDataFlushing"; $TP = "\Microsoft\Windows\Flighting\FeatureConfig\"
 $null = Enable-ScheduledTask $TN $TP
 Start-ScheduledTask $TN $TP
 while ( (Get-ScheduledTask $TN $TP).State.value__ -eq 4) {Start-Sleep -Seconds 1}
 "Task Completed"

I created this batch file to run that powershell script:
  @echo off
  :: RunConsumerESU.cmd 20251018 
  :: Batch file to auto-elevate and run Consumer_ESU_Enrollment.ps1
  :: This is version 1.0
  :: Check for admin rights
  net session >nul 2>&1
  if %errorLevel% neq 0 (
      echo Requesting administrative privileges...
      powershell -Command "Start-Process '%~f0' -Verb RunAs"
      exit /b
  )
  :: Path to the PowerShell script (same folder as this .cmd)
  set SCRIPT_PATH=%~dp0Consumer_ESU_Enrollment.ps1
  :: Run the script with ExecutionPolicy bypass
  powershell -NoProfile -ExecutionPolicy Bypass -File "%SCRIPT_PATH%"
  pause
  REM end of RunConsumerESU.cmd

That batch script runs this Run-ConsumerESU powershell script.
 # Run-ConsumerESU.ps1 20251018 
 # Forces Windows to reconcile the hidden Consumer ESU feature flags
 # This is version 1.0
 function Run-ESUTask {
     param([string]$TaskName)
     $TaskPath = "\Microsoft\Windows\Flighting\FeatureConfig\"
     # Enable and start the scheduled task quietly
     Enable-ScheduledTask -TaskName $TaskName -TaskPath $TaskPath | Out-Null
     Start-ScheduledTask -TaskName $TaskName -TaskPath $TaskPath
     # Wait until the task finishes
     while ((Get-ScheduledTask -TaskName $TaskName -TaskPath $TaskPath).State -eq 'Running') {
         Start-Sleep -Seconds 1
     }
     Write-Host "$TaskName completed." -ForegroundColor Green
 }
 # Run both required tasks
 Run-ESUTask -TaskName "ReconcileFeatures"
 Run-ESUTask -TaskName "UsageDataFlushing"
 Write-Host "All Consumer ESU feature tasks completed." -ForegroundColor Cyan
 # end of Run-ConsumerESU.ps1
 
The output of that sequence was the following:
 C:\> RunConsumerESU.cmd
      Evaluate ESU Eligibility state ...
      Eligibility Status: Eligible
      Eligibility Result: SUCCESS

      Obtain MSA Token ...
      Obtained token for Local user account

      Run Consumer ESU Enrollment ...
      Operation Failed: 0x80080259

      Evaluate ESU Eligibility state ...
      Eligibility Status: Eligible
      Eligibility Result: SUCCESS
      Press any key to continue . . .

This tells us:
 a. My system meets the local prerequisites 
    (Windows 10 22H2, correct CU, Consumer ESU feature flag enabled)
 b. The script successfully generated a backup enrollment token 
    (without requiring a Microsoft account)
 c. Operation Failed: 0x80080259 means the local token was accepted 
    syntactically, but the server refused to honor it such that the
    enrollment request was rejected by Microsoft's backend service.
 d. The registry and local checks still say eligible, but that 
    doesn't mean I'm actually enrolled. It just means the feature 
    flag is active on my machine.

Win+R > control update > Check for updates
 2025-10 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5066791)
 Successfully installed on ‎10/‎15/‎2025
 <https://support.microsoft.com/help/5066791>
 October 14, 2025—KB5066791 (OS Builds 19044.6456 and 19045.6456)

I ran my script to monitor Windows Update activity (previously posted).
It showed no updates occurring. 
 PS\> Get-WindowsUpdateLog
 C:\> gvim %USERPROFILE%\Desktop\WindowsUpdate.log

It's a huge file, with the latest date at the bottom. 
But I think I need to wait until there's an update to be had.

Does anyone know if there's a Win10 update already since the 15th?

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | alt.comp.microsoft.windows

csiph-web