Category Archives: Windows 11

Windows 10 Keeps PowerToys ComPal Error

On April 10, I blogged about how a new release of PowerToys (v0.90.1) apparently fixed a “Class not registered” error for the Command Palette from the previous version (v0.90.0). Alas, while ComPal (as I like to abbreviate this tool) is now rock-solid on my Windows 11 PCs, it’s still throwing errors after restart on my sole remaining Windows 10 desktop. That’s why my title here reads “Windows 10 Keeps PowerToys ComPal Error” — you can see the aftermath in Reiability Monitor as the lead-in screencap above.

Why Windows 10 Keeps PowerToys ComPal Error

Look at the screencap. Notice the Problem Event Name is “MoAppCrash.” This means a Modern App (aka UWP app, usually an MS Store App of some kind) has crashed. In this case it’s the PowerToys Command Palette user interface (MicrosoftCmdPal.UI.exe). Copilot says common causes include faulty, outdated app versions, corrupt system files or missing dependencies, conflicts with Windows updates, and issues with DLL files. My bets are on conflicts with Windows updates and/or issues with some DLL needed for ComPal to run.

I just tried to access ComPal on the affected Windows 10 machine. At first, it refused to respond to its shortcut (WinKey+Alt+Space) for related settings, But when I disabled, then re-enabled ComPal itself, that capability woke up and started working. So did the utility itself, without any easily discovered limitations.

What about Windows 11?

I have — and see — no such issues in Windows 11. So I’m forced to speculate that this is just a Windows 10 hiccup of some kind. Fortunately, once I disable, then re-enable ComPal, everything seems to work fine. There’s obviously some kind of minor gotcha at work, but it’s easy to get around.

Isn’t that just the way things work sometimes, here in Windows-World? Fortunately, even when the path to success isn’t automatic, or even a straight line, a small dogleg often does the trick. And so it was this morning…

Facebooklinkedin
Facebooklinkedin

Rebuilding P16 Windows 11 24H2

Allrighty then: I got tired of seeing odd, unfathomable and stuck packages in the component store. That image resides on the Lenovo ThinkPad P16 Mobile Workstation. So yesterday, I set about rebuilding P16 Windows 11 24H2 to come up clean. Let me explain what I did, and why I did it. The whole story shows in the lead-in graphic. It depicts the image going from 10 reclaimable packages to 2 and then to zero (0): clean! But you’ll  need keen eyes (or be unafraid to grab this screencap and make it readable.)

3 Steps To Rebuilding P16 Windows 11 24H2

STEP 1: My first step was to visit Settings > System > Recovery and then click the “Reinstall now” button to kick off an in-place upgrade repair on the P16’s suspect Windows image. For the record, it failed my “sniff test” because it kept showing 4 reclaimable packages that wouldn’t surrender to DISM /online /cleanup-image
/startcomponentcleanup.
The reinstall took about 45 minutes to complete, but required little or no effort from yours truly.

STEP 2: My second step was to run the aforementioned DISM …         /startcomponentcleanup command and see what remained. As I expected, that brought the number of reclaimable packages down from 10 to 2.

STEP 3: My March 21 blog post “Remove Package Kills Spurious Reclaimables” explains this use of a specific DISM /Remove-Package target that’s responsible for 2 spurious packages showing up in a canonical Windows 11 24H2 production image. TLDR version is: a deeply superseded package is stuck in WinSxS, but a single command removes both spurious reclaimables in one go.

The results appear in the fine print at the bottom of the lead-in screencap: a clean version of Windows 24H2 Build 26100.4061, with zero (0) reclaimables in the component store. Good-oh!

Facebooklinkedin
Facebooklinkedin

Windows Start Soliloquy Gets Fanciful

MS has started a new design blog under the general heading of “Behind the Surface.” It’s entitled “Start, Fresh –Redesigning the Windows Start menu for you.” The “Windows Design Team” is named as the author, rather than one or more specific individuals. It’s an interesting read, if a bit too breathless and wonder-struck for me. Indeed although this Windows Start soliloquy gets fanciful and overdone, IMO, it’s still worth your perusal.

Where (and How) Windows Start Soliloquy Gets Fanciful

In a list of so-called “guiding stars” the blog states four key principles driving Start Menu design. These serve as the lead-in graphic above, so I don’t repeat them. MS makes much of the work it took to rework the Start Menu. Those efforts presumably fit into the upcoming release of Windows 11 25H2 later this year. Here’s a representative quote from the post, likely from a user interaction during that process (note the tone and diction, please):

Help me find my apps faster. Let me bend Start to fit the way I work. And please—keep the magic, don’t lose the soul.

You’ve got to read the post and check out its images, tables, and language to really make sense of what it says. The key conclusions (and design changes) should include (each bolded item below is quoted verbatim from the blog post, sans quotation marks):

  • Dynamic recommendations: “files and apps” that “surface exactly when they matter.”
  • More and better views for all apps: Repositioned at the top of the Start Menu, you can choose “between logical categories, a neat grid, or the familiar A-Z list.”
  • Mobile content, gently blended: Integration with mobile devices mentions both Android and iPhone and stresses how you can reach out from the desktop to a mobile device.
  • Personalization, elevated: Stresses user’s abilities to zoom in on, or ignore, individual Start Menu sections, and to size it to match available screen real estate (bigger on big monitors, smaller on littler ones).
  • Under-the-hood speed: A commitment to making Start an “accelerator of your day” that loads “in a snap” not “dragged by lag.:

Generally MS makes an ongoing commitment to keep listening to user input and adjusting to what users have to say. Overall their goal is to meet their mantra for what the Start Menu should be:

Everything you need, right here, ready when you are.

This Should Be Interesting…

The rah-rah nature of the blog post and its overall tone and language aside, MS is putting itself out there. In the broadest of strokes they’re promising to improve the Start Menu, and to keep making it better. It will be interesting to see how that plays out in upcoming Insider Preview releases — and ultimately, in 25H2 itself. I’ll be watching — and sharing my observations — along that path. So will lots of other Insiders and other users. Stay tuned!

Note: here’s a shout out to Sergey Tkachenko at WinAero.com, whose story this morning pointed me at the MS blog post. Thanks! For a vastly different take on what’s going on here, see what Paul Thurrott has to say about this blog post.

Facebooklinkedin
Facebooklinkedin

Dev Home Leaving Soon

I’ve been away on a family trip to Boston. Upon returning to my desk this morning, WinGet brought a Dev Home update to the Lenovo P16 Mobile Workstation (see lead-in graphic). “Hmmmm,” I thought, “Isn’t Dev Home leaving soon?” Indeed it is, as per MS Learn as you can see in the next screencap.

With Dev Home Leaving Soon, What’s Next?

Good question! In the afore-linked MS Learn item, MS announced last January that Dev Home would be discontinued in May, 2025. I’ve been “staying tuned” for more info since then, but so far such info has not been forthcoming.

Well: May is here and I still can’t find anything new about Dev Home’s impending retirement. Ditto for which features will be preserved and where within Windows they’ll show up. Of the tools that Dev Home brings to the Windows party, these are the ones about which I’m most curious:

1. Support for ReFS volume creation in Windows 10 and 11.
2. GitHub connection with repos for access to tools and packages.
3. The Hosts File Editor and Registry File Editor utilities.
4. Consolidated view of development projects via its dashboard.

In January, MS dropped the first shoe to warn developers (and other interested parties) that Dev Home would be yanked in May 2025. Now that it’s May, the silence while waiting for that next shoe is nearly deafening. All I can say is: “Please give us a clue or two, Microsoft: where are the best bits of Dev Home going to wind up?”

Facebooklinkedin
Facebooklinkedin

Snipping Tool Text Extractor Rollout

Windows certainly has its weird and wonderful ways. I was forcibly reminded just now, when looking on a Canary test PC to see if the next Text Extractor tool was on my Snipping Tool toolbar. While you can see it in the lead-in graphic for this story, I couldn’t see it on my PC right away. At first, understanding that MS is conducting a new Snipping Tool Text Extractor rollout, I thought I might be on the outside, looking in. Not so: let me explain…

Working Thru Snipping Tool Text Extractor Rollout

When I first checked the app and saw the toolbar unchanged, I jumped to the assumption that my PC wasn’t in the first rollout cohort. Then I remembered: Snipping Tool is a Windows Store app. So I went to the store and clicked on the Downloads button. Nothing had been updated since 4/14 (two days ago), so I clicked the “Check for updates” button.

Guess what? There was indeed a new version of Snipping Tool ready for download. Once that step was complete, and a quick install later I saw what MS announced in its April 15 blurb. Yes, Virginia: there is now a text item in the Snipping Tool toolbar. Again you can see it in the second from right position in the intro image. MS even provides an intro blurb to tell you what this toolbar element does.

I checked it, and it works as advertised. Makes the steps involved in grabbing text from an image and dropping it into a file ever so much easier and faster. Thanks, MS for giving us something many of us can use and enjoy (your humble author included). Visit the MS Store on Canary and Dev Windows 11 PCs and you, too, can partake of this neat new feature. Cheers!

Facebooklinkedin
Facebooklinkedin

Reinstall Now Builds Current Images

Last Wednesday, I blogged that a repair install for Windows 11 unsticks WU. As I think about what that really means, I want to emphasize that using Settings > System > Recovery > Reinstall now does something remarkable. That is, Reinstall Now builds current images for whatever version Windows Update is serving at the time. It used to be only UUPDump.net could do that, by slipstreaming all the latest updates into the base Windows image (24H2 in this case).

How To See That Reinstall Now Builds Current Images

If you look at the Settings > System > About info that appears in the lead-in graphic, it tells pretty much the whole story needed for evidence. You can see it shows version 24H2, Build 26100.3775 with an install data of 4/9/2025. That’s the very day I ran the repair install, and the build number matches what follows in the wake of the latest CU (KB 5055523 — see the parenthetical phrase at the end of that title).

What makes this facility remarkable is that UUPDump.net has to build a Windows image for the baseline release, then apply as many updates — the latest security, cumulative and servicing stack items — as it needs to bring the image current. This requires some time-consuming DISM manipulations that can take an hour to complete. Interestingly, the WU facility handled the entire repair in about 35 minutes.

I still recommend UUPDump.net as a way to create an ISO for some specific (and non-current) Windows Build. But if you need to repair a current version, it looks like built-in Windows 11 recovery really is your best choice. Good to know! That’s why I’m telling you…

Facebooklinkedin
Facebooklinkedin

Leave Post KB5055523 Inetpub Folder Alone

I’d seen reporting on this yesterday, along with blithe assumptions about related cleanup (deletion). Today, MS has published a CVE-2025-21204 security note that explains what’s going on, and specifically advises users to leave post KB5055523 Inetpub folder alone — and intact.

Here’s a direct quote from the afore-linked source:

After installing the updates listed in the Security Updates table for your operating system, a new %systemdrive%\inetpub folder will be created on your device. This folder should not be deleted regardless of whether Internet Information Services (IIS) is active on the target device. This behavior is part of changes that increase protection and does not require any action from IT admins and end users.

Note: KB5055523 is a security update for Build 26100.3775 (production level Windows 11 24H2) released as part of the Patch Tuesday collection on April 8, 2025.

Why Leave Post KB5055523 Inetpub Folder Alone?

It’s part of the infrastructure upon which MS relies to fend off the named vulnerability. In other words, if the folder is present, MS can use it to protect against potential attacks. MS is sometimes fond of leaving folders behind in the wake of various installs (especially feature upgrades). Anything not needed is usually fair game for Disk Cleanup or the Windows Store PC Manager app.

That said, some OCD-friendly Windows users (you know who you are) relentlessly clean up things just because they must. This is apparently a case that flies against that impetus. MS, in this particular case, says “Leave it alone.” I guess I shall, and you probably should, too.

Though the Inetpub folder is empty after the update runs (see next screencap) it is meant to be and stay there. You’ve been warned! Indeed, as you can see, it’s properties are also set to “Read-only.”

The ‘Read-only’ status signals weakly that this item should stay put.

Final Warning: Don’t!

I’ve seen various online sources assert that it’s OK to delete this folder because it caused no observable ill effects on their test PCs. If what MS says about Inetpub’s presence or absence on a PC is true, you don’t want to sight what could happen if it were to be deleted. Let this particular sleeping critter keep snoozing, please.

Facebooklinkedin
Facebooklinkedin

Repair Install Unsticks WU

For the past 5 weeks or so, I’ve been working with the Lenovo ThinkPad T14s Gen5 laptop. For the last two weeks, updates have been stuck, with an error code that indicates file download issues. The usual repair techniques haven’t helped, either — namely run the troubleshooter or the reset & re-register Windows Update components. So this morning, with a new cumulative update out, I installed the latest Windows 11 24H2 repair version. That built-in repair install unsticks WU and catches me up with pending stuff, as you can see in the lead-in graphic.

Repair Install Unsticks WU Trades Time vs. Convenience

The problems with the afore-mentioned techiques (troubleshooter, reset&re-register) is that they take multiple steps and a bit of effort. Double that when, as often happens, remediation is also needed. It took a while to click Start > System > Recovery > Reinstall now and then work through that process. But the details took care of themselves and I didn’t have to do anything except fire it off to make it work.

In the end, this turned out to be easier and less vexing than the other techniques. Its results were also immediately apparent, and entirely positive, once completed — as you can see in the lead-in graphic. That said, Update History does become a little opaque when you conduct this repair. Here’s what it says now:

It doesn’t show the problem CU installed and running. It simply shows that “Windows 11, 24H2 (repair version)” got installed today. Of course, that means the installer used the latest version of the Windows image — including those problem CUs — as the install base. So really, it’s all fixed now. You just have to know what this reference means.

And ain’t that just the way things go here in Windows-World? The problem may be solved, but a hint of mystery — or is it confusion? — remains. Cheers!

Note Added 4 Hrs Later: Get-Hotfix Tells the Story

Reading through ElevenForum.com threads just now, I learned that running Get-Hotfix in PowerShell will shows installed KBs from a repair install image, to wit: This shows that various updates and security updates are indeed present in the newly repaired image. The current build number for that PC — 26100.3775 — also shows that KB5055523 has been applied. Good stuff…

Facebooklinkedin
Facebooklinkedin

Dell Updates Replaces Power Plan

Yesterday afternoon, upon returning from a lovely drive into the Texas Hill country “the Boss” remarked that she now had to power on her Dell Optiplex D7080 to wake it from sleep. “Hmmm” I thought to myself “I bet something changed with sleep/wake/hibernate.” It sure did: a recent item via Dell Command Update installed and selected a “Dell” power plan. Alas, when Dell updates replaces power plan, their chosen alternative forced use of the power button to initiate wake. Easily, easily fixed: read on for those details, please…

When Dell Updates Replaces Power Plan, Switch Back

As you can see in the lead-in graphic, there’s a new power plan in the mix. It’s named Dell and it had been selected by default after some recent item ingested through the Dell Command Update utililty. To inspect the contents of a power plan in PowerShell, two commands are needed: the first provides a list of all plans, the second inquires about the contents of a specific plan through its GUID. Those commands are:

powercfg -list
powercfg -query <GUID>

Fortunately, the list output includes both human readable names and GUIDs so I was quickly able to get the deets for the Dell power plan. And sure enough, as I suspected, it had a setting for hibernate after 1 hour of idle time. That was the key!

Wake from Hibernate Requires a Poke

A poke of the power button, in fact, which was just what the boss didn’t like. So, as you can see from the lead-in graphic, I switched her back over the the High Performance plan she’d been using before Dell Command Update made that switch. It doesn’t include hibernate, and it wakes on keypress or mouse click from sleep. That’s what she wanted. And now, that’s what she’s got.

Facebooklinkedin
Facebooklinkedin

X380 Yoga Can’t See QMR Hotfix

I shoulda known. When MS unleashed it Quick Machine Recovery (QMR) capability earlier this week, it said it would  provide a test fix so IT admins could try out its automatic repair facility. I blogged about enablement instructions on Monday, and have been waiting for that fix since then. I just learned that MS is gradually rolling it out to Beta Channel Insiders running Build 26120.3671. But alas, my test PC is on the outside, looking in. Certain units should find the test fix under a new “Hotfix” category in Settings > Windows Update > Update History. To my chagrin, my test X380 Yoga can’t see QMR Hotfix (neither category nor test item), as (not) shown in the lead-in graphic.

X380 Yoga Can’t See QMR Hotfix: Wait for It!

Gradual rollouts are unpredictable as to when a feature might appear. But they are pretty reliable, in that it should appear sometime. One just has no idea when that might be. If you look at the lead-in graphic you’ll see that it lists out:

  • Feature Updates
  • Quality Updates
  • Driver Updates
  • Definition Updates
  • Other Updates

When the QMR-aimed Hotfix finally makes it to the X380, a new category named Hotfix will appear. Then, should I use the reagentc.exe /BootToRe instruction to reboot the PC and tell it to look for and apply same, that should show me by example what it looks like and how it works.

So far, nada!

Standing By for My Turn

As seems to happen to me more often than not, I’m going to have to exercise patience and make sure that I keep checking for the Hotfix category and its test item in the Update History on the X380. Don’t know when that might be, but I’ll report in when that happens. Stay tuned!

Facebooklinkedin
Facebooklinkedin