Category Archives: Thoughts & concerns

Stamping Out Recurring Renewals

I got an email from a software vendor last week, informing me its auto-renewal would kick in Friday. I don’t want to identify the vendor. Thus, I’ll simply observe this was collaboration software I used to write a book in 2014, and haven’t used since. Time for that auto-renewal to end. But stamping out recurring renewals comes with an interesting and vexing set of challenges. Let me tell you more…

Sounds Easy: Stamping Out Recurring Renewals

You’d think this kind of thing would be as simple as logging into the vendor site, canceling the account and/or subscription. And in theory that’s true. But in practice, it’s not. First thing: I had to re-establish my login for the vendor site. My account was “inactive” so that meant a call to tech support and an interminable hold. All this just to get into my account only to cancel same and terminate my subscription.

But that still didn’t end the renewal cycle. Because I’d purchased the subscription via PayPal, I also had to log there, too. Then I had to manage renewals inside PayPal, and make sure permission for the vendor to charge me was removed. Again, that’s easy in theory. But I had to formulate the right query to get an inkling of where to go in the PayPal GUI to make that happen. Indeed PayPal just changed its Settings interface so that Google’s instructions are irrelevant. I had to use PayPal’s built-in Help to find what  I needed. It’s always something, right?

2-3 Hours to End One Recurring Charge

By the time I had finally gotten out from under, I’d spent between 2 and 3 hours to cancel the recurring charge for something I hadn’t used in a decade. I believe I totally get the value of apps/services like Rocket Money simply because it offers a one-click option to cancel subscriptions and recurring renewals.

Indeed, I’m thinking about giving it a try, just to help me deal with my two-to-three-dozen subscriptions and recurring software obligations. I don’t have to put a very high value on my time to justify some expense, given that it could otherwise take me a week’s work (40 hours) to deal with all that stuff manually.

Things get complicated sometimes, here in Windows-World. I’m hoping some relief may be at hand… But I’m too experienced to believe this more than a fond wish, rather than a likely outcome!

Facebooklinkedin
Facebooklinkedin

GeForce 1070Ti Nears EOL

I’ll admit it: I’m a cheapskate. Case in point: both of my 5800X PCs still run NVIDIA GeForce 1070Ti GPUs, scavenged from long-retired older builds. Reason: the Antec 200 cases in which they resided couldn’t accommodate the longer, newer cards available at the time. In a surprisingly cryptic “Deprecation Schedule” document, however, NVIDIA reveals that GeForce 1070Ti nears EOL. In fact, the 580 series of drivers will be the last to support Maxwell, Pascal and Volta architectures. The 1070Ti was one of the last Pascal-era devices to go to market, so its days are officially numbered. The brief announcement that seals its fate appears as the lead-in graphic. Sigh.

If GeForce 1070Ti Nears EOL, What’s Next?

Looks like I’ve gotta buy two new GPUs for my pair of 5800X systems. Copilot recommends the NVIDIA RTX 4060 Ti as a logical replacment. It still works with the same 8-pin power connector, costs US$450-500, and is supposed to be 20-30% faster. For about the same money, however, AMD RX 7700 XT costs the same but offers a 10% performance bump. I’ll have to ponder those diffs and do some competitive shopping analysis.

That said, the last 58x driver drops in October of this year, concident with EOS for Windows 10. But Copilot says NVIDIA will offer security-only updates for another two years after that (until October 2028). So maybe I don’t have to hurry too fast to make that switch. After all, procrastination is my middle name here in Windows-World when it comes to spending money on enforced updates.

But as the technology base keeps changing, and my hardware keeps aging (along with your humble author, who no longer even qualifies as a “summer chicken”), switchovers are inevitable. I hope to hang out here in Windows-World enough longer to survive a couple more major technology turnovers. We’ll see!

Facebooklinkedin
Facebooklinkedin

Pondering Window 10 Turns 10

There’s been a lot of coverage in the Windows trade press around Windows 10’s tenth birthday. It made its debut on July 29, 2015. As I’m pondering Windows 10 turns 10 — and its upcoming EOS on October 14 — I asked myself “How does a 10-year lifespan compare to other Windows versions?” Obligingly enough, Copilot provided me with a text-based histogram that lays things out as far back as Windows 1.x versions. It serves as the lead-in graphic for this post.

Pondering Window 10 Turns 10: Lifespans Compared

Here’s what I see when I look at that chart:

  • Only two versions have had longer runs than Windows 10 — namely, Windows XP (13 years) and Windows 7 (11 years). Both are arguably the Windows champs as far as versions go, and I used the heck out of them during their heydays.
  • I’d have to say that a life span of under 7 years pretty clearly separates winning Windows avatars from losing ones. That group includes Windows 1.x, 2.x, 95, ME, Vista, 8 and 8.1. Of those, Windows 95 is the only one I remember fondly, but I moved to 98 long before it got close to EOL.
  • Over this set, the distribution is pretty scattered and broad. The min is 2 years, the max is 13 years, the mean is 7.25 years, and the median is 6 years. Given my preceding observation about lifespans under 7 years, does that mean Windows is rather less than more successful? Interesting question, but I don’t think the answer is “Yes.” Arguably, Windows 7 persisted because neither 8 nor 8.1 could really pick up and run with the ball.

It’s interesting to step back and look at how many versions have come and gone and how each one has had its own lifecycle. My gut feel is that Windows 10 deserves to be in the same cohort as XP and 7. I’d argue further that Windows 11 could be in the same company — but of course it’s too early to say just yet. After all, it’s only just a bit over 4 years old.

Facebooklinkedin
Facebooklinkedin

24H2 Install Includes Up-to-date Store Apps

I learned some new Windows-speak this morning, I think. First, I read stories at WindowsLatest and Thurrott.com that mention “inbox” and “in-box” apps respectively. Then, I read the MS Tech Community post that inspired their interesting assertions. Seems that Thurrott’s use of “in-box” is probably the most appropriate nomenclature. What’s under discussion is the update status of MS Store apps as a new install of Windows runs for the first time. Indeed, a new 24H2 install includes up-to-date Store apps, for ISOs and installers (e.g. the Windows 11 Installation Assistant)  dated June, 2025, or later.

Why 24H2 Install Includes Up-to-date Store Apps Matters

In earlier Windows 11 installs, one of the first post-OOBE tasks the OS undertakes is a full-scale update of built-in Store apps. This occurs via the Store’s update facility. WindowsLatest observes this means that up to 36 apps are covered. In turn, that saves time and bandwidth. Under this new regime, apps included in the OS image get newer versions. Here’s what the afore-linked blog post says:

…newer versions of the inbox Microsoft Store apps [come] preinstalled instead of the release-to-manufacturing (RTM) version. This includes updated ISO images, virtual hard disks (VHDs), and Azure Marketplace images.

Basically, this means that MS now provides images with more up-to-date versions of Store apps. My take is that the actual update count depends on when download images got built.  MS replaces them on at least a quarterly schedule. Thus, this means fewer Store updates than in earlier Windows versions (23H2 and lower).

Good news, of a singular and restricted sort, here in Windows-World. I’ll raise a small cheer, and a word of thanks, to the Windows team in response.YAY!

Facebooklinkedin
Facebooklinkedin

Will BlueScreenView Go Black?

In upcoming versions of Windows 11, says Microsoft, the long-standing “Blue Screen of Death” will go black. That is, it will change color and appearance from its deep-blue, graphics- and text-laden format. It will transform to something sleeker and simpler, in pure black-and-white colors. According to Windows Latest, this change should appear in Windows 11 24H2 or 25H2 and “may not be backported to Windows 11 23H2.” All this given, I’m asking this question: “Will BlueScreenView go black?” Let me explain…

Unpacking the query: Will BlueScreenView Go Black?

To begin, let me identify BlueScreenView as a NirSoft tool, from Israeli programming dynamo Nir Sofer. It’s been around for over 15 years, and provides simple decodes for Windows mini-dump and crash dump files. It’s darned handy, in fact, if a BSOD (of either the black or blue variety) gets past you, and you didn’t record the STOP CODE error that provoked the crash, it will show it to you.

The afore-linked Windows Latest story works itself into something of a lather by observing that (a) the new black BSOD looks a lot like a post-GUI Windows Update screen (it does), and (b) that some Windows users may mistakenly see it as such and miss the STOP CODE for that reason. Here again, BlueScrenView should come in handy to help find and expand on those pesky codes.

What I want to know, however, is if Mr. Sofer will issue a new version of his program, and call it BlackScreenView instead. I’m guessing maybe yes, maybe no, depending on how much weight he puts on that change.

These are the kinds of things I wonder about as I putter around happily in Windows-World. Let’s see what happens, shall we?

Facebooklinkedin
Facebooklinkedin

WinTerm Windows 10/11 Divergence

Here’s something interesting — and purely temporary. My Windows 11 PCs and VMs are getting updates to Windows Terminal, but my Windows 10 PCs aren’t (yet). As you can see in the lead-in screencap that means there’s some WinTerm Windows 10/11 divergence currently happening. To the left, Windows 11 shows version 1.22.11751.0; to the right, Windows 10 shows 1.22.11141.0. An upgrade attempt on WinTerm for 10 says “No newer packages are available from the configured source” (which happens to be WinGet itself). What’s up?

Why There’s WinTerm Windows 10/11 Divergence

Simply put. MS is pushing the Windows Terminal upgrade to 11 before it gets around to doing likewise for Windows 10. It could happen in the next hour, day, or week. But it surely won’t take much longer than that.

Here’s what Copilot says:

The version difference you’re seeing—v1.22.1141.0 on Windows 10 versus v1.22.11751.0 on Windows 11—likely comes down to staggered rollout timing and platform-specific servicing.

Microsoft often releases Windows Terminal updates in waves, and while both versions fall under the 1.22 stable branch, the build numbers reflect incremental servicing updates. These can include bug fixes, compatibility tweaks, or minor enhancements tailored to each OS version. For instance, Windows 11 might receive a slightly newer build first due to broader feature support or integration testing, while Windows 10 gets a more conservative rollout.

It’s nice to get a decent explanation, and it helps me appreciate one thing that Copilot really is good at: summarizing and stating the MS party line on what’s going on when interesting things happen.

Eye of the Beholder

Of course, I recognize that what’s interesting to me is not interesting to everyone. Perhaps it’s not even interesting to that many others. But hey, it’s definitely a feature of the way things happen in Wndows-World. And if you read this blog, you already know I care a fair amount about that kind of stuff. Hopefully, you feel likewise — or what else would lead you here?

Here’s a shout-out to Shawn Brink at Eleven Forum, whose X tweet alerted me to this situation. See also the related news item. Thanks!

Note Added 6/26 (One Day Later)

And as I check the running instance of Windows Terminal on Windows 10 right now, it’s been upgraded. My guess is that Windows Store caught it on its usual light-night/early-AM update cycle. And sure enough, here’s visual proof:

Facebooklinkedin
Facebooklinkedin

Strange Crystal Dew World Hiccup

Yesterday, I noticed that both WinGet and PatchMyPC Home Updater hiccuped when trying to update CrystalDiskMark (8.0.6 to  9.0.0) and CrystalDiskInfo (9.6.3 to 9.7.0). This strange Crystal Dew World hiccup (that’s the home site for both apps) got me wondering if the developer had abandoned freeware versions of those tools for ad-driven (installer-based) or for-a-fee (MS Store) versions only. I’m please to report that my presumption was wrong, and new freeware versions for both programs are updating properly now.

What Caused This Strange Crystal Dew World Hiccup?

Apparently there was some delay between when the new version info got broadcast and when the Crystal Dew World website got updated. Indeed I saw web info (which serves as the lead-in graphic for the story) that led me to wonder if ad-driven (ZIP and Installer) or paid-for (Store) versions were the only remaining versions of CrystalDiskMark (CDM) and CrystalDiskInfo available.

This morning, however, when I went back to check again, things were different. I still see the same situation at Crystal Dew World (here’s a link to its CDM download which includes an installer named CrystalDiskMark9_0_0Ads.exe). But WinGet and PatchMyPC can both successfully upgrade these tools now (they threw “hash match fail” errors yesterday) and are proffering ad-free freeware versions that come from sourceforge (you can use WinGet Show CrystalDewWorld.CrystalDiskMark to reveal its database contents).

Updates Take Time to Propagate

I’ve seen similar things happen before — often, with MS facilities such as PowerShell and Windows Terminal — when an update emerges but packages and database contents don’t synch up. All in all, though, I’m glad that freeware, ad-free versions of these useful tools remain available. If they didn’t I’d have to find something else!

And, far too often, such things become necessary here in Windows-World. Not this time, apparently for CDM and CDI. Not yet, anyway… But the ad-oriented interface at Crystal Dew World strongly suggests it could happen if not now, perhaps later.

Facebooklinkedin
Facebooklinkedin

Pondering US$200 4TB SSD Availability

I’m working my way up, slowly, to rebuilding a 5800X AMD desktop (on an Asrock B500 Extreme4 motherboard). The current build lacks a second M.2 NVMe SSD, so I’m also thinking about what kind (and how much) SSD to emplace in that currently open slot. Based on a teaser from NeoWin this morning, I’m also pondering US$200 4TB SSD availability, and its potential impact on that refurbishment.

Why Am I Pondering US$200 4TB SSD Availability?

Other than the obvious — amazing price for decent performance — I’ve got lots of reasons to think about choosing my second drive for this rebuild. Here’s a list:

  • I’ve got 3 or 4 good 1TB NVMe SSDs already in hand, all with 3K+ MBps read/write capability, plus 1 2 TB that’s PCIe Gen 4 and on par with the cheap-o 4TB item.
  • The B550 manual says the max capacity of SSDs it handles tops out at 2TB. So a 4TB unit might not even work.
  • I am trying to contain myself on this redo, price-wise, so I’m not sure I want to fork out another US$200, even though it’s a pretty potent price/performance combination.

Then I Started Thinking About HDDs

You can still buy a Seagate 5TB 2.5″ 5400 RPM hard disk for between US$140 and $160. That puts cost per TB on a roughly equal footing, though it does significantly impact performance. Indeed,  the HDD’s 450 MBps read/write is a decimal order of magnitude slower than this SSD’s reported 4,500 MBps or better. FWIW, I already own two of those so I could easily emplace one as a backup or archival drive in that build. Backup/archival space won’t be an issue, for sure.

So you see my situation: I have to think about what I want from the rebuild, and manage the expense versus capacity/capability ratio. I’ll keep thinking, and keep writing about it here. So far I’m leaning heavily toward “use what I’ve got, keep it cheap.” But that could change: Stay tuned!

Facebooklinkedin
Facebooklinkedin

Recent Rising Reclaimable Counts

Recently, I’ve been noticing that Cumulative Updates (CUs) typically leave upwards of 10 or more reclaimable packages around, following installation. If my memory is any guide, numbers from 2-4 had been more typical until earlier this year. But recent rising reclaimable counts seem all too likely these days.

So I asked Copilot about it: “Why does dism /analyzecompo-nentstore find more reclaimable packages after CU updates recently?” Imagine my surprise when Copilot cited one of my very own blog posts in response as a potential source of “deeper insights.” Wow: that’s a shock to me!

Here’s what DISM told me after I updated Windows 11 24H2 to 26100.4202 last week: 10 packages reclaimable!

Why Rising Recent Reclaimable Counts?

When I check the component store using DISM /Get-Packages after recent CUs I see numerous staged and superseded items in the listing. These are what often gets cleaned up when a following DISM /StartComponentCleanup is run. Google AI says that  recent changes to “checkpoint cumulative updates” in 24H2 means that “Future updates then build incrementally from these checkpoints, leading to smaller downloads and potentially faster updates.” Looks like it means there are more and smaller items of this kind, rather than fewer and larger ones, as under the previous regime.

Thus, I think the phenomenon is real, and reflects a change in update approach and architecture. DISM dispatches these items pretty quickly (at least anecdotally more quickly than the older approach, in my own personal experience). So all in all, I’m inclined to find this a good thing.

It’s nice when incremental changes in Windows mean improvements in the general state of Windows-World itself. Today, that’s my story — and I’m sticking to it!

Note Added 6/7: A New Top Count!

I ran DISM /AnalyzeComponentStore on the X380 Yoga just now (running 24H2 Beta Channel Build 26120.4230). It reported a whopping 21 reclaimable packages, all of which vanish after running DISM /StartComponentCleanup. See this:

I’m inclined to take this as further validation of my thesis that CUs bring more (and smaller) packages for cleanup in their wake. What do you think?

Facebooklinkedin
Facebooklinkedin

Windows Start Soliloquy Gets Fanciful

MS has started a new design blog under the general heading of “Behind the Surface.” It’s entitled “Start, Fresh –Redesigning the Windows Start menu for you.” The “Windows Design Team” is named as the author, rather than one or more specific individuals. It’s an interesting read, if a bit too breathless and wonder-struck for me. Indeed although this Windows Start soliloquy gets fanciful and overdone, IMO, it’s still worth your perusal.

Where (and How) Windows Start Soliloquy Gets Fanciful

In a list of so-called “guiding stars” the blog states four key principles driving Start Menu design. These serve as the lead-in graphic above, so I don’t repeat them. MS makes much of the work it took to rework the Start Menu. Those efforts presumably fit into the upcoming release of Windows 11 25H2 later this year. Here’s a representative quote from the post, likely from a user interaction during that process (note the tone and diction, please):

Help me find my apps faster. Let me bend Start to fit the way I work. And please—keep the magic, don’t lose the soul.

You’ve got to read the post and check out its images, tables, and language to really make sense of what it says. The key conclusions (and design changes) should include (each bolded item below is quoted verbatim from the blog post, sans quotation marks):

  • Dynamic recommendations: “files and apps” that “surface exactly when they matter.”
  • More and better views for all apps: Repositioned at the top of the Start Menu, you can choose “between logical categories, a neat grid, or the familiar A-Z list.”
  • Mobile content, gently blended: Integration with mobile devices mentions both Android and iPhone and stresses how you can reach out from the desktop to a mobile device.
  • Personalization, elevated: Stresses user’s abilities to zoom in on, or ignore, individual Start Menu sections, and to size it to match available screen real estate (bigger on big monitors, smaller on littler ones).
  • Under-the-hood speed: A commitment to making Start an “accelerator of your day” that loads “in a snap” not “dragged by lag.:

Generally MS makes an ongoing commitment to keep listening to user input and adjusting to what users have to say. Overall their goal is to meet their mantra for what the Start Menu should be:

Everything you need, right here, ready when you are.

This Should Be Interesting…

The rah-rah nature of the blog post and its overall tone and language aside, MS is putting itself out there. In the broadest of strokes they’re promising to improve the Start Menu, and to keep making it better. It will be interesting to see how that plays out in upcoming Insider Preview releases — and ultimately, in 25H2 itself. I’ll be watching — and sharing my observations — along that path. So will lots of other Insiders and other users. Stay tuned!

Note: here’s a shout out to Sergey Tkachenko at WinAero.com, whose story this morning pointed me at the MS blog post. Thanks! For a vastly different take on what’s going on here, see what Paul Thurrott has to say about this blog post.

Facebooklinkedin
Facebooklinkedin