Category Archives: Thoughts & concerns

Why Switch One 2020 Mobo for Another?

I’m surprised. I’m actually considering replacing a 6-year-old Asrock motherboard with an MSI of the same age. Basically, I’ve gotten tired of fighting UEFI and firmware issues on the Asrock that serves as the foundation for my production desktop. I see reviews and other online evidence that the MSI MAG B550 Tomahawk Max will solve those problems. It costs US$150, which is a relatively small sum when compared to the days and days I’ve spend fighting with the Asrock board in the last month.

Why Not Switch One 2020 Mobo for Another?

I’m pretty sure I can take Flo6 apart, swap mobos, and get back up and running in an afternoon. I’ve almost had to take the whole thing apart half-a-dozen times recently to pull the GPU, various drives (including the primary SSD), and the CMOS battery. Why not go all the way?

Simply put: I don’t feel like funding a complete rebuild into a new system right now, given prevailing costs for RAM and SSDs. I can make this switch for another US$150, versus US$2,650 for a similarly equipped i714700K based build.

That’ll have to wait for the general exchequer to charge up a bit. Maybe next year? For now, I’ll be happy to get a system that boots properly, and handles Secure Boot without major issues. Let’s see what happens, shall we? I’m giving it a try…

Facebooklinkedin
Facebooklinkedin

Secure Boot Oddities Accumulate

Although I’m resigned to living without secure boot on the B550-based desktops here at Chez Tittel, that doesn’t stop me from trying other fixes from time to time. Indeed, I discovered a great thread about secure boot keys at ElevenForum, and learned more about what’s going on under the hood. Along the way, I gave myself a terrific scare as I saw more secure boot oddities accumulate. Here’s what happened…

Registry Key Change Helps Secure Boot Oddities Accumulate

One must provide Windows with a a couple of instrux to ask the OS to update secure boot key certificates, to wit:

Set-ItemProperty -Path “HKLM:\SYSTEM\CurrentControlSet\Control\SecureBoot” -Name “AvailableUpdates” -Value 0x40

Start-ScheduledTask -TaskName “\Microsoft\Windows\PI\Secure-Boot-Update”

One is then instructed to reboot Windows twice to get those instructions to work as they’re intended to. What it doesn’t say is that strange things might happen before the first reboot occurs.

Black Screen, No UEFI — No Nothin!

I about had heart failure when I rebooted my PC this morning and the Flo6 came up black with no normal boot sequence. No Asrock logo, no instructions to hit Del or F1 to load EFI, no F11 for boot menu. There’s not much one can do to fix a Windows PC that won’t do anything, short of taking it into a shop.

So I turned off the power supply, then hit the power button for 10 seconds to make sure all the capacitors got discharged. Then I took a break and walked away from the machine for 10 minutes. Then I powered on again. Phew! This time, the Asrock logo appeared, and it booted into Windows 11.  To my great relief, the second reboot was no big deal, and I was glad.

Here in Windows-World, you can make big changes without incurring at least some risk. This morning, I wondered if I’d bitten off more than I could chew. I even wondered if I’d bricked the Flo6. Thank goodness, I had not. I’ll take that as a win, even though you can see in the lead-in graphic that 2023 keys remain absent on this PC. Go figure!

 

Facebooklinkedin
Facebooklinkedin

Understanding El-Cheapo Windows Licenses

Every so often, a new round of bargain‑basement Windows license deals makes the rounds. You’ve seen them: Windows 11 Pro for ten bucks, Windows 10 Pro for even less. They pop up on StackSocial, StackCommerce, and a handful of deal‑driven tech sites. And like clockwork, the obvious question arises: Is this for real, or too good to be true? Neither and both: indeed, understanding el-cheapo Windows licenses hits both sides of this common wisdom.

More On Understanding El-Cheapo Windows Licenses

As someone who’s been around the Microsoft ecosystem for a long time — and who has more legit keys than I’ll ever need thanks to MVP status — I find the whole phenom fascinating. Not because I need another license, but because these offers sit right at the intersection of Microsoft’s licensing rules, its activation infrastructure, and the gray‑market economy surrounding both.

Here’s the key (pun intended): activation and licensing are not the same. Activation is a technical handshake with Microsoft’s servers. Licensing is a legal framework that governs how a key is properly obtained and used. Those two systems overlap, but they don’t enforce each other as tightly as many expect and assume.

Most $10 keys fall into one of three buckets. The first is unused OEM keys pulled from bulk hardware purchases. Perfectly valid keys, never activated on their original devices, but not transferable under Microsoft’s rules. The second bucket is decommissioned or oversold MAKs (multiple activation keys) — volume license keys with high activation counts that get resold repeately. They activate until the pool runs dry. The third bucket is region‑restricted retail keys, bought cheaply in low‑cost markets and resold elsewhere. They activate just fine, and Microsoft rarely retroactively enforces region boundaries.

None of these keys is counterfeit. They’re simply not authorized for retail distribution and sales. And that’s the crux of the matter. A key can be technically valid and still not legitimate under Microsoft’s licensing terms. That’s why you see disclaimers like “Microsoft may deactivate this license” — something never attached to a true retail key.

Why Not Stop This Madness?

So why doesn’t Microsoft shut this down? Because enforcement is aimed at organizations, not individuals.  Say a corporate MAK pool gets audited and is found to be leaking keys. Then, the consequences fall on the organization that holds the license — not the end user who bought a $10 key online. Microsoft’s activation infrastructure is built for compatibility and ease of deployment, not aggressive policing. As long as the upstream license pool stays quiet, the key will likely keep working.

That’s why you see technically savvy users reporting years of trouble‑free activation. They’re not wrong. They’re simply describing the operational reality, not the licensing reality.

In the end, these cheap keys occupy a curious middle ground: not fake, not fully legitimate, but functional and low‑risk for individual buyers. They’re a reminder that Windows licensing is strict on paper, pragmatic in practice, and full of gray areas that only get more interesting the deeper you dig.

Here in Windows-World one perforce gets comfortable with gray areas. This one seems a bit more gray and shadowy than most, but there you have it!

Facebooklinkedin
Facebooklinkedin

Secure Boot Pursuit Undone

We’ve been (and still are, I kid you not) snowed in here in Central Texas. With Winter Storm Fern bearing down on us, we started hunkering down here last Friday (1/23). On Saturday we had rain, sleet and snow, and woke up to snowy sights Sunday. Figuring I had time on my hands, I decided to see if I could get Secure Boot working on my Asrock B550 Ryzen 7 5800X Flo6 production desktop. Alas, after much wrestling with hardware and software, I saw my Secure Boot pursuit undone early, early this morning. Let me explain…

Why Is My Secure Boot Pursuit Undone?

Through all kinds of contortions (see list below) I couldn’t get the PC to boot with Secure Boot enabled. Let me enumerate some of them so you can appreciate what I tried and failed to get done this weekend:

  • 2 repair  installs of my current running OS
  • 1 “dirty install” (do not format partitions, but run installer which moves old OS into Windows.old and creates a new one: IDKYDT)
  • At least 2 each dism /restorehealth, sfc /scannow & chkdsk
  • Remove boot/sys drive from its M.2 slot to wipe NVMe config data from UEFI (have to remove GPU to access slot, sigh)
  • Swapped out old, soon-to-be obsolete 1070 Ti for 3070 Ti GPU.
  • spent over 30 hours fiddling with UEFI and Windows configs

After the “dirty install” I realized I’d hosed the primary MSA login on my main work machine. Not acceptable!! This morning, I built a new Macrium Reflect X Rescue disk, extracted the drivers from the Flo6, and restored my most recent backup (Friday afternoon, after I’d reorganized the boot/sys drive partitions).

Back in Business, Back to Work!

I learned a bunch about boot configuration data and related commands. I’m definitely completely up on booting the Flo6 into WinRE, Windows installer media, and the Macrium Rescue Disk. I’m much better acquainted with the Asrock UEFI than I’ve ever been before.

I also learned that my old MS Comfort Curve 4000 keyboard can’t (or won’t) send Fn key data to UEFI. Working on the ThinkPad P16 Gen 1 I soon figured out scrolling Copilot output was MUCH easier with an external mouse with scroll wheel than using the touchpad. Who knew?

And finally, I learned that Copilot will lead you all over the place trying to solve problems, heedless of time involved and consequence entailed. Sure, AI will tell you pretty much anything about Windows you want to know, but I wasn’t happy with the circuitous routes it took me on, and the circles it spun me through. Then it occurred to me: the words mendacious, malicious, utopia, and paradise all include AI, as do the phrases folie a deux and waste of time. Here in snowed-in Windows-World this weekend, I saw all those things play out. It was oddly engaging, but I’m glad it’s over.

Facebooklinkedin
Facebooklinkedin

NVIDIA Enters Windows on ARM Field

Here’s an interesting bit of news: AI heavyweight NVIDIA enters Windows on ARM field, as discussion of its N1 and N1X SoC offerings proliferate. These stories are popping today (Jan 20) but rumors have apparently been flying since last year. I got my info from WinBuzzer, but other key stories from TechRadar, DigiTimes, Tom’s Hardware, and more, are also worth a peek. Qualcomm’s exclusivity looks ready to expire, and x86/AMD64 CPUs likely to get even more competition soon.

As NVIDIA Enters Windows on ARM Field, Here’s What’s Known

The initial offering involves two “system-on-a-chip” (SoC) architectures known as N1 and N1X. According to WinBuzzer (confirmed at other sources) “the N1 designation likely targets desktops while N1X focuses on notebooks…” Deeper technical details are still emerging but here are some broad possibilities:

  • 20-core ARM CPU designed with MediaTek
  • 10 Cortex-X925 performance cores
  • 10 Cortex-A725 efficiency cores
  • NVIDIA Blackwell GPU
  • Built on TSMC 3mm process
  • NPU delivers up to 1000 TOPS for AI
  • Includes 128GB RAM shared between CPU & GPU

That certain raises the bar from where things stand with either generation of Snapdragon X processors (shipping X1 variant since last year, X2 planned for Q126 delivery).

Things Could Get Interesting…

The big news here, of course, is that NVIDIA is building in GPU capabilities that match their current discrete and laptop 5070 class devices. Qualcomm’s offerings have delivered sufficient computing power and astounding battery life. But their Adreno GPUs are underpowered for serious gaming, 3D modeling, simulations, and other display-intensive workloads.

Looks like NVIDIA is throwing down a gauntlet in the Windows marketplace. This should make life interesting for everybody, including prospective buyers, but also intel, AMD, Qualcomm. The biggest PC OEMs are already on board. Look out Windows-World, here comes another 800lb gorilla!

Facebooklinkedin
Facebooklinkedin

Windows 10’s Long Goodbye

Officially, it’s been “out of service” since October 14. And indeed, Windows 10 market share has been falling for some time now, with 11 ascendant. But, in unwinding Windows 10’s long goodbye from the desktop OS scene, there’s no sign yet of a spiraling vortex as the old OS goes down the drain. Remember, too, that older OSes — inlcuding 7,  XP and 8.x versions all show up in a range from just under 3% (7) to under 0.3% (XP, 8, and 8.1). Apparently old OSes never fade away completely…

Unwinding Windows 10’s Long Goodbye via 7

As I think about what’s going on here, I can’t help but use Windows 7 as a lens through which to view Windows 10’s upcoming decline. This actually shows itself quite nicely in a Copilot-generated desktop share graph (source: Wikipedia’s summary of StatCounter data 2015-2025).

2015, of course, was the year in which Windows 10 made its debut. It was also the same year in which Windows 7 transitioned from “mainstream support” to “extended support.” That’s what Windows 10 did this year, in slightly different terms.

Notice the shape of the curve imposes modest steps until the midpoint. It shows more serious declines since then. My gut feel is that Windows 10 will experience a similar fall-off. That said, I also believe the curve will drop more precipitously. That’s because MS has long sworn to limit extended support for 10 to 3 years, whereas it didn’t end ESU for 7 until the 5-year mark (2020) came along.

That would put the half-way mark three rather than 5 years out, with faster dropoffs after that. That said, with RAM and GPU prices currently on a steep rise, the impetus to buy new hardware to meet Windows 11 requirements may have hit a steep wall. Here in Windows-World the path from A to B (or 2025 to the New Year and beyond) isn’t always straight or simple. Let’s see what happens, shall we?

Facebooklinkedin
Facebooklinkedin

Thunderbolt 5 Status Approaching 2026

I’ve been thinking about new technologies lately, and the hurdles that OEMs face bringing them to market. Consider that only 2% of global PC sales are Copilot+ capable (which includes TB4). In that light, it’s not surprising that the market presence of TB5 is easily summarized as “slim to none.” Even so, I wanted to report on Thunderbolt 5 status approaching 2026, and share which laptops and mobos sport this latest, greatest iteration. Here goes…

What’s Thunderbolt 5 Status Approaching 2026?

There is a small number of laptops and motherboards currently available that include (or enable) TB5 support. Thus, for example, one must purchase an ASUS mobo with a TB5-capable header AND an ASUS Thunderbolt EX expansion card, to provide TB5 ports on a desktop PC.

Tasked with finding laptops with TB5 ports, Copilot produces a list of 12 models from 7 OEMs (MSI [3], Gigabyte [1], ASUS [1], Alienware (Dell) [1], Razer [1], Lenovo [1], Dell (Business) [1], and HP [1]). All come with MSRPs that exceed US$2,000. For motherboards, there’s one — and only one — source: ASUS for Z790 and Z890 (Intel) and X670E (AMD) and a hybrid (ProArt Creator). All seem to need the aforementioned expansion card to complete the connection.

Why Is TB5 Uptake Miniscule?

First off, the Intel Barlow Ridge controller is required for TB 5. Apparently, it is ill-suited for use in smaller, lighter laptops because of its space and power requirements. Second, TB5 comes with demanding power requirements (up to 240W passthrough) which requires beefier batteries and power leads to accommodate.

Finally, TB5 delivery issues from demand. And despite its formidable capabilities (120 Gbps video, PCIe 4.0 x4 host interface, DisplayPort 2.1, and up to 240W USB-PD passthrough) there’s apparently insufficient demand to drive it into lots of desktop and laptop designs. Over time, this will change. But for the moment, TB5 looks very much like a killer design looking for market uptake and support.

 

Facebooklinkedin
Facebooklinkedin

Windows 11 Hits One Billion Active Users

Here’s an interesting milestone that raises an even more interesting question. In his Ignite 2025 keynote, Pavan Davuluri made this statement “At Ignite 2025, we’re celebrating a major milestone: Windows 11 now powers more than one billion people worldwide.” Windows 10 hit that same number in March 2020. As Windows 11 hits one billion active users, the tide is turning on Windows 10, too. Let’s talk about this changeover, shall we?

After Windows 11 Hits One Billion Active Users, Then What?

According to StatCounter, Windows 10 accounts for 41.75% of the user base, with Windows 11 at 55.18%. Assuming the 1 B count applies as of that date — perhaps foolish, but a point of departure anyway — that means ~757M users still run Windows 10. It also means that ~30.7 M still run some older Windows version.

This shows several interesting things, IMO:

  • The Windows user base is pretty formidable, with perhaps as many as 1.8B users across all versions. it’s big but less than one-third compared to global 5.78B smartphone users.
  • Windows 11 crossed over 10 last June, and is over 13% ahead of the older OS now. I expect this split to continue, with 11 gaining ever more market share.
  • It took Windows 10 13 months to increase from 1B to 1.3B (April 2021); I think Windows 11 will cross that span more quickly.
  • It took Windows 10 five years to hit the 1B mark; Windows 11 did it in 4 years. With Windows 10 EOS behind us, it can only gain momentum.
  • With MS offering free ESU to consumer grade users for one year, that momentum may be somewhat blunted. This is offset by the remaining 30-35% of “strictly business” Windows 10 users who MUST pay for ESU. Estimates of ESU Windows 10 users vary widely, anywhere from 100-400M.

It’s an interesting situation, and an even more interesting landscape. As always, it will be fun to wait and watch for another such milestone announcement from MS. I wonder if that means Ignite 2026, or something sooner? Here in Windows-World, waiting and wondering are both hugely germane and useful attributes for those who labor in such fields.

Facebooklinkedin
Facebooklinkedin

WinGet Chaos Presages Changes

Just yesterday, I was catching up over at ElevenForum.com, and read a thread entitled “Winget errors…” It talked about issues accessing the WinGet source error. It reads "Failed in attempting to update the source: winget." I’ve seen this before myself. It occurs mostly when issues involved with accessing the MS WinGet servers come up. Then it happened to me soon thereafter, for updates and for an attempted export/import operation. This kind of WinGet chaos presages changes, as it shows a shakier Internet infrastructure than normal. Let me explain…

WinGet Chaos Presages Changes in Server Access/Reliability

In working with any cloud based service — including WinGet — the presumption is that the service is “always available.” Bad things, or nothing, happens when it’s unavailable. Ditto for issues when attempting to access the Internet infrastructure and cloud that leads to said service. Things don’t work like they’re supposed to — that’s where the “Chaos” part comes in — until the service returns to normal, expected behavior.

Recently, I’ve seen reports of outages or DNS attacks that have taken AWS, Google, Microsoft and others offline. Sometimes it’s just minutes, sometimes it’s hours; rarely, it’s half a day or longer. But chaos follows in the wake of such outages when things stop working, or don’t work as they should. Perhaps the strangest recent manifestion occurred when Internet-connected beds (human sleeping platforms) got wonky during an AWS outage.

Closer to my desk, yesterday’s WinGet weirdnesses reflect the same chaos that ensues when expected information sources and handling in the cloud go away. It seems to be happening more often. I’m inclined to look for ways to fall back on local information rather than simply failing when cloud information isn’t available.

In small things, and small ways, little bits of Chaos remain unavoiodable. Chaos is seldom desirable, especially in big doses. Let’s hope the wizards who make Windows-World such a big thing feel the same way, and help us work toward failover or workarounds to keep the Chaos at bay.

Note Added 4+ Hours Later: Azure Outage

As I’m reading Windows related news this afternoon, I see ample coverage of a major Azure outage yesterday afternoon. For example, Neowin  Microsoft Azure hit by massive outage… Whaddya bet the WinGet stuff falls under that umbrella. Seems to be working fine today, though.

Facebooklinkedin
Facebooklinkedin

Enduring Windows 10 Hangover

It’s interesting and perhaps a bit puzzling. For “compatibility reasons” — some having to do with browsing the Web — Windows 11 has long reported itself as a kind of Windows 10. Indeed, one must examine Build numbers, mostly, to figure out which version of Windows is really driving the bus. To see this enduring Windows 10 hangover try this string in PowerShell:

[System.Environment]::OSVersion.Version

You can, of course, get the real skinny by running winver.exe, or a more nuanced Get-ItemProperty command in PowerShell:

Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" | Select-Object DisplayVersion, EditionID, CurrentBuild

You can see the results of these two commands in this blog post’s lead-in graphic. It still shows my production Windows 11 PC (Build 26200) with a Major version number of “10,” while the Get-ItemProperly output shows the “real deal” on this machine.

Will Enduring Windows 10 Hangover Get Fixed?

Now that Windows 10 is past its End of Service date, will MS fix this strange reporting practice? Probably not. There are reasons upon reasons why this reporting quirk is likely to remain unaltered.

The whole compatibility thing is HUGE: lots of driver models, apps and applications, and enterprise tools assume that Windows 10 is the end-all and be-all for modern Windows versions. Indeed, it’s much, much more than a browser user-agent assumption. According to Copilot, “enterprise environments rely on registry keys such as ProductName and ReleaseId for automation,” so “those keys are often left untouched in Insider Builds to avoid disrupting telemetry and deployment pipelines.”

Hence the following, also from PowerShell using this command sequence:

Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber

Notice that my Production Win11 system reports in this command as Windows 10 Pro, version 2009, with correct build number.

At least, I now know why this apparent misreporting occurs, and understand that it’s for good cause. Here in Windows-World there are plenty of apparent mysteries whose simple explanations lie in the many twists and turns in Windows history. This is one of those, I reckon.

Facebooklinkedin
Facebooklinkedin