Category Archives: Windows 11

Scripting Macrium Rescue Disk Repair

Here’s something I’ve been chewing on for the past few weeks. I’ve had help from a persistent and curiously passive interlocutor at ElevenForum.com. I still use Macrium Reflect to back up at least half of my PC fleet.

For whatever reason, the Macrium Software team has yet to update its Rescue Disk creation to accommodate Secure Boot requirements. That’s what led me to scripting Macrium Rescue Disk repair using Copilot and PowerShell. Therein hangs today’s post…

What’s Involved in Scripting Macrium Rescue Disk Repair?

Basically, I asked Copilot to build a PowerShell script to fix the Macrium Rescue Disk for Secure Boot. Why? I use Secure Boot on all my PCs.

I can’t restore a Reflect boot image unless the Rescue Disk will actually BOOT the target PC. Only then can I perform the restore operation.

For the record, I’m using Macrium Reflect X, not the older versions numbered 8.x or lower. Working with Copilot, I had to chunk through three, then four versions before the script worked on my PC.

That PC is Flo6, my B550-based desktop. It has an MSI MAG Tomahawk MAX motherboard, Ryzen 7 5800X, NVIDIA RTX 3070 Ti, and 64GB RAM.

Using Copilot Requires LOTS of Trial and Error

The output from the script itself documents what it does pretty well, so I reproduce it here:

==============================================================
  fixmrrdv6.ps1  --  Secure Boot SVN Repair Tool              
==============================================================
   [>>] Validating target drive: G:                                                                                                                       
       [OK] Drive label  : ESD-USB                                                                                                                       
       [OK] File system  : FAT32
       [OK] Size         : 14.4 GB
       [!!] Label 'ESD-USB' does not contain MACRIUM -- verify correct drive.
   [>>] Locating boot.wim on rescue media                                                                                                                 
       [OK] Found WIM    : G:\sources\boot.wim                                                                                                           
       [OK] WIM size     : 557.2 MB
   [>>] Locating Secure Boot source files from live Windows
       [OK] External source: C:\Windows\Boot\EFI_EX\bootmgfw_EX.efi
       [OK] WIM source     : C:\Windows\Boot\EFI_EX\bootmgfw_EX.efi
       [OK] Winload source : C:\Windows\System32\winload.efi
       [OK] Backup root    : C:\Users\ed\AppData\Local\Temp\FixMRRD_Backups_20261026_155946
   [>>] Replacing external bootmgfw.efi on USB
       [OK] Backed up: bootmgfw.efi -> C:\Users\ed\AppData\Local\Temp\FixMRRD_Backups_20261026_155946\ExternalUSB\bootmgfw.efi
       [OK] Replaced: bootmgfw.efi from EFI_EX\bootmgfw_EX.efi
   [>>] Patching boot.wim (index 1) with Secure Boot files
       [OK] Mount directory  : C:\Users\ed\AppData\Local\Temp\FixMRRD_WimMount_20261026155946
       [!!] Mounting WIM (this may take a minute)...
       [OK] WIM mounted successfully.
       [OK] Backed up: bootmgfw.efi -> C:\Users\ed\AppData\Local\Temp\FixMRRD_Backups_20261026_155946\WIM\bootmgfw.efi
       [OK] Patched: bootmgfw.efi
       [OK] Backed up: bootmgfw_EX.efi -> C:\Users\ed\AppData\Local\Temp\FixMRRD_Backups_20261026_155946\WIM\bootmgfw_EX.efi
       [OK] Patched: bootmgfw_EX.efi
       [OK] Backed up: winload.efi -> C:\Users\ed\AppData\Local\Temp\FixMRRD_Backups_20261026_155946\WIM\winload.efi
       [OK] Patched: winload.efi
       [!!] Committing and unmounting WIM (this may take a minute)...
       [OK] boot.wim patched and committed successfully.

==============================================================
  All done! Secure Boot SVN repair completed successfully.
  Run check_bootmedia.ps1 against the USB to verify ALLOWED.
==============================================================

To debug this script, I kept catching error messages as it ran, reporting them to Copilot, and re-running rewritten versions until it produced a clean Rescue Disk on Flo6. How did I define that? By running Garlin’s check_bootmedia.ps1 script against it until it returned a clean result (all boot managers use CA 2023, show up as ALLOWED, use SVN 12.0). And indeed it works on Flo6 right now just fine.

What Works for Me, May Not Work for YOU

What I’ve learned from my interlocutor on ElevenForum.com is the following. Though the script runs on Flo6, it doesn’t run on his PC. Based on the errors he’s reporting, I think I know what’s going on. Writing files into a mounted WIM is tricky, as I’ve learned, and requires extensive mucking about with permissions. System ownership must be taken over, writing work done, then restored to pristine condition. This takes work and some understanding of how ACLs and the Trusted Installer work in modern Windows OSes (10 and 11, basically, though the same behaviors also hold in current Windows Server versions).

When things go wrong for me with a script like this one, I attack them with Copilot until they work. My interlocutor, apparently, isn’t inclined to do this himself. But that’s what it takes to make things work on YOUR PC here in Windows-World: a dogged determination to keep iterating until the error messages no longer appear, and the resulting functionality does what you want it to do.

Post some comments here to let me know if you’re OK with this “exercise is left to the reader to fully complete” approach. Those who really want the script to fix their Macrium Reflect X Rescue Disks can ask for it, and I’ll send it to them. But they’ll have to be ready to make it work on their PCs to achieve its intended use!

Facebooklinkedin
Facebooklinkedin

MediaMonkey Version Info Fools WinGet

MediaMonkey recently taught me another lesson about package managers: version information has to agree at both ends. Otherwise, automation can outstrip itself. Indeed, I’ve just witnessed how truncated MediaMonkey version info fools winget into a looping update.

I had already run a broad WinGet update using winget upgrade –all –include-unknown. MediaMonkey was included and its update completed successfully. Later, though, WinGet proffered MediaMonkey again. That follow-on install also completed successfully, leaving me wondering why an already updated application looked stale.

How Truncated MediaMonkey Version Info Fools WinGet

The lead-in screenshot makes a mismatch plain. WinGet identifies the package as VentisMedia.MediaMonkey.2024. Its list output reports the installed Version as “2024,” but Available is “2024.2.2.3222.” From WinGet’s perspective, those strings do not match.

A PowerShell registry query settles the question from the installed-software side. MediaMonkey 2024 records DisplayVersion simply as “2024.” The same entry identifies Ventis Media Inc. as Publisher and points to the 32-bit Program Files installation location.

Get-ItemProperty `
HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*,
HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*, `
HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* `
-ErrorAction SilentlyContinue | `
Where-Object DisplayName -Like '*MediaMonkey*' | `
Select-Object DisplayName, DisplayVersion, Publisher, InstallLocation, PSPath

That is the crux of the problem. The installed application advertises “2024.” The WinGet package advertises “2024.2.2.3222.” Thus, WinGet continues to find the need to upgrade even after installing the latest package.

A Blocking Pin Breaks the Loop

Rather than let routine upgrade runs keep revisiting MediaMonkey, I added a blocking pin against the package ID:

winget pin add --id VentisMedia.MediaMonkey.2024 --blocking

The next winget pin list confirms the result. MediaMonkey 2024 appears with version 2024, source winget, and pin type Blocking.

That choice is deliberately stronger than an ordinary pin. Microsoft documents a blocking pin as preventing upgrades through both “winget upgrade –all” and a direct package upgrade. The package must be unpinned before a normal WinGet upgrade can proceed, although the force option can override this specific pin behavior.

Watch, Wait, Then Unpin When It’s Time

For now, blocking is exactly what I want. The installed MediaMonkey is current based on the package I just installed, while its reported version remains too broad and unspecific for WinGet to compare cleanly.

The next move is patience. I will periodically check MediaMonkey and the WinGet package metadata. When a genuine new release appears, I can remove the block, run the upgrade, and see whether the installed DisplayVersion finally reports a fully qualified build number.

If that happens, WinGet should again have comparable version strings to work with. If not, the blocking pin can go right back on.

Version Metadata Makes the Difference

Yesterday’s episode is a useful reminder that WinGet can only act on available version information. A successful install does not guarantee the application and package catalog describe the result identically.

Here, two command-line checks tell the whole story. First, winget list exposes the disagreement. Second, PowerShell confirms what Windows knows about MediaMonkey. Until those values line up, a blocking pin turns an annoying repeat upgrade into a controlled watch-and-wait problem. Case closed, at least for now. Here in Windows-World it’s been added to the list of things I must watch and remember. It’s a big and pretty active one, as Windows pros already know…

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

Production Switchover Produces Unexpected Speed-up

Over the past week, I’ve switched two older PCs from Insider Preview to Production builds. For the record, the X380 is a 2018 vintage Lenovo ThinkPad X380 Yoga, while the X12 is a 2021 vintage Lenovo ThinkPad X12 Convertible Tablet Gen 1. Happily, this production switchover produces unexpected speed-up for both machines across the board. Let me tell  you more…

Why Production Switchover Produces Unexpected Speed-up

MS has been on a bit of a tear lately, trying to repair its user credibility and brand image for Windows 11. Industry observers have noticed and published stories like these:

My usual response to such coverage is “Yeah, right, sure…” (delivered with an eye roll and a skeptical tone of voice). But this time, it’s possible that the coverage is both apt and accurate.

What Improvements Might One Find in 26H2?

After the switchover from Beta (X380) and Insider Preview (X12) builds on those PCs to mainline 26H2 (Build 26300.9711 as I write this). I’ve noticed snappier response and quicker completions across the board on both machines. Some of this, says Copilot (and I agree) is simply a natural outcome of switching from a more heavily instrumented and closely monitored Insider release to a more streamlined and less tarted-up production release.

But there’s more. I am seeing noticeably faster performance on both PCs including:

  • Improved system responsiveness
  • Faster app launch times
  • Faster File Explorer
  • Lower RAM usage
  • Reduced latency in UI interactions

Case in point: I just ran winget upgrade -all --include-unknown on both PCs and they ran updates on CrystalDiskInfo, WinScript, CoreTemp and (as shown) MS.Gameinput. All did their work — checking the manifest, showing the update list, then performing the individual updates — enough faster than their previous usual that I noticed an improvement.

Same thing goes for app launches, installs and uninstalls outside of WinTerm. As old as these two machines are, I feel like they’ve gained a new lease on life. Here in Windows-World, that’s a win! Maybe I didn’t shoot myself quite as badly in the foot with the “Let’s try Installation Assistant and see what happens” experiment on these PCs as I had originally feared. Woo-hoo!

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

26H2 Installer Upgrades Insider Previews

Here’s something weird and interesting. In the wake of yesterday’s actions around updating the Installation Assistant, I discovered that 26H2 installer upgrades Insider Previews. At least, I’ve tried it on Beta and Insider Preview channel PCs and it’s worked. Thing is, those machine now show up as both 26H2 and still enrolled in the Beta channel, as you can see in the lead-in graphic.

Once 26H2 Installer Upgrades Insider Previews, Then What?

Good question. WU isn’t handing them the 2026-09 Preview Update (KB5124010) (26200.9550). They don’t show up under WU > Advanced Options > Optional Updates, either. I’m starting to wonder if my experimental maneuver might not have orphaned these Windows images.

BUT: today is Patch Tuesday. Copilot thinks that today’s mandatory CU will “take” on these installs. I won’t know until noon, local time (10 AM PDT, GMT -07:00). If it works, these installs aren’t orphans. If it doesn’t I may have to visit UUPdump to build a custom ISO to try another in-place repair install to catch up again.

I’m hoping I haven’t painted myself into another corner. That’s not an unfamiliar place for me to find myself, here in Windows-World. I’ll find out later today, and update this post accordingly. Sigh: it’s always something, right?

Après moi, le déluge…

Looks like WU is working the same on the updated Insider Preview PCs as on the mainline production models. All are offered the same four updates: KB5127694, MSRT, KB5130036 and KB5130034. So they’re not stuck. What they are, exactly, is still TBD. Interesting!

Now I know: KB5127648 is the key ingredient. WU doesn’t proffer it to my holdout PCs (the X12 and X380 upgraded to 26H2 thru in-place repair install). But I can grab it from the Update Catalog. Applying on both PCs right now (it’s a big’n: ~4.5GB). Takes a while to complete, But then “Something didn’t go as planned” and back into the previous state. Something ain’t right: I’ll be digging in.

Facebooklinkedin
Facebooklinkedin

Updated Installation Assistant Covers 26H2

On the still-working 2018 vintage Lenovo ThinkPad Yoga X380, WinGet delivered a new Windows 11 Installation Assistant this weekend. “Hmmmm,” I wondered to myself, “does this version incorporate the latest release?” It doesn’t really say in the update info shown in the lead-in graphic. But yes, this updated Installation Assistant covers 26H2. I’ll show you visual proof.

QED: Updated Installation Assistant Covers 26H2

And indeed, WinGet itself provides the proof. Notice the ID for this tool is “Microsoft.WindowsInstallationAssistant.” By happy chance, using that string with WinGet show includes “26H2” in its “Release Notes” field, to wit:

Release Notes identifies the installer as 26H2. {Click image for full-size view]

Copilot Leads Me In Another Direction

Officially, the Installation Assistant isn’t compatible with Insider Builds. And, as fate would have it, the X380 was running a 25H2 Beta build. Interestingly, the Installation Assistant runs: it downloads and installs 26H2 (and hangs forever at the 46% complete mark. but completes OK).

At first, Copilot says it doesn’t work “Assistant refuses all Insider builds.” But for both Beta and Insider Preview builds (26220.xxxx branches), it ran on both my X380 and on my Lenovo ThinkPad X12 Hybrid Tablet Gen 1. But first, I had to run PC Health Check even though both PCs were already running Windows 11. But in continuing along the install path after that detour, Installation Assistant showed me a new way to work around the typical bar on upgrading Insider builds using Production Windows images.

I’ll blog again tomorrow, and explain what happened on each machine, and where I wound up. It’s a surprising turn of events — to me, at least — here in Windows-world. Normally, this bar holds hard and fast. But the latest 26H2 installer may be an exception. Stay tuned: should be fun!

Facebooklinkedin
Facebooklinkedin

WU Offers Win11 26H2

OK, then. After reading numerous Windows rumors that the latest Windows version might drop today, I just ran the update check on WU. As you can see in the lead-in graphic, it’s offering qualified systems (including Flo6, P16, RyzenOfc and D7080) this item as the “Windows 11 2026 Update .” As WU offers Win11 26H2, that info provides the lead-in graphic for this very blog post.

When WU Offers Win11 26H2, Then What?

If you’re like me and love living on the edge, you’ll install it right away. If you’re in a corporate or other gated environment, you’ll bring up in a testbed first to see if it breaks anything. Given that this is another “enablement package” most of what’s coming is already here. And if last year’s 25H2 eKB (enablement package KB update) is any indicator, the whole experience should be pretty fast and painless.

Today’s Windows Experience blog post, from MS Product Mgmt VP John Cable, is entitled “How to get the Windows 11 2026 Update.” Appearances to the contrary in the title aside, it basically says “Comes to eligible devices via WU.” No download links, or anything like that. Fortunately, Shawn Brink’s covering post at ElevenForums provides x64 and ARM64 links to the eKB. Good enough for me!

The eKB Experience on AsusSnap

Because WU didn’t offer the eKB to my Snapdragon X Asus Zenbook A14 (aka AsusSnap), I grabbed the ARM64 download to try it out. It’s zipped and tiny (172KB compressed; 175K for .msu file). It completed in under 30 seconds on the target PC, and the reboot was pretty speedy, too. Shows up as Build 26300.9550 after the update:

Seems like mostly a no-brainer. Thus, I’m bidding adieu to 25H2 and saying hello to 26H2. Check it out: you may decide to do likewise!

 

Facebooklinkedin
Facebooklinkedin

Bye-Bye Copilot+ PCs

Looks like MS is retiring the Copilot+ PC branding and nomenclature. Why? As Trusted Reviews puts it “Microsoft dropping Copilot+ PC branding makes sense when every machine is AI-capable.” Or as more cynical observers might put it, If few people care, why bother? Even in September 2026, only 2-5% of PC sales fit the label anyway. With such a small market slice in play, no wonder MS isn’t shy about saying “Bye-bye Copilot+ PCs!”

A New Generation Also Says
“Bye-Bye Copilot+ PCs”

As I observed in last week’s Googlebook post, that company is entering a crowded field for AI-ready platforms, along with NVIDIA’s more formidable RTX Spark platform (both due week after next, Google’s on 10/4 and NVIDIA’s on 10/7). With all the hoopla for newer, different AI PCs could it be that Copilot+ PCs simply lost their shine? Methinks that is at leastly partly the case.

Looking at the proud branding from a May, 2024 article (appears as the lead-in graphic here), it now seems somewhat behind the times. Given the RTX Spark and Googlebook offerings, not to mention a new generation of AMD, Intel and Qualcomm 64-bit machines (laptops mostly, with a desktop or mini-PC here and there) the language seems over the top.

Indeed, I’ve got an ASUS Zenbook A14 here at Chez Tittel. While it is a real, honest-to-gosh Copilot+ PC, nobody would characterize it as one of “The fastest, most intelligent Windows PCs ever built.”

Usefulness Outlived: Time to Move On

With only a small sliver of the PC market covered, and a whole new set of AI-ready (and more capable) PCs in the offing, I guess Copilot+ PCs are simply passe. Time for the next big thing. MS has a Surface event coming up on the day of the RTX Spark on October 7. Perhaps the company will share a new vision for PC computing then?

Here in Windows-World, the more things change the more they stay the same. AI is still a happening thing for PCs in general (and laptops in particular). But it’s happening under a different umbrella (or set of umbrellas) soon. Should be interesting to see what happens next, and what MS has to say about it. Stay tuned…

 

Facebooklinkedin
Facebooklinkedin