Winerror versus Err: Enough, or Too Much?

Here’s an interesting dilemma. In the past, I’ve advocated use of the Windows Error Lookup Tool, currently Err_6.4.5.exe The other day, I had cause to rue my recommendation. I actually found a different, more focused tool named Winerror.exe. It’s part of the Windows Assessment and Deployment Kit, aka Windows ADK. But then, you might also need to grab the older Windows 10 version to get the tool I’m about to discuss. It seems to be missing in the Windows 11 version.

Winerror versus Err: Focused and General

You can see the issue in the lead-in graphic for this article. Notice that winerror provides two different expansions, one of which mentions normalization. Err_6.4.5, OTOH, provides 6. These come from a variety of error code source files: bugcodes.h, netmon.h, winerror.h, and ntstatus.h.

In simpler terms, winerror looks only at winerror.h; err… looks at a bunch of error code source files, including winerror.h. My point is that winerror may be worth consulting when you’re troubleshooting Windows 10 or 11. That goes double when the error reporting tool (err_6.4.5.exe) produces more output than you know how — or really want — to use.

Wm Blake Still Has a Point

The end half of the title for this story comes from William Blake’s Proverbs of Heaven and Hell. It makes the excellent point that you really don’t know you have enough until you have more than you need. That’s why I recommend using the older, but less general, Winerror.exe when you find that the latest error reporting tool (err_6.4.5.exe) has more to say than you really need to know.

‘Nuff said!

Facebooklinkedin
Facebooklinkedin

Windows 10 versus Windows 11 Uptake

I just read a fascinating story from the man himself — Paul Thurrott, that is — over at his website. Entitled “Windows 11 Usage Share Is Struggling…” it raises some interesting questions. Chief among these is “When deciding Windows 10 versus Windows 11, what do business users get?”

Thurrott’s analyses lead him to this conclusion: “Not enough to justify migration.” If necessary, add “…if hardware refresh is required” to that statement. FWIW, I agree. However, I’m not as inclined to finger-point at MS for market manipulation as he is. Let me explain…

Windows 10  versus Windows 11 Is a No-Op

Looking back at typical business migrations as far back as I can remember (the Windows 3.x era, circa 1991), I see a consistent pattern. It explains why business uptake of Windows 11 remains somewhat scant.

Here ’tis: It usually takes 2-3 years for businesses to get serious about migrating Windows versions. And then, that’s only if  the version of Windows is judged “successful” (not Windows Me, Vista, or 8/8.1, for example). Right now, it’s been just over a year since Windows 11 released: October 4 was the anniversary date. Thus, it’s simply too soon for most migrations just yet.

Thurrott and readers make at least two valid points

(a) for a good portion of the installed PC base, Windows 11 won’t run (40-50% by most estimates, in fact)
(b) most businesses manage their own refresh cycle timing, and aren’t inclined to let MS dictate when that should happen.

All this said, I don’t think even MS can derail all of the prior migration history it already knows about, points (a) and (b) notwithstanding. My gut feel is that something else is up beyond seeking ways to force business users forward faster.

Windows 10 EOL Remains Unchanged

October 14, 2025 is now about three years distant. This acts as a full-stop for most business. They don’t ordinarily want to pay for extended support  unless stuck between rock and hard place. (Example: US DoD for Windows XP and 7, on the way to Windows 7 and 10, respectively.)

Various sources put the PC refresh interval in business globally between 4 and 10 years, with the most common recurring value at 5 years. Depending on where organizations are in that cycle, I guess at least 80 of businesses would refresh anyway before Windows 10 hits EOL.  CPUs and TPMs in use in early 2018 define the boundary between what’s in and what’s outside of Windows 11 requirements. That puts the maximum interval for refresh at about 7 years and 9 months (7.75 years). IMO, that’s longer than normal for most concerns.

New PCs purchased since 2019/2020 will meet Windows 11 requirements as a matter of course. Thus it’s really PC’s purchased before January 2018 (or older models purchased through 2020, no doubt to obtain steep discounts) that really come into play.

My best guess is that, as with prior major versions of Windows (3.1, 95, 2000, XP, 7, and 10 — see the pattern?), 11 migrations will get serious in late 2023 and throughout 2024. That’s just in time to stay ahead of EOL for Windows 10. It’s also in tune with most prior migration cycles. Need I say more? I think not…

 

 

Facebooklinkedin
Facebooklinkedin

Further Kindle Update Follies

Yesterday I worked through my blog post from earlier in the week on yet another PC. As it happens, the initial step — using winget to uninstall the outdated Kindle version — was highly fortuitous. Even though the subsequent winget install Amazon.Kindle brought in the wrong version (because of the package definition), removing the old version is a good way to start the upgrade process. In my further Kindle Update follies follow-up, not uninstalling left the old version behind alongside the new. Wait! It gets even more interesting…

What Happened with Further Kindle Update Follies?

When I found I had two side-by-side versions, I ran Revo Uninstall to try to take out the old one. That left me with no Kindle at all (even though I didn’t do the post uninstall cleanup that Revo does itself). So, I got to install the correct version again. That worked!

Here’s my new recipe for manual Kindle updates.

  1. Grab the latest version from the Kindle download page.
  2. Run winget uninstall Amazon.Kindle in an admin PowerShell (or Windows Terminal) session
  3. Run the downloaded Kindle installer (as I write this, that filename is KindleForPC-installer-1.39.65323.exe, but that will change)

One more thing: before you follow this recipe, try opening the Kindle app. Sometimes — and I stress this word, “sometimes” — it will actually update itself as part of its launch process. Because I haven’t been able to figure out why it works sometimes and not others, the recipe serves as a follow-up should it not auto-update itself.

This is kind of whacko. I repeat an earlier plea to the Amazon developers: please add an update function to the Kindle for PC software. Or, have the installer clean up the old version after it brings in the new one. It’s just too tricky to find and manage updates for ordinary users right now. IMO, that definitely needs fixing …

Note Added November 7

I’ve been working through updates on a bunch of PCs today. Many (most) have needed a Kindle update. I can now conclusively confirm that my foregoing recipe works to update Kindle without apparent issues. Consider it a validation, of sorts…

Facebooklinkedin
Facebooklinkedin

2023 Windows Insider MVP Application

Well, then. The deadline for the 2023 Windows Insider MVP application is in two days (November 4). I just uploaded mine a few minutes ago. I’m nearing the completion of my first 5 years with the program — I was first admitted in 2018 — and hoping to keep it going for at least that long again. As I filled out the application, I perforce took a look at my Windows related activities over the past 12 months. I’d like to report on same to my readers here as well.

2023 Windows Insider MVP Application Highlights

Here’s an abbreviated, bulleted list of what I reported to the Windows Insider Team in making my 2023 application:

  • 217 posts in the period from November 1, 2021 to October 31, 2022 right here to EdTittel.com
  • 27 Windows-related articles for ComputerWorld (including revisions)
  • Over a dozen Windows-related articles for each of Tom’s Hardware and TechTarget
  • Over 500 posts to TenForums.com and over 200 posts to ElevenForum.com
  • Regular social media presence for Windows work on Twitter, LinkedIn and Facebook

It’s not much different from what I’d been doing for the preceding 4 years, but it’s always fun and interesting to see how much happens over the course of a year.

What Comes Next?

It takes a while for the Windows team to handle all the incoming applications, including renewal apps from the 100-plus people who already belong to this program. You can check out that list under the “Get to know Windows Insider MVPs” heading on the program’s home page. Here’s what my listing there looks like:

2023 Windows Insider MVP Application.listing

Hmmm. Looks like I need to update my profile mention of Windows 11, too. [Click image for full-sized view.]

Indeed, Windows 11 certainly took a lot of my time over the past 12-18 months (it made its preview debut on June 28, 2021: I got in the second day of release). I can’t wait to see what happens next, and to learn how to install, use, tweak and troubleshoot same.

Wish me luck: I’m hoping for another 5 years of WIMVP status, if not more. As soon as they let me know if I’m in or out for 2023, I’ll report here. Fingers crossed, in the meantime.

Facebooklinkedin
Facebooklinkedin

Winget Remove/Replace Handles Kindle Directly

I don’t know why this is, but I have the devil’s own time following Amazon’s instructions to download a fresh — and current  — Kindle version. You place and complete a zero-cost order and you’re supposed to be able to click a link in the order record to do the download. Not happening for me! I decided to contact Amazon tech support to confirm that’s how it’s supposed to work. It is, indeed. Interestingly they could or would not provide a direct download link. Next, Winget remove/replace upgrades Kindle directly, if incorrectly. Let me explain…

What Winget Remove/Replace Upgrades Kindle Directly Means

I learned the term remove/replace back in the days when I still did my own car repairs. It basically describes what’s involved in fixing a broken car part. First, you remove the non-working part. Then you replace it with a new, working one. Fixed (unless calibration is also needed)!

In this case, it means uninstall the old, outdated version of a program. Then install the new, up-to-date version in its place. This technique works when other update methods fail. I’ve used it successfully with the Zoom app, for example, when its maker quit offering in-app update facilities on the free version.

With Kindle, it half-way works for me when the Kindle app download service fails to deliver me a new version as it’s supposed to. If you look at the lead-in screencap, you see first the command

winget uninstall Amazon.Kindle

That’s the “remove” part of the sequence. Next, comes the “replace” part:

winget install Amazon.Kindle

Behind the scenes, this uninstalled version 1.39.0.65306, and replaced (installed) version 1.33.0.62002, which is neither current nor up-to-date. Notice the newly-installed version number is lower (and hence, older) than the one it replaces. Shoot, what now?

SUMo to the Rescue

I’ve got a paid-for version of the Software Update Monitor (SUMo) from KCSoftwares. When I checked the update status for Kindle there, it pointed me to a direct download link at Amazon (which their tech support folks were unwilling or unable to furnish). That link is Get started with the free Kindle app. For whatever reason, search engines don’t find this (it’s probably blocked). Using this link, however, you can indeed grab the latest Kindle version and put the remove/replace operation to work.

Why didn’t winget grab this version? The existing package definition for Kindle install is obviously pointing at the wrong download. That’s why you can’t always count on winget to get things right, though it does so most of the time. That’s also why I use multiple update scanners (including PatchMyPC) to help me keep my small PC fleet up-to-date.

Shame on you, Amazon, for not making a direct download link available. And shame again, for not equipping your tech support staff with the direct download link that SUMo provides. Sigh. At least, I got there eventually, if not by the most direct route.

Facebooklinkedin
Facebooklinkedin

Using Winget For 4 Ways To Update

I’ve been researching an upcoming ComputerWorld story about the terrific and powerful PowerShell based Windows packager: Winget. It’s a peach! I mostly use it for keeping applications and supporting elements current. Lately,  I’m  using Winget for 4 ways to update my apps. Let me explain…

How-to: Using Winget for 4 Ways to Update

Way 1: Check Pending /Available Upgrades

By itself, the command winget upgrade simply shows what’s ready to upgrade. It doesn’t actually do any upgrades. Thus, it offers a quick easy way to see what upgrades are available. That’s why it appears as the lead-in graphic for this story.

Ways 2 & 3: Perform Blanket Upgrades

In fact, two different command strings provide varying degrees of upgrade capability

  1. winget upgrade –all
  2. winget upgrade –all –include-unknown

By default winget only upgrades to a new version when it recognizes the current version. Then, if the current installed version is lower-numbered than the pending one, the upgrade goes ahead. Some-times, for whatever reason, winget can’t find the current running version into. In such cases, the upgrade –all variant skips them. Thankfully, adding –include-unknown to the string tells winget to upgrade those anyway. Consequently, I use that more inclusive variant because there’s less follow-up needed.

To illustrate, the next screencap shows winget upgrade –all –include-unknown output on the PC that produced the lead-in snap. Notice please: 5 items found, 5 items upgraded. Good-oh!

The –all –include-unknown variant of winget upgrade covers the most possibilities. On this PC, all 5 candidates upgrade.
[Click image for full-sized view.]

Way 4: Targeted Winget Upgrades

Examined closely, both preceding screencaps shows an ID column. Indeed, that information provides a “package name” for its associated application. Thus, you can always upgrade a single package at time using this syntax:

winget upgrade <package-name>

For example, names shown in the screencaps include Mozilla.Firefox, TeamViewer.Teamviewer, AntibodySoftware.Wiztree, Google.Chrome and Microsoft.WindowsSDK. That follows a mostly predictable structure: builder-name.package-name. For speed, I like to use it when winget presents only a single option, or when a winget blanket command fails.  I’m learning that happens sometimes, for various odd reasons.

There are many ways to work with winget I haven’t yet mentioned. These could appear in future posts here. Certainly, they’ll definitely be covered in my upcoming ComputerWorld piece. Right now, that’s scheduled to appear online before month’s end. Hopefully, you’ll get a chance to catch that during the busy holiday season.

 

Facebooklinkedin
Facebooklinkedin

KB5018482 Announces Impending 21H2 End

OK, I’ll admit it. I wasn’t expecting much excitement upon downloading and installing KB4018482 yesterday. Sure, it raised the Build level to 19045.2193 on my production desktop. And it brought various modest updates and fixes. What I wasn’t expecting, upon reading its Support blurb, was to see that KB5018482 announces impending 21H2 end of service.

Here’s that it says, reproduced verbatim (dated October 11, two weeks prior to the KB pub date [black, bold emphasis mine]):

IMPORTANT All editions of Windows 10, version 21H1 will reach end of service on December 13, 2022. After December 13, 2022, these devices will not receive monthly security and quality updates. These updates contain protections from the latest security threats. To continue receiving security and quality updates, we recommend that you update to the latest version of Windows.

You could say it kind of jumped out at me as I read the notice. It’s not exactly a surprise — this date’s been known for a long while — but it’s pretty final, and it’s now just over 6.5 weeks away (46 days, as I write this).

Why KB5018482 Announces Impending 21H2 End Counts

Lots of business Windows users run Windows 10 — the vast majority, in fact (e.g. Statcounter says 71.87% of all desktops). I suspect that more than half that population is still running one 21H2 build or another. For those users, this announcement is a wake-up call that it’s time to make some kind of change before time runs out in mid-December.

Business users have two options to stay on Windows 10 — namely:

  • upgrade to 22H2 (this can use any valid Windows upgrade technique, including WSUS, WU, deployment tools, and in-place upgrade)
  • switchover to  LTSC 2021 (works only via ISO and in-place upgrade)

Either way, planning, testing, scheduling and deployment will be necessary. And six weeks (plus 4 days right now) ain’t much time. The clock, as they say, is ticking…

Postscript: So Long, NetMarketShare!

In writing this item, I got a another surprise. And it, too, touches on end of life. For a long, long time NetMarketShare has been my go-to source for Windows OS market share data. Apparently, that’s over now too. Here’s partial text from the Windows OS landing page:

IMPORTANT NOTICE:
After 14 years of service and being used as a primary source in tens of thousands of articles and publications, we are retiring NetMarketShare in its current form. October, 2020 is the last month of data. All billing for existing accounts has been stopped. All outstanding balances are being refunded.

Why? An upcoming change in browsers (https://github.com/WICG/ua-client-hints) will break our device detection technology and will cause inaccuracies for a long period of time.

In addition, we have focused on bot detection and removal as a key part of the quality control process. It is the most complex part of our codebase. As time has gone on, it has become increasingly difficult to manage this process. So, instead of accepting increasing levels of inaccuracy, we thought it would be a good time to call it a day.

Too bad. I’ll be sorry to do without their information and the insights it provided. Auld ang syne, and all that…

Facebooklinkedin
Facebooklinkedin

USB4 Delivers Consistent NVMe Performance

OK, then. I finally laid hands on my second USB4 NVMe SSD enclosure yesterday. I deliberately sought out the cheapest one I could find so I could compare it to a more expensive alternative already on hand. When I say that USB4 delivers consistent NVMe performance here’s what that means:

1. The same SSD, cable, and host PC are used for comparison. Both drives have the “cache tweak” applied (this Oct 14 post has deets). Same tests performed, too (CrystalDiskMark and a Macrium Reflect backup).
2. The only thing that changes is the enclosure itself.

In short, I wanted to see if spending more on hardware returned a noticeable performance advantage (I’ll talk more about this below). Long story short: it doesn’t seem to make much, if any, difference. Let me explain…

Why Say: USB4 Delivers Consistent NVMe Performance?

The lead-in graphic shows the results from the cheap enclosure on the left, and the more expensive one on the right. The average difference in CrystalDiskMark performance shows 2 wins for el cheapo, 5 wins for the higher priced item, and 1 tie. On first blush, that gives the more expensive device an advantage. So the next question is: how much advantage?

This is where a little delta analysis can help. I calculate that the average performance difference between devices varies from a high of 6.2% to a low of 0.03% (not including the tie). That said, the average performance difference across all cells is merely 1.54%. (Calculated by taking absolute value for each delta, then dividing by the number of cells.) That’s not much difference, especially given the prices of the two devices: $128.82 and $140.71. That delta is 8.4% (~5.5 times the average performance delta).

I will also argue that comparing CystalDiskMark results is interesting, but not much of a real-world metric. Thus, I’ll compare completion times for a Macrium Reflect image backup on the same PC, same OS image. The expensive device took 2:25, the cheap one 2:44. That’s an 11.5% difference, greater than the price delta but not amazingly so.

Deciding What’s Worthwhile

I can actually see some differences between the two enclosures I bought. One thing to ponder is that NVMe drives tend to heat up when run full out for any length of time (as when handling large data sets, making backups, and so forth). I’ve seen temps (as reported in CrystalDiskInfo, reading SMART data) go as high as 60° C while M.2 SSDs are busy in these enclosures. At idle, they usually run at around 28° C. The more expensive NVMe enclosures tend to offer more surface area to radiate heat while active, so that’s worth factoring into the analysis.

But here’s the deal: I can buy a decent USB3.1 NVMe enclosure for around US$33 right now. The cheapest USB4 NVMe enclosure I could find cost almost US$96 more. That’s a multiplier of just under 4X in price for a device that delivers less than 2X in improved performance. Let me also observe that there are several such enclosures that cost US$160 and up also on the market. I still have trouble justifying the added expense for everyday use, including backup.

There will be some high-end users — especially those working with huge datasets — who might be able to justify the incremental cost because of their workloads and the incremental value of higher throughput. But for most business users, especially SOHO types like me, the ouch factor exceeds the wow value too much to make it worthwhile. ‘Nuff said.

Facebooklinkedin
Facebooklinkedin

KB5018496 Lands Poorly So Far

KB5018496 is out as of October 25. It takes production-level Windows 11 22H2 systems to Build 22621.755 when applied. To be fair, it’s a Preview CU, so not entirely cooked yet. But I observe that KB5018496 lands poorly so far because

(a) I don’t see any of its cool gradual rollout features on any of my PCs (e.g. right-click in Taskbar to launch Task Manager)
(b) When I attempted to explore the new Microsoft Accounts (MSA) capabilities, it crashed when I attempted to open the P16’s camera. I know that works because I use camera-based Hello to log onto that machine and had just done so minutes before. Sigh.
(c) I was unable to verify my identity in Settings → Accounts, because of the camera issue, so also unable to backup my MSA data. Sigh again.

Again: this is a preview release. And I’m qvetching about gradual rollout elements that either haven’t made it to my PCs, or that aren’t yet working as they should be. It’s a kind of “business as usual” thing, I guess.

What KB5018496 Lands Poorly So Far Really Means…

It’s pretty much par for the course that a few rough edges will show up in a preview release. Thus, for example, when I went to Accounts → Windows backup in an RDP session, the PC “knew” it couldn’t use the camera for validation. So I got an email to my MSA address instead. That worked just fine. The relevant screencap appears as the lead-in graphic for this story.

I assume there’s some kind of driver hiccup with the camera when logged in directly. It threw an error code that pointed squarely in that direction. That should be easy to run down and fix, so I’ll report it to Feedback Hub later today.

I’ve been using the right-click access to Task Manager in the taskbar on Insider versions of 22H2 for a while now. Thus, I also know it’s just a matter of time before it, too, shows up in production versions of 22H2.

Self-Inflicted Wounds? Perhaps…

So why do I install previews on production PCs? Because I’m an Insider and it’s my job to take such stuff on, and report what I see and find. I make daily image backups on those PCs, so the worst that can happen is a rollback to the previous image. I don’t generally do real work on those PCs unless I’m on the road. And in that situation, I probably wouldn’t mess with a preview because I wouldn’t want to lose the time (or the work done) since the last backup anyway.

And that’s how things go here in Windows World. Stay tuned for further developments. I’ll qvetch some more another day, for sure!

Facebooklinkedin
Facebooklinkedin

Winget Updates PowerShell 7.2.7

Here’s something new in my personal experience. I ran Winget on one of my Dev Channel test PCs this morning. The latest version of PowerShell came up as an upgrade option. So I exercised it, and indeed the PowerShell version incremented from 7.2.6 to 7.2.7. Hence my claim that now, Winget updates PowerShell 7.2.7. You can see the process underway in the lead-in graphic for this story.

What Happens When Winget Updates PowerShell 7.2.7?

Things get a little weird along the way. Notice that after Winget starts the package install for PowerShell, it shows a “Cancelled” notification at the lower left corner of the Terminal session window. At the same time, the PowerShell installer (small pane at lower right) reports ongoing progress in removing the old version, then installing and configuring the new version.

When the progress bar goes all the way to the right, it simply disappears with no further communication from the installer. On a whim, I closed the open Terminal session window. When I opened a fresh one, here’s what I saw:

Winget Updates PowerShell 7.2.7.new-window

Once the progress bar completes, the installer goes silent. But if you close the open Terminal session, then open a new one, you’ll see it’s indeed been updated to 7.2.7.

I’m not sure how it’s supposed to behave because I’ve never seen winget upgrade PowerShell before. Normally, a full installer window opens with the masked PowerShell avatar (see below). Then, one steps through the typical standalone installation sequence. This time, with PowerShell running things it worked differently. A bit disconcertingly, too. But it’s installed now and works as expected. So I guess, all’s well that ends well. Cheers!

Winget Updates PowerShell 7.2.7.avatar

I guess I’ll miss the avatar going forward, but I do appreciate the convenience of upgrading inside PowerShell.

Facebooklinkedin
Facebooklinkedin

Author, Editor, Expert Witness