Category Archives: Windows 11

Copilot+ PCs, Insider stuff, Recent Activity, WED Blog, Windows 11

Copilot+ PC High-Perf Power Plan

Leave a comment

Here’s something interesting. I’ve got a Lenovo ThinkPad Yoga Slim 7i Aura 15 (aka Model 15ILL9) Copilot+ PC. It’s the Intel follow on to the Snapdragon X models let go earlier this year. In reading over Paul Thurrott’s November 14 review of that unit, I saw that defining a Copilot+ PC high-perf power plan will produce more reliable and faster output, albeit at some cost to battery life. FWIW, this accords with my own observations and experience. But by default, all Copilot+ PCs use the Balanced power plan. It gets better…

Where’s the Copilot+ PC High-Perf Power Plan?

Alas, likewise by default, Balanced is the ONLY power plan defined and available for Copilot+ PCs (and indeed, for most PCs that support the S0 sleep state). What to do? You can create one, but that involves tweaking more than a handful of settings. Wait: there’s a better way.

I went trolling around at ElevenForum.com and found a thread that linked to a Web site named  Windows Answer File Generator. It includes an entry named Windows 10 Power Configuration. Indeed, that script works for Windows 11 as well. So I used it, then downloaded the resulting file named power.bat to the afore-mentioned 15ILL9 Copilot+ PC. It ran within a Command Prompt session without issue, and shows up now as the current, in-use Power Plan:

After running the script, High Performance is the chosen Power Plan.

Good stuff! If you find yourself in a situation where you need more performance or reliability from a Copilot+ PC, this technique and its tool stand ready to help. Do yourself a favor, and give them a try…

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
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
Copilot+ PCs, Insider stuff, Recent Activity, WED Blog, Windows 10, Windows 11

MS Sez: Copilot+ PCs 5X Faster Than 2019 Models

Leave a comment

Here’s an interesting MS announcement from last week. I saw it, but didn’t read it all the way through. This morning, I read follow-up coverage (e.g. this WindowsLatest story). It’s entitled “How prepare for Windows end of support by moving to Windows 11 today.” Overall, it’s an eminently predictable bit of upgrade rah-rah. But specifically MS sez: Copilot+ PCs 5X faster than 2019 models.  I translated “5-year old PCs” from the original to get this year.

Weighing Copilot+ PCs 5X Faster Than 2019 Models

It just so happens that this cut-off equates to 10th Generation Intel CPUs (e.g. Comet Lake and Ice Lake). It also hits 3rdGeneration AMD Ryzen models (Matisse and Renoir). I’ve got 4 8th Gen Intel laptops here at Chez Tittel. I’ve also worked with 3 Copilot+ PCs (2 Snapdragon X models, and 1 Intel Aura/Lunar Lake model). My own gut feel, and my ongoing observation of resource intensive tasks — such as disk cleanup, updates, upgrades, big installs, and so forth — absolutely agrees with this claim.

If you dig into the October 31 announcement, you’ll find a section entitled “Benefits of upgrading to Windows 11.” Therein, author and MS EVP/Consumer Chief Marketing Office Yusuf Mehdi avers that when compared to Windows 10, 11 is

  • more sure and trusted
  • better optimized for speed and efficiency
  • better at multitasking
  • more accessible
  • more energy efficient

The 5x speed claim is footnoted to a May 2024 MS Learn item entitled Copilot+ PC performance details. That’s where the 5X claim gets some substance, which turns out to rest on the Cinebench 2024 Multi-Core benchmark. Further investigation shows this to be a 10-minute rendering test using the Redshift engine. Looking at the laptop segment at CPU Monkey, I see the first recognizable Copilot + PC in 17th place, with a value of 1,150 (Apple M2 Ultra (76-GPU) takes 1st place , with a value of 1,918).

Moving Up Probably Means Copilot+

With a handful of older PCs that I’ll need to upgrade in the next year or two, I am thinking about “what’s next” here at Chez Tittel. And indeed, most of what I’m thinking about buying into is Copilot. My first such purchase will probably be a Yoga Slim 7x (blogged July 1, 2024). It’s got a killer screen, runs like a demon, and represents a good value for its cost (~US$1,200 for 16 GB RAM, 0.5 TB SSD, and X1E-78-100 Snapdragon X CPU).

There will be plenty of other models to consider in the months ahead, as the Intel and AMD offerings get fleshed out alongside the earlier ARM Snapdragon X offerings. I’ll be choosing among those, or their successors, in the next year or two as I start upgrade. You should probably be thinking along those same lines. Unless and until something better comes along…

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

Forced 24H2 Upgrade Throws BSOD

Leave a comment

I couldn’t help myself: I HAD to try it. On the Lenovo ThinkStation P3 Ultra, I used the Windows 11 Installation Assistant to bring on the newest version. Alas, my forced 24H2 upgrade throws BSOD with error code 0X85 SETUP_FAILURE. Quick research found an MS Learn article on that very topic. Alas, it also says “a fatal error occurred during setup” and suggests unplugging peripherals and trying again, but provides no real repair advice. You can see my iPhone BSOD photo, skews and all, as the lead-in graphic here.

Bad Cess As Forced 24H2 Upgrade Throws BSOD

Please note: even though the BSOD text reads in part “We’ll restart for you,” I had to toggle the power button to bring the P3 Ultra back to life. Sigh: looks like its Intel i9-13900 Intel CPU is subject to some documented issues. Indeed, I just found an Intel Community post that says if Turbo Boost is enabled in the BIOS, it can crash during the Windows 11 upgrade process.

So I visited Settings > System > Recovery > Advanced Startup and then entered the BIOS. Sure enough, Turbo Mode was enabled, so I disabled same. Now, I’m running the Installation Assistant again. It zoomed through download and verification phases, so the files from the original download were obviously still present. Now it’s doing the GUI install portion …

Is the 2nd Try Charmed, or Doomed?

It took about 10-15 minutes for GUI install to complete. Turning off Turbo Mode notably slows things down. The post-GUI install went much slower, though: it zoomed up to 71% in 5-8 minutes, then took the better part of an hour to work its way to completion and OOBE.

But I’ve now got a working 24H2 installation on the ThinkStation P3 Ultra,  as you can see in the next screencap. It shows Lenovo Vantage device info, above which I’ve positioned Winver output. Then I had to go back into the BIOS and turn Turbo Mode back on. With Turbo Mode restored, the system runs very much faster.

Winver 24H2 in front, Lenovo Vantage Device Details in back.

Now, I have to ask: is this disable/enable in BIOS looming over all future upgrades, or is it just a one-time 24H2 thing? As the clue that pointed me toward this fix came from 22H2, probably not. Another thing for me to remember, in that case…

And isn’t that just the ways things go from time to time, here in Windows-World? You betcha!

 

Facebooklinkedin
Facebooklinkedin