Category Archives: Windows Update

Beta 26220.7262 Update Gets Interesting

Imagine my surprise when I rebooted my old X380 ThinkPad this morning, only to have an Edge window open up on my desktop to proclaim “Your Windows 11 PC has been updated.” And indeed it went on to explain in a series of screens what new stuff I could find should I care to investigate further. I’d just applied the latest Quality Update, only to learn that this Beta 26220.7262 update gets interesting all on its own. You can see the first Edge page as the lead-in graphic above.

How Beta 26220.7262 Update Gets Interesting

In a series of 5 subsequent screens (with a Page Control to match), I saw the following

1. Your PC just got a new sense -- sight
   Try now button
2. Your voice is all you need
   Try now button
3. Stay connected right from the Start menu
   Add either Android or iPhone device from Start menu
4. Transform notes into polished ideas
   Try now button (Notepad gets structure)
5. Unleash your inner artist
   Try now button (Paint offers "creative control")
6. Discover 5 features ... get more from your device
   Discover Windows tips (sub-page with Try now)
   Customize your settings (sub-page with Try now)
   Pin sites to taskbar (sub-page with Try now)

This is all quite interesting, but a little bit disconcerting. The latter, mostly because I wasn’t expecting an unsolicited pop-up on my desktop. Makes me wonder if this is an emerging new kind of post-update behavior for Windows 11. If so — and I hope the team is reading my blog (though I’ll post to Feedback Hub as well) — this is the kind of thing I’d like a Settings option  for under the Windows Update –> Advanced Options hierarchy. Something like “Opt out of post-update notifications” would be nice. If I want to find this info, I already know where to look (that is, in KB5070303, in this case).

Sometimes, surprises in Windows-World aren’t benign. This one is mostly nugatory, if still unexpected. Gosh, you’d think they’d have mentioned that Windows will open an Edge window with update news in the Announcement as well — but they didn’t. Go figure!

Facebooklinkedin
Facebooklinkedin

DISM /Add-Packages Loses Windows 11 Mojo

This week, I’ve been updating a story for ComputerWorld. Along the way, I learned a little about .msu files for the Microsoft Update Standalone Installer. They differ widely between Windows 10 and 11. TLDR version: it’s pretty easy to extract a usable .cab file from Windows 10 .msu from Microsoft Catalog downloads. For Windows 11 .msu, it’s not. That’s why I observe that DISM /Add-Packages loses Windows 11 mojo. Let me now explain…

Why Say: DISM /Add-Packages Loses Windows 11 Mojo

The contents of .msu files for Windows 10 versus 11 updates reveals some stark differences. For recent such updates  I chose KB5066791 for Windows 10, and KB5067036 for 11.

Turns out you can open .msu files in 7-Zip to examine their contents. The two files couldn’t be more different internally. The latest 10 update includes 5 files and is just over 700MB in size. The latest 11 update includes over 100K files and comes in at just under 3.5 GB.

The really big difference is that DISM /Add-package /online (the incarnation of that command that permits working on a running Windows image) REQUIRES a .cab file to do its job. Simply put: Windows 10 makes that easy to find, extract, and use; Windows 11 makes it pretty much impossible.

Where the Mojo Went…

That means you can use DISM /Add-Package on Windows 10 to apply updates to a running image, when Windows Update isn’t working or something goes sideways with some particular update. But if you want to use DISM to add a package to a running Windows 11 image, you must take that image offline, apply the update, then bring the image back online.

The net effect is that a quick and handy alternate update technique that works fine for Windows 10, turns into a slow and cumbersome slog for Windows 11. Better to try something else, instead. I’m sorry to lose a helpful tool from my Windows fixes and workarounds toolbox, but that’s the way progress sometimes works in Windows-World.

Facebooklinkedin
Facebooklinkedin

Driver Upgrade Fixes 0xC1900101 Errors

I’ve seen it  before, and I’ll probably see it again. When I first ran the Beta Channel upgrade to Build 26220.7051 on Friday, it failed during the post-GUI install (aka SECOND_BOOT) phase . Basically, it hung at 10% complete for half an hour or longer, and I force-rebooted the X380 Yoga. When the rollback process completed, WU/Update History showed me an error in the 0xC1900101 range. From long experience I recognized this as some kind of device driver issue. Fortunately, a driver upgrade fixes 0xc1900101 errors. Let me tell you more…

Why Say Driver Upgrade Fixes 0xC1900101 Errors?

Alas, I didn’t record the exact error code string yesterday. I simply grabbed the latest version of Snappy SDIO from PatchMyPC Home Updater, and used it to upgrade the drivers on the X380. (TMI: That’s version R817, as far as I can tell.) This took about half an hour, give or take 5 minutes, and replaced 17 drivers.

The next go-round on the update process took quite  a while to complete (probably a bit over an hour). But it went all the way through, and resulted in a successful installation. The table you see in the lead-in graphic here comes from Copilot after I asked it to tell me about 0XC19001… Windows 11 install errors. It’s pretty informative, so I figured I’d share it.

Here in Windows-World, when a Windows 11 install goes wonky, it’s nice when prior experience retains its relevance for current troubleshooting. Again: I’m glad the tried-and-true technique for this kind of error code still works.

Facebooklinkedin
Facebooklinkedin

Version Dev Gets No 25H2

On the last day of September, the Windows Experience blog announced “the availability of the Windows 11 2025 Update (aka Windows 11, version 25H2).” A little careful perusal of this info, and some checking from your humble author shows that availability not only includes production versions. It also includes Insider Preview versions in the Release Preview and Beta Channels as well. By extension that means Dev and Canary Channel fall outside this umbrella. That’s what I mean when I say “Version Dev Gets No 25H2,” as you can see in the lead in-graphic (shows an ambiguous “Version Dev” instead).

Version Dev Gets No 25H2 Means More Than It Says

On my Canary test PC (the stalwart, still kicking 2020 vintage Lenovo ThinkPad X12 Hybrid Tablet) the version line from winver.exe gives things away. It reads “Version Dev” instead of 24H2 or 25H2. Both Dev and Canary Channels fall outside the Windows 11 versions that can upgrade to 25H2 at present. That’s because they belong to a different Windows 11 Build branch, with higher build numbers that bypass 25H2 entirely. That’s probably why MS forgoes 24H2/25H2 nomenclature in identifying the version as shown in the lead-in screencap.

OTOH, I was able to use the Installation Assistant yesterday to upgrade my Beta Channel test PC to 25H2. It shows the latest build status in Settings > Windows Update > Windows Insider Program, as you can see here

But it also shows up as 25H2 in Winver, and up-to-date in WU, as you can see here:It’s all a matter of how close the bits come to matching the currrent production version of Windows 11. Because Canary and Dev Channels are further out, they’re not able to show a 25H2 base. That’s by design.

Interesting that Beta and Insider Preview Channels can move on up to 25H2 though, while Canary and Dev remain in the 24H2 zone. This will be interesting to watch in the months to come. I wonder if Canary will get its own version, or stay lumped in with Dev? We’ll see!

Facebooklinkedin
Facebooklinkedin

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