Category Archives: Cool Tools

WinGet Updates PowerShell, Error Aside

I have to chuckle. There’s a new PowerShell 7.4.4 out. I just used WinGet to update my production PC and it applied the update package. But when it got the end of the update, it reported “Installation abandoned” and ended the WinGet update session. Because 7.4.4 came when I closed, then re-opened, Windows Terminal it looks like WinGet updates PowerShell, error aside. You can see the sequence in the lead-in graphic.

WinGet Updates PowerShell, Error Aside

Notice that a “Cancelled” item shows up below the “Installation abandoned” notification. I’m guessing this last item refers to jumping out of the WinGet update sequence, because you see a normal command line prompt (spiffed up, thanks to Oh-My-Posh).

And sure enough, running WinGet upgrade –all –include-unknown finishes up the remaining items that appeared below PowerShell in the update list. In the next screencap I show a two-pane Windows Terminal session. On the left, you see the sequence of update packages installed; on the right, you see the PS Version is now 7.4.4.

To the left you see WinGet at work; to the right a newly-opened PS session says it’s v7.4.4. [Click image for full-sized view.]

One more thing: the final item in the upgrade sequence on the X1 Extreme was Winget itself (which appears as Microsoft.AppInstaller inside the upgrade list). At its conclusion, WinGet closes things out a bit more reasonably. It says:

Successfully installed. Restart the application to complete the upgrade.

Cancelled

I think that confirms my suspicion that the cancelled item refers to the WinGet session itself. It even throws a couple of Ctrl-C (^C) characters to make sure things get closed out. Here’s a screencap:

Facebooklinkedin
Facebooklinkedin

Getting Past Crowdstruck Requires Access

Last Friday (July 19), cybersecurity firm Crowdstrike pushed an update to its threat sensors. Ultimately, that ended up with over 8 million Windows PC unable to boot, stuck on a BSOD for invalid references in a kernel-mode driver. Behind the scenes, all kinds of companies from hospitals, to government agencies, to airlines, and more, found themselves unable to use updates machines after a post-update reboot. What really caused the heartburn? Getting past Crowdstruck requires access to affected machines on a one-at-a-time basis.

If you look at the BSOD screencap at the head of this blog post, you’ll see a driver named csagent.sys. This is the CrowdStrike Agent driver which runs at kernel mode by design. That ensures it can’t be easily accessed or tampered with by hackers. But when something runs as a kernel mode driver it must be rigorously and thoroughly tested and vetted, or it can crash any PC on which it runs. Errors, in short, cannot be tolerated. Oops!

Why Getting Past Crowdstruck Requires Access

Part of the Crowdstrike software run as a Windows kernel-mode driver. That means it has the same level of access as privileged parts of the OS itself. If any of this code throws an error — as Crowdstrike has publicly admitted its update did — Windows crashes itself. That’s by design,  out of an abundance of caution to avoid loss of data or other damage to affected systems.

Here’s where things get interesting. Windows can’t boot and run until the offending driver is removed. In turn, the affected PCs must boot into safe mode or a recovery image. Either can operate on the damaged Windows image, remove the bad driver, and stand Windows back up again. This is easy when admins or IT pros have physical access to affected PCs. Indeed, Copilot recommends using the “three strikes” method to get into Windows recovery. (Three consecutive boot failures autoomatically triggers Windows alternate boot.) Then, using WinRE (or Windows itself in safe mode, from the Advanced Boot Options), repairs can go forward.

The problem is that many, if not virtually all, of the affected machines stayed down, stuck in a “boot loop.” They remained that way because their operators DIDN’T have physical access to those PCs. I’ll bet that most of them had to be teleoperated through a KVM device that can work around PC  problems that extend all the way down to the hardware level (outside the scope of normal remote access and RDP). This kind of thing doesn’t scale well, either, so it takes time to work through hundreds to thousands of remote PCs (think of the PC behind the counter at AA or Delta, where the gate or ticket agent is completely clueless about boot-level Windows repairs).

An “Interesting” Problem, Indeed!

Far too many cybersecurity and IT pros found themselves in the grip of the old Chinese curse (“May you live in interesting times”) after the *291* driver for Crowdstrike  tried to run on Friday. Organizations that prepare and drill for these kinds of outages were doubtless at an advantage in already knowing how to broker and run boot repairs remotely. I can only imagine the hair-pulling that went on at other outfits less well-equipped to handle this outage.

Here’s a moral to ponder for those who run remote Windows PCs where physical access is impossible, difficult or impractical: Can your remote management infrastructure and automation work with a Windows PC that’s not booting, and won’t boot until it’s restarted in some special way? If your answer is “yes,” you’re probably over the Crowdstruck hump already. If your answer is “no,” you’ll probably make that a top priority as soon as you can kick-start and repair all remaining affected Windows nodes. In the meantime, my deepest sympathies…

Facebooklinkedin
Facebooklinkedin

Copilot+ PCs Bring Better USB4 Support

When I went to build recovery media for the Lenovo Yoga Slim 7x Copilot+ PC last week, I dropped a Belkin TB3 dock into one of its 3 USB-C ports. Why? Because I needed a USB-A port into which to plug the Mushkin Atom UFD I targeted for that purpose. The lead-in graphic shows the dock at the “other end” of USB4 host router 1 (right-click the graphic and open in its own tab to see the whole thing). The next screencap shows the Hardware tab from Properties for that recovery drive (E:). Thus, I claim that Copilot+ PCs bring better USB4 support because until USB4 hubs and devices appeared in settings, users had to run a separate (and less informative) Thunderbolt app from Intel to see what was what. This has improved!

Copilot+ PCs Bring Better USB4 Support.e-drive-hwprops

The Mushkin E: drive is an older USB 3.0 Atom device.

So What If Copilot+ PCs Bring Better USB4 Support?

Though I’ve yet to see any laptops or PCs endowed with USB 4 2.0 (you can see version 1.0 in the lead-in graphic) this is now part and parcel of Windows 11 as well. It will also allow channel speeds to double from 40 Gbps (which 1.0 supports) to 80 Gbps (2.0 only, and primarily limited to video links). This probably doesn’t matter much right now, given that these top-of-the-line versions aren’t yet widely available. But for those who need the speed, this will matter once the peripherals and docks gain USB4 2.0 support.

I’ve got a Qualcomm Copilot+ Developer Kit SFF PC showing up here at Chez Tittel in the next day or two (today, even, maybe). I’ll be quite curious to see what Settings > Bluetooth & devices > USB > USB4 hubs and devices has to tell me about what’s inside and the docks and other devices I plan to hook up. Indeed, I’m going to start with a Lenovo P27u20 monitor, with its integrated TB4 docking capability. Hopefully, it will not only provide a great display, but also the means to hook up my keyboard and mouse. Stay tuned! These USB4 adventures will continue…

Facebooklinkedin
Facebooklinkedin

Calc Key Follies Fixed

Here’s an interesting one. I have a Microsoft Comfort Curve 4000 ergonomic keyboard (and two more in my parts closet: I LIKE them). Lately, though, when I press the “Calculator” (Calc) key on the very top row of long, narrow silver keys at furthest right something odd occurs. Calc shows me a “blank face,” as you can see in the lead-in graphic. Basically it’s just a big blue block of nothing much. Attend, and I’ll explain I I got these Calc key follies fixed.

For the record, I don’t *want* to see the blank face of Calc. I want to see the keypad so I can use the darn thing, like so:

Multiple Methods Get Calc Key Follies Fixed

I discovered these methods partly by searching the web, and partly by experimentation. There are three of them, to wit:

Method 1: Close Calc, then hit the Calc key again. This one’s my favorite so it’s my go-to now. It involves the lease effort and goes fastest.

Method 2: Open the Calc app from the Start Menu. Even though pressing the Calc key shows a blank face, visiting the Calculator app through Start always works. It takes added mouse clicks, though. Until I figured out Method 1 by experimentation, this was my go-to method.

Method 3: Go to Settings > Installed Apps, click on the ellipsis for Calculator, Click the Advanced Options button, scroll down to Reset, then click the Repair button. That’s 5 mouse clicks and a bit of scrolling. Waaaaaaay too long for me, but it does do the trick. But then the question is: why does this condition keep coming back, even after an app reset? I think I know the answer: read on, please.

Special Keys Require a Custom Driver

The Comfort Curve 4000 keyboard has a whole row of elongated, narrow silver keys that use special, driver-based, context-sensitive macros. These do things like jump to the home screen, open a search window, open email, access the volume controls (up and down), and so forth. And yes, at far right you can see the Calc key that’s been acting up lately. They occupy the top row from left almost to the numeric keypad at right, as shown here:

My best guess is that something in the driver is losing its proper connection to the Calc app so that when the key is pressed once, it gets close to launch but not all the way there. Fortunately, it’s relatively easy to get the Calculator working as I’ve described.

But gosh, aren’t these little foibles fascinating? It’s a bit of a pain to run into them, true. But it’s a blast to figure out what’s happening and why, and then to find fixes or workarounds. Just another day here in Windows-World!

 

Facebooklinkedin
Facebooklinkedin

MS Intel/AMD Copilot+ PC Date Drop

Though the details aren’t terribly specific, MS has provided an inkling of when Copilot+ PCs running Intel and AMD CPUs should ship. In an item about a new incremental update technique dated July 15, MS provides the snippet depicted in the lead-in graphic above. This states that “Windows 11, version 24H2 will be available as a traditional feature update to all devices later this year.” Thus, I call this an MS Intel/AMD Copilot+ PC date drop — of sorts, at least.

What Does This MS Intel/AMD Copilot+ PC Date Drop Mean?

I confess: I’m reading somewhat between the lines as I interpret this. But I’m not alone: you’ll find stories at WindowsLatest, TechRadar, Windows Central, and elsewhere that draw the same conclusions I do. Of course, the words “later this year” could occur any time between now and December 31, 2024, so that stipulation is far from precise or narrowly targeted.

That said, I’m in accord with most industry watchers — including the afore-linked stories — in believing that 24H2 is likely to drop some time in Q4 2024. My best guess would be “after Thanksgiving, but before Christmas” to give room to steer around major end-of-year holidays and associated time off for breaks. But it could happen earlier, to get 24H2 out of the way before the holiday season kicks off in late November. Only time will tell…

Further Points of Possible Confirmation

Intel’s May 20 press release for its Lunar Lake CPUs reads “Starting Q3 2024 in time for the holiday season, Intel’s upcoming client processors … will power more than 80 new laptop designs across more than 20 [OEMs]…” A June 2 press release from AMD steers clear of dates for its Ryzen AI 300 Series CPUs, but does mention partnerships with ” Acer, ASUS, HP, Lenovo and MSI” that will surely ship at or about the time time that Intel’s OEM partners offer up their competing laptops and so forth.

Could it be that interesting options for end-of-year gifting might include snazzy new technology toys? MIght you or I want one? For sure!

Facebooklinkedin
Facebooklinkedin

Channel Speed Trumps Device Speed

I kind of knew this already, but I wanted to prove it to myself through hands-on experience. Thus, I sprung for what Tom’s Hardware calls “the fastest SSD” around right now. It’s depicted in the lead-in graphic: The Crucial T705. It’s read/write ratings range from 13,600/10,200 MB/sec for big items to 1,400K/1,750K IOPS on random 4K items. That’s fast!

Why Say: Channel Speed Trumps Device Speed?

I know this NVMe drive would scream if I mounted it in an M.2 PCIe x5 slot on a motherboard. But I wanted to see if it made any difference if plugged into the M.2 slot inside a 40Gbps USB4 NVMe enclosure. Long story short: it doesn’t. It runs more or less indistinguishably from the 2022 model WD Black SN770 I replaced in the US$53 Maiwo USB4 fan-cooled enclosure.

Although the T705 is much faster than the SN770, those speed differences only count when the bandwidth from the SSD to the CPU is fast enough to actually show off such deltas. Because Lenovo sent me the Yoga Slim 7x with a smaller, slower C: drive device, I’ll probably end up plugging into that PCIe channel to see what it does as an internal drive.

But that’s a project for another day. Today, I have two “lessons learned” to share:

1. A PCIe x3 or x4 NVMe SSD is plenty fast enough for even the fastest, most expensive USB4 drive enclosures currently available.

2. The T705 at US$165 is about twice as expensive as the SN770 (and the SN770 2TB model at US$120 is a much better deal, $/GB-wise)

What can I say? I had to know. Now I do, and I’m moving on to other, better uses for the T705. I may have to use Linux to clone the existing 0.5TB NVMe in the Slim 7X, but I’ll figure out how to make that swap work. As I said earlier: that’ll have to wait for another day.

Facebooklinkedin
Facebooklinkedin

Notepad Gets General Spellcheck

Since March, 2024, or thereabouts, MS has been testing spellcheck within the venerable Notepad app in Windows 11 Insider Preview versions. As of the latest Store version (11.2405.13.0) however, it is now popping up in production/stable Windows 11 builds (22631.3380, as I write this item). Hence, my proclamation that Notepad gets general spellcheck for Windows 11. The lead-in graphic shows what this looks like for a simple sentence with 2 typos.

If You Don’t See that Notepad Gets General Spellcheck

Whenever I read about new features or capabilities showing up in Windows, I like to go look for myself and confirm their presence or absence. So when I read about this yesterday in a story from Sergey Tkachenko at WinAero, I tried it out to see what was what. At first, spellcheck didn’t work.

First thing: I checked Settings to make sure it was turned on. Indeed, it was. So I toggled it off, then toggled it back on. That did the trick — and produced the spell-checked text you see in the lead-in screencap. If you find yourself facing the same circumstances, that simple operation will hopefully produce visible spellcheck output, too.

One more thing: spellcheck is sensitive to file extensions. It does spellcheck text types. But it does not check scripts, programming language source code, or log files (e.g. .ps1, .py, or .log/.evt). You’ve been warned! So far, I like I what I see when Notepad does its spellcheck thing. Check it out!

 

Facebooklinkedin
Facebooklinkedin

UUPDump Covers ARM64 ISOs

OK, then: now that I’ve got a Copilot+ PC with Snapdragon X Elite CPU, I’m paying attention to backups and restores, plus repairs and rebuilds. Thus when I saw Paul Thurrott’s (Premium) post this morning The Windows 11 on ARM ISO Conundrum I immediately jumped over to UUPDump.net to check ARM64 status. To my great relief, UUPDump covers ARM64 ISOs — along with other kinds — as you can see in the lead-in graphic. This is doubly valuable, because neither the Windows 10 nor the Windows 11 download pages provide ARM64 ISO options. Thus, they can’t build ARM64 ISOs, either (10 offers x86 32- and 64-bit, 11 x86 64-bit only).

Thank Goodness: UUPDump covers ARM64

I used the search string “24H2 arm64” at UUPDump.net to produce the lead-in graphic. Checking my Lenovo Yoga Slim 7X Copilot+ PC using winver.exe, I see it’s running Build 26100.1000 right now. As you can see in the lead-in graphic, that’s the top/most recent version of Windows 11 24H2 available at present.

Just for grins, I’ll visit the site and generate myself an ISO for this version later today. Who knows? It may come in handy for repairs and/or as the basis for a bootable flash drive. Lord knows they’re handy whenever Windows gets weird as it will sometimes do on its own. And when I’m beating on a review PC I do have a tendency to break things a-purpose, just to see what happens. Repair/recovery media are always good just in case they’re needed, right?

Other News on the ARM64 Front

I’ve got some deadlines today, but I’ll be reaching out to Lenovo tomorrow. I still haven’t been able to get into a VM on the Slim 7x. I keep getting hung up at the Start screen, which goes straight to PXE boot and then gets nowhere. There’s got to be a trick I haven’t been able to figure out on my own, so I’m going to ask the real professionals for help — namely the support SMEs who try to help hapless reviewers like yours truly who dig themselves into the occasional hole.

Stay tuned: I’ll keep you posted on my ongoing adventures with limited-access Windows 11, as well as all the other versions I’m running around here.

Facebooklinkedin
Facebooklinkedin

SDIO Replaces Studio with Game-Ready

I’m looking over what Snappy Driver Install Origin (SDIO) wrought by way of massive driver updates on a couple of Lenovo laptops. I noticed something interesting. Something perhaps even mildly disconcerting, in fact. In updating drivers, SDIO cheerfully replaces Studio with Game-Ready drivers for GeForce GPUs.

I’m not sure that’s what users would want, if informed in advance of this switcheroo. Indeed, I had earlier noticed and reported on SDIO replacing Realtek Universal Audio Driver (UAD) drivers with High Definition Audio (HDA) ones. As with the prior NVIDIA driver types UAD offers things that HDA does not. For example: UAD adds Realtek Audio Console support while HDA is a no-go. Thus, some users wouldn’t want to switch — myself included.

Why SDIO Replaces Studio with Game-Ready

Methinks SDIO’s approach to driver updates is pretty simple-minded. And indeed, the release date for the NVIDIA Game-Ready driver is newer than that for the Studio driver. A simple data comparison makes it “logical” for the younger item to prevail. But IMO that shows other considerations are needed. If you check the lead-in graphic, you’ll see that SDIO recommends Realtek HDA drivers, though I’m happily using UAD and the Realtek Audio console.

This kind of thing needs “exception handling” in SDIO. If it supported rules to over-ride strict date-based selection, it could easily work around the kinds of situations pertaining to NVIDIA graphics and Realtek audio drivers. I guess I’ll file a feature request to see what happens.

Know Your Tools; Work Around Deficits

This illustrates how important it is to observe and understand what tools are doing. When they do something unexpected or unwanted it’s often because the developer didn’t consider certain use cases. By bringing them to developers’ attention and learning how to work around them until they’re fixed, IT pros can keep on keeping on even when their tools don’t always work exactly as they want them to.

That’s life, here in Windows-World. I intend to keep watching, and keep enjoying its eddies and rhythms, for some time to come! Happy 4th of July, too, for those who celebrate this holiday.

Facebooklinkedin
Facebooklinkedin

Snappy versus Vantages Poses Sharp Contrast

In case you didn’t know, I’ve got a boatload of Lenovo laptops here at Chez Tittel (I count 6 in my office right now, with another upstairs). The company is kind enough to loan me the occasional unit (just over half that total) and I’ve purchased many more over the years than are currently on hand. That means frequent driver checks and hunts to keep those units up-to-date. I performed a clean install on the P16 Mobile Workstation  last eweek.  I also recognize extended procrastination on the X1 Extreme (both are ThinkPad models). Consequently, I’m observing that Snappy versus Vantage poses sharp contrast in items found and updates needed. Let me explain…

Why Say: Snappy versus Vantages Poses Sharp Contrast

For the P16, Vantage found 8 drivers in need of updating after I’d completed the clean install. For the X1 Extreme (running Build 22635.3858) Vantage says “nothing to see here.” From the Snappy Driver Installer Origin (SDIO) perspective, it found 61 drivers to update on the P16 (delta = 53), and 59 on the X1 Extreme (delta = 59). IMO, that’s a pretty sharp contrast. You can see it at work downloading packages prior to installing updates for the X1 Extreme in the lead-in graphic.

SDIO is an open source project, for which Glenn Delahoy is primarily responsible. It’s donation-ware, and worth supporting (I just anted up US$5 and thanked him for his work). I find it to be a reasonably accurate driver scanner and absolutely the least intrusive of all many and various ones I’ve tried over the years.

The download phase takes a while because that many drivers perforce means downloading a number of good-sized driver package files for SDIO to use. On the X1 Extreme, it just took about 15 minutes to download 8.4GB of stuff, then another 20 minutes or so to chunk through the 59 driver installs. I was bemused that each of the CPU’s 12 cores required its own download and install of an”Intel Dynamic Tuning Generic Participant” and another “Intel Dynamic Tuning Processor Participant,” but that’s apparently the way it rolls.

Indeed, there was lots of Intel stuff in the mix (I’d say around two-thirds of the components overall). But the updates went through and produced no blivits (Unknown Device entries) in Device Manager. Indeed, the X1 Extreme seems to be running faster and more smoothly, too. Go figure!

Facebooklinkedin
Facebooklinkedin