This news comes from the Microsoft Windows Blogs dated May 26. It’s entitled “Delivering Delightful Performance for More Than One Billion Users Worldwide.” That’s the day after Build 2023 concluded, and the first time that MS has publicly disclosed user count data for Windows 11 in about a year. It’s also the first time they’ve proclaimed that the Windows 11 user count tops 1B worldwide.

These are the four instances in the afore-linked item where the “billion” word occurs:
1. In the title of the blog post, as quoted in the preceding ‘graph
2. In a sentence that reads (in part) as “... with over one billion users and a rich PC ecosystem…”
3. Diagnostic data includes “…over 70.4 billion scenario performance data points per year.”
4. Final paragraph, penultimate sentence reads (in part) “…thanks to our Windows Insider community for helping us continue to improve Windows for the over one billion users worldwide.”

What Windows 11 User Count Tops 1B Worldwide Means

According to Statista, as of June 2023, the company expects a ratio of 68.6% for Windows 10 vis-a-vis 18.12% for Windows 11. Thus, if there are 1 B Windows 11 users, there must also be  around 3.78 B Windows 10 users. To me this means one of two things:

(a) The ratio of visitors that Statista tracks doesn’t accurately model the Windows population of active users
(b) Microsoft’s claimed 1 B figure does not translate to active users 1-to-1 (makes sense, given that one active user can run multiple instances of the OS, especially VMs)

In January 2023, for example, Jason Wise reported at EarthWeb that MS claimed 1.4 B active devices running Windows 10 and 11 monthly in January 2022. They use this data, plus additional insights, to assert that “Windows, new versions and otherwise, run on more or less 1.6 billion devices around the world” as of January 2023.

Even assuming a monthly growth rate of 3% that puts the global Windows population at 1.85 B in May, 2023. How can there be at or over 1 B Windows 10 users and a similar number of 11 users with a total that’s arithmetically lower? Something here doesn’t make sense…

It should be interesting to see the pundit corps chew this over. Stay tuned, and I’ll keep you posted…

Note Added 1 Hour Later…

It’s got to be devices, counting both physical and virtual machines as individual devices. I use 10 PCs here at my house, and I have at least another dozen VMs across various Windows versions at my disposals. That’s over 20 “devices” but only one user. That leaves room for a tangible “muliplier” between users and devices, IMO.

There’s an interesting tidbit in the Support Note for KB5026435, released May 23, 2023. Indeed, it is the concluding Windows 10 22H2 non-security preview release, ever. It goes so far as to say “no more” such releases are forthcoming. In a way, this marks the beginning of the end for Windows 10, whose EOL date is 10/14/2025 (about 17.5 months from today). As you can see from the lead-in graphic, I just installed it onto my sole remaining Windows 10 production desktop.

Sussing Out the Concluding Windows 10
22H2 Non-Security Preview

MS elaborates further on the future release scheduling for Windows 10 in the afore-linked Support Note. It says:

Only cumulative monthly security updates (known as the “B” or Update Tuesday release) will continue for these versions. Windows 10, version 22H2 will continue to receive security and optional releases.

Here’s what I think this means:

1. 22H2 is the final release for Windows 10 (unless something big changes).
2. No more second (4th) Tuesday preview releases for Windows 10 22H2.
3. There may be some second (4th) Tuesday security and optional releases from time to time.

The inescapable conclusion is that Windows 10 is now purely in “maintenance mode.” That means we’re unlikely to see more (or at least, precious few) Windows 11 features “back-ported” into 10.

Take it as a signal, business users. MS is clearly warning you that it’s time to start planning the transition to Windows 11 (or beyond). It should be interesting to see how this plays out between now and mid-October 2025. Stay tuned, and I’ll opine further on what’s up, what’s hot, and what’s not.

Whoa there! I couldn’t help but notice that my production PC slowed briefly to a crawl this morning. A not-so-welcome first, in fact. A quick jump to Task Manager showed me the Macrium Reflect Backup tool was the culprit, with CPU utlization stuck north of 75%. It took about 5 minutes to subside to normal levels. This tells me quite a lot, but let’s start with the blunt observation that Macrium Reflect swamps CPU short-term.

Note: I cheated on the lead-in graphic. It’s from a much older PC where it’s frightfully easy to swamp that CPU. Notice all four cores are pegged at 100% utilization in the ever-handy CPU Usage gadget. I have 8 threads on 4 cores on the i7-Skylake production unit, and they were all likewise pegged at 100%, albeit for a short time. Thus, I saw what I show here, doubled, as that PC bogged down.

What Does Macrium Reflect Swamps CPU Short-Term Mean?

Good question. Beyond the inescapable fact that this program — which was running my daily 9AM backup when this happened — brought my production PC to its knees, there’s more. Let me spell a few things out:

1. This is an i7-Skylake (6th gen) Intel CPU [3.4GHz], 32 GB RAM [DDR4-2133], 512 GB NVMe SSD [Samsung 950 Pro]. I built it in 2017-2018.
2. It’s not Windows 11 capable, so it’s running Windows 10 22H2 Build 19045.2788: that’s the latest preview CU scheduled for general distribution on April Patch Tuesday.
3. It’s never hit the wall performance-wise before to my notice. I beat the beejesus out of this machine daily (there are 13 apps and 148 background processes running, with 4% CPU utilization, as I write this screed). Indeed, this PC (mostly) does what I need it to do.

But it’s old and somewhat out-dated.  And I have a Ryzen 7 5800X in an Asrock B550 mobo ready to take over the production PC role. That leads me to a vital question:

Why Not Switch Over, Already?

I have lots of obvious answers including inertia, laziness, ongoing usability and the usual fiddle-faddle. But here’s the real reason, in succinct visual form:

Count ’em: 10 mounted physical drives (4 SSDs, 6 HDDs).
[Click image for full-sized view.]

This totals up to about a nominal 16TB  of storage, of which 40% or so is occupied. Thus, we’re talking around ~6.5 TB of stuff, of which I need to keep at least 5TB’s worth. There’s going to be some thinking, planning, time and effort involved in moving my show to another PC. I’ll have to back everything up to another drive (an 8TB unit should do) and then figure how to map it into a new set of storage devices on the target PC. That should be interesting. I guess I’d better get started. This morning, I got my “early warning!”

OK, then, they’ve been gone for some time now. But Dev Channel Build 25300 restores Taskbar Clock seconds to its display capabilities. The lead-in graphic shows that Settings checkbox, next to Winver for the build.

Note: we’ve not had access to seconds readouts in the Windows 11 taskbar clock since Day 1 of the release. It popped in — and then out again — in a recent Insider Preview. And right now, it’s only available in the Dev Channel release fork. Just sayin…

Find this by clicking through Settings → Personalization → Taskbar. Then, open the Taskbar behaviors pane. That’s where you’ll find the checkbox labeled: “Show seconds in system tray clock…” Notice that it comes with this caveat: “(uses more power).” MS has long put this theory forward (it recommended against turning on the second hand in Vista-era clock gadgets for the same reason) but doesn’t really present actual data to report how much more power is used — or battery life lost — as a consequence of turning this on. Sigh.

If Build 25300 Restores Taskbar Clock Seconds, Then…

I can only interpret the MS caveat as a warn-off of sorts. I guess we should be grateful they’ve deigned to restore this capability to those bold (or stupid) enough to use it. Count me among that number, and decide for yourself its potential significance. Here’s what it looks it, after you turn seconds back on:

Even at the cost of a bit of power, glad to get those seconds back!

Small though this change may be, I am glad to have the choice as to whether or not I get seconds with my time readout on Windows 11. It’s been that way in Windows as far back as I recall. And now, it’s back again.

Sometimes, those little things do make a difference. I count this as a minor victory for the small people, here in Windows-World.