Insider stuff, Recent Activity, WED Blog, Windows 11, Windows Update

KB5022913 May Break Customization Tools

Leave a comment

Some people learn to live with Windows and make the best of it. Others refuse, and turn to third-party tools to bring back bits and pieces of prior capability that MS has removed. Ditto for adding functionality missing but desired in Windows. When MS released its “Moment 2” updates on February 28, it announced that KB5022913 may break customization tools in common use.

If KB5022913 May Break Customization Tools, Then What?

If an update breaks a third-party tool, users have two choices:
1. Remove the third-party tool, and continue forward with the update.
2. Uninstall the update, and keep using the third-party tool.
Of course, neither option is perfect but sacrifices are sometimes necessary here in Windows-World.

Here’s what the announcement says, verbatim (emphasis mine, for easy identification of possible offenders in the first paragraph; emphasis in the second paragraph is Microsoft’s):

After installing KB5022913 or later updates, Windows devices with some third-party UI customization apps might not start up. These third-party apps might cause errors with explorer.exe that might repeat multiple times in a loop. The known affected third-party UI customization apps are ExplorerPatcher and StartAllBack. These types of apps often use unsupported methods to achieve their customization and as a result can have unintended results on your Windows device.

Workaround: We recommend uninstalling any third-party UI customization app before installing KB5022913 to prevent this issue. If your Windows device is already experiencing this issue, you might need to contact customer support for the developer of the app you are using. If you are using StartAllBack, you might be able to prevent this issue by updating to the latest version (v3.5.6 or later).

Notice that MS puts the onus for figuring things out if Windows doesn’t work properly with such a third-party tool on that tool’s developer. This could make life extremely interesting for related tech support operations.

To Tweak, or Not to Tweak?

With apologies to Hamlet (and Shakespeare), the real question is how much, how often and what kinds of tweaks Windows users can safely make to their own installations? I’m of the opinion that “less is more” because it involves fewer things that could go wrong, and fewer such things to keep track of.

That said, I do indeed enjoy tinkering with Windows. I don’t see what MS is doing here as a general injunction against such efforts. Instead I see it as a warning against “unsupported methods” that some developers use. I agree with MS that on principle such tools are best avoided. But that puts an interesting burden on users to figure out what’s working and what’s not. I can tell you from copious personal experience that diagnosing and pinpointing trouble can be difficult and time-consuming. Indeed: the MS workaround seems like a well-intentioned way to shortcut that work, and bypass related problems.

Note Added March 2 AM

This morning, the first thing I saw on WinAero was a story entitled “A new version of ExplorerPatcher fixes issues with Windows 11 “Moment 2” Update.” According to WinAero principal Sergey Tkachenko, at least one set of already-identified problems is addressed. I guess that’s the kind of response you’d hope for, if you were an ExplorerPatcher user. While I am not, I see plenty of people over at ElevenForum who use (and praise) it.

Another item has joined the list of offenders, though: Stardock’s Start11 (says Neowin). That one, I do use, on some of my Windows 11 PCs. Guess I’ll have to watch closely and take evasive action as needed.

Stay tuned: this looks like it could get increasingly interesting…

Facebooklinkedin
Facebooklinkedin
Insider stuff, PowerShell, WED Blog, Windows 10, Windows 11

Strange wt.exe Windows Terminal Behavior

Leave a comment

I’ve got to admit I love nothing better than a good Windows mystery. And right now: I seem to have a doozy on my hands. Here’s the deal: if I open Windows Terminal on my production Windows 10 PC, it won’t run another terminal instance (wt.exe) either in PowerShell or in a Command Prompt pane. You can see this in the lead-in graphic above. The PowerShell error message also provides profound guidance on what’s going on here with this strange wt.exe Windows Terminal behavior. Can you see it, too?

Why Get Strange wt.exe Windows Terminal Behavior?

The clue is in the error message text where it shows the path for the version of wt.exe that PowerShell or Command Prompt tries to run. It’s the Preview version, which I have installed alongside the production version on this — and only this — PC here at Chez Tittel. By no coincidence, it’s also the only machine here that’s having this problem.

That said: I’ve also found various workarounds that bypass this issue:

1. Providing the complete path spec for the non-preview version launches a new Terminal window from  Command Prompt. The complete path spec for the preview version still provokes “access denied.” It sits there and does nothing inside PowerShell.
2. Opening Voidtools Search Everything, right-clicking and selecting “Run as administrator” launches a new Terminal window for either version. The same approach works in File Explorer, too. Ditto for Start menu access (but only for the production version, which is the only one that has a Start menu entry).

Version Confusion Path Dynamics

To me, this problem seems obviously path related. And indeed, the first entry in the PATH variable on the affected PC reads:

C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_
1.17.10234.0_x64__8wekyb3d8bbwe;

That explains why the shell tries to run the Preview version in the first place when it’s called at the command line. It’s very likely a side-effect of the Terminal Preview installation process. I didn’t edit PATH to include it, that’s for sure.

And it turns out that when wt.exe runs, it adds itself to the PATH. This raises the question of why, even when I launch the production version, the Preview is the version added to the PATH. Interesting!

Workarounds Will Cover My Needs

For the time being I can get Terminal to do what I need it to do without completely figuring out this strange path dynamic that’s at work. I imagine that I could simply uninstall the Preview version and my issue would disappear. I’ll think about and fool around with this for a while yet, and see if I can figure another solution. For further discussion of what turns out to be a bigger mystery than I was expecting see this github issues thread: Windows terminal path is different if launched with wt.exe. This one appears to possess Dantean qualities (“Abandon all hope, ye who enter here…).

Let me be clear about this, though. This happens only on one of my near-dozen Windows PCs. And it’s the only one with both Preview and Production versions of Windows Terminal running side-by-side. It’s definitely a tempest of sorts, but one in a pretty small teapot.

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, WED Blog, Windows 10, Windows 11

Update Semantics: Current versus Preview

Leave a comment

Here’s an interesting situation that frosts me just a tad. The other day, I found myself chasing a version of OneDrive that I couldn’t find on its Release Note page. According to that page, I had the current release of that software installed on my production PC. Turns out that KC Softwares Software Update Monitor (SUMo) disagrees with Microsoft (and me, FWIW). It points users at what I learned by experiment is the current Insider preview update. This has me questioning their update semantics: current versus preview. I’ll explain

Questioning Update Semantics: Current versus Preview

Common usage for current in the context of “current software release” is usually understood as “official vendor or developer sponsored software release that represents that latest and greatest stable version.” A “preview software release” OTOH usually means “a preview of upcoming software that’s not guaranteed to be bug-free or stable.”

If you look at the lead in graphic, then at the item after this paragraph, you’ll see that what SUMo recommends as the current release for OneDrive is actually the Insider preview update. I think that’s a mistaken approach. But I’e noticed that SUMo tends to recommend the highest-numbered version for software it tracks. That happens sometimes (e.g. SpaceDeck) we when AFAIK (and have been able to ascertain) that version number does not exist!

Notice the SUMo version available matches pre-release version at right top.

Because I’m quibbling about semantics here, I’ll give SUMo credit for saying that the higher-numbered release is available not current. But gosh, they expect you to download, and update or install to that version number. If that’s not at least an implicit claim that it’s the right version to run, I’m sadly mistaken. I wish instead they’d key on the version from the release notes page which Microsoft clearly labels as the current (stable and shipping) version. C’mon people! Get it right… And while you’re at it, adopt this practice for all the apps you track. Thanks in advance … I hope.

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, WED Blog, Windows 11

Win11 Allows March Beta Escape

Leave a comment

Here it comes. In the surest sign that a new version of Windows 11 is headed for production Win11 allows March Beta escape. An explanation appears in this February 23 post to the Windows Insiders blog. Indeed, MS offers a limited-time-only “Off-ramp for Windows Insiders in the Beta Channel.”

What does this mean, in plainer English?  If you opt in, you can leave the Beta Channel for Insider Preview. In fact, you’ll return to the production version of Windows as it settles down in the wake of the upcoming release.

If Win11 Allows March Beta Escape, Why Do It?

It’s the easiest way to unenroll from the Beta program, and go back to a production version of Windows. Works equally well for physical PCs and VMs. I’ll summarize the basic elements of the “escape” (read the announcement for all details):

  1. The off-ramp started January 23. It’s open through March 8.
  2. Offer applies only to those running Build 22621.1325 or 22623.1325 (older Beta Channel builds are not eligible; I assume this means newer minor builds will also qualify — the announcement does not specifically spell this out).
  3. While the offer is open, a troubleshooter handles the unenrolling process, which requires a reboot to change status from Beta to production. Once unenrolled, the PC no longer gets Beta builds.
  4. When the troubleshooter finishes, the “in-place upgrade with the March 2023 “B” release (the next Patch Tuesday)” is installed. This puts it into the then-current release for Windows 11 22H2.

Why I Like This Off-Ramp News…

It tells us that a new version of Windows 11 22H2 is headed our way. It’s always nice to know for sure. I’m looking forward to it. Thanks, Microsoft!

Here’s a shout-out to John Callaham at Neowin.net. His story there alerted me this morning to yesterday’s announcement. Thanks!

Facebooklinkedin
Facebooklinkedin
Insider stuff, Networking, Recent Activity, WED Blog, Windows 10

So Long Surface Pro 3

Leave a comment

OK, then. I think I’m at the end of a long, long road. I remember buying my Surface Pro 3 in 2014. It was the first in a long series of tablet PCs I’ve bought over the years. Included were models from MS (Surface), Dell (Latitude), Fujitsu (Stylistic) and Lenovo (ThinkPad). But now, it’s time for me to say: “So long Surface Pro 3.”  Please: let me explain what’s going on…

Why It’s Time for So Long Surface Pro 3

This morning when I logged into my network, I noticed the SP3 had switched over from the wired GbE port in the dock to its wireless interface. It’s been dropping this wired connection for months now. As (almost) always, a reboot brought the wired interface back up. But I can tell the dock is starting to fail.

I just spent US$19 last week to replace the power supply brick for the dock. But I hesitate at replacing the dock outright (costs about US$100 for a refurb unit). It’s time to quit futzing around with this old beast, and unload it into proper disposal channels.

Where to Take This Aging Beast

For years, I’ve given my older PCs to Reglue, a charity that placed them in the hands of under-served students and their families to confer low-cost/no-cost Internet access. But alas, the founder of that organization has retired and is no longer accepting donations.

For about the same period of time, I’ve recommended Goodwill as a safe, responsible drop-off for used PC electronics of all kinds. Thus, I’m glad to see that the Austin Reuse Directory likewise recommends Goodwill for such purposes. I’ve already got a Goodwill bag going with some old hard disks, memory modules, cables and interfaces ready for drop-off.

I’ll need another bag for the SP3 and its accoutrement, though. I’ve accumulated a major mound of stuff for this unit over the years. This includes:

  • an MS keyboard with fingerprint reader
  • the dock, with its external power brick
  • the original power brick shipped with the SP3
  • a Brydge aluminum keyboard that turns the SP3 into a clamshell style laptop

Another thing to take care of this weekend, when out running errands and shopping. Good thing my nearest Goodwill location is only 3.2 miles away!

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, WED Blog, Windows 10, Windows 11, Windows Update

Start10 Blocks 11 Upgrade

Leave a comment

For some time now, my spouse Dina has resisted upgrading to Windows 11. Her 11th gen Dell 7080 Micro meets all of the hardware requirements. But she’s not ready to take the plunge. Thus, when somehow, someway Windows Update started the Windows 11 upgrade process on her PC, I got a little worried. I shouldn’t have bothered — part-way into the install process, the installer halted the upgrade. Why? Because of a compatibility hold, Start10 blocks 11 upgrade on that PC.

Easy Fix for Start10 Blocks 11 Upgrade, But…

Yes, I know: if I were simply to uninstall Start10, the upgrade would proceed without further demur. Ironically, it serves as a form of insurance in this case. When Dina’s ready to upgrade, I’ll upgrade her (and install Start11 on the resulting build to minimize the impact of that change). That’s when I’ll take Start10 off the board, then…

The frequently-offered upgrade got started somehow in the last week. Somebody must’ve clicked the “go-ahead” button without really understanding what was going on. If it happens again, I now know that the upgrade process will quit before it gets to the post-GUI install phase.

Shoot! It might even be the case that now the compatibility hold is known to the Windows Installer, it won’t even try again. I certainly hope so. But sometimes, here in Windows-World what looks like a curse is actually a blessing. Of course, that vice is often versa, so it doesn’t always (or only seldom) works in one’s favor.

Thus, I’ll revel in this surprisingly friendly turn of events. It will certainly help to preserve domestic tranquility here at Chez Tittel. It should also suspend the too-typical “What did you do to my PC?” that “The Boss” has been known to emit after Windows Update does its periodic thing on her machine.

When this error shows up in WU, I can bail on the upgrade. Funny that it doesn’t screen in advance, but after downloading and during the GUI install phase (about 35% of the way in, if what the UI says is true). Go figure!

Facebooklinkedin
Facebooklinkedin
Cool Tools, Networking, Recent Activity, WED Blog, Windows 10, Windows 11

Intel PROSet Still Ticking Along

Leave a comment

In surveying my PCs this morning, I learned it was time to update the Intel PROSet software. This remains an entirely routine matter. It’s easy if a bit time-consuming to accomplish. Hence, I’m pleased to find Intel PROSet still ticking along. I have an admittedly small population of PCs (11 in total right now). Of those 6 show Intel interfaces in Advanced IP Scanner. I’m aware of at least 3 more Intel interfaces that don’t register on its scans. (Example: my Asrock Z170 motherboard has two Intel GbE interfaces: an I-211 and an I-219V.)

If Intel ProSet Still Ticking Along, Then What?

The download/install routine is pretty straightforward. Search Intel Downloads/Drivers&Software for the string “Intel Ethernet Adapter Complete Driver Pack” (for wired Ethernet). or for “PROSet wireless” (for Wi-Fi connections). Either way, you’ll get a ZIP file out of the download. Unpack it to a folder of its own, and you can use the autorun.exe file therein to perform installations for drivers (if applicable) and the latest PROSet software version (28.0.0.2 for wired; 22.190.0 for wireless).

Note: Don’t ask me why the window shown above reads “intel Network Connections.” It’s been that way for a long, long time. If memory serves — and this goes back far enough that it may not serve very well — this used to  be the general description for intel network drivers and software before PROSet came along. But that’s what it says, no matter if my recollection is correct or not.

The lead-in graphic shows the wired package, as you can see from the version number at the lower right of that image. The whole update process took less than 5 minutes on each of the affected machines. If you unzip the contents of the download to a shared drive, it works like a charm for all PCs on an accessible network.

It’s Easy to Get Lost in the Weeds

There are tons of advanced settings for Ethernet (especially wired GbE or higher speeds) available. PROSet provides access to such things pretty directly, or you can go through the Advanced Properties tab for the target interface in Device Manager under the Network Adapters heading. All-in-all, PROSet is a bit less unwieldy to use than DevMgr (where it is available).

So if one needs to monkey around with such things, I find PROSet preferable for such shenanigans. If you’re not already using this tool and you’ve got Intel interfaces to manage, give it a try.

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 11

Short-Lived CalDigit TS4 Hiatus

Leave a comment

My first job out of college, I worked as a studio engineer in recorded sound. I remember one of the senior engineers telling me one day: “The hardest problems to diagnose are the intermittent ones.” Over the years, I’ve seen that revealed as a terse understatement. I was reminded of that principle last week when my $400-plus Thunderbolt 4 dock quit working. As I dickered with CalDigit tech support to try to get an RMA number for that momentarily dead device, it came back to life. Because of this Short-Lived CalDigit TS4 hiatus I never did get an RMA; instead it’s back at work. Sigh.

When Short-Lived CalDigit TS4 Hiatus Ends, Then What?

As you can see from the front and back views in the lead-in graphic, the CalDigit Thunderbolt 4 Station (aka TS4) is a port-laden beast of a dock. I purchased it last August because I wanted to test this top-of-the-line Thunderbolt 4 (TB4) unit against other TB4 docks from Belkin and Lenovo. Until last week, it has behaved flawlessly, and worked well under every test of its capabilities I could devise.

Initially, I explained my symptoms to CalDigit tech support: no power light, no DC pass-through to power plugged-in devices, no appearance in Intel’s Thunderbolt Control Center (TCC) app when plugged in (and ditto for inserted TB4 or USB4 devices, either). They didn’t seem to want to believe me. So, under their guidance, I tried the device by itself (no power light, TS4 box didn’t warm up as it previously did). Next, I tried the device with their TS4 cable into a laptop. Still nothing. I reported those results and asked again for an RMA.

The Waiting Is the Hardest Part…

While waiting for a reply from Tech Support, I unplugged the device and left it completely alone and unused. When I got a response from CalDigit a couple of days later, they had me try one more thing: hook it up to a different laptop, in a simple configuration (TB4 from CalDigit to laptop for power and connectivity, GbE and USB-C for a storage device on the dock). To my utter astonishment it worked! And it kept working, even when I switched it back to the original laptop.

As far as what happened, nobody knows. Now the power indicator works. Pass-through power has kept my Lenovo ThinkPad X12 Hybrid Tablet humming for the past 4 days without interruption. And the TCC has consistently reported the presence of the dock and the Konyead USB4 NVMe drive enclosure also plugged into an open USB4/TB4 port (see below).

I’ve gotten into the habit of checking things as I sit down with my first cup of coffee to start up my day. And since last Thursday, everything been peachy. No problems at all.

But gosh, doesn’t that just underscore the loathing and dread that an intermittent failure can inspire? Why am I checking this stuff every day? Because I’m waiting for the next failure to pop into view. CalDigit doesn’t seem concerned, and hasn’t issued an RMA. Why can’t I be as cheerfully indifferent to the possibility of impending doom? Because I bought and paid for the unit, the problem is mine, all mine, I guess!

And boy, isn’t that just the way things go sometimes, here in Windows-World? Stay tuned…

Facebooklinkedin
Facebooklinkedin
Benchmarking, Device drivers, Insider stuff, Recent Activity, USB devices, WED Blog

Newer USB Justifies Added Costs

Leave a comment

I had a revelation via contrasting benchmarks yesterday. A friend returned a mid-range USB 3.1 NVMe drive enclosure after an extended loan. Thus, I popped it into my production desktop (an i7 Skylake Gen 4 PC) to see how fast it ran. Good enough. Then, just for grins I popped it into the 2021 vintage Lenovo P16 Gen 1 Mobile Workstation (an i9 Gen 12 PC). Much faster! Enough so, in fact, that it’s clear that newer USB justifies added costs of acquisition. Let me explain…

Why Say: Newer USB Justifies Added Costs?

Take a look at the lead-in graphic. It shows the difference between older USB technology in the Skylake desktop vs. newer USB technology in the Gen 12 mobile workstation. Both are using USB 3.1 ports (though the older PC goes via USB-A, the newer goes thru USB-C) to the same hardware running the same benchmark. Why is the new so much faster than the old?

Short answer: UASP, aka the USB Attached SCSI Protocol. The newer PC supports it, while the older one does not. You can see there’s a driver difference in Device Manager when it comes to accessing the NVMe drive enclosure and its installed SSD: the older machine runs a driver named USBSTOR.sys, while the newer one runs UASPStor.sys. Plain as day.

The Deal With UASP

The Wikipedia article on UASP is a good place to find some explanation. To wit: “UAS [USB Attached SCSI] generally provide faster transfers when compared to the older USB Mass Storage Bulk-only (BOT) protocol drivers.” In a nutshell, that’s UASPStor.sys versus USBSTOR.sys.

As I learned about this technology in the period from 2016 to 2019, the word at TenForums.com ran something like “Speeds of 500 MBps mean USB bulk transfer; 1 Gbps or better means UAS transfer.” And that, dear readers, is the difference you see between the right-hand side in the lead-in graphic (USBSTOR.sys on the Skylake) and the left-hand side (UASPStor.sys on the Gen 12).

In practical terms, this translates into much, much faster IO on the newer PC vis-a-vis the older one. I think it’s incredibly worthwhile, given that backups complete 2-3 times faster on the P16 than the Skylake. Likewise for big, bulk file transfers (such as Windows ISOs, which I mess with frequently).

Retrofit and Replacement

Does this mean one has to toss older PCs and replace them with newer models? Maybe, but not necessarily. For between US$50 and 100, you can purchase UASP capable PCIe adapter USB cards. As long as you’ve got an open PCIe x4 port available on your motherboard (desktops only, so sorry) this could be a good solution. I’m a fan of this US$95 StarTech unit for that purpose.

Older laptops can be dicey and depend on support for USB ExpressCards. I mucked around with these on some 2012-vintage Lenovo ThinkPads in the 2014-2016 timeframe (an X1 and a T420). They work, but they’re cumbersome and expensive (see this Amazon Review for a great discussion).

For best results, it may be time to shell out for a new desktop or laptop PC. That way, the fastest USB (and even Thunderbolt) technologies are likely to come built-in and ready to go. Could be worthwhile!

 

 

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, Thoughts & concerns, WED Blog, Windows 11

Build 25300 Restores Taskbar Clock Seconds

Leave a comment

OK, then, they’ve been gone for some time now. But Dev Channel Build 25300 restores Taskbar Clock seconds to its display capabilities. The lead-in graphic shows that Settings checkbox, next to Winver for the build.

Note: we’ve not had access to seconds readouts in the Windows 11 taskbar clock since Day 1 of the release. It popped in — and then out again — in a recent Insider Preview. And right now, it’s only available in the Dev Channel release fork. Just sayin…

Find this by clicking through Settings → Personalization → Taskbar. Then, open the Taskbar behaviors pane. That’s where you’ll find the checkbox labeled: “Show seconds in system tray clock…” Notice that it comes with this caveat: “(uses more power).” MS has long put this theory forward (it recommended against turning on the second hand in Vista-era clock gadgets for the same reason) but doesn’t really present actual data to report how much more power is used — or battery life lost — as a consequence of turning this on. Sigh.

If Build 25300 Restores Taskbar Clock Seconds, Then…

I can only interpret the MS caveat as a warn-off of sorts. I guess we should be grateful they’ve deigned to restore this capability to those bold (or stupid) enough to use it. Count me among that number, and decide for yourself its potential significance. Here’s what it looks it, after you turn seconds back on:

Build 25300 Restores Taskbar Clock Seconds.clock-showing

Even at the cost of a bit of power, glad to get those seconds back!

Small though this change may be, I am glad to have the choice as to whether or not I get seconds with my time readout on Windows 11. It’s been that way in Windows as far back as I recall. And now, it’s back again.

Sometimes, those little things do make a difference. I count this as a minor victory for the small people, here in Windows-World.

Facebooklinkedin
Facebooklinkedin

Author, Editor, Expert Witness