I’m flummoxed. I just upgraded PowerShell from version 7.3.3.0 to 7.3.4.0. It’s the latest stable version, as you can plainly see at GitHub. But even after updating, that preceding version still shows up using winget list powershell. An explicit uninstall request reports “No installed package found matching input criteria.” Hmm; WTF? I can only call this a PowerShell update oddity version confusion problem!

If you look at the left-hand tab in the lead-in graphic, you’ll see two versions of Powershell, one numbered 7.3.3.0 and the other 7.3.4.0. But when I try to uninstall the older one, winget can’t find it. And indeed when I try to open it in the right-hand tab, it comes up at the current (latest) version. I’ve seen something like this before, so I start thinking about causes and workarounds. Read on to see how I resolved this one…

Resolving PowerShell Update Oddity Version Confusion

I’m of the school that says if you can’t do it one way in Windows, you can almost always find another. If I poke around in my file system searching on “pwsh.exe” (the name of the powershell executable file), I see an app-based instance of the 7.3.3.0 version in ProgramFiles\WindowsApps. And sure enough, inside Settings → Apps, I find three (count ’em) versions of PowerShell. Here’s a snap:
AFAIK, I only need the middle one, so I right-click to uninstall the other two. When I’m done, I check Windows Terminal, and it tells me I need to reset my default profile. I do, and choose version 7.3.4.0. When I open a new Terminal window and run winget list powershell again, it shows only a single (and correct) version. Problem solved!

Now, all I have to do is figure out why the winget uninstall didn’t work, but a manual uninstall inside the Apps widget in Settings did the trick. I’m gonna have to think about that for a while… Stay tuned!

In dealing with the never-ending story of Windows OS and app/application updates, I sometimes marvel at the obvious and visible role that certain installers play in that process. Fortunately, some tools — like PatchMyPc — make a virtue out of “silently installing” such things, too. The arrival of a new Intel Bluetooth driver this morning on some of my PCs prompted the observation that installing updates silently (or not) has real value. For me, at least… (see lead-in graphic for my inspiration).

Why Installing Updates Silently (or Not) Matters

It’s all about the user interactions. Some installers demand that users respond to their requests for permission and acknowledgement before they’ll proceed. This morning’s Bluetooth item, for example, required no less than four mouse clicks to go through its paces.

This matters because it makes life interesting for admins who have to automate updates via scripting and automation. It also explains the broad appeal of a product like RoboTask and AutoHotKey (see this Windows Report story for some useful coverage of this topic). Capturing mouse movement and clicks and replaying them becomes a vital ingredient in turning something done “by user, by hand” into something that can run as part of a general scheduled update process. But in general, such things are best avoided if possible.

Going Down the Rabbit Hole…

Switching over to silent updates can be challenging, though. Take a look at this Spiceworks forum thread that walks readers through the requirements involved in working with Chrome templates and Group Policy Objects (GPOs). It’s kind of scary, but also pretty fascinating. There’s a lot of research and, sometimes, effort involved in putting complete update packages together for automated deployment. That’s the kind of stuff I like to observe, and learn from, when I have the chance.

Courtesy of NeoWin, I’ve just learned that March 31 is World Backup Day. There’s even a website at — you guessed it — worldbackupday.com. Sponsors include Amazon, Mega (file download service provider), iStorage and Backblaze (online backup/storage providers) and mijn.host, along with the World Backup Day organization. There’s even a pledge: “I solemnly swear to backup my important documents and previous memories on March 31st. #WorldBackupDay.” Indeed, let me wish all readers a happy World Backup Day 2023.

Note: the intro graphic comes from the WorldBackupDay.com home page, and is intended to motivate people to back up their stuff. I can only endorse this proposition. I myself learned the importance and value of backups in 1990 when a 300MB SCSI drive on a Mac died on me, and lost me a book I was writing at the time (and more). It was a disaster! But I learned my lesson, and I’ve lost nothing important since to the slings and arrows of outrageous fortune.

What Happens on World Backup Day 2023?

Ideally, everybody makes sure they make a backup of everything they want to keep, or protect against damage, loss or breach. Personally, I back up my production PC daily (including the system drive, plus two smaller drives where I keep all ongoing project work).

But there’s more:

1. You must know how to restore the backups you make.
2. You should make yourself familiar with rescue or repair media so you can boot and restore a backup even on a PC (or other device) that’s not booting normally. Some backup packages require separate bootable media for each protected PC (I have a tray full of teeny-tiny Mushkin Atom flash drives for just that purpose).
3. You should practice a restore occasionally. I end up using restore capabilities at least once a month myself — mostly because of self-inflicted issues arising from experiments — so I’m always ready to rock’n’roll.
4. Ideally, you should keep one or more backups offsite or online. That way if a meteorite takes out your home or office, you can still get back online by restoring to a different PC. I keep two backups in the cloud: one on OneDrive, the other in Norton Backup.

My basic guiding principle is that anything worth storing once is worth backing up at least twice (as just described). Thus, let me repeat the salutation “Happy World Backup Day 2023” and gently urge you to backup, backup, backup. Cheers!

(Free) Backup Software Worth Using

My go-to backup solution has long been Macrium Reflect Free (I also use the paid version). But its maker, Paramount Software, has announced its discontinuing that version at the end of 2023. I’m casting about for a replacement, given that something free is important for me and my fleet of 10 PCs (6 of which are loaners from Lenovo for testing purposes). I’m digging into stories like this one (and more like it) at PC World “The best free backup software and services…” and Lifewire‘s more comprehensive coverage to find a Goldilocks solution that’s “just right.” Stay tuned…

If you’ve been reading my posts lately, you’ve probably noticed that I’ve complained — just a little — recently about the Software Update Monitor (SUMo) update utility. Over the weekend, the developer himself tweeted me to let me know he’d seen my input and fixed the issue. In fact, he agreed with me that SUMo shouldn’t be recommending a preview/beta version of ANY software. Hence my assertion that the SUMO developer pays attention. He does!

If SUMo Developer Pays Attention, Then What?

He obviously read my recent (Feb 27) post entitled “Update Semantics: Current versus Preview.” And indeed, SUMo is no longer recommending an update to pre-release versions of OneDrive. As you can see in the screencap at the head of this blog post, the current version is indeed recognized as the current version now. It’s highlighted in blue, and comes up with the same version I agree is the current one. Good-oh!

But What About CPU-Z?

I thought I’d caught him out again for asserting this week that CPU-Z needed an update. The download page reports it as version 2.0.5, but SUMo wants version 2.0.5.1. And, sure enough, upon downloading and updating the latest version from the home page, it self-reports as version 2.0.5 (no fourth digit). But after updating and looking at the readme file, here’s what it says:

Sure enough, it really IS version 2.0.5.1. Says so right there!

I’ll be darned. Sometimes the toolmakers know more than the owners/developers do — or what they report, anyway. Very interesting! My thanks to @KCSoftwares: it is nice to know somebody’s paying attention.