Category Archives: Thoughts & concerns

Benefits from Buying One Generation Back

Patience isn’t a virtue many tech shoppers cultivate. But here’s the thing: waiting just one product cycle can put serious money back in your pocket. Buying one generation back is one of the smartest, most underappreciated moves in the PC-buying playbook. You get hardware that was cutting-edge twelve months ago, at prices that make last year’s flagship look like a budget pick.

Case in point: a June 19 Windows Central story entitled “Dell’s stunning XPS 13 drops to under $1,000, packing a massive 32GB of RAM.” Careful reading and a little thought reveals that with the newer, faster, more efficient CPUs now out in the market, a markdown seems the right way to clear out this older inventory.

Why Buying One Generation Back Makes Sense

When a manufacturer ships a new laptop model, retailers have a problem: they’re sitting on inventory of the outgoing model. They need it gone. Fast. So prices drop — sometimes dramatically — to clear shelf space and warehouse stock.

Here’s the kicker: the old hardware didn’t suddenly get worse. The processor that impressed everyone last year still handles your spreadsheets, video calls, and browser tabs just fine. Performance gaps between consecutive generations are usually modest — often 10–15%. That’s not worth full MSRP. But a 25–40% discount? Now we’re talking.

Retailers, manufacturers, and third-party sellers all play this game. The window is finite, though. Once inventory clears, deals disappear.

Real Savings, Real Hardware

Don’t take my word for it. Here are four real examples of what buying one generation back actually looks like in dollar terms:

  • Dell XPS 13 (9345) with Snapdragon X Elite: Dropped from $1,399.99 to $999.99 — that’s a full $400 in savings — after newer XPS models landed on shelves.
  • Dell Inspiron 15 (13th-gen Core i5, 2K touchscreen): Fell from $849.99 to $549.99 at Best Buy — $300 off — as 14th- and 15th-gen Inspirons took over the lineup.
  • HP OmniBook 3 (Snapdragon X, 14-inch, 16 GB RAM): Slid from $949.99 to $549.99 — a whopping $400 discount — following the launch of the updated OmniBook 5 and 7 models.
  • Lenovo Yoga Slim 7x (Gen 9, Snapdragon X Elite, 14.5″ 3K OLED): dropped from $1,300 to $800 at Best Buy — a $500 savings — as the 2026 Gen 11 (Snapdragon X2 Elite) arrived to replace it.

Those aren’t rounding errors. That’s real money. On the XPS 13 and Slim 7X alone, you’d save $900 combined. Buy both and you’ve basically gotten one laptop free.

Where to Hunt for Such Deals

You have to know where to look. The best hunting grounds are the Dell or Lenovo Outlet stores, HP’s certified refurbished storefront, and Best Buy’s clearance section (online and in-store). Open-box listings at major etailers are also worth bookmarking.

Timing matters. The best deals on buying one generation back typically surface right when a successor model is formally announced or begins shipping. That’s your signal. Manufacturers and retailers want the old stock gone before the new wave arrives.

Pro Tip

Set price-drop alerts using tools like CamelCamelCamel (for Amazon) or Google Shopping alerts. You’ll catch markdown as they pop up, before the good stuff disappears.

Bookmark those clearance pages right now. Set price alerts on the models you’ve been eyeing. Then act fast when the drop hits. Wny? Because quantities on outgoing inventory are always limited, and once it’s gone, it’s gone. Buying one generation back rewards the prepared shopper, not the hesitant one. A little patience up front means a lot less money out the door at checkout.

Here in Windows-World, we must grab our savings while the discounts persist. He or she who hesitates is lost. Get your budget together and keep you eye on the “new new” PCs, so you can cash in on the “old new” PCs!

Facebooklinkedin
Facebooklinkedin

Evolving Windows Device Security Hardware

This weekend, I pulled up the Windows Security Device security panel on my ThinkPad P16 Gen 3 (2025 build) and my ThinkPad X380 (2018 build; made a 2017 debut), and put them side by side. The difference showed me something interesting — namely,  evolving Windows Device Security hardware.

Both machines run Windows 11. Both are solid, business-class Lenovo laptops. However, the P16 Gen 3 panel is full: every tile is lit, every checkmark is present. The X380 panel, OTOH, shows obvious gaps. It closes out with a blunt verdict: “Standard hardware security not supported.” The lead-in screenshot tells a story of Windows device security hardware evolution over 7 years.

The X380 isn’t a bad machine. It was just built before the security landscape it now lives in actually existed. That distinction matters, so it’s worth unpacking what’s missing and why.

What Evolving Windows Device Security Hardware Means

The most visible absence on the X380 is the Secured-core PC badge. Not surprising when you check the timing: MS launched the Secured-core PC initiative on October 21, 2019. That’s over a year after the X380 shipped. The X380’s 8th-generation Intel Core (Kaby Lake Refresh) silicon predates the Dynamic Root of Trust for Measurement (DRTM) and System Guard Secure Launch capabilities that Secured-core status requires.

In sharp contrast, the P16 Gen 3 runs Intel Core Ultra 9 silicon that fully implements Intel Hardware Shield. That’s what underpins DRTM and Kernel DMA Protection at the hardware level. In addition, Secured-core mandates HVCI (Hypervisor-Protected Code Integrity) enforced at the silicon level. Older CPUs can enable this in software. Alas, they cannot deliver the hardware-based capability that Microsoft’s Secured-core PC requirements demand.

The second gap is the Security processor tile. The P16 Gen 3 surfaces an explicit tile confirming that TPM is visible, active, and reports correctly to the Windows Security layer. The X380 does have a TPM  (Lenovo shipped TPM chips on all commercial machines by 2017). However, Windows Security on the X380 doesn’t surface that tile. Its firmware TPM integration doesn’t offer stricter attestation-visibility that newer UEFI and firmware stacks expose to the operating system. The chip is there, but the trust handshake simply isn’t good enough for Windows to show it as an attestable asset.

The X380 Bottom Line Is…Not Quite There

That brings us to the X380 bottom-line verdict: “Standard hardware security not supported.” Windows delivers this message when a device cannot simultaneously confirm TPM 2.0 attestation, Kernel DMA Protection, and VBS readiness at the hardware level. The X380 can satisfy some of those requirements individually, but not in hardware. As a result, it falls short of the full baseline. That is not a misconfiguration, but falls out because the required silicon-to-firmware-to-OS trust chain simply wasn’t designed into the X380.

What Both Machines Get Right

Let’s be fair to the X380, because calling it obsolete would be wrong. Core isolation runs. And indeed, Virtualization Based Security operates in software mode. Secure Boot is fully active, with all certificates up to date. BitLocker encrypts the drive. These are the foundational Windows security capabilities that survive on older hardware, and they aren’t trivial. The X380 still protects data at rest and guards boot integrity against tampering. It simply cannot make the firmware-to-OS trust chain guarantees that silicon-rooted security delivers. There’s a meaningful difference between those two tiers, but the lower tier is not nugatory.

A Seven-Year Gap in Numbers

Between 2017 and 2025, Intel moved from 8th-generation Kaby Lake Refresh to Core Ultra (Meteor Lake and Arrow Lake). AMD traveled from Ryzen 1000-series to Ryzen AI 300. Along the way, Microsoft introduced Secured-core PC certification (2019), Windows 11’s hard TPM 2.0 requirement (2021), the Pluton security processor co-design with AMD and Intel (2022 ), plus evolving memory encryption standards. Thus, the Device Security panel on a 2025 machine doesn’t just reflect software updates . It also reflects seven years of deliberate co-design among Microsoft, Intel, AMD, and various OEMs, baked directly into the silicon and firmware before the OS even loads.

Wondering About Continued Viability?

If you’re running a 2017/8-era machine and wondering why your Device Security panel looks thin, it’s not your fault and it’s not your settings. It’s the silicon that falls short. The hardware security stack that Windows 11 fully expects is built into CPU microarchitecture and firmware design from 2019 onward. No amount of registry tweaking can close that gap. That said, your older machine isn’t broken. Instead it’s working at a lower tier of the trust hierarchy, but it still does real security work. When it is finally time to refresh, pull up the Device Security panel on your new, Secured-core PC. It  fills those gaps, and offers more and  better security capability. Worth it!

Facebooklinkedin
Facebooklinkedin

Sandbox Effect Keeps Spreading

OK, I admit it. I run Adblocking software inside my web browsers. To see web pages nowadays, that means I bump them up to 150% so I can read the text. That leaves less room for other stuff, especially ads. But I’ve noticed that an increasing number of websites simply won’t let viewers visit unless those visitors permit the ads to show. So I open those sites inside Windows Sandbox because it works as a no-filters and no-blocks-applied environment. Alas, this “Sandbox effect” keeps spreading as more and more sites make me do this.

Why Say: Sandbox Effect Keeps Spreading

I got a particularly rude wake-up call about this on Wednesday. In fact, I didn’t even figure it out until this morning. Two days ago, I noticed that WinAero was coming up in Firefox (where it’s in my favorites) as an all-back page. I even asked Copilot what might be wrong and it speculated that something with the CDN (Content Distribution Network — e.g. Akamai, etc.) might be wonky.

Wrong. This morning, it dawned on me that this “black screen” might be a particularly draconian implementation of a “no ad blocking” policy. And indeed, that’s what it appears to be (lead-in graphic, left). When I open the same site in Windows Sandbox (lead-in graphic, right) it comes up in readable form right away. Wowie-Zowie.

The Sandbox List Is Growing

Minutes ago, I had a similar experience at Thurrott.com. I suppose I should be grateful, because that site operator at least had the courtesy to tell me what was going on. Here’s what it showed me after a click-through from a “problem loading the page” error message:

Life is interesting when one is inclined to appreciate being informed that they must watch ads on a website, or skedaddle. Here in Windows-World, gratitude often takes unusual forms. This one, methinks, is more unusual than most. Happy Friday!

Facebooklinkedin
Facebooklinkedin

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