Category Archives: Insider stuff

Intermittent Mouse Needs New Battery

I have a kind of love-hate relationship with mice. Because I work on a desktop PC by choice, I’m more or less forced to use a USB-attached pointing device. I’ve switched back and forth between wired and wireless models because their weaknesses sometimes vex me. For the wired meese, the wire tends to snarl up with other cables on my desk. For wireless models, what frosts my jowls is intermittent or imprecise cursor stuttering or movement. I started to experience that on my current mouse this morning: a usually unflappable (and wireless) Microsoft Mobile Mouse 4000. Then I noticed a dimly pulsating red indicator light atop the device. Oho! This intermittent mouse needs new battery to work properly.

Why My Intermittent Mouse Needs New Battery

According this MS Community thread, the light is a battery life or status indicator. When you plug a new battery in, it shows green for 5 seconds, then turns itself off. Ditto when you power the mouse back on. When the battery is starting to fail, it shows red for the same interval upon power-up. And when battery levels are going critical — that is, it’s about to die — the dim red pulsations begin. Good to know!

We shop at Costco, so we always have lots of batteries around. As soon as I swapped out the old AA for a new one, I got the green glow for 5 seconds. Now it’s dark again. And presto! The mouse is no longer stuttering, and it’s tracking exactly where I want it to go. Yay!

The Best Issues Get Quick, Easy Fixes

Working with PCs in Windows-World means there’s always something in need of fixing or figuring out. Once you identify an issue, the troubleshooting process begins. Over my decades working with this stuff, I’ve learned to appreciate problems that are easy to recognize, diagnose and fix. Today’s successful battery swap definitely falls in that category, even if another one bits the dust as a result.


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!



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 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 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.


Painful Tradeoff: System Update vs. Hyper-V

I just learned something new yesterday, as I’m still breaking in my new Lenovo Yoga Slim 7x Copilot+ PC. It seems one can’t use the Lenovo Service Bridge and/or its System Update facility without turning off the Hyper-V feature (and support for VMs). To me, this is an extremely painful tradeoff, because System Update vs. Hyper-V means doing without one or the other. I want both!

Uncovering Painful Tradeoff: System Update vs. Hyper-V

It was actually slightly worse than simply disabling the Hyper-V feature using Control Panel item Programs and Features built-in Turn Windows features on or off option. As you can see in the next screencap, the Hyper-V feature box is unchecked (turned off).

Painful Tradeoff: System Update vs. Hyper-V.turned-off

When the Hyper-V box is unchecked, it’s not available on that host PC.

In addition, I also had to remove an exclusion on a range of dynamic (upper-address) TCP ports because Hyper-V reserves them for its exclusive use. That required the following command:

netsh int ipv4 delete excludedportrange protocol=tcp 50000 60

What this does is remove the exclusion range from TCP port number 50000 through 50059 (60 ports total, as per the final value). When I turned Hyper-V back on, I had to reboot the PC as per SOP. But I had to re-exclude that range of TCP ports to restore Hyper-V Manager’s ability to access the network. Until I did so, it showed no information when trying to access predefined MS image resources. As you see in the empty “Select an operating system” pane for Quick Create, there’s no there there…

The syntax to restore the excluded port range is:

netsh int ipv4 add excludedportrange protocol=tcp startport=50000 numberofports=60

But I couldn’t get it to work in a way that would return the Gallery files to Hyper-V Manager. Now amount of fiddling around with TCP port reservations returned those items therein. Sigh. So I elected to run a Repair install instead using Settings > System > Recovery > Fix problems using Windows Update. This took about 15 minutes to complete and it still didn’t fix my problem. I’ll try a reset next.

Terrible Trade-offs Suck!

I’m reaching out to Lenovo in hope of some additional help. I don’t like the situation of trading System Update against Hyper-V. I will keep working until I can have both. Stay tuned. This isn’t over…


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.


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!


Lenovo Yoga Slim 7 Gets Accolades

For over a week now (11 days, actually) it’s been my pleasure to work with the excellent and affordable Lenovo Yoga Slim 7 Copilot+ PC. It’s got modest stats — Snapdragon X Elite X1E78100, 16 GB RAM, 512GB SSD and a gorgeous OLED display — but a modest MSRP of ~US$1,200. And it’s got Copilot support with a 45 TOPs NPU to take advantage of AI capabilities and planned support features. In short, it’s a pretty great ultrabook-style laptop with usable features and capabilities at the low end of the price spectrum for such devices.

Who Says Lenovo Yoga Slim 7 Gets Accolades?

Lots of reviewers give it high ratings or rankings. Paul Thurrott has written about it 4 times in the last week with positive things to say in every piece. WindowsCentral says it has the “best bright screen,” and one of its other reviewers says it “may be his favorite Windows laptop ever.” Online reviews abound with phrases like:

  • Great bang for the buck
  • Hidden Gem
  • Everything you Need
  • Amazing Display + Battery Life
  • A solid graphic design laptop

Indeed, all of these breathless exhortations match my own recent experience working with the unit myself. I’ve reviewed a LOT of Lenovo laptops (probably around 100 or so, over the past 15 years) and this one is in my personal top 3, along with the still-amazing X12 Hybrid Tablet and the equally killer P16 (Gen 1) Mobile Workstation.

Still Looking for a Killer Justification

Because MS pulled its Recall feature owing to security concerns, I’m still trying to decide if the pre-loaded AI models on the Yoga Slim 7 –which account for  fair amount of its 100+GB on-disk footprint when delivered — provide enough added value to further tip purchase decisions in its favor. That’s nothing on MS or Lenovo: I need to learn enough to figure out how to use them and what they’re good for. So it’s on me!

But as a new laptop, I think the Yoga Slim 7 represents a great value for the money (I’ve seen prices — e.g. Best Buy — at $100 lower than Lenovo MSRP). So far it’s handled everything I’ve thrown at it with grace and dispatch. It won’t run Google Drive (no ARM support yet) but seems to run pretty much everything else. If I needed to buy a laptop right now, I’d be happy to buy this one. It’s a good value and should have enough oomph to carry users for 3-5 years with ease. Given AI (and Hyper-V/VM) appetites for RAM and storage, you might want to opt in for the 32GB RAM and 1 TB SSD model. That said, I don’t see it for sale in the Lenovo Store just yet…


Font Handling Works Through Settings

OK, then: In the wake of the clean install on the Lenovo ThinkPad P16 Mobile Workstatation, I’ve been reworking some of my runtime stuff. Customizing Windows Terminal comes under that heading, near the top of my priorities. To take proper advantage of OhMyPosh, I have to add a so-called Nerd Font to that PC’s collection. Turns out this is way easy in Windows 11 because font handling works through Settings in that OS. Let me show you!

How Font Handling Works Through Settings

Once upon a time installing fonts in Windows meant visiting the C:\Windows\Fonts directory and dropping the various .ttf (typeface) files there. Then Windows could add them to its collection and display them in a variety of forms in the Control Panel element named Fonts.

And indeed, the Fonts CPL is still alive and well. But if you visit Settings > Personalization > Fonts you see the add fonts window there, with its “Drag and drop to install” instruction. Arguably this is exactly the same at using Control Panel > Fonts. But IMO it’s less work and more fun to use. At least it worked quite well for me.

What Came Out of My Visit to Fonts

Thanks to all the files in my personal account folders and their auto-backup to OneDrive, when I set up a new PC with the same MSA, it inherits all that stuff. So as soon as I visited Nerd Fonts, downloaded CakaydiaCove NF, and installed OhMyPosh on the P16, this is what Windows Terminal looks like (it’s using Jan De Dobbeleer’s eponymous theme named “JanDeDobbeleer” in its config file).

Font Handling Works Through Settings.winfetch

Windows Terminal showing winfetch and OhMyPosh at work, overlaid atop the Nerd Fonts download page. [Click image for full-size view.]

FWIW, I use the various Caskaydia Cove NF (Nerd Font) variants in Windows Terminal because they look great with OhMyPosh. But it’s both worthwhile and fun to poke around that collection to find something that you like and looks as good or better.


P16 Blows Up, Requires Clean Install

Wow! I took an unexpected detour yesterday. Upon rebooting my Lenovo P16 Mobile Workstation after CU KB5039302, it got stuck in perpetual Restart. After about an hour wasted on the spinning balls and apparently going nowhere, I forcibly rebooted the PC. Bad idea! Long story short: soon thereafter the P16 blows up, requires clean install to restore to working order. Sigh: let me explain…

Why P16 Blows Up, Requires Clean Install

I’ve seen my share of Windows crashes since the 3.1 days. This was one of the scariest. Indeed, it is the first one I can recall where even the Macrium Reflect Rescue Media couldn’t bring the system back from the dead. I could boot up the restore environment but the trackpad was MIA (fixable with an external mouse) as was the external NVMe drive where the restore image resides (not fixable at all).

So I downloaded a fresh Windows 11 23H2 ISO, turned off secure boot, and fired off a bootable UFD created using the MS MCT. That got the PC running again. But I still found myself woefully short of device drivers. A quick install of Lenovo Vantage and a set of updates later, that defect was remedied: I went from 20-odd “Unknown devices” in DevMgr to zero (0). Good!

Right now, I’ve just reinstalled Macrium Reflect, and am rebooting to be able to make a snapshot of the rebuilt system (and create new Rescue Media). After that I’ll try the lone pending update for the P16 and see if it finally goes through. My best guess is that something went sideways after that update. Indeed the P16 automatically rebuilt its BIOS when I did finally get the machine to reboot after the CU hung on me. So whatever affected the system, it was at a pretty low level.

Fingers Crossed, I Try Again…

With a new rescue disk, and a fresh image backup demonstrably at hand (see next screencap), I once again tried CU KB5039302.

P16 Blows Up, Requires Clean Install.exp-list

Today (6/26) there’s a fresh backup available!

Downloading takes some time . . . but eventually, it gets to installing . . . and about 20 minutes later (!) I’m ready to restart again,  with appendages overlapping for as much luck as I can get. So I fire off the restart and watch it count down (or up) . . . reboot . . . restart . . . spinning circle . . . and a second restart?! . . . SUCCESS!!!

That was officially weird, and I’m glad it’s behind me now.

The News Catches Up

This morning, I came across a story about KB5039302 at WindowsLatest. The title says it all Windows 11 KB5039302 breaks PCs, MS pulls the update. It specifically mentions the very “boot loop” that I describe earlier, and ties to nested virtualization. (I’m a heavy user of Hyper-V VMs on that PC so: no joke!)

The recommended fix is what I guess I should’ve done, rather than a clean install (though without trackpad drivers or access to USB-attached NVMe drives, things were challenging):

You must use the WinRE page to access the troubleshooting tools, remove the update, or do a clean install.

OK, now we know. But here in Windows-World, there’s always something around the corner looking to bite  you if it can. It certainly bit me! But that’s what Windows Insiders are for, I think . . .

Concluding Unscientific PostScript

I also understand now why the initial application of KB5039302 blew up on the P16, but why the post-clean-install upgrade worked. In the former case, Hyper-V and nested virtualization was already present and active. In the latter case, I didn’t enable Hyper-V and VMs until AFTER I’d applied the update. Turns out that was exactly the right thing to do. Better sometimes, indeed, to be lucky than good!


WinGet VPN Update Gotcha

I’ve seen it before, and I’ll see it again. In running routine WinGet updates yesterday, I noticed that my VPN (Private Internet Access, a paid-for subscription) wasn’t getting handled. I figured out why pretty quickly, too: it was because the VPN was running and WinGet didn’t want to mess with that connection. Although I’ve labeled this as a WinGet VPN update gotcha, it’s evidence of the program’s conservative outlook on interrupting something actively underway.

It’s Not Really a WinGet VPN Update Gotcha

Take a look at the lead-in graphic. You can see that WinGet knows an update is pending. You can also see that WinGet doesn’t apply that update. What you can’t see is that between the winget upgrade  command and the following winget list command, I opened PIA (Private Internet Access) and used its internal update function to perform that pending operation. Thus the winget list command shows the latest version number (3.5.7+08120). Indeed it’s the very same version number that shows in the preceding winget upgrade command as  “Available.” If you can’t see it on-screen, right-click that graphic and open it in a separate tab (it’s at bottom center).

In working with WinGet over the past few years  — it first appeared in May, 2020, and I started using it early in 2022 — I’ve observed that it will often skip over updates when the program involved is running. This happens pretty regularly with web browsers (e.g. Chrome, Edge, and Firefox, in my case), but with other applications, too.

I appreciate this approach because it minimizes the risk of lost connections or data resulting from an upgrade. It can be a little disconcerting when it happens, but quick investigation usually straightens things out in short order. Keep up the good work, people!