Category Archives: WED Blog

Cool Tools, Insider stuff, Recent Activity, Updates, WED Blog

Quick WinGet Post-Thanks Catch-Up

Leave a comment

Today’s my first day back in the saddle after a blissfully long weekend. It started Tuesday, November 26 and ended this morning (December 2: 6 days). Interestingly it looks like most other outfits were lollygagging around as well. Indeed, I assert that’s why I had such a quick winget post-thanks catch-up.  Running over the fleet this morning, it averaged 6-7 updates (min: 5, max: 8, most 6 or 7).

Explaining Quick WinGet Post-Thanks Catch-Up

As I said already, I’m quite sure the fallow period that precedes and accompanies a major hiatus (or holiday) is the culprit. To me, that explains little or no change over the past 6 days. That said,  a little bit of everything shows up on update lists. That includes 7-Zip, CrystalDisk (Mark and Info), TeamViewer, Visual Studio, OhMyPosh and more. For me, they are all very much among the “usual suspects” when WinGet does its thing.

And I think there’s more like that to come. The frequency and heft of updates in the period from now until after 2025 pops in will no doubt drop. It’s a simple outcome of the way business gets done around the globe. I hope that gives me more time to play with other stuff. Why? I’ve got two loaner units from Lenovo — a ThinkBook and a ThinkStation — that I need to set up, review, and return to sender.

That should keep me busy, right? Glad to be back at work, and hopeful that 2024 may go out on a happy note. Let’s see, shall we?

 

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

Troubleshooting 8Gadget Pack Crash

Leave a comment

I admit I’m still running Helmut Buhler’s excellent and informative 8GadgetPack, 12 years after MS withdrew support for gadgets when Windows 8 emerged. Since then, I’ve run it on Windows 8.x, 10 and 11 as a constant, useful source of desktop info. About 10 days ago, after updating Windows 10 to version 19045.5131, 8GadgetPack started throwing “Stopped working” and “APPCRASH” errors (via Reliability Monitor — see lead-in graphic). Since, then I’ve been troubleshooting 8GadgetPack crashes, which has — until a this weekend — prevented its use on the affected PC.

Lucky Guess: Troubleshooting 8Gadget Pack Crash

After updating Windows 10 to 19045.5198 today, I’d hoped the Gadget crisis would simply fade away. Not so. On a whim, I right-clicked the app and opted to “Run as administrator…” It not only worked, it also threw an error message that informed me it couldn’t run an “invalid gadget” named Currency.gadget. After I found that item in my AppData folder hierarchy, and deleted same, the tool returned to normal working behavior. Fixed, but weird. Also: lucky that’s a Gadget I don’t need or use.

Another funny thing is that I’m running 8GadgetPack on every Windows 11 version except Dev Channel Insider Preview (I don’t have one installed ). No problems there, nor any problems on the 3 VMs I have that also run some version of Windows 10. Go figure!

ReliMon Helps Illuminate Errors, Not Causes

If you look at the lead-in graphic, you’ll see these errors popped up on November 12, the very day that 19045.5131 appeared and got installed on my production PC. I actually exchanged some messages with Mr. Buhler and learned he was running the same build without any issues. (Shout out to Mr. B: Thanks!) That helped me understand it was something local causing trouble, not that specific update.

I don’t know why I decided to run the launch command:

"C:\Program Files\Windows Sidebar\sidebar.exe" /showGadgets

as an administrator, but I’m glad I did. It gave me just the information I needed to fix my problem and keep on Gadgeting. Sometimes you get lucky, here in Windows-World. I’m going to savor this win for a while, knowing that other problems won’t be as tractable…

For those who celebrate the Thanksgiving holiday: Happy Turkey Day! My best regards to all, including those who don’t get Thursday and Friday off. I’ll be off the air myself until next Monday, December 2, to spend some quality time with my family. I leave in three4 hours to go pick my son up at the airport, home from college. Cheers!

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

Canary Compresses Date/Time Layout

Leave a comment

Every now and then, Microsoft likes to mess with Windows desktop display stuff. Today’s case in point come courtesy of Windows 11 Canary Build 27754, installed two days ago. In this go-round, Canary compresses date/time layout at the far right of the notification area. You can see its incredibly brief form: 10:23 above, and 11/22 below in the lead-in graphic. Does that mean I have to like it — or even want like that? Heck, no. If Canary compresses date/time layout on its own recognizance that gives me cause to report here, and remonstrate elsewhere.

If Canary Compresses Date/Time Layout, Then?

Based on my attempts to reformat the date from its current minimalist form to something a bit more informative, neither Settings > Time & Language > Language and Region nor Control Panel > Region > Date and time formats exercises any obvious effect on its appearance. I filed a Feedback Hub request to ask them to allow the prevailing settings to work rather than changing them independendly. Sheesh!

If you want to upvote my Feedback Hub suggestion, see it at Notification time/date in Canary Build 27754. TIA.

The More Things Change, the More They Stay the Same

I’m not sure why MS rearranges things at its own whim, or for reasons not fully understood, explained, or immediately obvious. But it happens from time to time. Looking at the 27754 announcement, MS has this to say:

You can revert to the long form of the date/time and bell icon visuals by toggling the values in the Settings via Settings > Date and Time under “Show time and day in the system tray” and Settings > System > Notifications under “Notifications”.

Then I found it: there’s a down-caret for a dropdown menu on the “Show time and date in the System Tray” entry in the “Date & time” section. If you open that dropdown, you can switch back to long-form displays. Here’s what that looks like:


As you can see, I clicked the entry “Show seconds…” Once I did that the time then displays as 11:15:27 AM and the date as 2024-11-22, as per my settings. It looks like one must go the long way around to get to the right destination. That’s not a totally unexpected experience in Windows-World, either!

Why didn’t the announcement simply say, switch from Show abbreviated date and time to Show seconds in system tray…? I would’ve understood that immediately, and known exactly what to do. Sigh.

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

Revo Uninstaller Poses Typical Update Trap

2 Comments

I’ve seen it before. And I’m pretty sure I’ll see it again. Recently, I’ve noticed the Revo Uninstaller app popping up on my desktop without any action on my part. When I checked (enabled) Startup items in Task Manager, it was absent. But then, I did some poking around online. That’s how I learned that Revo Uninstaller poses typical update trap: when it updates, it resets its Options to check a box labeled “Check for update on startup.” Perforce that means it starts the app, and leaves it running on the desktop as well.

Foiling Revo Uninstaller Poses Typical Update Trap

You can see the Options window from Revo Uninstaller in the lead-in graphic above. To stop this from happening you will forgo update checks. But you’ll also forgo the application open on your desktop at startup. I’m willing to trade the inconvenience of the former against the annoyance of the latter. Problem is, this gets reset each time the app updates. So one must remember to uncheck the re-rechecked box to stay ahead of the annoyance. I guess that means I’m really trading annoyance against annoyance, and absorbing a minor inconvenience.

Too bad Revo doesn’t create a WinGet package for inclusion in its packages database. Then I’d catch this issue more readily in my usual day-to-day routine. That said, PatchMyPC Home Updater might manage to handle this without activating the checkbox — at least, as far as I can tell. Goes off to check… Nope, it leaves that alone, too.

Just another little sniglet of update trivia to track here in Windows-World. I guess I’m used to that by now…

Facebooklinkedin
Facebooklinkedin
Backup/Restore, Insider stuff, Recent Activity, Security, Troubleshooting, WED Blog

Windows Resiliency Initiative Includes Quick Machine Recovery

Leave a comment

It’s that time of year again, when MS meetings and conferences — Ignite 2024, in this case — heat things up with future promises and new idea campaigns. Yesterday’s Windows Experience Blog from David Weston (MS VP Enterprise & OS Security) is a case in point. Entitled Windows security and resiliency: Protecting your business, it asserts that a new Windows Resiliency Initiative includes Quick Machine Recovery as a key capability. Very interesting!

Explaining Windows Resiliency Initiative Includes Quick Machine Recovery

This new initiative “takes four areas of focus” as its goal — namely (all bullet points quoted verbatim from the afore-linked blog post, except for my [bracketed] commentary):

  • Strengthen reliability based on learnings from the incident we saw in July. [Crowdstrike kernel mode error took down 8.5M Windows PCs.]
  • Enabling more apps and users to run without admin privileges.
  • Stronger controls for what apps and drivers are allowed to run.
  • Improved identity protection to prevent phishing attacks.

The first and arguably most impactful preceding item is what led MS to its announcement of Quick Machine Recovery. Here’s how Weston explains it:

This feature will enable IT administrators to execute targeted fixes from Windows Update on PCs, even when machines are unable to boot, without needing physical access to the PC. This remote recovery will unblock your employees from broad issues much faster than what has been possible in the past. Quick Machine Recovery will be available to the Windows Insider Program community in early 2025.

In other words, this new feature should enable what savvy administrators had to do using OOB access to affected machine via KVMs smart enough to bootstrap machines otherwise unable to boot.

Great Addition: How’s the Execution?

IMO this is something MS should’ve built into Windows long ago. I’m curious to see how (and how well) it works. I’m also curious to see if it will be available for Windows 10 as well as 11. Only time will tell, but I’ll be all over this when it hits Insider Builds early next year. Good stuff — I hope!!

Facebooklinkedin
Facebooklinkedin
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