Category Archives: Windows 11

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

24H2 Compatibility Holds Block WU

Leave a comment

OK, then: thanks to Paul Thurrott, I think I know why my half-dozen Windows 11 23H2 PCs are getting no 24H2 offers. Among the half-dozen “Known Issues” that could bollix such an upgrade is an item named Fingerprint sensors might experience problems after a device is locked. And wouldn’t you know it: every one of my Lenovo laptops that could get the offer has one. And now I know: 24H2 Compatibility holds block WU from offering 24H2 to such PCs. You can see the issue label and first ‘graph of text as the lead-in graphic above.

When 24H2 Compatibility Holds Block WU…

One can always decide to upgrade forcibly if WU declines to make an upgrade offer. That’s what I did on the Lenovo ThinkPad P16 Mobile Workstation — which includes a fingerprint sensor and a Windows Hello IR camera. And indeed, it’s been running 24H2 since October 2 without issues or hiccups.

If you decide you want to upgrade ahead of WU offers, just be sure to make an image backup beforehand. That way, if anything goes sideways, you can reboot to WinRE and run a repair or rescue disk (Macrium Rescue Media, in my local cases) to restore that image. It takes 3-7 minutes to make such an image on my PCs, and up to 15 minutes to restore same. Well worth it IMO, to sidestep potential or actual trouble when needed.

In the meantime, I’m standing pat on my other Windows 11 23H2 PCs (both test and production units) waiting to see how long the compatibility holds will persist. If history is any guide, it’ll probably take another month or three before that happens. Stay tuned: I’ll keep you posted!

Facebooklinkedin
Facebooklinkedin
Cool Tools, Insider stuff, PowerShell, Recent Activity, WED Blog, Windows 11

WinGet Discord Update End-Around

Leave a comment

I absolutely love Microsoft’s built-in package manager WinGet. But occasionally things happen when updating application that it can’t (or won’t) handle. As you can see in the lead-in graphic, it cheerfully discloses in red that Discord “…cannot be upgraded using winget.” Indeed, its own built-in update facility did nothing to get me to version 1.0.9165. Thus, my only shot at a WinGet Discord update end-around was the tried-and-true uninstall-reinstall maneuver. That worked, as you can see…

Why Use a WinGet Discord Update End-Around?

Short answer: because it worked. Apparently, it’s uninstaller is smart enough to leave user account information alone. Even though I uninstalled the old version and then installed the new one, it carried over anyway. I’d been worried I’d have to set accounts back up, but no. Everything came up as it should’ve even after an “out-with-the-old, in-with-the-new” operation had completed.

I’m counting myself lucky in this case. There are plenty of other applications that don’t ask if you want to keep personal, account and config info. Then they cheerfully wipe all that stuff out as part of the uninstall process. That makes getting back to where one started a little more time-consuming, especially when a reinstall requires account, password, and possibly even other information to complete.

What’s with Discord’s Pinned Status Anyway?

Notice my attempts to unpin Discord reported “There is no pin for package Discord” (line 7 in the intro graphic). In the past, WinGet has often reported it can’t update Discord because the app is pinned. That’s an experimental feature in WinGet that prevents ordinary syntax for updates from working on certain apps.

Contrary to expectations, though, Discord wasn’t pinned. Yet WinGet couldn’t update it, either. Because the built-in updater didn’t do anything when I tried it (right-click on the notification area icon, then select “Check for updates…” in the resulting pop-up menu), I didn’t have a lot of other options. Thus, I’m grateful that the remove-replace approach did the trick. As you can see from the name of the package downloaded, I did wind up with version 1.0.9165. That’s just what I wanted.

Good thing one can sometimes get lucky here in Windows-World. Glad to have this behind me with no apparent ill effects.

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

Assistant Handles 24H2 Upgrade

Leave a comment

OK, then: I read this morning that MS dropped the “official” 24H2 release yesterday. “This time,” I thought to myself, “I’m taking a different approach.” From the Download Windows 11 page, I grabbed the Installation Assistant. Prosaically enough, it’s named Windows11InstallationAssistant.exe. File properties show today’s date for creation and modification, so I’m hopeful it will get me to 24H2. But I’m still wondering if the assistant handles 24H2 upgrade as expected, or not. Right now it’s going into its initial restart.

Deciding if Assistant Handles 24H2 Upgrade

If you look at the lead-in graphic it shows the Assistant in phase 3 of the upgrade process — namely 75% through installing the new stuff. After this got to 100%, I rebooted that PC (Lenovo ThinkPad P16 Gen 1 Mobile workstation). It’s now 30% through the post-reboot install process (white  text, spinning arrow, black background).

…Aaaaaand then, it stayed at 30% long enough for me to finish a round of Backgammon waiting for it to complete. But complete it did, only to drop into the OOBE portion of the install next. A couple of minutes later, I had a Windows 11 desktop. But which version is it? Here’s what winver says:

Looks like the Installation Assistant is a workable way to get to 24H2 from 23H2, if you’re of a mind to do that. And it also looks like indeed the upgrade is officially out. I’ll go some exploring and report my findings in tomorrow’s blog post. In the meantime you could try it yourself to see what happens… Cheers!

 

Facebooklinkedin
Facebooklinkedin
Copilot+ PCs, Insider stuff, Recent Activity, Windows 11

Onscreen Keyboard Lacks Copilot Key

Leave a comment

Consider this: Copilot itself tells me that my ThinkPad T14s Gen6 Copilot+ laptop should show a Copilot key on its onscreen keyboard. It definitely has one on its physical keyboard: I can see it right now, plain as day. But none of the fixes Copilot recommends gives me such a key, nor can I access settings for that keyboard either. As you can see in the lead-in screencap, the onscreen keyboard lacks Copilot key (it would normally appear between Right-Alt and Right-Ctrl on the bottom row). Sigh.

Does It Matter If Onscreen Keyboard Lacks Copilot Key?

Not really, because the Copilot icon is pinned to the taskbar by default. I’ve always been able to open it with a single click anyway. But what I find interesting is that Copilot itself says there SHOULD be such a key on the onscreen keyboard. It’s clearly not visible.

Copilot also says I should be able to access Settings for the onscreen keyboard as well. But when I open the On-screen Keyboard menu, it shows me only options for Restore, Move, Size, Minimize, Maximize and Close. No Settings anywhere, nor does right-click help, either.

It Gets More Interesting at MS Learn

So I truck over to MS Learn to examine its article Get to know the touch keyboard. It offers versions for both Windows 10 and 11 (the preceding link is for 11, because it’s the only one with Copilot key capability AFAIK).

There’s an interesting sentence in this document though. It says “Select the keyboard settings icon in the upper-left corner of the touch keyboard to view and switch between options.” That’s the same thing I’ve been doing to try to access Settings. I don’t see the things it tells me I should see.

I’m left to draw one speculation: perhaps Lenovo didn’t update the onscreen keyboard for Windows 11 (24H2 or even earlier versions). I jump onto the P16 Mobile Workstation (23H2 Build 22631.4169). It shows me the exact same onscreen keyboard, with the same missing items. And indeed, it’s identical to the onscreen keyboard I see in Windows 10, too, with the same top-left icon menu and behaviors. Now, I think I have a clue…

Emailing Lenovo to ask about this. If I learn anything interesting I’ll be back in touch in this post… Isn’t that just the way things sometimes go, here in Windows-World? You betcha!

Facebooklinkedin
Facebooklinkedin
Device drivers, Insider stuff, Recent Activity, Updates, WED Blog, Windows 11

KB5043145 Throws Interesting Stopcode

4 Comments

Here’s one I’ve not run into before: Stopcode 0XEA. It shows up on BSODs as THREAD_STUCK_IN_DEVICE_DRIVER. The intro screencap show results running that stopcode against the MS error code lookup tool. Basically, it says a device driver thread is stuck in an infinite loop. (See the MS Bug Check 0xEA page for further deets.) Apparently, it’s showing that optional CU KB5043145 throws interesting stopcode and BSOD/GSOD  on some PCs. Notably, says WindowsLatest, that includes some 2022 and 2024 Asus laptops.

If KB5043145 Throws Interesting Stopcode, Then What?

If that happens to any of your PCs, you’ll need to boot to WinRE on bootable media, and use the “Uninstall Update ” item in its Advanced Options menu to uninstall it from your Windows Image. When a PC won’t boot because the image is damaged, that’s pretty much the only repair that works, short of a clean Windows (re)install.

Alas, this is eerily reminiscent of the July 19 Crowstrike update, which took down 8+million Windows PCs. Fortunately, it doesn’t seem to be anywhere near as widespread nor impactful as that incident turned out. That said, Windows users should be aware that this optional CU could force recovery and repair to undo. Fortunately, such updates do not typically affect production environments, where update get tested and vetted long before they get scheduled for some update window.

But gosh, it seems like we’ve run into rather more problematic updates that is typical in 2024. FWIW, the update hasn’t caused any trouble on those test machines here at Chez Tittel where I can make it run. Even so, it’s a great reminder to be careful out there in Windows-World…

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

Outlook Search String Magic

Leave a comment

This is an IDKYCDT item. I work with Outlook every day, and have done so since the 1980s. You’d think I’d have learned a long time ago about how to make Outlook search string magic stand up and bark. Not so: in trolling the Internet today I learned about the “isread:no” string in Outlook search, which shows you all unread messages for the current search focus. Indeed, it’s the bomb when applied to my inbox, where things can sometimes pile up alarmingly.

You can see a sample search string of this type in the lead-in graphic. It reads the sender field (from:) in messages, and shows those that match what’s on the other side of the colon. In this case, recent stuff from one of my main project editors at Actual Tech Media.

Exploring Outlook Search String Magic

By itself, this isread:no string is a big boon to my productivity. But naturally, I’d like to find a compendium of all such strings. The closest I could come as an MS Support note entitled “How to search in Outlook.” It lists a pretty good number of such strings. But it isn’t really structured, appropriately organized, or complete in that specific area . Ditto for another support note “Use Outlook’s built-in search filters.”

In fact, the more I look around, the less I’m able to find a useful resource. I’m thinking I should reach out to the father of the AskWoody newsletter — Woody Leonhard himself, author of many books on Word and Office — and see if he can point me in the right direction. Who know where this may lead? Can’t wait to find out.

Stay tuned!

Facebooklinkedin
Facebooklinkedin
Hyper-V and VMs, Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 11

Chkdsk /f Fixes DISM Issues

Leave a comment

Here’s an interesting item. As part of routine maintenance, I ran DISM /online /cleanup-image /analyzecomponentstore on the P16 Mobile Workstation this morning. Imagine my surprise when it threw  “Error 2; The system cannot find the file specified.” at about 80% complete. I’d never run across this one before. But a Google Search soon revealed that this happens when DISM encounters a corrupted entry in the component store. MS Answers also reported that, nearly always, chkdsk /f fixes DISM issues of this kind. So that’s what I tried: as you can see from the lead-in graphic, it worked!

How Chkdsk /f Fixes DISM Issues

This particular disk scanning operation repairs any corrupted files it finds, if it can. That has me wondering if sfc /scannow might not have had the same salutary effect. I think that’s at least possible, so I’ll have to try it next time around. The only follow-on is that repairs to the C: drive (especially for the kinds of files that DISM cares about) must run while the Windows OS image is not in use. That means scheduling that check and repair during boot-up before the OS takes over operation of the PC (that is, while the boot loader is running things).

Thus, I had to reboot the P16, and watch the check run as a pre-boot task (large white text against a black screen). Here’s a capture from inside a Hyper-V VM (otherwise, it’s challenging to grab boot-time screens from Windows).

Once that repair had completed, I was able to run the previously inoperative DISM command without trouble. Every now and then, one gets lucky in Windows-World. This time, the repair worked just like it was supposed to. Good stuff!

 

Facebooklinkedin
Facebooklinkedin
Copilot+ PCs, Insider stuff, Recent Activity, WED Blog, Windows 11

ARM 24H2 Shows Spurious Reclaimables

Leave a comment

When I laid hands on my first Copilot+ PC — the inestimable Lenovo Yoga Slim 7x in late June — I checked DISM /analyzecomponentstore on that machine right away. Unlike other versions of Windows 11, the ARM version of 24H2 showed no such anomalies. But last week, while running a routine cleanup on the ThinkPad T14s Gen 6 that represents my current Copilot+ PC capability, there they were. 14 of ’em, as you can see in the lead-in graphic in which ARM 24H2 shows spurious reclaimables. Notice the successful clean-up ahead of that report, which is what lets me label them spurious.

What ARM 24H2 Shows Spurious Reclaimables Means

There’s something odd that happens with certain Windows Updates. It causes dism /analyzecomponentstore to report some number of apparently bogus reclaimable packages as you can see in the graphic above. For x64 PCs that number is usually 13; ARM goes one better, and takes that total to 14.

So far, I’ve seen no actual pathology in Windows 11 related to this odd report. One can make this report go away by performing an in place upgrade repair install (Start > Settings > System > Recovery, then clicking “Reinstall now” under the “Fix problems using Windows Update” heading. But those spurious updates have a way of reappearing after the next CU, so I’ve let go of my OCD on that front and learned to live with this oddity.

It’s been that way for x64 versions of 24H2 pretty much since it first appeared, and even shows up on some of my 23H2 PCs as well (both test and production instances). For a while, I thought the ARM version was exempt. But the lead-in graphic argues otherwise. This comes as no great surprise to me, but I’d hoped that the ARM version of Windows 11 might avoid this phenomenon.

Isn’t that just the way things often work, here in Windows-World? You betcha!

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

Canary Gets New Clock-based Widgets

Leave a comment

With the arrival of Build 27695, Windows 11 Canary gets new Clock-based widgets. One is named Countdown, the other Timer, so their clock affiliation should be obvious. One or both may be pinned quite easily into the Widgets column at the left-hand edge of the pop-up Widgets panel. Hint: Launch this by entering WinKey+W at some keyboard.

When Canary Gets New Clock-based Widgets, Then What?

You can see what these simple-seeming widgets look like by default in the lead-in graphic (Countdown left, Timer right). Inside the Widget Panel, you must click the top-line “+” (Plus sign) to open the Add a widget display. Then, you can pin either or both widgets, and they’ll start showing up in the Widgets Panel.

It’s always nice when MS starts adding functionality to its facilities. For a long time, that collection was pretty limited. Right now the count is up to 14: Counddown, Dev Home, Family Safety, Focus session, GitHub, Instant Play, Phone Link, Photos, Sports, Timer, Tips, Traffic, Watchlist, and Weather.

And if you click the “Find more widgets” option at the end of the Pin widgets list, you’ll be wafted off to an MS Store page named “Find your next widget.” Highly recommended: it offers better — and more nicely organized — widget listings than a simple search inside Store on “Widgets” offers.

Good stuff: too bad I can’t figure out a URL for that access. You’ll just have to follow the button inside the Widget panel as I did to get there. Enjoy!

AFD  until Tuesday, September 24

Later today, I’m going in for cataract surgery on my left eye. If all goes well — and they tell me this routine procedure has a 95-99% success rate — I’ll be back at the keyboard next Tuesday. Wish me luck!

BTW, AFD means “Away from My Desk.” I’m not sure if it’s a legit acronym, but I used it to shorten that heading length. Hopefully, it at least makes sense. Happy trails…

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

OneNote Updates Sticky Notes

Leave a comment

Here’s an interesting tidbit. If you install or upgrade OneNote on a Windows PC, it will also upgrade to a new version of Sticky Notes. Check the lead-in graphic: it labels this new version as such, and the old version (lacking that same (new) label)shows up in the Start menu. Hence my assertion that OneNote updates Sticky Notes. But wait: there’s more…

Exactly How OneNote Updates Sticky Notes

This dual appearance persists even after you add the (New) version via a OneNote update (or install). If you quiz that version for its About info, you’ll get the OneNote for Microsoft 365 info . It shows up as (line broken for WordPress readability, original is a one-liner):

Microsoft® OneNote® for Microsoft 365 MSO
(Version 2408 Build 16.0.17928.20114) 64-bit

OTOH, if you quiz the older version, it calls itself a UWP app with version number 6.1.20 (and a 2020 copyright date). Go figure!

Two Versions, or One?

If you want to keep both versions, that’s fine with me. If you want to lose the old version, I’d recommend using WinGet to uninstall same. The name of this app is “Microsoft Sticky Notes” so you need to enclose it in quotes (internal spaces) to get it to work. Or, you can uninstall it using the app id, as follows:

winget uninstall --id 9NBLGGH4QGHW

instead. Your choice. I did the latter on one of my X380 test PCs and it worked correctly. Now, I see only Sticky Notes (New) in the Start menu. Just for grins, I did likewise on my Windows 10 production PC: it behaves in exactly the same way, so this works for both OSes. Cheers!

Facebooklinkedin
Facebooklinkedin