Category Archives: Updates

Updating Intel Processor ID Utility

Hmmmm. Here’s an interesting one. SUMo just told me that the Intel Processor Identification Utility (Legacy Model) needs an update. Poking around on the Intel site, I found a download page that covers Intel processors by generation: the new one goes Gen 12 and up; the old one Gen 11 and down. The old one appears beneath the new in the lead-in graphic, so it’s the one I downloaded and installed. That got me through Updating Intel Processor ID Utility on my i7 Skylake.

Why Bother Updating Intel Processor ID Utility?

The latest version of the new utility is 5/22/2023. The legacy one that works for my i7 Skylake shows a date of 5/17/2023 on the General Properties tab for the ProcID.exe file. That means it’s the latest and greatest of such files. I’m not aware of any security or other issues that the new version fixes. I’m just in the habit of updating as new versions come out. It runs just fine on the production PC. Here, for example, is the “CPU Technologies” info from that tool:

Updating Intel Processor ID Utility.CPU-tech

CPU Technologies show instructions, virtualization, sleep and other state info support (or not).

Intel Always Makes Updates Interesting

I feel lucky this morning that the landing page for Processor ID Utility took me to the update I needed. Sometimes, they don’t make it totally easy or simple to find the latest versions. Indeed, searching on version number ( didn’t work all that well for me. But this tool has an “Update” button subordinate to its Help menu. Now that I know this is an option, I bet it will work immediately next time around. That’s what makes updates interesting in general (and Intel in particular): there’s almost always a way to get a boost from the developer, if you know where and how to look for same. Sigh.


Winget Just Keeps Chugging Along

I’ve started a new writing and editing gig with I’m contributing 3-4 articles a month on Windows 10 and 11 topics, and providing input and feedback on their overall desktop OS coverage. Just recently, I started a series of stories for them on the Winget package manager for Windows. I’ve been using it daily for about a year now, and  I have to observe that Winget just keeps chugging along — and getting better all the time.

What Winget Just Keeps Chugging Along Means

Take a look at this morning’s results on my Windows 10 production PC (see lead-in graphic above). It just updated VS Enterprise 2022, TeamViewer, and Chrome, in under 2 minutes with only minimal effort from yours truly. I seldom encounter winget issues — and when I do, they’re nearly always easily resolved.

What continually suprises me is that using winget for updates is often faster than the in-app (or in-application) update facility itself. Visual Studio 2022 made an interesting case in point just now, when it updated that hefty environment (nearly 400 MB to start it going, and over 150 packages as the process worked to completion). It finished in well under 2 minutes on this aging desktop PC (i7 SkyLake, 32 GB RAM, 500 GB Gen 2 PCIe SSD).

Where Winget Falls Short Is Not Its Problem

I do still use other tools to keep my apps and applications updated. But that’s not winget’s fault. As I discuss in my March 17 post here, winget relies on developers to provide package manifests for their software so that it can do its install/update/query/uninstall things.

The list of items for which I have to use other tools includes some apps or applications that seldom get packages (Kindle, Zoom, Box, Dropbox, and others) or that have none (AFAICT). I encourage all developers who don’t already update winget manifests as they push updates to get in that habit.  (See this MS Learn item “Create your package manifest” to dig into that semi-automated YAML and PowerShell-based process.) It will make everybody’s lives easier in the Windows admin world — including mine! ‘Nuff said…


Pet Peeve: Upgrade Walls Around Free Versions

I was checking upgrades over the weekend (part of my daily routine, in fact). I found myself having to search for a specific version of a favorite app. Why? Because the developer erected upgrade walls around free versions of the app. It’s just a “little reminder,” I guess, that users should support developers by paying for what they use.

Why Put Upgrade Walls Around Free Versions?

Basically, the developer steered its “manual update” capability into the purchase dialog for the same program’s for-a-fee version. I have the paid-for version on my production PC, in fact. But I don’t pay for the instances I run on my test PCs (which vastly outnumber my home desktop and traveling “work laptop” — by 5 to 1). It just ticks me off when the developer leads users down a road with no obvious access to downloading the free version through the application’s own built-in update facility. Am I wrong to feel that way?

I don’t think so. But in this case, I had to remember that the name of the free version includes “lite” in its name (cute). Then, I had to Google the name of the application with that string in its name to get to the right download page. Not too challenging, but at least mildly vexatious, IMO.

The Pecuniary Imperative

Sure, developers need income to justify their time and effort spent in creating and maintaining their offerings. But do users need to be reminded that they could pay for the for-a-fee version each time they update (or upgrade) its free counterpart? Depends on who you ask: some developers obviously feel that the answer to that question is “Hell, yeah!” As for me, I just find it somewhat annoying.

Sigh. That’s just the way things go in Windows-World sometimes. Thanks for letting me vent…


Intel DSA Version Confusion

OK then, I’m back in the office after a 10-day hiatus. Natch, after meeting today’s writing deadlines, I started updating all 11 of my Windows PCs. Along the way, I found myself caught up in Intel DSA version confusion for that company’s Driver & Support Assistant software.

Look at the lead-in screencap. The Intel download page shows version is the latest and greatest version. Yet the details for the download file show it as version And indeed, when you install or repair DSA using the file the lower-numbered version is what’s installed. Go figure!

Overcoming Intel DSA Version Confusion

After handling over 100 updates, the Patch Tuesday and incidental WU stuff, I didn’t want to find myself troubleshooting a bogus update problem. But that’s what I’ve got going on. Until Intel puts the update for version in the “Latest” position on its download center, there’s not much I can do to fix this.

C’mon Intel: please fix this issue so OCD updaters — like yours truly — can get caught up. I’ve already got (the version that actually appears in the Properties window for the download) installed. I can’t catch up until the right file gets posted to the download center.

It’s Always Something, Right?

Just goes to show you that here in Windows-World there’s always some kind of gotcha lurking to make life more interesting. In some cases, my issues are of my own making. In this particular case, it looks like something odd is up with the Intel download page itself.

Just for grins, I went to an alternate download source. Much to my surprise, that installer shows the correct version number for this file, to wit:

Intel DSA Version Confusion.alt-source

An “alternate download source” DOES have the right file.
Go figure again!

I wish I knew how the other source got the right file, when I couldn’t grab it myself directly. As Mr. Churchill said of Russia, that makes this “a riddle, wrapped in a mystery, inside an enigma.” I don’t know whether to laugh, or cry.


Winget Discord Update Trick

I’ve got a new PC waiting in the wings to take over for my aging production PC. Right now, it’s ensconced in my son’s bedroom, where I use it as a test machine. He also games on it when he comes around. As a Discord user, he checks in on that app daily when he’s here. One of his tools pinned that app, so Winget can’t upgrade it through normal means (e.g. Winget upgrade –all or some equivalent). But I’ve discovered a Winget Discord update trick that works nonetheless.

Pinning Requires Winget Discord Update Trick

For some time now (as described in this July 2020 GitHub thread) users and programs can “pin” packages for Winget. This explicitly holds Discord to some specific version (or range of version numbers). It also means that unless Winget upgrade is targeted with a specific Discord version, it doesn’t perform the upgrade.

The trick to a successful upgrade is to use the –version parameter with Winget upgrade to explicitly specify the upgrade target. For example, I successfully upgraded the upstairs PC with this command:

winget upgrade Discord.Discord –version 1.0.9012

Note: I had to use the “full package name” for the Discord app (“Discord.Discord”). I also had to provide the complete version number (1.0.9012) following the –version parameter. After jumping through those hoops, the pinned version allowed the update. One presumes that the same approach will work for other pinned apps and applications with Winget as well.

It may take some squinting, but you can see Discord’s version info in the lead-in graphic at the far right. It reads “Host 1.0.9012 (30921).” To the left is a Terminal window that shows a successful targeted upgrade (update, actually) of the Discord app itself. It’s easy — if you know how. Those are the deets! And now, it’s all good…


The Never-ending Windows Update Story Carries On

Back on March 6, I posted an item about Windows Application Update Rhythms. This offered a snapshot for a week’s update activities across my various PCs. Since then, of course, the updates have continued as the never-ending Windows Update story carries on. I’ve made some interesting observations since then, too.

The lead-in graphic above shows one such data point. I’ve begun to notice that sometimes Winget will update Chrome, and sometimes it won’t. It seems to be related to whether or not the app is open at the moment (yes if closed; no if open).

Never-ending Windows Update Story Keeps Going…

The same thing appears to be true for PowerShell as well, as you can see in this next screencap. Amusingly, the app itself is PowerShell so indeed it’s obviously running too. But there are ways to force a PS upgrade within the app, so this default behavior can be over-ridden. The second post in this SuperUser thread explains how to do just that. It grabs and uses the PS install MSI from GitHub to make that happen.

Never-ending Windows Update Story.update-PS

Winget updates neither Chrome nor PowerShell here.

What’s Behind the Apparent No-Upgrade Behavior?

In various discussions online as to what’s at work here, I learned (or re-learned) a few things. When installer formats change (MSIX to MSI, MSI to EXE, and so forth) Winget won’t perform the update. Indeed, I’ve seen explicit messages to this effect in Winget output from time to time. This thread explains how to grab, then use, the download URL for the Chrome installer to bypass the failed (and silent, error-message-wise) Winget update. Likewise interesting!

The more I work with Winget, the more I learn about its various hiccups and gotchas. But the tool continues to impress because there’s nearly always a clever workaround to get things done. It’s definitely made the various installments of the never-ending Windows Update story around Chez Tittel shorter and more entertaining. What more could a Windows-head like me want?


Winget Suffers Blanche DuBois Effect

There’s a famous line in Tennessee Williams well-known play, A Streetcar Named Desire. It comes from trashy, tragic Blanche DuBois. It reads “I have always depended on the kindness of strangers.” I hope I’m not over-reaching in finding a connection between Blanche and Microsoft’s built-in package manager Winget. Why do I say that Winget suffers Blanche DuBois effect? Because third-party developers must provide package definitions so Winget can handle their updates. Some do, some don’t is my experience on this front.

Overcoming Winget Suffers Blanche DuBois Effect

I turn to other tools to help me catch what happens when the “Blanche DuBois Effect” fails — namely, when a developer or owner does not supply Winget with the necessary package definitions. You can see what I mean by this in the figure below. (Click on it to expand to full-sized view to read what it says for yourself.)

Note that Winget sees 4 items in need of update; SUMo sees 7 or 8.

For the record, Winget sees about half of what KC Software’s Software Update Monitor (aka SUMo) does, to wit:

Tool Count List of items
Winget 4 VSEnt22, SUMo, TeamViewer, Jabra Direct
SUMo 8 Firefox, CPU-Z, Jabra Direct, Edge, Snagit, TeamViewer, WizTree (2)


For accuracy, Winget sees one thing that SUMo does not — namely, Visual Studio Enterprise 2022 (abbreviated as VSEnt22 above). OTOH, SUMo sees 5 (or 6) things that Winget does not — specifically, Firefox, CPU-Z (a false positive, in fact), MS Edge, Snagit, and WizTree (in both 64- and 32-bit versions). That’s why I use other application update tools to help me keep up on the ten-plus PCs in residence here at Chez Tittel.

Winget Supplements of Choice Are…

My tools of choice to cover what Winget misses are:

1. Software Update Monitor (aka SUMo) from KC Softwares
2. PatchMyPC from

Why two? Because PatchMyPC sees fewer things than SUMo does. But what the freeware version of PatchMyPC sees, it also updates automatically and easily. The free version of SUMo sees more, but only the paid version tries to update those things for you (and its track record is far enough from stellar on performing updates that I’m not sure it’s worth the US$25-30 you’ll be asked to pay for it).

I’ve learned to use SUMo solely for detection, then I let PatchMyPC handle for me what it can. I do the rest myself manually.

Frankly, though, I think MS should put some of its much-vaunted AI capability to work so that Winget can generate packages for third-party applications on its own with no need to, as Blanch DuBois once did, rely on the kindness of strangers.


Installer Borks PowerPanel Program

Here’s an interesting one from the trenches. In working my way though today’s round of software updates, I found myself unable to get info from the CyberPower CP1500D uninterruptible power supply. It protects my primary production PC, so that’s a concern. I did some online research into the far-from-transparent error message “PowerPanel Personal Service is not ready.” I learned I was dealing with a documented bug. Turns out a rogue installer borks PowerPanel program . That said, it’s easily fixed. Let me explain…

When Installer Borks PowerPanel Program, Then What?

A search on the error string “PowerPanel Personal Service is not ready” took me to Woody Leonhard’s (in)famous AskWoody website. I learned that it wasn’t the installer that broke the service connection to the UPS, but the immediate reboot that it advised upon completion. Go figure!

But the recommended fix worked like a charm. Basically, it’s a remove-and-replace operation. That is, uninstall the CyberPower utility, remove all traces, then reinstall. Upon completion, don’t reboot immediately. Everything works!

Revo Uninstaller Recommended

The advice from AskWoody MVP “bbearren” recommends using Revo Uninstaller (the free version is fine: it’s what I used). It offers clean-up after it runs the program’s own installer and gets rid of leftover files and registry entries. (I used the middle “Moderate” clean-up setting.)

Then, I reinstalled the latest version of the CyberPower PowerPanel Personal software (2.4.8) from the download I’d already made for the update. It chunked through to a happy completion, after which I did NOT reboot my PC despite the installer’s recommendation. You can see the working results in the lead-in graphic for this story.

Problem solved! It’s nice when they go down easy and quick. That actually happens sometimes, some days here in Windows-World.


2023 Gets Underway For Real

OK, then. The family is back from our later-than-usual winter vacation. On Saturday we returned from San Diego. This morning, son Gregory hopped another silver bird to return to school in Boston. So now, I’m catching up my modest PC fleet as 2023 gets underway for real here at Chez Tittel. As usual, there are numerous interesting items to report.

Once 2023 Gets Underway for Real, Then What?

First things first: I’m checking and updating all the Windows PCs around here. Here’s what things are looking like by some numbers — namely Winget updates and SUMo items:

PC Name         Winget     SUMo Items
i7Skylake          4           6
Surface (Pro 3)    1           3
X380Test           6           3
X380              12           9
P16 (Mobile WS)    1           4
X12 Hybrid Tablet  3           3
X1 Extreme         2           9
Yoga 7i            5           9
D7080 (wife PC)    1           4
AMD5800X           6           8

Of course, the time these various systems spent untended before the break affects the number of updates they need. It’s no exaggeration to observe that those with more updates in both columns (Winget and SUMo) had been idle longer than those with fewer (especially X380 and the AMD box).

Total time required to get everything caught up (except for the Lenovo P360 Ultra, which is still in the closet upstairs) was just under 3 hours. I learned a few interesting things along the way, too.

Update Lessons Learned

Zoom won’t auto-upgrade to the latest version in one jump. I had to upgrade several systems twice, to work through the sequence of updates since they were last accessed. Sigh.

I did finally find the new versions of Asrock App Shop, RGB Sync, and Restart to UEFI. I haven’t tried them on my Z170 mobo yet, but am curious to see if old and new are still close enough to work. And indeed, the new B550 targeted software still works on the old Z170 motherboard. Go figure…

For some odd reason, SUMo wants users to upgrade to beta versions of Firefox and SpaceDesk. I’m NOT going there, because I want my production PCs to run production software. If you make use of this otherwise excellent tool, be sure to check the provenance of recommended updates (like those two) before blindly following along.

2023, here I come. Stay tuned…


Winget Upgrade Include Unknown Gets Ilustrated

Here’s an interesting tidbit. I checked for upgrades this morning on my production PC. Winget informed me “1 package has a version number that cannot be determined.” It recommends using the “–include-unknown” parameter. And presto! Winget Upgrade include unknown gets illustrated nicely in forthcoming results. See the lead-in graphic…

When Winget Upgrade Include Unknown Gets Ilustrated…

An abstract explanation that Winget may not recognize an update’s version is one thing. But the example in the preceding graphic is clear and unmistakable. First, Winget finds no installable packages. It recommends using –include-known. Once used, an upgrade is found — and installed — without difficulty. How clear is that?

I’ve been using Winget daily on most of my PCs for more than six months now. Along the way, I’ve learned a lot about how (and when) it works best. Winget is now essential for my maintenance regimen. The foregoing illustration explains nicely why using –include-unknown is customary. It’s a peach!

Winget Upgrade Include Unknown Gets Ilustrated.SUMo

SUMo sees things that need updates (applications mostly, but also some apps) that Winget does not.

Where Winget Comes Up Short

Please examine the preceding screencap. It shows 4 updates and upgrades that Winget misses. That same shot also shows why I still use KC Softwares’ Software Update Monitor (SUMo, depicted).

Indeed I also use PatchMyPC updater as well. That’s mostly because while it doesn’t catch everything that SUMo does, what it does catch it also updates automatically. SUMo only does that if you use the for-a-fee version (and even then, it doesn’t always do it automatically, either). Sigh.

In addition to the items shown, other things occasionally pop up that Winget misses. Other browsers (e.g. Chrome) may appear, as do some apps/applications, including Kindle, Nitro Pro, and more. I’ve learned how to handle all of them by now — or not, as is sometimes a good idea. For example: I’ve never been able to find the version of ASRock APP Shop ( that SUMo claims is current. There are a few other such “false positives” but nothing too major. Please read my December 28 item “Windows 10 OCD Update Stymied” for further ruminations on this topic.

‘Nuff said, for now!