Insider stuff, Recent Activity, WED Blog

Latest Canary Lacks Spurious Reclaimables

Leave a comment

An interesting Windows wart has gone missing in the latest Canary release (Build 27754, installed November 21). This is where you run DISM /online /cleanup-image /StartComponentCleanup in some Windows version and get a non-zero count when you follow that up with DISM /online /cleanup-image /AnalyzeComponentStore. This makes it impossible to get to zero for the “Number of reclaimable packages” line in that latter command’s output. When, I assert that the latest Canary lacks spurious reclaimables, I mean it shows a zero count as you’d expect it to after a successful cleanup.

Showing That Latest Canary Lacks Spurious Reclaimables

Take a look at the lead-in graphic. The “Number of reclaimable…” line clearly shows 0. Something about earlier updates in Windows 11 (including at least the GA and Beta releases — I just checked) causes the OS to show anywhere from 2 to 13 spurious packages. I define that to mean “non-zero number of reclaimable packages showing after a DISM … /Startcomponentcleanup operation completes successfully.”

Interestingly, the latest Windows 10 release (Build 19045.5198) also shows a zero value when I go through those same manuevers. So it lacks the spurious reclaimables now, too. It’s been showing those, on and off, for at least the past 18 months (see this post for an early report from yours truly). This revelation is simultaneously interesting, odd and mostly meaningless. Why that last adjective? Because this “issue” has no obvious or adverse affects on Windows operations, as far as I can still. Still: it’s NOT TRUE when it shows up.

For Incurably OCD Readers Only…

You can indeed fix this in other Windows 11 versions (e.g. Beta, Developer, Release Preview and GA) if you must. But if history is any guide that fix will last only until you install the next CU (cumulative update). Simply use the “Reinstall now” button under Settings > System > Recovery to perform in inplace repair install on your PC. That will temporarily get DISM … /AnalyzeComponentStore to report zero reclaimables. But again, that changes as soon as you install any CU. Go figure!

Facebooklinkedin
Facebooklinkedin
Uncategorized

Pondering Apparent Windows 11 Build Fork Jump

Leave a comment

If you look over my blog posts for the past few days, you’ll see I was trying to get the Lenovo ThinkPad X1 Extreme (2018 8th-Gen i7, etc.) from 23H2 to 24H2. I provide a list of links and capsule summaries to those item below. But the reason I’m puzzled is that manually applying KB5046633 took me from Build 22635.4460 (23H2 Beta) after which using the Installation Assistant took me to Build 26100.1742 (24H2 GA/Production). That’s supposed to be impossible. Thus, it’s got me pondering apparent Windows 11 build fork jump that somehow occurred.

Installer Oddity Has Me Pondering Apparent Windows 11 Build Fork Jump

I didn’t think the installer let one jump from Insider Preview versions (Beta Channel, in this case) to GA/Production images. But something I did — I think it’s the manual application of KB5046633 — let that happen. Once I got there, though, I was stuck. I couldn’t repair install my way to either the current GA Build (26100.2314) or its Beta Channel counterpart (22635.4510).

I can only surmise that I somehow slipped a version check. It might have happened when using the afore-linked KB item. Or, it could’ve happened when running the Windows 11 installation assistant after that. Truth to tell, I was relieved when my final repair operation hit a dead end, and the Windows Installer basically forced me to clean install Windows 11 from scratch.

Factor 1: Multi-Version Manual KB Installs

Indeed, KB54046633 works on both 23H2 and 24H2 based Beta Channel versions. The upgrade path from one to the other doesn’t necessarily need the full-blow installer (including the Installation Assistant). Indeed, Copilot tells me that when I applied KB5046633 it could’ve upgraded me from 23H2 to 24H2. But it did not.

Factor 2: Using the Windows 11 Installation Assistant

When I ran the assistant, that’s when the fork jump actually occurred. And again: I didn’t think it was supposed to work at all, let alone the way that it did. That’ s how I found the X1 Extreme enrolled in the Beta Channel but showing a GA/Production Build number.

The moral of this story is to limit yourself to the kinds of upgrade techniques you elect to use. Thank goodness these were all well-backed-up, non-essential machines. This could turn into a real snake pit for those not aware of such potential pitfalls. Me: I enjoy fallling into them, and then figuring out how to get to a better place. Thus, I hope you can learn from my mistakes … errrrr … adventures here in Windows-World.

Here are links to my previous blogs in this series with capsule summaries:

  • Nov 12 X1 Extreme Still Gets No 24H2 Offer: explains that this 2019 vintage laptop is still on some kind of update hold
  • Nov 13 X1 Extreme 24H2 Beta Pickle: Explains the sequence of updates that got me from a 23H2 Beta Build to a 24H2 GA Build
  • Nov 14 MSA Switch Brings Standard 24H2 Aboard: Explains how changing to a non-registered MSA produces only clean install option for 24H2.

Gosh this has been interesting and educational, too.

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, WED Blog, Windows 11, Windows Update

MSA Switch Brings Standard 24H2 Aboard

Leave a comment

Here’s the happy, happy conclusion of my recent saga involving the ThinkPad X1 Extreme laptop. When I ran the clean install of 24H2, I also provided a different MSA than the one I’d used previously. Because that combination of MSA and machine name is not enrolled in the Insider Preview program, the Windows installer went with the standard General Availability (GA) channel. Hence, I aver that an MSA switch brings standard 24H2 to that PC.

Why Say: MSA Switch Brings Standard 24H2?

The results speak for themselves, as you can see in the Winver output in the lead-in graphic. You can also see that the machine is not enrolled in any Insider Channel. Instead it says “Join the Windows Insider Program.” That means it’s not enrolled.

Because I use this machine on the road, especially for legal cases, that’s a good thing. I’m actually pleased to have this laptop back on the primary GA track. That means it should be as stable as Windows 11 gets. So, all’s well that ends well, but it took some doing.

A Long and Winding Road to 24H2 26100.2314

After I completed the clean install and started into the OOBE, I supplied a different MSA for this machine setup. It was therefore happy to stick with the GA thread of 24H2 releases. I did have to apply two sets of updates (2 CUs and one preceding update, plus an MSRT and a Confugration Update). I show most of that history in the next screencap:

2 CUs, another update, MST and configuration stuff (plus 8 drivers and 2 Defender updates) make the install current.

The Rest of the Schlemozzel

Now, of course, I need to restore the applications I like to use on my production PCs. PatchMyPC Home Updater can handle many of them, but I’ll need to install Office 2024, Nitro Pro, WizTree, and a few other odds’n’ends to bring the machine back to its former glory. But hey! I’m caught up to 24H2, back in the GA channel, and ready to rock and roll. It’s what passes for a happy ending, here in Windows-World!

Bottom line: as soon as the installer recognized it could only handle a clean install, things got on the right track. I’m not sure how I got off that track when I manually installed a CU the other day, but I’m glad to have a clue as to what’s what on that laptop finally restored.

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, WED Blog, Windows 11, Windows Update

X1 Extreme 24H2 Beta Pickle

Leave a comment

For me, a key aspect involved in learning Windows’ many ins and outs is occasionally painting myself into a corner. That’s what I seem to have done with the Beta Channel Windows 11 install image on my Lenovo ThinkPad X1 Extreme. ( Equipped with 8th-Gen i7-8850H, 32GB RAM, 2xNVMe SSD, and NVIDIA GTX 1050 Ti/Intel UHD 630.) As I explained in yesterday’s post I got it to build 22635.4460 under the 23H2 version umbrella. Upon discovering it was an Insider Preview anyway, I decided to run the 24H2 Installation Assistant, and let the chips fall as they would. Fall they did, and now I’m in an X1 Extreme 24H2 Beta pickle. Let me explain…

Easier Into than Out of X1 Extreme 24H2 Beta Pickle

Take a look at the lead-in graphic. It shows Settings > Windows Update > Windows Insider Program with the X1 Extreme in the Beta Channel. Alas, it also shows the Build number as 26100.1742. According to Copilot it was released on September 10. 2024 as part of the original Windows 11 24H2 update. It’s not a Beta Channel release. Rather, it’s a production release build (and what obviously provided the image info for the corresponding ISO or contents that the Installation Assistant uses).

That’s the corner I’m in right now. The Insider Program thinks I’m in the Beta Channel, but my current build and image fall outside that channel. On a whim I tried repairing the image with an ISO for 26100.2314 — the most current production build. To my combined relief and chagrin, this failed with a “The install failed” error. That’s what I’d expect from a version mismatch.

Onto the Next Repair: Beta Channel ISO

I’m now going to try again, with the latest Beta Channel item from the Windows 11 Inside Preview ISO Downloads page. My best guess, and my fervent hope, is that this will make for a successful in-place upgrade repair. At this point, I’m past the half-way point in the download. I’ll be able to access and use the ISO shortly…

The ISO mounted as the G: drive. I’m running setup.exe from the root directory right now. It’s checking for updates, then the installer had to restart itself. I’m now accepting the EULA and then comes the moment of truth: the only option available is for a clean install, as you can see here (note the two “keep” options are greyed out, and unavailable):

The Windows Installer finally gets wise and requires a clean install.

That’s an acceptable offer, and I’m going to take it. But first I want to experiment with WinGet Export to save all my stuff and attempt to import it back later on. I also need to make an image backup in case something goes wrong in my next planned steps.

Tomorrow, I’ll close this out, report on how the clean install went, and reflect on the whole experience. Stay tuned…

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, WED Blog, Windows 11, Windows Update

X1 Extreme Still Gets No 24H2 Offer

1 Comment

I’m getting down to the bitter end, and it’s troubling me. The Lenovo ThinkPad X1 Extreme still gets no 24H2 offer from Windows Update. Indeed, it’s my only remaining 23H2 holdout. Looking at the 24H2 Known Issues List, I can’t figure out why. One outstanding possibility is the Synaptics WBDI fingerprint reader. But shoot, it’s dated 12/4/2022. I’m puzzled… OTOH, Copilot says that Intel Display Audio drivers include Intel SST audio support, and that’s a listed issue as well. It could be the blocker, and a good thing to know.

Waiting Impatiently, as X1 Extreme Still Gets No 24H2 Offer

Here’s what I’ve done to try to address potential update hold issues:

  1. Applied all Optional updates, including drivers
  2. Use Snappy Driver Installer Origin (SDIO) to update NVIDIA and Intel Display Audio drivers (restart required)
  3. Run comprehensive cleanup and integrity checks (PC Manager, DISM, sfc, etc.)

Still no joy, and no real clue on how to get over this hump. All in all, I’m both miffed and bemused that a 2018 vintage (8th-Gen) i7 PC is still lagging behind the update pack. I’m biting my tongue, holding back on forcing matters. I guess I have a perverse desire to see how long it’s going to take for WU to come through with 24H2.

Only time will tell, I guess! And that’s they way things go sometimes, here in Windows -World.

Additional Oddments Present on X1 Extreme

OK, so today is Patch Tuesday. I couldn’t get WU to present KB5046633, so I downloaded the self-installing update file (.msu). It took nearly an hour to get it up and going again, but the PC is now running 22635.4460. I suddenly understand that this PC is running the Beta Insider version (a surprise to me, or perhaps a “senior moment”). THAT explains why the update took so long: it had LOTS of work to do to fit it into the beta release…

Given that it’s running an Insider version anyway, I’ve decided to force matters using the 24H2 Installation Assistant. Here goes… Chunking through the GUI portion without issues, but took awhile (~ 45 minutes). First reboot to completion: same again. But I had no idea the Windows Installer could play such hopscotch with Insider Preview updates. I just flat thought it wouldn’t work. It’s actually kind of amazing. And, with many things in my Windows experience, the biggest surprises — like this one — are mostly self-inflicted.

There is a problem though: the Build Number currently self-reports at 26100.1742. This corresponds to the early October build for plain-vanilla 24H2, NOT the beta version. I just ran WU and updated again, and it still reports the same build number. Very strange! I’m going to build an ISO for 22100.2314 and see if it will repair install. This is getting decidedly interesting…

Facebooklinkedin
Facebooklinkedin
Cool Tools, Insider stuff, Recent Activity, WED Blog, Windows 10, Windows 11

Fixing Winget Source Update Fail

Leave a comment

In the past two-plus years that I’ve used WinGet nearly every day, I’ve seen one error show up occasionally. It reads “Failed in attempting to update the source: winget.” This means that the winget command is looking to its own repository of known packages to obtain the latest list but unable to complete that access request. You can see what this looks like at the top of the lead-in graphic. The error follows right after the initial WinGet upgrade… command. The bottom part of that same screencap (it’s two pieces stitched together, actually) shows what’s involved in fixing WinGet Source update fail.

Fixing Winget Source Update Fail Has Its Own Command

It should come as no surprise that there’s a WinGet Source command that takes various subcommands to add, list, update, remove, reset and export WinGet sources. You can read all about these items in this MS Learn item The winget source command.

As you can see at the bottom of the lead-in graphic I used WinGet Source Update -n WinGet for my fix. Basically, that tells Winget to “try again” with updating the default WinGet source named WinGet. It does so automatically when you run WinGet Upgrade… But it does occasionally fail. And when it does, most of the time the Source Update at the head of this paragraph fixes things.

When Might WinGet Source Update Itself Fail?

A variety of problems could provoke error messages from the WinGet Source Update -n WinGet command I used for my fix. It might be that the WinGet source is offline. It might be some kind of networking communication problem is preventing access. I’ve never had this happen, but it would no doubt produce a different error message to help point you in the right direction. WinGet is well engineered that way.

Indeed, WinGet is now an essential part of my admin toolbox. I simply can’t live without it anymore. Cheers!

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, WED Blog, Windows 11

Replacement Production PC Planning

Leave a comment

All righty, now. I’m making the move to switch over from my now-ancient i7 Skylake B550 desktop to a Lenovo ThinkStation P3 Ultra. That has me jumping 6 Intel generations: the Skylake is a 7th-Gen beast; and the P3 is home to a Core i9-13900. I’ll also be switching over to a newish 46″ 2022 vintage monitor from a pair of 2017 Dell 27″ UltraSharps. As I get into the minutae of replacement production PC planning, big changes are afoot. It’s past time — and I’ll keep the Windows 10 box running to observe EOS and beyond — but I need to get production on a newer footing.

Comparing Cases: Replacement Production PC Planning

The lead-in graphic shows two PC cases side by side. On the left: the new SFF case on its side for the P3 Ultra. On the right, the Rosewill BlackHawk Ultra case (ordered from Newegg in 2015).  The picture is emphatically not to scale. By volume the P3 case would fit 4.77 times into the Rosewill case. The old beast is MUCH bigger.

But much of that size is meant  to accommodate as many as 8 3.5″ HDDs. By contrast, the P3 can accommodate 1 2.5″ SATA device and 2 M.2 NVMe SSDs. This is driving a lot of my pre-migration acquisition plans. Here’s the current iteration:

  • A modestly-priced Gen4 NVMe for the 2nd unoccupied slot in the P3 (estimated cost ~US$200).
  • 2 more 32GB DDR5-5600 SO-DIMMs to bring the unit up from 64GB to 128GB RAM. ($US150 or so).
  • If it will fit, I’ll use one of my Seagate 5 TB 2.5″ SATA drives in the unit’s SATA enclosure (it’s a tall drive heightwise: 15mm). If not, I’ll probably buy another 4TB SATA SSD (US$180 or so)

I’ve got everything else I need to bring the build together and start moving everything over. Max total budget looks like US$530 or so. Not too shabby. I’ll probably buy another copy of PC Mover to get everything moved over, unless I somehow get persuaded otherwise. It’s been my modus operandi for my last two production moves and seems to work reasonably well.

Stay tuned: more is surely coming … and soon, I hope.

Facebooklinkedin
Facebooklinkedin
Uncategorized

Copilot Still Hallucinates Occasionally

Leave a comment

I knew it remains a possibility. And I’ve seen it myself, from time to time. But this morning, I got slapped in the face with it: Copilot still hallucinates occasionally. I’m assembling parts to migrate my production desktop over from a 2016 vintage i7 Skylake desktop rig. I’m moving to a snappy 32-core Lenovo ThinkStation P3 Ultra. I need a lot of storage for that setup, so I asked Copilot the question in the lead-in graphic: “What’s the highest-capacity 2.5″ hard disk available right now?” I was stunned by the answer at at first, then…

Showing Copilot Still Hallucinates Occasionally

I’ve got a couple of Seagate 5TB HDDs here at Chez Tittel. I purchased them 3 years ago. At the time, they were the biggest 2.5″ drives available. And as it happens 5TB Seagates are STILL the biggest 2.5″ models for sale today.

Follow the link to the Tom’s story cited in the Copilot response. Then jump to Amazon for that Seagate IronWolf Pro 20TB item. Guess what? It clearly says “CMR 3.5 inch SATA 6 Gb/s, 7,200 RPM, 256 MB Cache” in laying out that drive’s specifications. It’s not a 2.5″ drive, period.

The good news is: if I want to use a 5TB 2.5″ HDD in this rig, I’ve already go two of them. The bad news is they’re pretty slow, as old-fashioned mechanical storage media can’t help but be. But there’s another hope!

Given the 5TB Limit, I consider 4 TB NVMe

Gosh, there’s not much capacity difference (25% figuring up, and 20% figuring down) between a 5 TB HDD and a 4 TB NVMe SSD. I’m coming around to the idea that I should buy a 4 TB NVMe for my second storage slot in the P3 Ultra. Decent models are available for around US$300, while the 5TB Seagate HDD costs US$233 or so. This provides roughly 10X the speed for 130% of the price. That’s a good trade-off. I’m still thinking but now I know how I’m leaning.

In the meantime, keep checking those blithe and speedy Copilot answers carefully. You wouldn’t want to be misled. Here in Windows-World it’s smart to stay skeptical, and double check what AI tells you.

 

Facebooklinkedin
Facebooklinkedin
Cool Tools, Insider stuff, Recent Activity, WED Blog, Windows 11

WinTerm Customization Remembered & Repeated

Leave a comment

I’m closing setting up and tweaking my Lenovo loaner SFF PC , just the way I like it. Indeed, I plan to switch my production desktop over from the 2016 vintage Skylake i7 I now use.Instead I’ll go with an uber-powerful ThinkStation P3 Ultra. It’s equipped with a 13th-Gen i9-13900, 64 GB RAM, Nvidia RTX A2000 12 GB, and a Hynix 2TB Gen 4 SSD. As a near-final step, I am fumbling through WinTerm customization remembered & repeated. You can see what I mean in the lead-in graphic…

Digging Thru WinTerm Customization Remembered & Repeated

It took four steps to get all the pieces lined up to customize my Windows Terminal as you see it in the graphic:

  1. Install Jan DeDobbeleer’s OhMyPosh for a custom prompt. That also required creating a $Profile file for startup. There are plenty of good how-tos around on this. I’m sad to report, however, that TekkiGurus.com is off the air. And thus, my series on this subject, too — find it instead on the WayBack Machine.
  2. Download and install the CaskaydiaCove Nerd Font (which I grabbed from NerdFonts.com) so that OhMyPosh can do its fancy thing with Windows Terminal prompt characters and environment variables. Handy now that drag-n-drop font install works inside Settings > Personalization > Fonts.
  3. Grabbed one of my favorite MS SpotLight images and then dimmed it up (30% opacity or thereabouts) to use as the Windows Terminal background. Dare I say I find it fetching?
  4. Ran the command Install-script WinFetch inside WinTerm to visit the script archive and install the eye candy that this displays about target systems when run.

Looks pretty good, doesn’t it? I’ve learned to expect and appreciate a bit of Windows Terminal pizazz to keep my eyeballs entertained while working at the command line.

And there you have it. Just another day in the paradise known to some as Windows-World. Good stuff!

Facebooklinkedin
Facebooklinkedin
Cool Tools, Insider stuff, Recent Activity, Updates, WED Blog, Windows 10, Windows 11

PatchMyPC Home Updater Mini Annoyance

Leave a comment

First things first: I’m a HUGE fan of PatchMyPC’s Home Updater product. Indeed, I got invited to try out the company’s latest version — an app-based implementation that supersedes PatchMyPC.exe — because I’ve written about it often and positively. In the interests of sharing my enthusiasm and support, I also have to report a recent PatchMyPC Home update “mini annoyance.” Let me tell you more…

What Is the PatchMyPC Home Updater Mini Annoyance?

It’s a Store app, so you must call it via the Start menu as “PatchMyPC Home Updater” to launch the program. But it’s NOT available in the Windows Store. Rather you must download it direct from the maker’s website, from the PatchMyPC Home Updater home page. If you try to find it in the MS Store, you get a big fat zip instead. Ditto for a search on “Patch My PC” as it appears here:

Only the website will do: the app is NOT in the MS Store.

Forewarned is forearmed, I guess. But gosh, it’s kind of a minor thing to add an app to the Store, isn’t it? C’mon guys: fix this sooner, rather than later. I applaud the new UI and the switch to a modern app style for this excellent tool. But please: finish the job and put it in the Store. Just sayin…

Facebooklinkedin
Facebooklinkedin

Author, Editor, Expert Witness