Category Archives: Windows Update

KB5018496 Lands Poorly So Far

KB5018496 is out as of October 25. It takes production-level Windows 11 22H2 systems to Build 22621.755 when applied. To be fair, it’s a Preview CU, so not entirely cooked yet. But I observe that KB5018496 lands poorly so far because

(a) I don’t see any of its cool gradual rollout features on any of my PCs (e.g. right-click in Taskbar to launch Task Manager)
(b) When I attempted to explore the new Microsoft Accounts (MSA) capabilities, it crashed when I attempted to open the P16’s camera. I know that works because I use camera-based Hello to log onto that machine and had just done so minutes before. Sigh.
(c) I was unable to verify my identity in Settings → Accounts, because of the camera issue, so also unable to backup my MSA data. Sigh again.

Again: this is a preview release. And I’m qvetching about gradual rollout elements that either haven’t made it to my PCs, or that aren’t yet working as they should be. It’s a kind of “business as usual” thing, I guess.

What KB5018496 Lands Poorly So Far Really Means…

It’s pretty much par for the course that a few rough edges will show up in a preview release. Thus, for example, when I went to Accounts → Windows backup in an RDP session, the PC “knew” it couldn’t use the camera for validation. So I got an email to my MSA address instead. That worked just fine. The relevant screencap appears as the lead-in graphic for this story.

I assume there’s some kind of driver hiccup with the camera when logged in directly. It threw an error code that pointed squarely in that direction. That should be easy to run down and fix, so I’ll report it to Feedback Hub later today.

I’ve been using the right-click access to Task Manager in the taskbar on Insider versions of 22H2 for a while now. Thus, I also know it’s just a matter of time before it, too, shows up in production versions of 22H2.

Self-Inflicted Wounds? Perhaps…

So why do I install previews on production PCs? Because I’m an Insider and it’s my job to take such stuff on, and report what I see and find. I make daily image backups on those PCs, so the worst that can happen is a rollback to the previous image. I don’t generally do real work on those PCs unless I’m on the road. And in that situation, I probably wouldn’t mess with a preview because I wouldn’t want to lose the time (or the work done) since the last backup anyway.

And that’s how things go here in Windows World. Stay tuned for further developments. I’ll qvetch some more another day, for sure!


WU Reset Fixes Weird Windows 11 Upgrade Freeze

With Dev and Beta Channel releases, it’s always “just a matter of time” before something gets wonky. Yesterday, in fact, I ran into difficulties upgrading one of my X380 Yoga laptops to Build 25227. In November 2021, I wrote a blog post here entitled WU Reset Tool Works on Windows 11. Good thing, because WU reset fixes weird Windows 11 upgrade freeze, too. Let me explain…

I’m Glad WU Reset Fixes Weird Windows 11 Upgrade Freeze

Here’s what’s weird about this failure. The laptop hung during the post-GUI update phase, after the old OS hands over control to the installer’s WindowsPE-based runtime environment. Indeed, it got all the way to 98% complete before it hung interminably.

Yet, as you can see, the hex code speaks to a “download error.” I have to guess there was some essential bit of data that the installer needed to read right at the end of the post-GUI installation process. When that failed, the whole shooting match went south. Stuck forever!

The Charm Came on the 2nd Try

I probably got lucky. I ran the invaluable reset/reregister batch file cited in the WU Reset Tutorial at ElevenForum, Then I tried the 25227 upgrade again: it worked this time! That said, this one took 30-40 minutes to complete (a fair while longer than previous but recent Dev Channel upgrades). But it sailed through to completion and is now working properly on the X380 laptop.

On the plus side, the login issues I’d been having with RDP on the same laptop also disappeared with the upgrade. That’s a relief. But on the minus side, my other Dev Channel test machine acted a bit wonky during the upgrade, too. It shut down after the reboot from the GUI phase into the post-GUI phase of the install. I had to manually power back on to finish the job. That hasn’t happened for a while with Dev Channel releases, either.

But hey! The purpose of Insider participation is to help catch — and hopefully kill — bugs and weirdnesses before they get into general release. We’re all just doing our jobs by finding and reporting this kind of stuff.

And that’s how it goes sometimes, here in Windows World. Good thing I enjoy it, and relish my appetite for problem solving and troubleshooting.


First Windows 11 22H2 Moment Arrives

OK, then. We knew it was coming. And with yesterday’s release of  KB5019509 it’s here. That’s right: with this out-of-band  update, the first Windows 11 22H2 moment arrives. This time, it includes the tabbed version of File Explorer, which wasn’t quite ready for release when 22H2 made its debut on September 20.  This new, snazzed-up File Explorer version provides the lead-in graphic for this story, shot from my just-updated P16 laptop.

What First Windows 11 22H2 Moment Arrives Means

I guess it helps to understand that a moment is shorthand for what ComputerWorld (CW) describes as “small, quarterly feature updates” in a September 14 story. (This story in turn relies on a July Windows Central hearsay report about the terminology.) And indeed, support for tabs in File Explorer makes a perfect illustration of what such a “moment” could bring to users.

But there’s more to KB5019509 than File Explorer tabs. Here are  descriptions of two other new features, straight from that update announcement (blue text emphasis mine for ease of identification):

  • New!It adds a feature called Suggested Actions for items that you copy. This is available for customers in the United States, Canada, and Mexico. For example, when you copy phone numbers or future dates, we provide suggestions, such as make a call with Teams or Skype or add an event in the Calendar app.
  • New! It adds a taskbar overflow menu. The taskbar will offer an entry point to a menu that shows you all your overflowed apps in one space.

We’ll Have These Moments to Remember…

If the CW description is correct, this is just the first of a series of such moments that will pop up from time to time. I can’t tell if MS will itself use the “moment” terminology or not. In fact, KB5109509 calls the aforementioned introductions “quality improvements” instead. A search on the word “moment” turns it up nowhere in this text.

Other new quality improvements in the update include using nearby sharing to “discover and share more devices, including desktops,” a switchover to Windows Settings from Control Panel to “uninstall, repair and modify all apps,” and improved “performance of federated authentication.” All told, KB5109509 appears to offer some interesting stuff.

But if a quality improvement isn’t explicitly called out as a “moment,” why bother with this terminology? Good question! I wish I had an equally good answer. We’ll have to see how this all unrolls. In the meantime, I’m just going to savor this particular moment…



Get-Hotfix Shows What WU Sometimes Cannot

When MS lifted the safeguard hold on  my Lenovo P16 Mobile Workstation, I upgraded it to Windows 11 22H2. Naturally, my first thought thereafter was to check on status of recent updates and fixes. That’s when I figured out that KB5018427 was included in the 22H2 version installed. Seems that Get-Hotfix shows what WU sometimes cannot — at least as far as Update History goes.

It’s all apparent in the lead-in graphic for this story. In case it’s not legible enough, right-click on that image and select “Open image in new tab” (Chrome, Firefox, Edge, etc.). That should show it at original resolution. If necessary, you can use the browser’s Zoom controls to magnify the text.

How Get-Hotfix Shows What WU Sometimes Cannot

Update history shows only user-alllied updates. It does not show updates that — like KB5018427–get rolled up into the windows image file (WIM) used to install a version upgrade. That’s what makes the PowerShell Get-Hotfix command so useful. Its image analysis tool tells it what’s there, whether the user applied it directly, or whether it’s already “in there” as is the case here.

An important clue appears in the “Installed on” date shown in the output of Get-Hotfix. Although the KB item itself is dated 10/11/2022, it didn’t get rolled into the WIM until 10/14/2022.

What Led Me Down This Trail?

I read the Windows Latest story about KB5018427. Naturally, I wanted to check on its status in the upgraded 22H2 version. When I didn’t see it in Update History, I visited the Microsoft Catalog and downloaded the 64-bit MSU file. Upon attempting its installation, it searched the updates already installed on the PC. That produced the following status message:

That made me understand the KB had been included in the WIM file I’d already installed. A search on “use PowerShell to show updates installed” led me to the Get-Hotfix command.

As the afore-cited PowerShell docs states:

The Get-Hotfix cmdlet gets hotfixes, or updates, that are installed on the local computer or specified remote computers. The updates can be installed by Windows Update, Microsoft Update, Windows Server Update Services, or manually installed.

Thus Get-Hotfix can catch patches and fixes no matter how they get included in the image it checks and reports upon. The rest, as they say (drum roll, please)… is history!



P16 Safeguard Hold Lifted

OK, then. I performed my daily ritual WU check on the P16 Mobile Workstation on Friday (Oct 14) . This time, the P16 safeguard hold lifted, and I was able to update to Windows 11 22H2. As you can see in the lead-in screencap, the 22H2 download was available during capture. Neat-o!

And indeed a quick visit to the 22H2 Known Issues page shows that my hold-up — the Intel SST drivers — appears as “mitigated.” Here’s what that looks like:

P16 Safeguard Hold Lifted.SST-info

The P16 blocking issue is now resolved, thanks to Intel driver updates. These appear in DevMgr under the “Software Components” heading.

With P16 Safeguard Hold Lifted, Upgrade Proceeds

I got a little concerned right after the first reboot (from the GUI-based portion of the install, into the post-GUI phase). The P16 sat at 0% complete on processing updates for what seemed like an eternity (about 4 minutes). But then, it started to chunk through the process and finished in about 20 minutes during that install phase.

I noticed that the update included a raft of driver updates –14 in all — by checking Reliability Monitor later on. The two items of greatest import show up in the software components category where various sound -related items reside.

Whatever the issue might have been, I’m glad to see it resolved. And so far, the P16 is running without apparent issues. I’m connected to it remotely via RDP right now, so that recent bugaboo is not present here, either. Good-oh!


WU Starts Windows 11 22H2 Delivery

OK, then. When I made the rounds of my PCs this morning, the Lenovo X1 Extreme got the offer through Windows Update. That’s right: for me, WU starts Windows 11 22H2 delivery right now. You can see what that offer looks like in the lead-in graphic.

When WU Starts Windows 11 22H2 Delivery, Then What?

Even though WU reports that “You’re up to date” as shown, a “Download & install” button is provided for 22H2. After clicking said button, it took about 5 minutes to download. The GUI-based install took another 25 minutes. It took 2 minutes to cycle through update processing before the first reboot. Post-GUI install took 6 minutes more, and then 2 added minutes to get to the intial desktop. At 35 minutes in all, that’s longer than I remember the Windows 10 to Windows 11 upgrade taking.

At the end of the process, Winver shows me running 22H2, Build 22621.521. A quick follow-up check for updates shows a Defender item, and KB5017271 (.NET Framework 3.5 and 4.8.1 CU). I run those, after shooting this screencap:

WU Starts Windows 11 22H2 Delivery.newwinver

Windows 22H2 Status at Chez Tittel

What about my other production Windows 11 PCs? The Lenovo P16 Mobile Workstation is still on safeguard hold (Intel SST  Audio drivers). I’d already force-upgraded the P360 Ultra, the Ryzen 5800X PC, and the Lenovo Yoga 7i. That means all my production 11 PCs are as upgraded as they get for the moment. It’s a good place to be. I think I’ll enjoy it for a short while, at least…


Windows Upgrades Bring New Drivers

Whenever one upgrades a Windows installation, the installer locates and installs a new slate of drivers by default. There are ways to overcome this by customizing the Windows install image (with DISM, for example). But I was forcibly reminded that Windows Upgrades bring new drivers. It happened two days ago when the Installation Assistant took the P360 Ultra to Windows 11 22H2.

Fortunately, I knew how to fix this. Because the latest Nvidia driver is the culprit, I simply switched to Intel UHD graphics. This took me from a black screen to working graphics output. I’ll roll back the affected driver this weekend. That will put things back to rights.

Showing Windows Upgrades Bring New Drivers

I had to roll back the Nvidia driver on the P360 Ultra to get the RTX A2000 GPU to work. That’s because there is a known issue with all drivers newer than, as I learned from Lenovo’s engineering folks last week (see this Sept 16 item for details).

I’m a big fan of the GitHub DriverStore Explorer project (aka RAPR.exe). As you can see from the following screen snippet, there’s an older INF file on the U360 Ultra for my proper target version ( But alas, DevMgr won’t roll back to that version (I think it’s because the older version is a Quadro/Studio driver, while the new, in-place version is a Game-ready driver).

Windows Upgrades Bring New Drivers.RAPR

RAPR confirms that the new version is installed, and shows the old version, too. [Click image, then zoom to 200%.]

Luckily I still have the Lenovo update package that they provided. As its Properties window shows, file m3vdo008d.exe is exactly what I need. I know from recent experience – the first time I fixed this gotcha – that I can simply install this exe file, and it will replace the buggy new driver with the stable, working older driver. Sometimes, one has to run the Driver Display Uninstall (DDU) tool to completely remove all traces of the new, before installing the old. That’s NOT the case here, I’m happy to say.

Windows Upgrades Bring New Drivers.LenovoPkg

If I install this older driver, I can then use the Nvidia GPU without problems.

How Driver Trouble Happens During Upgrade

If a particular PC needs an older (or non-current) driver, Windows isn’t smart enough to steer around such potholes. As soon as I upgraded this PC, I knew I was going to have to fix the automatic update it would make to the latest (and incorrect) Nvidia driver. Sometimes, that’s the kind of thing you need to watch out for when upgrading Windows. Consider yourself notified, if not warned!


Accidental Pause Kills In-Process Updates

I just learned something I didn’t really want to know. I “oopsed” my way into pausing updates on a Dev Channel test PC this morning. As I did so, the download for Build 25201 was underway, as was the install for KB5017257 (CU for .NET 3.5 and 4.8.1). Alas, this accidental pause kills in-process updates. Thus, I had to restart to apply all the other stuff that had finished, then un-pause updates. Next, I had to redownload Build 25201. Both installed correctly, and another reboot finished the job.

Living with Accidental Pause Kills In-Process Updates

Oh well. If that’s the worst thing that happens to me today, it will still be a good day. What I didn’t know was that in-process items would come to a screeching halt. That’s because I’d never accidentally clicked “Pause for 1 week” during the update process before. Sigh.

Hopefully, alert readers can profit from my mistake without having to learn the hard way for themselves. Tip: stay away from the “Pause…” button while updates are in process. That’s the best way I can think of to skip the whole learning experience entirely.

Compounding the Mistake…

Because I hadn’t yet applied last week’s Patch Tuesday updates to the affected machine, as well as pending Dev Channel build 25201, this was a pretty big update cycle for that machine. I count 1 driver update, 2 Definition updates, and 3 “Other” updates among that number, as well as the items already recited.

But alas, that’s the way things sometimes go in Windows World. Fumble fingers got me pretty good this time. Hopefully, we’ll all be exempt from this particular gotcha going forward. Sigh.


KB5012170 Can Provoke BitLocker Recovery

Here’s an interesting tidbit that’s making the rounds right now. KB5012170 appeared on August 9 on the latest Patch Tuesday. According to various sources — see this Neowin story, for example — some users’ PCs boot into BitLocker Recovery after the mandatory post-update restart, rather than business as usual. Thus, applying KB5012170 can provoke BitLocker Recovery (though unintentionally).

Of those affected, some have been able to get back to rights by applying the PC’s BitLocker Recovery key. Others have had to update their UEFI before that key application “takes.” In my case, I apparently dodged that bullet, because none of my production Windows 11 machines (four Lenovo laptops of various descriptions, and a Ryzen 5800X desktop) fell prey to this gotcha.

You can see the “success” report for this KB item boxed in red in the lead-in graphic for this story, in fact…

If KB5012170 Can Provoke BitLocker Recovery, Then What?

BitLocker keys can be stored in at least three ways. 1. On paper, 2. Electronically (usually on a USB drive). 3. Associated with a specific MSA (Microsoft Account). I prefer method 3 because it’s easy to set up and MS manages it automatically on your behalf.

You must log into your MSA online (I go through Then go to Devices, and pick the affected PC. Next, click on Info & Support. There you’ll find a Bitlocker data protection item that includes a link to “Manage recovery keys.” That’s what you want. It will show you recovery keys for all the devices associated with that MSA (I show 11, of which I’m actually using 2, so I just got rid of the rest after saving a backup copy to an encrypted disk).

BTW, that means it’s essential to add all devices you might ever want to recover to your chosen MSA. Do so right away, if you haven’t already!


KB5015684 Provides Quick Windows 10 22H2 Upgrade

Here’s an interesting item. Turns out that MS has made KB5015684 available through its update servers. Thanks to the team at you can find x86, x64 and ARM64 versions of either .CAB or .MSU files. All have links of the form or .msu. They must be legit, right? Hence my claim that KB501864 provides quick Windows 10 22H2 upgrade.

I just ran it on my production Windows 10 PC, and it went through without hitch or glitch. Completed in under 2 minutes, including download, install and reboot time, too. May be worth a try for those with Windows 10 PCs not expected to elevate to Windows 11 soon (or ever). So far, I see no discernable changes in look, feel, or behavior — just a new Build number 19045 (vs. 19044). Same minor extension as before, in fact: 1826.

What KB501864 Provides Quick Windows 10 22H2 Upgrade Really Means

Two things:
1. MS is getting close enough to a 22H2 public release for a preview to go out.
2. The code for the 22H2 release is stable enough to start it through the Windows Insider program.
Note: I didn’t have to join the Insider program to install this update, which appears as a “Quality Update” in Update History. The Windows Insider Program page on this PC, post-update, does NOT show itself as “joined-up” either. So one need not be concerned that applying the update automagically changes the PC’s status to that of an Insider machine. That’s a relief!

I ran the .MSU x64 version of the upgrade, simply because a self-installing update file is a little easier to apply than CAB files can sometimes be. You can find all links in the original article (6 files in all). It might be a good idea to apply this upgrade to test machines with some caution, if you’re concerned about possible unwanted side effects. That didn’t stop (or hurt) me on this PC, though…

If you’re interested, have at it. Cheers!