Category Archives: Updates

Secure Boot Values Vary By Version

The most recent Patch Tuesday brought an interesting Secure Boot wrinkle to my Windows 11 test fleet. Production and Insider Preview systems now report different component versions, even though both appear fully updated. That sounds contradictory at first. A closer look says otherwise, even as Secure Boot values vary by version.

What’s Involved When Secure Boot Values Vary By Version?

On my production Windows 11 26H2 PCs, Garlin’s Secure Boot check reports SVN 12.0 and SkuSiPolicy version 3.0.0.20. My Insider Preview systems remain on Windows 11 25H2. There, the tool reports SVN 12.0 as well, but with a different associated file version and SkuSiPolicy 3.0.0.19.

The temptation is to assume that .19 is behind .20 and therefore needs fixing. Garlin says not. On both groups of systems, its final verdict is the same: “SUCCESS: UPDATES ARE FINISHED.”

Secure Boot State Matters More than Version Numbers

That result is the key to understanding what’s happening. Secure Boot servicing does not require every supported Windows branch to carry identical files. Microsoft says Windows 11 versions 24H2, 25H2 and 26H2 share a common servicing foundation. Version 26H2 can be enabled on eligible systems through an enablement package.

At the same time, Microsoft’s November 10, 2026 security update continues the Secure Boot certificate transition. Microsoft says the update adds more high-confidence device targeting data, expanding the population eligible to receive newer Secure Boot certificates automatically through Windows Update.

Windows release identity, individual Secure Boot component versions and Secure Boot remediation state are related. But they are not the same measurement, and they need not line up in synch.

SVN 12.0 Is Reassuring

For me, the most important common value is SVN 12.0. Both Production and Insider Preview have reached that security version number even though their SkuSiPolicy revisions differ.

That makes the .19 versus .20 split look like a branch-specific payload distinction rather than an incomplete update. I have found no Microsoft documentation that says SkuSiPolicy 3.0.0.20 is mandatory before Secure Boot remediation is considered complete.

Garlin’s identical success result reinforces that take. The tool sees both configurations as having completed the applicable Secure Boot update sequence.

Insider Doesn’t Mean Every File Is Newer

There’s another useful lesson here. We often think of Windows Insider Preview as automatically ahead of Production. That is true for many operating-system changes, but it does not mean every individual serviced component must carry a higher version number.

Right now my Production systems have moved to the Windows 11 26H2 designation, while my Insider Preview installations still identify as 25H2. Production also happens to have a newer SkuSiPolicy revision.

If It Ain’t Broke…

I won’t copy SkuSiPolicy 3.0.0.20 from Production to those Insider machines merely to force congruence. Secure Boot is specifically intended to maintain a trusted boot chain. Manually transplanting policy files because one version number looks newer would substitute my judgment for Windows servicing.

For now, the practical rule is simple. Check the security state, not just individual file versions. If SVN is current, Secure Boot is operating normally, and Garlin reports “UPDATES ARE FINISHED,” differing payload revisions can still describe fully serviced Windows installations. Here in Windows-World that means Secure Boot is A-OK. Good!

One More Thing…

After the Production update, I DID have to run Update_UEFI-CA2023.ps1 -SkuSiPolicy and reboot my production machines. That’s what took that value from 3.0.0.19 to 3.0.0.20 on those machines. After that Garlin’s check tool reports complete success as shown in the right-side half of the lead-in graphic. This is becoming a “thing to check” for Windows admins after applying Windows Update packages, especially Patch Tuesday CUs.

Facebooklinkedin
Facebooklinkedin

MS Store Sees Update Coming, But…

It’s definitely a Monday. I’ve got interesting oddities popping up right and left. Take a look at the intro screenshot. When I run “Check for updates” from the Updates and Downloads tab in MS Store, it sometimes tells me that it itself needs an update, but couldn’t run because the “App was in use” (as shown). Funnily enough, if I close the app then re-open it, that pending update no longer shows but is also missing in the “Recent updates list” below. Thus, MS Store sees update coming, but no longer see it when it’s done. Weird…

Yes: MS Store Sees Update Coming, But No History

I had to ask Copilot what it thought was going on. To my relief, it confirms that indeed this particular self-update goes untracked:

Once the update completes, the Store process reloads into its newly installed package. The Updates & downloads page then refreshes from inside that replacement package. Apparently, the Store does not reliably copy its own completed update into the user-facing Recent updates list.

So it seems to be a case of “Lost in transition” rather than “Lost in translation.” Just another interesting oddity to notice. It doesn’t seem to exact any consequences, as far as I can tell.

Self-Updates Are Almost Always Interesting

In working with WinGet over the past 6-plus years, I’ve noticed that things get interesting when running packages have to handle their own updates. That’s what I call a self-update. For example, WinGet itself (Microsoft.AppInstaller), PowerShell, and Windows Terminal, all get a little flustered when they themselves handle updates in an active Windows Terminal session.

Usually, the right way to straighten things out is to close them, then re-open them. Sometimes, a reboot may be needed to untangle the thorniest of self-updates. But gosh, this is the first time I can recall that the update history itself drops a stitch and misses its own incremental advancement. That’s odd, even here in Windows-World. But it’s all part of its strange charm…

Facebooklinkedin
Facebooklinkedin

New AMD Chipset Drivers Arrive Cleanly (8.09.28.1124)

AMD released Ryzen Chipset Driver 8.09.28.1124 on October 21, 2026. The 79 MB package supports Windows 10 and Windows 11 across a long list of Ryzen, Threadripper, AM4 and AM5 platforms. AMD characterizes this release simply as including bug fixes. But for me it was noteworthy that these new AMD chipset drivers arrive cleanly. No muss, no fuss, and pretty fast, too.

I installed 8.09.28.1124 on two AMD desktops, Flo6 and RyzenOfc. Both installations completed successfully, and neither installer asked for a Windows restart. I rebooted anyway, because that remains my preferred practice after chipset-level changes.

What’s Behind New AMD Chipset Drivers Arrive Cleanly?

Calling this a chipset driver is convenient but a bit of an understatement. Inside the .exe file, you find a platform-driver bundle with a plethora of independently versioned components. AMD’s release documentation says the package contains various independent drivers for supported Windows platforms.

I unpacked the installer for a closer look. Its Info.xml manifest lists components for PCI devices, I2C, UART, GPIO, PSP, SMBus, power management, USB4, HSMP and other functions. It also contains hardware-specific items for 3D V-Cache and multiple Platform Management Framework, or PMF, families.

Not every listed component lands on every target PC. The manifest describes the package’s total payload. A separate DevID.xml file associates setup tags with AMD and other hardware device IDs. Together, those files show why one download can service many different AMD systems.

Small Update, Big Coverage

AMD lists 8.09.28.1124 for chipsets ranging from A320 and X370 through B550, X570, B650, X670, B850 and X870, plus several Threadripper platforms. Processor support also spans generations, although availability varies by Windows version. It covered both my MSI and Asrock B550 mobo-based desktops quite nicely.

The release notes are unusually terse about changes. AMD says bug fixes are included but does not detail individual problems in its release highlights. Thus, I would treat 8.09.28.1124 primarily as a maintenance update rather than expect noticeable headline features or obvious performance changes.

No Reboot Prompt Here

My two installations offer a useful practical footnote. Flo6 and RyzenOfc both accepted the package without complaint, finished normally and presented no restart request afterward. That’s an observation from these systems, not a claim that every possible hardware combination will behave likewise.

Even so, the experience was blessedly uneventful. Download, install, finish. For a package that reaches deep into Windows platform support, boring is good. I still recommend restarting when convenient after a chipset update. It costs little time and starts the newly serviced system from a clean boot state.

For AMD system owners, 8.09.28.1124 looks like exactly the sort of chipset update I like to see: broad support, modest changes and, on my two PCs at least, clean installation with no reboot demanded. If you’d like to check this out for yourself visit the 8.09.28.1124 landing page (note: you’ll need to scroll down for some ways to see the donwload link: don’t worry, it’s there).

Facebooklinkedin
Facebooklinkedin

Correction: Installer Repairs Windows Images

Last Tuesday I incorrectly claimed that the Windows 11 installer upgrades Insider Previews. As I have now figured out, with some useful input from Copilot, it actually repairs those images. Had I actually tried to “upgrade” them, it would have failed. But I now know that the installer repairs the target image it’s run against. That’s the basis for my corrected assertion — namely, that the Windows 11 installer repairs Windows images. Let me explain.

Explaining Installer Repairs Windows Images

Simply by updating the Installer using Winget, it launches that app. When I allowed to proceed further, it was on me to halt things or let them proceed. Windows Setup (which runs inside the Installer, from a downloaded ISO) checks the following data:

  • Windows edition (Pro, for both X380 and X12)
  • Major version (Windows 11)
  • Feature Update family (26H2)

Indeed, Setup.exe permits a repair install to go ahead even if one or more of the following conditions is true

  • The installed build is newer (false)
  • The installed build is Insider (true)
  • The ISO build is older (false)
  • The ISO build is production (true)
  • The device remains enrolled in the Insider program (true)

Copilot’s summation “Setup does not block this build because a repair install is not considered a downgrade” (emphasis mine).

NOW I Get It…Finally!

I didn’t understand that Setup.exe could cross the Insider/Production boundary. It can, as I’ve now demonstrated to myself on two former test PCs. I’m going to promote two newer machines — RyzenOfc and AsusSnap to Insider versions — and leave these older machines on production builds. To that end, I’ve toggled the “Unenroll” switch on each of them.

Call this a lesson learned for yours truly. It’s not a mistake I will repeat. I tried it out to see what would happen. Now I understand how and why to steer myself around this pothole. And in a cack-handed fashion, it’s another way to pull a PC back from Insider status without a clean install. I’m still deciding if I like it or not: stay tuned, and I’ll tell you after I live with it for a whiile…

 

Facebooklinkedin
Facebooklinkedin

PowerToys Gets Double Upgrade

Here’s something I’ve not seen  before. As is my usual practice, I ran winget upgrade --all --include-unknown this morning. Upon returning to WinTerm after it was done I noticed something odd. The version number in the release notes for PowerToy (open automatically after any release) was higher than the target version in the Winget uprade info. Upon closer examination, I determined this is a case where PowerToys gets “double upgrade”. Let me explain…

How PowerToys Gets Double Upgrade

Indeed, winget took PowerToys to the targeted version (0.102.2862.0). But in the meantime, the PowerToys (PT) team released a higher-numbered version (0.102.2883.0). And because I have PT configured to auto-update upon launch, once the winget driven update finished, the program itself took care of the second one on its own.

For a split second, I wondered about possible pixies — or gremlins, maybe. Then  I realized it’s all baked into the way the app itself behaves. Here in Windows-World what looks like a mystery can just be the way things look odd sometimes, even as they do what they’re supposed to.

That’s what passes for entertainment these days here at Chez Tittel. And I admit, I’m both entertained and bemused.

Edge Rears Its Install Technology Head

Speed reader that I am I also initially conflated the message from Edge — entirely in character and seen many times before, BTW — with what PowerToys was doing. Not so. I just had to run the updater inside Edge itself and this momentary hiccup also cleared.

Keeping things updated is as much about remembering edge cases and exceptions as it is about following the channel in the river of new packages continuously showing up via winget. I do have to remind myself about that occasionally. But again: it’s all in good fun here in Windows-World.

Facebooklinkedin
Facebooklinkedin

UniGetUI Handles Discord Updates

In my September 16 post, “WinGet Mistakenly Reports Discord as Pinned,” I covered a quirk in how winget labels certain packages. I was reminded of same, as I observed that UniGetUI hanldes Discord updates easily and directly. If winget marks Discord as pinned and skips it, how can UniGetUI update it anyway? Let me ‘splain it to you.

How UniGetUI Handles Discord Update, While WinGet Fails

It is a handling difference that distinguishes the two package managers. Actually, WinGet itself stumbles only when using update --all. WinGet actually CAN handle a Discord update but it has to be commanded correctly and directly. UniGetUI uses WinGet to get (at least some of) its work done (also works with Chocolatey, Scoop, etc.). The trick turns out to hinge on how WinGet is told to upgrade Discord. The blanket approach just described fails because of a manifest flag (see 9/16 post for deets). Winget simply skips over that upgrade.

UniGetUI does things differently. Under the hood, it calls winget using an explicit package ID for each app that needs an update. For Discord it works just as if it had entered

winget upgrade --id Discord.Discord --include-pinned

at a command line (cmd.exe or PowerShell). In fact, WinGet will update Discord if you use similar syntax, to wit:

winget upgrade --id Discord.Discord --force

Manual Override Is a One-Off Avventura

Please note: the preceding command string is a one-time override. The RequireExplicitUpgrade: true flag that causes WinGet to skip over Discord for WinGet upgrade --all stays in place. Future winget upgrade –all runs will still skip Discord, so you would need to repeat the command each time you wanted to force that update manually.

UniGetUI’s approach turns this winget blind spot into a non-issue for anyone who prefers a GUI workflow. I’m actually coming to like this program more and more because of its consistent, user-friendly package handling. But WinGet remains number one in my heart because it’s command-line native, and readily susceptible to scripting and automation.

Facebooklinkedin
Facebooklinkedin

Powershell Update Goes Sideways

Interesting doings in the Windows Terminal PowerShell world. Running WinGet in that environment just now, I updated PS. Not only did that activity produce an “Installation abandoned” error msg, it initially threw up cmd prompt instead of PS when I clicked the plus sign to launch a new WinTerm session. Alas, it looks like this PowerShell update goes sideways (and more so on some PCs).

Ways PowerShell Update Goes Sideways

First, let’s survey the landscape. Windows PowerShell 5.1 is built into Windows and goes nowhere. It is a system component, not something you update through a package manager. PowerShell 7.x is a completely separate, side-by-side install. It lives in its own directory and uses its own executable, pwsh.exe.

The standard command for updating PowerShell 7.x is clean and simple. You open a terminal and run winget upgrade --id Microsoft.PowerShell. However, what looks simple on the surface can hide a lot of failure modes underneath.

Updates can stall mid-stream, roll back without a clear explanation, or appear to succeed while doing nothing at all. That last scenario is especially maddening. You see a success message, then run pwsh --version and get the old build number staring back at you. Something broke during the install, and winget did not catch it.

Oh No! Installation Abandoned…

I’ve seen this error message (see lead-in graphic) before. Normally, that means the PS installer has lost its connection to Winget via PowerShell and WinTerm. You can often see the PS installer window open, still running, and finishing its work. Closing, then re-opening WinTerm usually sets things back to rights.

Not this morning, on my Flo6 desktop (B550 mobo with AMD Ryzen 7 5800X CPU). After the upgrade, a new PS session launched cmd prompt instead. WinTerm lost its path to the pwsh.exe executable. When I went to look at its profile, it showed as empty. So I had to delete it, and recreate it, then point to the PowerShell 7 icon. That fixed things right up.

That Worst Case Isn’t Ubiquitous

When I updated PS on the Lenovo ThinkPad P16 Gen 1 mobile workstation, I got the same “installation abandoned” error message. But when I opened a new PS session (using the menu bar “+” control) the new version popped right up in a proper PowerShell pane.

I’m not sure why some machines act out more than others when the PS install goes sideways. Shoot! It could have been cosmic rays. But whatever happens, you can fix it if you check the profile and make sure it’s properly defined. Here in Windows-World knowing what to fix and how to fix it goes a long, long way. This morning, it went far enough to set things back up properly on Flo6. May it do the same for you, should you need it to!

One More Thing…

Just ran the same update on the ASUS Zenbook A14 (Snapdragon X ARM CPU). Completed successfully! I’m starting to think that platform diffs may play into this situation. The AMD platform failed and carried a persistent error state. The Intel platform failed, but recovered. And the ARM platform sailed right thru. Go figure!

 

Facebooklinkedin
Facebooklinkedin

Another OOO, Another Catchup

OK then, I’ve been away from home since October 1. Sorry to report it was to attend a memorial service for my brother-in-law, Mike Carey, who succumbed to lung cancer on September 19. Now that I’m back in the saddle, my first task was to check and apply all outstanding updates to the Windows fleet here at Chez Tittel. That sort of make my marching orders read “Another OOO, another catchup.” Let me tell you what that meant this morning…

Working Through Another OOO, Another Catchup

There are 8 PCs in the fleet at present. Two AMD, one Snapdragon X, the rest Intel. I ran through the gamut of update checks on each one and did the necessary.

Name WinGet DSA PMP Other Total
X12 5 3 2 0 10
P16 2 0 1 0 3
X380 9 0 1 1 11
Flo6 4 0 1 2 7
P3Ultra 4 1 3 0 8
AsusA14 5 0 1 0 6
Ryzen 11 0 1 1 13
D7080 3 0 3 3 9
Totals 43 4 13 7 67

In the column heads PMP = Patch My PC Home Updater and DSA = Intel Driver & Support Assistant. As you can see, I had a decent number of updates to handle (67 for 8 machines averages between 8.0 and 8.5). Under “Other,” I accessed Lenovo Vantage, Dell Command Update and the ASUS update facility, on related systems. And both of my NVIDIA-equipped PCs (RyzenOfc and Flo6) got GPU updates. But it’s all taken care of now.

Now What’s Next?

I keep up with WinGet on a more or less daily basis. The other stuff falls into the “as I read about it in the news” or “once a week” category. So I should be good until next week for now.

It’s good to be back. I look forward to catching up and commenting on recent Windows news, updates and introductions. Stay tuned, and I’ll tell you more.

Facebooklinkedin
Facebooklinkedin

Insider Preview Build Expiration

In today’s coverage at Windows Central, I found an interesting item. Indeed, the title is a little scary “Windows Insiders have one week to update their PCs, or else.” It seems that Insider Preview builds come with “flight certificates” that include an expiration date, and numerous builds will be hitting that date next Tuesday, August 11. Insider Preview build expiration comes with some gotchas, so it’s a good idea to update in advance to avoid them. Let me explain…

What Does Insider Preview Build Expiration Mean?

Thankfully, any Insider Preview expiration date is easy to find. If you look at the snippet of winver.exe output above, you’ll see it identifies itself as “[t]he Windows 11 Pro Insider Preview operating system…” It also provides expiration data, i.e. “Expires 10/31/2027 6:43 PM.”

As it happens, Microsoft embeds time-limited cryptographic certificates in every Windows Insider Preview build. These are called flight certificates, and when they expire, things get weird, fast. This post covers what flight certificates actually are, how to check whether your build has been renewed, and what happens if you let that clock run out.

Not Just a Pun:  Flight Certificates

A flight certificate is a code-signing certificate that Microsoft embeds directly into every Windows Insider Preview build. The name comes from Microsoft’s internal terminology for Preview builds — “flighting” — the practice of distributing pre-release builds to rings of volunteer testers. Think of the certificate as both a seal of authenticity and a built-in expiration thing.

Both of the flight certificate’s jobs are straightforward. First, it authenticates that the preview build you’re running is genuinely from Microsoft. That is, it’s not some 3rd-party repackage of dubious origin. Second, it acts as a gentle but insistent timer. As the certificate approaches its expiration date, the system begins reminding you to update. Let it fully expire, and the nudging stops being gentle.

There are some things a flight certificate is not: it has nothing to do with product activation, your MSA, or installed apps and files. Your activation status is unaffected by certificate renewal. The cert lives at the build level, not the license level.

Flight Certificates Come and Go Regularly

Microsoft renews flight certificates routinely, with an updated cert inside each new Insider Preview build. What’s unusual about the current renewal cycle is its scope. Historically, certificate renewals have mainly been a Canary Channel issue. This time, the renewal covers all channels (Experimental, Beta, and Canary). That’s a broader reach than typical and tells us that the flight certificate now applies across all active Insider flighting channels.

Here’s the thing (and the reason for the clickbait style Windows Central article title). The old certificate expires August 11, 2026. For Beta Channel on 25H2, the minimum renewed build is 26220.9022, which has been available since July 31, 2026. If you’re on that build or later, you’re already good through October 2027.

If not, unpleasant things may happen to your PC if you don’t upgrade in advance. As the Windows Central article states: “You will also stop receiving automatic background updates once the flight certificate expires.” See next section for more icky details.

Finding Flight Expiration Info

Checking your expiration date takes about ten seconds. Press Windows key + R, type winver, and hit Enter. The About Windows dialog that pops up will show an Evaluation copy line near the bottom, followed by an expiration date. If that date is after August 11, 2026, congratulations — you’re already on a renewed build and can stop worrying.

If your date is on or before August 11, 2026, you’ll want to act before the deadline arrives. Here’s what happens if you don’t:

  • A persistent “This build will expire soon” watermark appears on your desktop. You can’t dismiss, minimize, or right-click it away.
  • Automatic background updates stop arriving. You fall off the flighting pipeline entirely.
  • The machine doesn’t stop working, but it does become an isolated island: no new Insider Preview builds, no flight certificate renewal, no path forward except a manual update (clean install).

The fix is mercifully simple. Head to Settings > Windows Update > Check for updates. Then, let it find and download whatever’s on offer, install it, reboot. One update cycle and you’re current. The renewed certificate ships with the build, the watermark goes away, and normal flighting resumes.

I’ll admit: I’ve watched cert expirations play out on test machines over the years. But this one genuinely caught me off guard — not because it snuck up on me, but because my Beta Channel machine had already sorted itself out entirely on its own before I’d even noticed there was a deadline to worry about. Silent competence from Windows Update. Here in Windows-World that counts as success.

Further Reading

If you’re running multiple test PCs across channels the way I do, this is worth bookmarking now rather than rediscovering in a scramble on August 10th. For a solid news-side breakdown of the timeline and urgency, start with Sean Endicott’s Windows Central report, which does an excellent job of framing the stakes for everyday Insiders.

For the authoritative technical detail straight from Microsoft, including channel-by-channel minimum build numbers and step-by-step renewal instructions, Microsoft’s flight certificate renewal FAQ is the definitive doc. And if you’re new to the Insider Program or just want a solid orientation on how the whole flighting system works, the Windows Insider Program on Microsoft Learn is a good starting point. For a comprehensive look at which builds are available in which channels right now, the Windows Insider Flight Hub tracks the complete build-by-channel matrix.

Stay current if you can. The whole point of Insider Preview build expiration is to keep the testing community on builds that reflect where Windows is headed, not where it was six months ago. Keeping up is part of the Insider credo. You’ll get used to it: I sure have!

Facebooklinkedin
Facebooklinkedin

WinGet List/Install Orders Seldom Match

If you run winget upgrade --all --include-unknown regularly, you have probably noticed something odd. The packages listed in the upgrade table rarely install in the order they appear. I hit this recently on my ThinkPad X12 Hybrid Tablet, where six packages needed attention: Google Chrome, Microsoft Teams, MiniTool Partition Wizard Free, Oh My Posh, Patch My PC Home Updater, and Windows App. They were listed in one sequence but installed in a noticeably different one. The explanation stems from WinGet’s dependency resolver. It’s worth understanding, and explains why WinGet list and install orders seldom match each other.

Why Do WinGet List/Install Orders Seldom Match?

As you can see in the lead-in screencap, the upgrade table that WinGet displays before installation is sorted alphabetically by package display name — that is the first (Name) column, not the Id column. It’s purely cosmetic: WinGet queries its source index, collects available updates, and orders the results for human readability. The order in that table carries no weight when determining which package installs first. Think of it as a shopping list arranged by aisle label, not a build sequence.

Install Order Shows a Dependency Graph

Before the first installer touches the PC, WinGet’s dependency resolution engine reads every package manifest in the upgrade set. It constructs a directed acyclic graph (DAG) of declared dependencies. Next, it runs a topological sort namedGetInstallationOrder() on the winget source. That produces an install sequence where no package arrives before its pre-reqs are satisfied. This re-ordered queue need not follow name or ID order.

The X12 Hybrid Tablet Run

In the screencap, you see the raw WinGet output from a recent run on the X12 Hybrid Tablet. Six packages are available, listed in alphabetical order by display name — Chrome, Teams, MiniTool, Oh My Posh, Patch My PC, Windows App. The three declared VCLibs and Windows App Runtime dependencies follwing that list reinforce that notion that other elements than those that appear are in the mix. In the end, the actual install order was MiniTool Partition Wizard, Patch My PC…, Chrome, Teams, Windows App, and finally, Oh-My-Posh.

When List Order and Install Order Do Align

Occasionally the two sequences match — but that is coincidence, not design. It happens when none of the packages in the upgrade set declare inter-package dependencies and WinGet’s internal queue order happens to mirror alphabetical sequence. As soon as one package declares a dependency on another — or on a shared runtime — the topological sort reshuffles the queue and the coincidence evaporates.

A Practical Takeaway

No need to manage this manually. Winget’s dependency resolver handles the sequencing reliably. Indeed, fighting it with flags like --skip-dependencies is rarely worth the risk. Tyring to drive this yourself, you might end up with a package that installs against a runtime version it does not actually support. Trust the DAG, watch the dependency notice block that appears before the first installer fires, and you will get a clear picture of why the WinGet upgrade install order looks the way it does.

Next time you notice that WinGet installs packages out of listing order, check the dependency notice block at the top of the install run. That block is where WinGet “shows its work.” That’s where the topological sort result gets laid out in plain text. It is one of those quiet, well-engineered behaviors that rewards users who take a moment to read the output carefully.

Further proof of my earlier contention (see this June 27 post) that “WinGet knows more than it says.” I think so, but you can make  your own judgement. Here in Windows-World, there’s plenty of room for multiple takes on what’s REALLY going on. This is mine…and I’m sticking to it!

 

Facebooklinkedin
Facebooklinkedin