Category Archives: Windows Update

Gradual Rollout Strikes Notification Update

I guess it’s inevitable. Upon reading about how Windows 11 25H2 finally extends notification area pop-ups to non-primary displays on multi-monitor rigs, I checked my own production PC. This is, of course, the Asrock B550-based Ryzen 7 5800X with its dual Dell 2717 UHD displays. And wouldn’t you know it? Works on the primary, but not the secondary. As I check the KB5065789 announcement, I learn why. Once again, gradual rollout strikes notification update, and my PC is NOT in the forefront. Sigh.

Explaining Gradual Rollout Strikes Notification Update

If you look at the lead-in graphic, you can see the text from the afore-linked announcement. It reads:

​​​​​​​[Notification Center] New! The Notification Center functionality is now available on secondary monitors. To open it, select the date and time in the system tray on the taskbar. With the August 2025 non-security update (KB5064081), you can also show a larger clock with seconds above the calendar.

What that doesn’t show, alas, is that this occurs under the “Gradual Rollout” heading in that announcement. In turn, that means this feature is trickling out to 25H2 PCs, not all of them at once. I’ll hook a second monitor up to one of my Copilot PCs and see if that machine gets the new functionality. Nope, doesn’t work when I used HDMI to connect up a second monitor to the Lenovo Copilot+ AIO9i model, either.

It Remains the Hardest Part: Waiting…

I’m just going to have to wait for MS to flip whatever switch it takes to get one  or more of my 8 or so 25H2 PCs to attain this capability. I’m no stranger to this position in the Windows-World feature sweepstakes — that is, on the outside, looking in. Sigh again.

 

Facebooklinkedin
Facebooklinkedin

Copilot+ PCs Hit 25H2

OK then, yesterday was Patch Tuesday. It included amidst its offerings the eKB enablement package KB5054156. All (both) of my current Copilot+ PCs got the upgrade. The Intel-based AIO got it automatically, with an after-hours upgrade. I just used the self-installing upgrade package (.msu) for ARM64 on the Snapdragon X based ThinkPad T14s Gen 6 laptop. The whole process: download, GUI install, post-GUI install and reboot to desktop took less than 2 minutes. I’ve been waiting for this for some while, so I’m glad that, finally, my Copilot+ PCs hit 25H2 version levels.

When Copilot+ PCs Hit 25H2, Then What?

Time to poke around in Settings (and elsewhere) to see what’s different and potentially new. I just learned that because the AIO doesn’t have a battery I don’t have access to the new Power Mode settings under Settings > System > Power & battery. Go figure!

On the Snapdragon X PC, however, the new “Best Power Efficiency” and “Best Performance” options do indeed appear. I opted into the latter (“Best Performance”) to see what impact it might have.

Learned something else amusing: because I’m remoting into the AIO, I can’t mess with Recall settings (nor, presumably, other AI stuff as well). Apparently, I need to set up Windows Hello authentication locally to make that happen… goes off to do so … OK now it’s working through RDP.

Adventures Ahead, For Sure!

Copilot tells me it’s gained new capabilities (as have other MS app) especially via Click to Do. There’s a new “help agent” in Settings that can actually manipulate Windows configurations and settings to some degree. All kinds of AI stuff all over the place. Now, I just need to find the time to actually DO this. And wouldn’t you know it? Right now, I’m swamped in paying work, so I have less time to learn and play. A welcome change of pace in Windows-World, but one that may frustrate me for a while…

Stay tuned: as soon as I have more time, I’ll share what I’m learning.

Facebooklinkedin
Facebooklinkedin

25H2 Enablement Blazes on Lenovo AIO9i

I’m working with a Lenovo Copilot+ PC review unit these days: it’s a snazzy Yoga All-in-One AIO9i. It comes equipped with an Intel Core Ultra 7 258V (8 cores: 4 each P-cores and E-cores/8 threads), integrated Intel Arc 140V GPU, 32 GB LPDDRx-8533, Hynix OEM PCIe x4 NVMe SSD, and more. It also has Windows 11 Pro for Workstations installed. I’m not sure what makes this PC so fast, but 25H2 enablement blazes on Lenovo AIO9i.

Details: 25H2 Enablement Blazes on Lenovo AIO9i

How fast? The whole process, after opting into the Release Preview channel on the Insider program, took under three minutes to complete. That means:

  • Downloading the enablement package (under 30 seconds)
  • Running the GUI-based portion of the update (under 30 seconds)
  • Reboot and post-GUI update handling (under 40 seconds)
  • Resume desktop through lock screen and login (under 10 seconds)

There are lots of reasons why this is so fast. For one. the enablement package itself is svelte (under 1MB in size). That’s because MS has already included most of the code in earlier updates, and the enablement package — as the name indicates — simply turns such stuff on. As Copilot puts it, earlier “monthly cumulative updates (LCUs) have quietly staged the new features in a dormant state.” It continues: “The enablement package simply flips the feature flags — no need to download or install new core components.”

Other contributing factors to speed:

  • No drive revalidation, no app compatibility scans, no migration of user profiles
  • As the preceding bulleted list observes, this process requires only one update to complete
  • No rollback staging or recovery partition updates are included, to reduce disk I/O and system prep times

Indeed, inspection of $WinDrive (C:) shows no Windows.old partition, as one might usually find after a version uplift. Likewise, Disk Cleanup finds only 1.53 GB of files to clean up in the upgrade’s wake. That’s much less than the more typical 25-30GB on production Windows 11 systems here at Chez Tittel when transitioning from 23H2 to 24H2, for example.

Wow: Just Wow!

I’m not sure that Windows for Workstations made any difference here, either. Despite this version in place, it doesn’t use advanced features — e.g. ECC RAM and ReFS — that might speed things up. I think this is just one very lean, mean and fast enablement package. It’s worth enrolling a test PC in the Insider Program, Release Preview Channel just to check it out for yourself. Speedy!

 

Facebooklinkedin
Facebooklinkedin

Dev Channel Gets 25H2

I started seeing some news about this last Friday — most notably at Eleven Forum. The specific item was labeled “Get ready for Windows 11 25H2.” Shoot! I’ve been ready for months. What I needed to do was figure out how to get in on that act. Turns out it’s just an enablement package for Insiders in the Dev Channel. That’s how I got mine on Saturday, once I understood what was what. You can see, in fact, that Dev Channel gets 25H2 in the lead-in screencap.

After Dev Channel Gets 25H2, Then What?

Thanks to the afore-linked Eleven Forum post, I also learned that while I couldn’t see the enablement package in Update History directly, I could see it another way. By clicking through Settings > Windows Update > Update history > Uninstall updates, I saw “Feature Enablement for Dev Channel Preview Update (KB5054156)” as you, too, can see here (at bottom):

Given that it’s an enablement package, not a full-blown OS install it’s also speedy to download and run. The whole thing took less than three minutes on the brand-new dynabook X40M2 laptop I ran it on.

I expect this release to get banged on and patched for the next three-four months. That takes us to September or October, which is when it’s highly likely that 25H2 will make it into more widespread distribution — barring unforeseen hurdles or noxious gotchas.

But hey, this is Windows-World. While we THINK we know what may happen, anything and everything remains possible. Let’s just wait and see what unfolds next. In the meantime, I’ll be exploring the newest avatar for Windows 11 — 25H2, Build 26200.5670. Cheers!

Facebooklinkedin
Facebooklinkedin

Undoing Enterprise Version WU Defaults

This morning, I read a fascinating story from Mayank Parmar at WindowsLatest. It covers the one-year grant that MS plans to offer Windows 10 users to participate in the Extended Security Update (ESU) program at no charge. Given that around half of all Windows users still run version 10, that makes sense to me. But there’s a catch: apparently this offer extends to neither Enterprise nor Education versions of Windows 10. But first, that meant undoing Enterprise version WU defaults to figure this out. Let me explain…

Why Bother Undoing Enterprise Version WU Defaults?

I couldn’t opt into the “Get the latest updates…” option in WU unless and until I used gpedit.msc to explicitly disable a Group Policy setting. But I didn’t find it on my PC where MS Learn said it should reside, instead it was an additional level down, to wit:

Computer Configuration>Administrative Templates>Windows Components>Windows Update>Windows Update for Business

On Windows Home and Pro PCs (and probably Workstation as well) the hierarchy doesn’t automatically include WU for Business. On Education and Enterprise versions it does.

Long story short, I couldn’t see “Get ready for Windows 11…” or “Get the latest updates…” until I had explicitly disabled the policy named “Select the target Feature Update version.” As I think about it, that makes sense. MS is NOT giving ESU away to government, education and businesses; the grant only goes to SOHO and individual users. The others can — and many will — pay for their coverage plans. You don’t see the enroll info that Parmar shows in his story on my PC — and that’s because it’s running Enterprise.

And apparently, those running Enterprise and Education versions will not get the free ESU offer. I’m going to stand up a Pro version VM to double-check this, but I’m betting that’s right.

And boy howdy, isn’t that just the way things go in Windows-World. There’s always a wrinkle, and sometimes you have to dig and think, and think and dig to figure out how to understand and deal with things.

Facebooklinkedin
Facebooklinkedin

Recent Rising Reclaimable Counts

Recently, I’ve been noticing that Cumulative Updates (CUs) typically leave upwards of 10 or more reclaimable packages around, following installation. If my memory is any guide, numbers from 2-4 had been more typical until earlier this year. But recent rising reclaimable counts seem all too likely these days.

So I asked Copilot about it: “Why does dism /analyzecompo-nentstore find more reclaimable packages after CU updates recently?” Imagine my surprise when Copilot cited one of my very own blog posts in response as a potential source of “deeper insights.” Wow: that’s a shock to me!

Here’s what DISM told me after I updated Windows 11 24H2 to 26100.4202 last week: 10 packages reclaimable!

Why Rising Recent Reclaimable Counts?

When I check the component store using DISM /Get-Packages after recent CUs I see numerous staged and superseded items in the listing. These are what often gets cleaned up when a following DISM /StartComponentCleanup is run. Google AI says that  recent changes to “checkpoint cumulative updates” in 24H2 means that “Future updates then build incrementally from these checkpoints, leading to smaller downloads and potentially faster updates.” Looks like it means there are more and smaller items of this kind, rather than fewer and larger ones, as under the previous regime.

Thus, I think the phenomenon is real, and reflects a change in update approach and architecture. DISM dispatches these items pretty quickly (at least anecdotally more quickly than the older approach, in my own personal experience). So all in all, I’m inclined to find this a good thing.

It’s nice when incremental changes in Windows mean improvements in the general state of Windows-World itself. Today, that’s my story — and I’m sticking to it!

Note Added 6/7: A New Top Count!

I ran DISM /AnalyzeComponentStore on the X380 Yoga just now (running 24H2 Beta Channel Build 26120.4230). It reported a whopping 21 reclaimable packages, all of which vanish after running DISM /StartComponentCleanup. See this:

I’m inclined to take this as further validation of my thesis that CUs bring more (and smaller) packages for cleanup in their wake. What do you think?

Facebooklinkedin
Facebooklinkedin

Unsticking Lenovo System Update

From May 6 through 12, I had a Lenovo System update stick in WU. That is, it would attempt to install, fail, and then push a retry button at me. Alas, that meant WU wouldn’t show me any newer updates, either. At the end of this cycle KB5058496 came along. It didn’t show up in WU, either. That’s when I found myself unsticking Lenovo system update on the Lenovo ThinkPad Yoga X380 where it happened. How did I do that? I ran the:

Reset_Reregister_Windows_Update_Components_for_Windows11.bat

batch file from the Eleven Forums tutorial Reset Windows Update in Windows 11. As it so often does, the Lenovo System update worked the next time I tried after said reset operation had completed and I’d rebooted that PC (as per the batch file’s own instructions). The new CU installed, and went to Build 26120.3964.

More on Unsticking Lenovo System Update

I’m not sure why the WU version got stuck, nor why it stayed that way for some time. When I looked in the Windows-Update.log file I produced via the PowerShell Get-WindowsUpdateLog cmdlet, no supporting detail told me why it happened, either.

All that Copilot could tell me was that it must be a Lenovo servicing driver update of some kind. Google was willing to speculate it might be the driver for the Lenovo Intelligent Thermal Solution. Lenovo Vantage kind of confirms this in a back-handed way, in that its history shows the latest version dated March 2024 with version number 2.1.14.0, which certainly seems to follow in the general numbering track for the item that got stuck.

So I checked Device Manager > System devices > Lenovo Intelligent Thermal Solution properties. Sure enough, the currently installed version is 2.1.52.0. Interestingly the install date shows as 4/11/2025 (same as in WU update history). That leaves me glad this already-installed driver somehow got itself unstuck. I’m still wondering why WU offered it repeatedly from 5/6-12.

These meaningless mysteries never stop in Windows-World. I’m just glad this apparently unnecessary driver offer stopped when I reset WU. Now the machine is running Build 26120.3964 and the right Intelligent Thermal Solutions driver without further issues. I’m good for now, but sure something similar will pop up soon, on one or more of my mini-fleet of 12 PCs. Stay tuned!

Facebooklinkedin
Facebooklinkedin

KB5058379 Forces 8GadgetPack Manuevers

On Patch Tuesday (May 13) I installed the latest updates on my PC mini-fleet (12 units right now). I didn’t reboot the Windows 10 production PC until yesterday. As soon as it came up, so did 8GadgetPack. Alas, the latter promptly crashed — and kept crashing — as I tried to bring it up. Next I realized that KB5058379 forces 8GadgetPack maneuvers, as  I tried uninstalling, then reinstalling that application.

That approach worked nicely to bring 8GadgetPack back up. Next, I performed a couple of follow-up gadget shenanigans along the same lines. That is, I had to remove individual gadgets that didn’t render on screen properly, then replace them from the Add Gadget repository. (Screen 1 from that tool serves as the lead-in graphic.) The whole exercise took about 10 minutes. And now, it’s all good.

Apparently, that update caused more havoc on other PCs. Keep reading for some of those ugly details…

KB5058379 Forces 8GadgetPack Manuevers … and More

This morning, I’m reading online that KB5058379 apparently causes other, more serious problems, too. The title of this WindowsLatest item (dated May 15) captures much of what’s amiss: Windows 10 KB5058379 locks PCs, BitLocker Recovery triggered on boot, BSODs. I guess you can say that while I got irked by having to mess about with 8GadgetPack, I’m now relieved that I didn’t have to go into full-blown troubleshooting and recovery mode yesterday instead.

In one way or another, all of these issues appear tied in some way to BitLocker issues. In the afore-linked Windows Latest story, Mayank Pamar explains a demonstrated repair strategy on some PCs. See that story for the details. The TLDR; version is “Turn off Intel TXT  in the PC’s BIOS/UEFI (may show up as “Trusted Execution” or “OS Kernel DMA Support”). This turns off BitLocker, but lets the update finish. Then you can turn it back on again.

Uninstall/reinstall or turn off/turn on seems to be the underlying theme for today’s blog post. That’s why undoing and redoing stuff remains a tried-and-true troubleshooting technique here in Windows-World, I guess!

Note added 5/16: After the next Release Preview CU, the same thing happened again with 8GadgetPack. And once again, uninstall-reinstall returned it to working order. Sigh, and sigh again. It’s looking like this may become part of my post CU recovery process. I can’t say I find that a delightful prospect, but it is a tolerable one.

 

Facebooklinkedin
Facebooklinkedin

Correlating KB Items and DISM Package IDs

Here’s an interesting situation. I was reading on Neowin this morning that MS has fixed a Windows 10 issue that caused BSODs on some systems (not mine, thankfully). To find or uninstall such an item, one must use DISM. But DISM deals in “Package Identity” strings, not in KB article numbers (e.g. KB5057589, as in this case). Surprisingly, correlating KB items and DISM package IDs turns out to be vexing and tricky. Indeed, this SuperUser thread more or less confirms what I quickly figured out. That is: the only datum both items have in common (using Update History for KB items and DISM Get-Packages for PkgIDs) is their install date/time.

Fortunately, what I was seeking showed up dead last in the Get-Packages output in PowerShell/Windows Terminal. As you can see in the lead-in graphic, it’s the only item whose install date matches that for KB5057589. But there’s no inherent correspondence with its PkgID: Package_for_WinREServicing~31bf3856ad364e35
~amd64~~19041.5728.1.1. What to do?

More On Correlating KB Items and DISM Package IDs

I figured there might be a PowerShell script (or something similar) already available to establish this correlation. AFAIK, nope! I thought that Copilot might be able to write me such a script. Nope again: it wants to look for the KB item ID inside the PkgID. You can see from the foregoing item (or by looking at installed updates using DISM Get-Packages) that this just ain’t so.

It looks like the only way to put all this together is to install the PSWindowsUpdate module, then use its built-in Get-WuHistory cmdlet. By writing that to a file, and then doing likewise with output for DISM Get-Packages, it should be possible to use matching date strings for KBs from the former with the “Install Time” attribute value from the latter to find and document matches.

Another Project for My List

Now that I know what I must do, I need to figure out how to do it. That will make excellent fodder for another blog post. As soon as I find the proverbial “round tuit” I’ll put that together and post it here. In the meantime, it’s nice to see that the obvious path to success (looking for the KB item ID inside the DISM PkgID) isn’t the actual path to success. Here in Windows-World, that’s all too often the case. I’m glad it keeps me entertained. I hope you feel likewise.

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