Category Archives: Windows Update

WU Reset Tool Works on Windows 11

I’ve been a member over at TenForums for almost 7 years now. In fact, I joined up on November 14, 2014 shortly after the first Technical Preview emerged. This weekend, I was relieved to discover that the batch file Shawn Brink created as a WU reset tool works on Windows 11, too. (The preceding link goes to a tutorial that provides a download and explains how to use it to reset Windows Update, or WU).

It’s a Relief that WU Reset Tool Works on Windows 11

My Lenovo ThinkPad X380 Yoga test machine would start downloading updates from WU just fine. But part-way through the download process, progress would stop. Eventually, I would get an “Update failed…” error message, with a Retry button. After several tries, each with its own similar failure, I knew sterner measure were needed.

I actually keep the batch file from the afore-linked tutorial on my shared desktop in OneDrive. It’s called

Reset_Reregister_Windows_Update_Components.bat

and it does a thorough reset of the Windows Update environment. It begins by halting all update-related services, then it empties all folders where recently-downloaded update files reside, checks (and if necessary resets) various WU-related registry settings, then restarts those same services. A reboot follows next, after which one can try one’s luck with WU again.

So I ran the batch file in an administrative cmd prompt on the affected machine, let it do its thing, then restarted that PC. Presto! After restarting, my next update attempt succeeded. I wasn’t 100% sure it would work on Windows 11 because the tool was built for Windows 10. But to my great delight and relief, it set the Windows Update environment back to working order. And thus, I was able to catch that machine up with the current state of the Dev Channel.

Should you ever find yourself in a similar situation, I recommend the tool and its accompanying tutorial highly. Find it at TenForums as Reset Windows Update in Windows 10. Hopefully, Mr. Brink will soon do a run-through to create a Windows 11 specific version. Should that occur, I will add a link to that version here as well.

Facebooklinkedin
Facebooklinkedin

Windows 11 Upgrades Gain Momentum

This morning (October 26) Twitter is ablaze with reports of qualified PC getting the “Windows 11 offer” via WU. I just checked my eligible PCs still running Windows 10 (all both of them). The Intel i7 11th gen machine gets the offer; the AMD Ryzen 5800X does not. So, as Windows 11 upgrades gain momentum the coverage remains partial. I guess, it’s just a bigger piece of the overall pie.

Twitter Sez: Windows 11 Upgrades Gain Momentum

But gosh, I see dozens of posts on Twitter this morning from people with all kinds of PCs indicating they’ve accepted the offer. Most report a successful install. Some report hanging, of which most seem to involve the post-GUI install phase somewhere between 80 and 100% complete.

FWIW, such issues have been common with other new Windows versions. One could argue — and MS often does — that the whole point of the “gradual rollout” they now follow is to ensure the highest likelihood of success to those who get “the offer.”

What I Do if WU Upgrade Hangs

This hanging has happened to me often enough in my 7 years as an Insider that I’ve got a step-by-step approach to trying various fixes:

1. Power off and restart. Often, the install will pick where it left off and continue to completion.
2. If rollback happens after restart, I try using the setup.exe from an ISO equivalent to the current install version. That has worked for me in most (9 out of 10) cases.
3. If a standalone/local installer won’t cut it, that often indicates driver or hardware issues. I’ll often roll back and wait for the next upgrade or a new ISO to come along. For those who MUST get to Windows 11, the only thing left to try is a clean install from the same ISO as in Step 2. This works for 9 of the remaining 10 hard cases.

But as I’ve recently learned with the Lenovo X1 Carbon Gen 9 that has a Thunderbolt Firmware issue I can’t fix for love or money, even a clean install doesn’t ALWAYS work. That’s why I’m sending that one back to Lenovo with a “Thunderbolt doesn’t work” note in the box. Sometimes, the forces of darkness do prevail. I can only add that I *HATE* when that happens.

Facebooklinkedin
Facebooklinkedin

Windows Updates Gain Expiration Dates

Take a look at the web page for this June vintage 19042 Windows 10 preview item KB5003690. As the concluding term in its title states, this item is EXPIRED. It’s also no longer available for download. Revised MS policies mean that some Windows Updates gain expiration dates (or status, anyway) when they reach obsolescence. The lead-in graphic for the story shows the revised KB5003690 title and its EXPIRED status above.

If Windows Updates Gain Expiration Dates, Then What?

It’s not exactly like a carton of milk from the grocery store. You won’t know in advance when any particular KB item might (or will) expire. This looks like the kind of thing that will pop up when you try to access older updates that Microsoft has removed from circulation.

The details of Microsoft’s EXPIRATION NOTICE read like this:

NEW 7/21/21
EXPIRATION NOTICE

IMPORTANT As of 7/21/2021, this KB is no longer available from Windows Update, the Microsoft Update Catalog, or other release channels.  We recommend that you update your devices to the latest security quality update. The latest security quality update is cumulative and contains all the addressed issues in this update.

Apparently, the idea is that as certain updates age out, they will no longer clutter up the update universe. WindowsLatest opines this will be a boon to those who might pause or skip updates, by reducing download items and data volume. They also assert that “… older and redundant packages will now expire automatically, which can improve the performance of Windows Updates and reduce update cache size.” Same effect applies to scan time: with fewer updates to look through, scan results should come back more quickly as Windows PCs “Check for updates” in WU.

Less Is More?

Certainly from data management and networking perspectives, reducing the population of update items is a good thing. I’ll be curious to watch for this status to start coming up when checking KB items.

Just for grins I checked a newer Preview update for status. KB5005101 (released on 9/1/2021) remains available, and its Catalog download likewise. Looks like expiration dates don’t kick in until an item — even a Preview item — gets to be four months old, or older. Time will tell if that boundary is flexible, or fixed…

Facebooklinkedin
Facebooklinkedin

Windows 11 Gets New Update Stack Package

Last June, MS announced the release of a Windows Feature Experience Pack (120.2212.3920.0) to Insiders in Beta and Release Preview Channels. In yesterday’s Dev Channel Preview Build 22478 release notes, they announced something called “Update Stack Packages.” Let’s call the former WFEPs and the latter USPs for brevity. USPs provide a “…new process for delivering new update improvements to our customers outside of major OS updates…” But if Windows 11 gets new Update Stack Package, what does that really mean?

Sussing Out Windows 11 Gets New Update Stack Package

The key to understanding comes from a sentence in the release notes discussion of USPs. It reads “The Update Stack Package will help ensure that your PC has the highest likelihood of successfully installing new updates with the best and least disruptive experience available.” Sounds like a mechanism to make sure the OS image is free of potential impediments to upcoming updates. Why does this remind me of “servicing stack updates?”

Overall, the discussion of USPs is much like that for WFEPs earlier this year. To wit:

1. USPs are currently limited to “a very small set of update-related system files … developed independently of the OS.” WFEPs have been small and limited since their June 2021 introduction. That said, they focus on “feature improvements to customers outside of major Windows 10 feature updates.”

2. USPs and WFEPs both come to Windows installations via WU.

3. Both seek to sanity-check and test their approach and capabilities with Insiders, but ultimately aim to “expand the scope and frequency of releases in the future” (quote from WFEP June announcement).

Looking for Enlightenment…

What’s really going on here? MS seems to be experimenting with different kinds of update mechanisms independent of “major OS updates.” Given that feature updates are dropping back to yearly frequency, this provides a way to introduce changes more often than that. I’m curious to see either (or both) of these mechanisms deliver something meaty. So far, they’ve been used only for tentative, small-scale updates and changes. I guess we’ll have to wait and see how they behave when they get a more serious workout.

Right now, for both USPs and WFEPs there’s far more fanfare than clarity or understanding. Hopefully time and experience will cure that imbalance and bring some useful demonstrations of what these things are for, and what they can do when exercised more heavily.

Facebooklinkedin
Facebooklinkedin

Windows 11 GA Follies Underway

OK, then. I learned something new and interesting yesterday. Thanks to Mary Jo Foley at ZDNet, I now know that October 5 really started at 4 PM Eastern (US) the day before. That meant I was able to try out two new facilities late in the day, as Microsoft got the Windows 11 GA follies underway in earnest. Let me explain…

What Does Windows 11 GA Follies Underway Mean?

GA stands for “General Availability” and represents the timeline entry for an OS release at which point anyone can access it. If they have a legit Windows 10 license they can upgrade to it. They can also now access numerous Windows 11 specific tools through the Download Windows 11 page, including:

  • The Windows 11 Installation Assistant (for upgrading the machine you’re using)
  • The Windows 11 Media Creation Tool (for creating a bootable UFD or DVD)
  • Download Windows 11 Disk Image (ISO) to obtain a mountable multi-image ISO for planned installation or image customization

I’ve already done all of those things, though I haven’t yet used the UFD I built, or put the downloaded ISO to work. Here’s a brief recitation of what happened.

Item 1: Installation Assistant

My first GA upgrade target was my trusty Lenovo ThinkPad X1 Extreme laptop (8th-gen Intel CPU, 16 GB RAM, 1 TB NVMe SSD, TPM 2.0 and Secure Boot enabled). I’d already made sure it met Windows 11 requirements, but I did hit a snag during installation.

I had Start10 installed on this PC. And when the Installation Assistant got about 80% through with the installation part, it stopped and told me I had to uninstall Start10 before it could proceed. Because uninstalling Start10 itself requires a restart, I knew this meant I had to clear this out and then start over. So that’s what I did.

To my surprise, the Installation Assistant kept the install files so I didn’t have to download them again. This short-circuited the process by a good five minutes. But the second try at install took quite a while to complete — nearly 40 minutes by my clock. My advice to readers: if you’re running a start menu replacement program, uninstall it before you begin the upgrade process. In the long run it will save on time and aggravation.

Item 2: MCT Revisited

The new version of the MCT is named MediaCreationToolW11.exe. At 9,532KB in size (as reported in Explorer) it’s a pretty quick download. I like it that MS is labeling MCTs with the version of Windows they’ll grab for you. Makes them much easier to tell apart. In fact, I usually label them when I download them anyway for that very purpose. Glad to see MS beating me to the punch here.

Just for grins I went through the UFD drill with an older 8 GB UFD I had sitting around. The download part took less than a minute to complete (I have a fast Internet connection, fortunately). Building the on-media image took a little bit longer: a bit under five minutes on a 2016 vintage Patriot Blitz 8GB UFD device. It got renamed to ESD-UDB during the build process (which reflects MS use of the compressed version of WIM for speedier download/smaller disk footprint). Total disk space consumed: 4.16 GB.

Item 3: ISO Download

Because I’m a huge Ventoy fan (and regular user) this method gets me images for all kinds of uses (install, repair, troubleshooting and so forth). That’s why I don’t mess around with bootable UFD devices anymore. MS advertises, and DISM confirms, that this is a multi-part ISO image (7 parts, in fact, as shown in the following screencap):

Windows 11 GA Follies Underway.dism-scan

7 total images, each with its own index, in the official Win11 ISO
[Click image for full-sized view.]

So Far, So Good. What’s Next?

I have now force-upgraded the X1 Extreme (and then installed Start 11, which is supposed to get a major update in a couple of days). I plan to update my wife’s Dell 7080 Micro with its 11th-gen CPU today or tomorrow. I’m going to wait on WU for other Windows 11 ready machines to see when the get “the offer.” Stay tuned: I’ll keep you posted as the rollout proceeds. So far, though, it’s been pretty easy and straightforward. Except for the Start 10 surprise in fact, it’s been smooth as glass.

Facebooklinkedin
Facebooklinkedin

Windows 11 Dev Channel Goes Nickel

Just yesterday, September 2, the MS Windows Insider team re-forked the Beta and Dev Channels for Windows 11. The Windows 11 Dev Channel goes Nickel. Thus, it picks up a new release branch where experimental features not tied to specific upcoming releases can be exposed and explored. Note the major Build number in the lead-in graphic. It jumps to 22449, far ahead of other build numbers of any sort.

The Beta Channel, on the other hand is still tied to 21H1 and Build 22000.  As the upcoming Windows 11 release date — October 5 — edges ever closer, that should remain constant. Beta will be the focus for bug hunts and ongoing fixes. The run-up to that GA date (32 days away as I write this story) should be interesting.

Finally, these two release forks now diverge. I predict Beta will continue to track “the next, upcoming Windows 11 release.” Dev will show us what’s possible but not inevitable for future releases .

When Windows 11 Dev Channel Goes Nickel, What to Expect?

MS has already warned Insiders about future Dev channel releases. They will be less stable and more subject to gotchas and bugs. The 22449 release blog says (emphasis mine):

These builds are from the earliest stage in a new development cycle with the latest work-in-progress code from our engineers. These aren’t always stable builds, and sometimes you will see issues that block key activities or require workarounds while flighting in the Dev Channel. It is important to make sure you  read the known issues listed in our blog posts as we document many of these issues with each flight.

And please: if you participate in the Dev Channel, I urge you to follow Microsoft’s advice. That is: “read the known issues” as each new upgrade emerges. More than once, I’ve been bitten because I jumped first, and read the issues list second. Thus, I’ve learned from first-hand experience, little of it positive, to heed that warning.

I’m glad to see this happening. I look forward to what emerges in  Dev Channel releases going forward. That’s why I joined the Insider Program to begin with. It’s why I look forward to bashing bugs, reporting (and learning from) issues, and making things work. For some of us in Windows-World — including me — this passes as entertainment!

Facebooklinkedin
Facebooklinkedin

Windows 10 Build 19043.1165 Install Button

Here’s an interesting departure from the usual. Today, August 10, is Patch Tuesday. That means it’s the second Tuesday of the month, and normally when Microsoft pushes updates out on its normal monthly cycle. But when I checked for updates, after they downloaded, the process paused. As you can see in the lead-in graphic, I had to push a Windows 10 Build 19043.1165 install button to make the install continue. What’s up with that?

When Is a Windows 10 Build 19043.1165 Install Button Typical?

Normally, one doesn’t see such things unless there’s some kind of preview element in the update mix (and rarely, if ever, does that hit as part of Patch Tuesday offers). That said, there is a KB5003791 Enablement Package update out today to take 2004, 20H1 or 21H1 to 19044 (21H2) build levels. Perhaps the button shows up because of that item? Interestingly, it was not offered to my PC (nor should it have been, as it is an Insider Preview element).

Even more interesting, I saw the update process cycle around for the KB5005033 item on my production desktop PC. That is, it counted up to 100%, stayed there for a while, then dropped back into the 60s and counted back up to 100% a second time before showing the usual “Restart now” button upon completion. That’s not exactly unheard of, but it is a little unusual. Thus, Patch Tuesday brings me a little unexpected excitement today.

Here’s what came through today, as part of the update package:
1. KB5005417 .NET Core 3.1.18 Security Update
2. Windows Malicious Software Removal Tool KB890930
3. KB6005033 Cumulative Update for 19043.1165
I don’t see anything in there that would normally induce the “Install now” button to appear. But as the lead-in graphic shows, I got one anyway.

And that’s the way things go here in Windows-World sometimes. Go figure! I’m clueless…

Facebooklinkedin
Facebooklinkedin

Upcoming PowerShell Updates Arrive via WU

Here’s an interesting tidbit. Starting with Preview edition 7.2 preview 5 or newer, Windows Update will take over responsibility for updating PowerShell as new versions emerge. Used to be it would notify users an update was available, but they would have to visit GitHub to grab the .msi,  or use a package manager to install the new version. But now, certain upcoming PowerShell updates arrive via WU.

It’s not clear when this will click in for production versions, but the shift is already underway for preview versions. If you download and install PowerShell 7.2 preview 5 or 6, you’ll be queued up for this grand experiment. (Visit the Releases GitHub page to find them.)

Rolling Out Upcoming PowerShell Updates Arrive via WU

As is typical when introducing new features and capabilities. MS will start this process with Preview editions of PowerShell. You can read more about the rollout plan in the June 16 PowerShell blog “Preview udpating PowerShell 7.2 with Microsoft Update.” Some registry tweaking is required, but the blog post provides all necessary commands in scripts designed for easy cut’n’paste use.

This is a nice step forward for Windows-heads who, like me, are regular and interested PowerShell users. It’s one step closer to real OS integration now. The post doesn’t say when this treatment will include PS production versions, but I’m hoping it will be soon. Perhaps it will come along for the ride into “next generation” Windows 10? Stay tuned, and I’ll tell you when that news hits.

Facebooklinkedin
Facebooklinkedin

Forcibly Upgrading 20H2 PCs Many Ways

OK, I’ll admit it. I got tired of waiting. This weekend, I forcibly upgraded my 20H2 production desktop to 21H1. As it happens, when forcibly upgrading 20H2 PCs many ways to the new version are open. I took one of the easiest: installing the enablement package. Links for x32, x64 and ARM64 versions are available at TenForums, via KB5000736 self-installing update files.

Forcibly Upgrading 20H2 PCs Many Ways Requires Follow-up

Of course, it’s been a while since KB5000736 first appeared on May 18. After I got through that install — which took under 2 minutes on my SkyLake i7-6700 PC — I had additional updates to install:

  • KB4023057: Update for Windows 10 Update Service Components
  • KB5004476 Out-of-band MS Store fix for Xbox Game Pass games

These took MUCH longer to download and install than the enablement package for 21H1, much to my surprise. Not all updates, apparently, can happen as quickly or easily as its minimalist changes (which mostly involve flipping switches for stuff already in the 20H2 OS).

Other Ways to Forcibly Upgrade from 20H2 to 21H1

Though it may be the fastest way to get from 20H2 to 21H1, other methods are also available. The Microsoft Update Assistant and an in-place upgrade install from mounted 21H1 ISO (both available on the Download Windows 10 page) will do the trick as well. But not only do these methods take longer, they also leave Windows.old and related cruft behind. That’s why I use the enablement package whenever possible. If you run out of patience like I did, I suggest you take the same route to get to 21H1 yourself. Enjoy!

Facebooklinkedin
Facebooklinkedin

X390 Yoga Replaces X220 Tablet

With the 2012 vintage Lenovo X220 Tablet going into a well-earned retirement, I need a replacement Dev Channel test machine. I’ve decided to call upon my 2019 vintage Lenovo X390 Yoga to fill that role. As the X390 Yoga replaces X220 Tablet, I’m sure I’ll be learning a lot more about this machine, even though it’s been around for 16 months or so.

More About X390 Yoga Replaces X220 Tablet

Originally, I purchased this laptop to replace my wife’s aging Ivy Bridge mini-ITX PC. I ended up going for a Dell Optiplex 7080 Micro instead. Since I bought the machine in December 2019, I’ve been using it to test the current GA version of Windows 10. Now, it’ll switch over to following the latest bleeding-edge Dev Channel releases.

Here’s how that PC is equipped:

  • 8th Generation (Whiskey Lake) i7-8565U CPU
  • 16 GB RAM (2×8 GB, soldered, DDR4 2400 MHz)
  • Intel UHD Graphics 620
  • SSDPEKKF512G8L Intel 1TB NVMe SSD
  • Intel Wireless-AC 9560 160Mhz Wi-Fi adapter
  • 13.3″ FHD (1920×1080) touchscreen
  • Fingerprint reader, Windows Hello camera
  • 2xUSB 3.1 Gen 1; 1xUSB-C; 1xUSB-C/Thunderbolt 3
  • MicroSD card slot
  • ThinkPad Pen Pro stylus included
  • Dimensions: 12.2″ x 8.6″ x 0.63″ / 310.4 x 219 x 15.95 (mm)
  • Weight: 2.85 lbs (1.29 kg)

Lenovo’s port map graphic that follows shows where everything is, on the unit’s right and left sides. It’s been a treat to work with and use.

X390 Yoga Replaces X220 Tablet.portmap
X390 Yoga Replaces X220 Tablet.portmap (click image for full-sized view).

Backup and Restore

Any test machine has to have backup/restore capability. That’s because there’s always the chance that updates, upgrades, or fiddling about will cause trouble. That’s what beta testing is about. I’m also prone to occasional “what-ifs” that have landed my PCs in trouble. Thus, it pays to be prepared.

I’ve got a speedy SATA-III SSD (Sabrent enclosure, Samsung EVO 500 nominal/465 GB actual) plugged into the USB-A port for backup. It takes about 6.5 minutes to do a complete image backup of the boot/system (and only current) drive. I’ll need to pop for a microSD card for this machine, now that’s it’s moving into a more active test role. I’ve also got a Macrium Reflect bootable Rescue Media USB Flash device ready to run restore as and when I need it.

How I Work with Test Machines

I don’t work directly on my test PCs, unless there’s some activity or utility that won’t work remotely. Frankly, I use RDP from my primary desktop for most interactions. That’s because I can do everything from my comfortable desk chair working on 2 Dell 2717 monitors. Almost everything works well that way. And if I do need to access the X390, I need only rotate my office chair to the left to access the unit. It’s situated atop a rolling file cabinet right next to my desktop case.

As time goes by, I’ll be writing about this nifty little laptop more and more in dealing with Windows 10 Dev Channel releases and related topics. Keep an eye out, and you’ll soon see evidence to support this prediction. Cheers!

Facebooklinkedin
Facebooklinkedin