Category Archives: Updates

Build 26058 Explorer Brings Button Labels Back

It’s a small change but a helpful one. In Canary Channel  Build 26058 Explorer brings button labels back. That is, instead of simply showing labels and forcing you to do one of these:

  • Remember what they are and what they do
  • Mouse over the label icon and read the text tip
  • Pick one and hope for the best

Explorer once again shows text to accompany the icons so users know what they’re doing. These show up at middle in the lead-in graphic, with icon buttons above and text below. To wit: Scissors button/Cut, overlaid pages/Copy, Text “A”/Rename, Block with pointer/Share, and Trashcan/Delete. Good stuff!

You can see what the old way looks like in the production Windows version (Build 22631) below where the icons appear at the bottom of the Explorer right-click context menu for files inside a folder. Much less intelligible, IMO.

Build 26058 Explorer Brings Button Labels Back.notext

Notice the line of icons at the bottom of the content menu. Mouseover will show tip text.

Rejoice When Build 26058 Explorer Brings Button Labels Back

It’s not a huge change to see text show up with a button, unprompted. But it is a comforting usability improvement. I’d always wondered why MS adopted this ultra-compact approach. But given the presence of tip text on mouseover, I’d always been able to suss things out if I wasn’t 100% what was what.

This latest improvement saves the time and effort involved in mousing over. I definitely appreciate it. On the one hand: thanks! On the other: Why’d it take so long?

And if those aren’t among the major dueling dualities here in Windows-World, I haven’t been paying attention for the past 30-plus years. Yeah, right…


PS Update Orphans PowerToys CNF

Here’s an interesting one. I’ve noticed recently that when PowerShell gets an update, the next time it launches PowerToys “Command Not Found” (CNF) drops an error message. Hence this post’s title: PS Update Orphans PowerToys CNF.

You can see how this story starts in the lead-in graphic. It shows the error message that CNF.psd1 did not load “because no valid file was found in any module directory.” Seems like an impasse, don’t it?

NOTE Added February 15: It’s the profile not the PowerShell!!! The following observations are correct — the profile and the reference to CNF are indeed mismatched — but it’s NOT PowerShell’s fault. It’s because I’m backing up my profile stuff in OneDrive and the location in the profile is incorrect. Uinstall/reinstall fixes that issue until the next time OneDrive replaces the (correct) local profile copy with the (incorrect) cloud-based one. Sigh. I’ll write about this on Monday, Feb 19, after I’ve had time to figure all the angles!

PS Update Orphans PowerToys CNF Easily Fixed

I superimposed the CNF panel from PowerToys Settings for a reason, though. Even though its status messages and detections all show green, it turns out the real problem is that PowerShell itself can’t find the CNF module.

Here’s the easy fix. Uninstall CNF (click the Uninstall button at center right). Then it changes to an Install button. Now, click that and CNF gets reinstalled. Now, the next time you open PowerShell everything is copacetic, with CNF back at work, as shown in response to my now-standard “vim” test string:

PS Update Orphans PowerToys CNF.retry

After uninstall/reinstall CNF in PowerToys, close and then re-open PowerShell. [Click image for full-size view.]

Sometimes, when certain little things get you, other little things can set them back to rights. In this particular case, that’s how I’d generally describe the path to an error-free PowerShell startup after update, with a working PowerToys CNF as well. Cheers!


Winget GPU-Z 2.57.0 Download Error

Here’s something I’ve not seen before, but immediately understood. Yesterday’s update check found a pending update for TechPowerUp’s nifty GPU-Z software. But it forced a Winget GPU-Z 2.57.0 download error upon attempted retrieval, as you can see at the bottom of the intro graphic.  I kind of like the error message “Download request status is not success.” Methinks the download link or path might be incorrect, what?

Hint: To actually *see* the bottom of the screencap, right-click the intro image and select the closest thing in your browser to “Display image in its own tab” (Firefox) or “Open image in new tab…” (Chrome or Edge) or whatever else you might find in your software of choice.

Overcoming Winget GPU-Z 2.57.0 Download Error

Although the error message is a bit convoluted, the associated HTML error code  — namely, 410 — is not. Here’s what has to say about this particular code number (bold emphasis mine):

The 410 Gone is an HTTP status code returned by the web server when the client (a browser or a web crawler) requests a resource that is no longer available at the requested address. It is one of the so-called “client errors,” meaning that the error is on the client side, not on the server.

Unlike the 404 Not Found response code that can be shown for non-existing or mistyped URLs, the 410 code indicates that the resource was in use but is no longer available and will not be available again at the requested address.

This would seem to indicate that TechPowerUp has moved or deleted the resource associated with the download link. I believe this is on them to fix, so the winget manifest can be appropriately updated. I have emailed the EIC to that effect.

A Dead Simple Workaround

When I visit the home page for GPU-Z, I can access its download link page, where I see what may be part of the problem. It points to 10 mirrors, from any one of which a download may occur (6 in USA, UK, NL, DE and SG [Singapower]). Probably, the developer who supplies manifests needs to pick one mirror and let winget use it exclusively — or write code to handle localization and pick a proximate mirror instead. Which do you think is more likely?

Winget GPU-Z 2.57.0 Download Error.mirrors

Count ’em: 10 (ten) mirrors!

Long story short: when I access any US mirror, I can download the 2.57.0 file without difficulty. Run that file (GPU-Z.2.57.0.exe) and it updates the program without problem. Solved!


DiskGenius Poses Odd Winget Issues

OK, so here’s an interesting set of issues. The otherwise usable and worthwhile free version of DiskGenius poses odd Winget issues. ICYDK, DiskGenius is a disk partitioning toolbox that also does data recovery, backup and restore and disk management. The free version offers more limited capability than its paid-for counterpart. But it definitely has issues related to its package structure inside Winget. Let me explain…

Evidence: DiskGenius Poses Odd Winget Issues

Take a look at the lead-in graphic. It’s from a PowerShell tab inside Windows Terminal. It shows the results of a winget update scan. I made it just AFTER I had forcibly uninstalled DiskGenius using Revo Uninstaller Free, then used Winget to install it afresh:

Winget install eassos.DiskGenius

As you can see, winget upgrade –all –include-unknown still wants to update DiskGenius. It wants to update to the same version that’s already installed: 5.5.1. According to the application’s Help/About info, it’s actually version x64. This makes me think there is some kind of problem with the manifest where the local installed copy of DiskGenius reports a different version than is associated with the manifest even though they’re the same. My best guess, in fact, is that the .1508 x64 at the end is getting truncated or lost.

As you can see in the next screencap, DiskGenius clearly shows 5.5.1 as its version number from the winget show output. (I split the pane to block out a bunch of extraneous details from the release notes.)

DiskGenius Poses Odd Winget

Winget Show DiskGenius shows version number, publisher, and so forth.{Click image for full-sized view.}

Because DiskGenius happily runs as a portable app without actual installation, I’ve decided to uninstall it and run it from a flash drive when I need it. That way I don’t have winget constantly nagging me for an update that I neither need nor want to read about. Problem solved.

The Other Issue…

Remember, I mentioned “odd Winget issues” (plural) in the headline? So yes, there’s something else. When I initially installed DiskGenius I chose a USB-attached NVMe drive as the target. These problems started popping up when I unplugged that drive from its original host PC and plugged it into another one for some testing. Winget still complained about the need for an update, but then failed on the update because — of course, of course — it couldn’t find what wasn’t there. Plus, we already know it woudn’t have changed the nag report anyway…

Turns out installing left sufficient traces in the registry and file system that winget could know DiskGenius was supposed to be present, but nowhere to be found. Even using the uninstall option in Settings → Apps → Installed apps didn’t get rid of all traces. I had to use Revo Uninstaller and remove all registry entries and remaining files (mostly shortcuts that pointed to the now-missing E: drive) to make this stop.

But eventually, I got it all cleaned up. And now, I’m just going to run it as a portable app from the USB-attached SSD enclosure where it now lives. And sigh loudly, because that really is the way things too often go here in Windows-World.


NVIDIA Drops New Driver Batch

As I work through the Windows news each morning, I check X (Twitter), LinkedIn, Facebook and Mastodon by way of social media. I also check in on WinAero, WindowsLatest, MSPowerUser, Ghacks, Thurott and Windows Central as well. Today, most of them told me something like NVIDIA drops new driver batch 551.23. And indeed, I found Game-ready and Studio versions for consumer grade GPUs, as well as Quadro (551.23 aka Release 550) among the pro lines. You can see the Studio version from GeForce Experience in the lead-in graphic above.

Fast facts on this latest version:
1. Target Directory: C:\ProgramData\NVIDIA Corporation\
2. Filename: 551.23-desktop-win10-win11-64bit-
3. Download size: 519KB (downloader only)
4. On-disk file size: 1.93 GB (all files downloaded & expanded)
5. Download & install time: ~3:30 (average across 5 PCs)

Why NVIDIA Drops New Driver Batch 551.23

Most often updates follow close on the heels of new games (or game features). Sometimes, they pop up to support new NVIDIA GPU offerings. It’s the latter this time, with the release of the game- and AI-ready RTX 4080 SUPER at CES on January 8, 2024 (also includes 4070 Ti SUPER and 4070 SUPER in that mix).

Heh! I’m not sure I’m ready to fork over the long green needed to buy into the latest NVIDIA generation, but it’s nice to know they’re out there when I build my next desktop. I usually buy either a 4070 or 4070 Ti model because I can’t really justify the price/performance tax that a top-of-the-line model adds to my build costs. But gamers everywhere will probably be fighting off a new case of techno-lust.

Drivers Downloaded and Updated

Amidst my modest fleet of about one dozen PCs (8 laptops and 4 desktops), there are 7 machines with NVIDIA graphics cards of one kind or another. I’ve got the updates running on all of them right now (except for the desktop my son is using away at college, so I’ll mention this to him the next time we talk). By the time you read this, they should all be updated.

If you’ve got an NVIDIA GPU in your neighborhood, now you know there’s a new update out there, too. Three cheers for the 551.23 release!


Overcoming WingetUI Hiccups

Lately, I’ve been switching between winget at the command line, and WingetUI (Martin Climent’s UI-based GitHub project). Just this morning, I observed that the CLI version didn’t see a couple of updates that WingetUI did — namely, PSGallery CredentialManager and a fresh update for the Python Interpreter (Python.Python.2). Interestingly, the source for Python does show up as “Winget.” But when I scan for updates in the CLI version it doesn’t “see” Python as out-of-date. But letting WingetUI run in the background, both updates kept failing. Thus, overcoming WingetUI hiccups took direct intervention and a bit of thought. Let me explain…

Get Busy: Overcoming WingetUI Hiccups

I’m not sure why both items failed in the background, but they did. Alas, I clobbered the error messages from WingetUI without recording them first. But when I ran WingetUI directly, the Credential-Manager upgrade went through immediately. But the Python update failed again.

Looking at the right-click options, I noticed that among its entries for individual updates, WingetUI includes a “Run as administrator” item. So I tried that next. This opened a Python update windows (which had not appeared during earlier attempts). And sure enough: it worked and the update went through.

Further Details Show Something Familiar

I couldn’t help but notice that WingetUI reported needing version 2.0.0 of CredentialManager while seeing version 2.0 already installed. I wrote about this version parsing peccadillo in my last post (Laughable Stardock Version Mixup) in connection with Start10. Here it is again, with a PowerShell Gallery element. Apparently, this happens more often than I’d noticed! This might also explain why it shows up in WingetUI and not in the CLI version: that latter runtime is incredibly careful about changing stuff when processes are running or when slight changes to the installer or runtime could occur. And indeed, Demitrius Nelon confirmed this behavior for me in an X/Twitter message last Friday, so I’m pretty sure it’s a real — if entirely trivial — thing.

As for Python, that’s a little more interesting. Looks like administrator privilege cracked some kind of access or permissions issue, and allowed the update to proceed. That’s a good “second try” technique for me to keep in my toolbox. Now that I’ve seen it work, I’m sure I’ll find occasion to use it again. Maybe you will, too!

Cheers, and welcome to a new year in Windows-World. It’s already off to an interesting start…


Laughable Stardock Version Mixup

I have to chuckle. Winget just told me to upgrade Stardock Start10 on my lone remaining physical Windows 10 PC. Why? It sees a version numbered but wants to take that package to 1.97. Of course, they are one and the same thing, and the update install fails with error code 9, as shown in the lead-in graphic. This laughable Stardock version mixup tells me there may be an issue with how version numbers get parsed and divided up inside winget’s package database.

Laughable Stardock Version Mixup: v 1.97

When I run the about screen from the version that’s actually running what you see next is what I see too. Guess what? The in-app update check confirms that 1.97 is indeed already running and the most current release. So what’s the confusion?

Laughable Stardock Version Mixup.197-already-on

Not only is 1.97 already running, in-app update says it’s current.

This is one of the little mishaps to which winget sometimes succumbs. It’s no big deal, and it’s actually kind of endearing. And it gives me something to report in to the team. Not that they’ll be short of things to do next week when the world gets back to work!

I’m guessing it will take one or two database corrections to fix this, and probably less than 5 minutes’ work. Perhaps I’ll be finding out. If I do, I’ll share here so stay tuned!


Learning About UpdateStar

With the shutdown of the SUMo database on November 1, I’ve been casting about for a new update scanner that covers my bases. I had been considering UpdateHub, UCheck and UpdateStar. Based on the number of items that each program finds, and the ease of working with them (free versions only), I’ve now pretty much settled on UpdateStar freeware (make sure you can down to the button that reads “Download” under the Free of charge heading). It’s not without its foibles, though…mostly, that learning about UpdateStar involves completely do-it-yourself updates.

Learning About UpdateStar Means DIY  Updates

Unless you want to pay US$34.95 (first year)/$19.95 (subsequent upgrades, with discounts for 3 PC packages), working with UpdateStar means it scans only for what’s out of date. It doesn’t help you find or install new stuff. It will, however, uninstall specific versions of software, which can be helpful when updates aren’t smart enough to uninstall their predecessors. That happens pretty regularly.

Most of the time searching for “update splat” where splat is the name of the program you wish to update will tell you what you need to do. It mostly works for me, anyway. And many of the odd and interesting tricks I’ve learned while working with SUMo transfer over to UpdateStar reasonably well, too.

The Current UpdateStar Situation

Right now,  on my production Windows 10 PC (it’s the with the most apps and applications installed: 113 in all) I’m getting reasonable results from the program. It shows me 9 programs in need of updates and I was able to take care of all of them. For 8 of them, that meant finding and installing the necessary updates (2 of them left old versions behind and UpdateStart uninstalled them for me quite happily). For 1 of them, I decided an uninstall was a good idea, because I have a better tool (Micosoft Update Health Check, to which I greatly prefer Brink @’s Reset_Reregister
_Windows_Update_Components.bat script).

That said, UpdateStar did produce some false positives. These were current programs that were indeed up-to-date, but for which the program incorrectly claimed newer updates were available (Revo Uninstaller and Snagit 2024). Easily checked and ignored, however.

By and large this program works pretty well. I’m still figuring things out, so will probably learn and report more over time. For the moment, I give it “one thumb up” (a positive, but not ringing, endorsement). Let’s see what happens next… I’m still on the upward slope of that learning curve!



Winget WT Update Workaround Needed

In going through update maneuvers yesterday, I observed there was a winget WT update workaround needed. That is, my attempt to upgrade Windows Terminal (WT) using winget failed. You can see what happened in the lead-in screencap. It shows that an initial attempt to install a dependency for WT — namely Microsoft.UI.Xaml — failed because a higher-numbered version is already installed. Whoa!

What Is the Winget WT Update Workaround Needed?

What to do? Fortunately, there are always multiple ways to update or upgrade in Windows-World. This time around, I went to the WT GitHub page and checked the version number on the latest release. As you can see in the next screencap, it’s the very same version that winget tried, but failed, to install as shown in the lead-in graphic.

Winget WT Update Workaround Needed.github

Funny thing: latest version matches winget’s target. That means there’s another way…

Given that GitHub has the same version, there should be some kind of Windows installer amidst its list of downloads. When I see it’s named Microsoft.WindowsTerminal…msixbundle, realize it’s targeting a Store version of WT. So off I go to check updates in the Store first. Nothing there, so I download and install the afore-mentioned msixbundle file. It works, as you can see in the About info from WT on that PC.

Winget WT Update Workaround Needed.about

Click the down-caret in the title bar in WT, then select “About” in the drop-down menu. Here ’tis!

As shown, the manual update using the msixbundle file did the trick. I could have waited, and the Store would have (eventually) handled the update automatically. But if I could have waited, I probably wouldn’t be the rabid Windows Insider I’ve always been, since day 2 of that program’s launch. LOL!

Feedback Followup…

I’m pretty sure winget should be smart enough to keep going if it finds a higher-numbered version of a dependency already in place on a target update PC. I’m going to share this blog post with the nice folks on the winget team. I bet they’ll fix this muy pronto! TIA, people…

Just Checked In … And It’s Fixed

I sent feedback to the team yesterday and got a reply that the dependency check should be a “min version check.” That is check to see that version is “greater than or equal to” versus “equal to.” And indeed, it now seems to be fixed. Thanks, guys: hope you all have a marvelous holiday break.


SUMo Is Turned Off

I have to laugh, so I don’t cry. Despite rumors that its developer, Kyle Katarn, might republish his dandy Software Update Monitor (S U Mo) utility as Open Source code, the supporting servers shut down on November first. Notice the company slogan for KC Softwares (Katarn’s company, and the program’s maker) reads: “We are here to stay.” Now that SUMo is turned off, there’s some irony there, eh?

When SUMO Is Turned Off, Then What?

I had a general inkling that things might go sideways on November 1. Why? Because the website reads:

KC Softwares activities are to be terminated by end of October 2023.
All products are to be considered as End-Of-Life (EOL) on October 31st 2023.

And indeed, when I tried to run the program on November 1, I got an error message as it tried to scan its database for the first item in its inventory (7-Zip, by virtue of its position at the top of the alph sorting order).

SUMo Is Turned Off.server-error

Trying again later is not going to help. The server is off.

Other, Less Palatable Alternatives

LifeWire has a September 11, 2023 story “11 Best Free Software Updater Programs.” At this point, I’ve tried them all. I’m a big fan of Patch My PC, but it doesn’t cover enough of my installed software base to do the job on its own. And so far, none of the others have really captured my fancy or regard.

Why is that? Most of the free versions have paid-for counterparts. And most of them also qualify as “teaseware” — that is, they tell you about things they could do for you if you purchased the paid-for version. For now, I’m getting by with winget (and WingetUI), Patch My PC, and a bit of elbow grease. Hopefully, a real contender will emerge (and sooner is better than later).

Stay tuned! I’ll keep you posted. But don’t hold your breath, either. This could — and probably will — take a while…