Category Archives: Cool Tools

Recent Updates Bork Reset Option

In its Windows Issues list, Microsoft confirms that recent updates to Windows 10 and Windows 11 22H2 and 23H2 may cause the “Reset PC” option to fail if invoked. The actual issue is entitled “Reset and recovery operations on some Windows versions might fail,” and specifically identifies KB5063875 as a potential cause in Windows 11. WindowsLatest  also reports that KB506370 could do the same for Windows 10. Hence my heading “Recent updates bork reset option,” though versions 24H2 and 25H2 appear to be exempt.

Workarounds When Recent Updates Bork Reset Option

If either of the previously cited KB updates has been applied to a Windows install, one should avoid tempting fate. That means: don’t use the “Reset PC” button on such instances. Consequently, two options present themselves as workarounds:

  1. Perform a clean install of the same Windows version using an MS ISO or the identical version from UUPdump.net. Of course, that also means one must reinstall drivers and other software present on the PC when it left the factory…
  2. Roll back the update, then use the Reset PC button. The easiest way to do this is to visit Settings > WU > Update history, click the KB item therein, and select Uninstall. Alternatively, wusa /uninstall /kb:<number> /quiet /norestart should do the trick.

Better Not to Use It, If in Doubt

WindowsLatest also reports that the “Reinstall now” option may be likewise affected on 23H2 and 22H2 PCs (it’s not available on Windows 10). The best approach is to use alternative methods for repair and recovery, or one of the preceding workarounds, for possibly affected Windows PCs. This is a big enough deal, however, that MS will probably fix it as soon as it can.

Hopefully that mean this situaiton won’t persist for too long. But hey: It’s Windows-World. Anything is possible, and careful repair is always a good strategy. Stay tuned!

 

Facebooklinkedin
Facebooklinkedin

So Long Dynabook X40M2

It was nice while it lasted, but my time slot has expired. I’m shipping the Dynabook X40 M2 PC back to the maker’s PR group this afternoon. It’s been an enjoyable month working and playing with this handsome, sturdy, compact laptop. Though it’s no longer a Toshiba, it’s still called a Portege (a well-known and long-lasting laptop moniker). When I reviewed PCs for Tom’s back in the 2000s, I had a quite a few Toshibas pass through my hands. This new model is very much in the same vein. But now, alas, I must say “So long, Dynabook X40M2.” Let me conclude my adventures with some closing thoughts and observations…

Not Copilot+, But That May Not Matter Much

I was initially disappointed when I got this PC, to understand that it didn’t meet Copilot+ requirements.  Indeed, its Core Ultra 5 225U doesn’t hit the minimum TOPS number (40). That said, this unit has done everything I’ve asked it to with reasonable performance and battery life.  I chose to model typical productivity work involving Office, Adobe Acrobat, email, and so forth (no gaming or heavy creative workloads here) to reflect what students or office workers might demand of such a machine in the classroom, on the job, or on the go.

Small digression: I wondered how many PCs being sold these days are Copilot+ capable. Interestingly, Copilot tells me that 1.9% of global PC shipments in 2025 (in round numbers 1 in 50) fits that bill. So it seems that most buyers aren’t looking for such capabilities anyway. Outside that realm (which is most of the landscape) the X40-M2 plays very, very well.

Dynabook rates the unit’s battery life at 12-14 hours. I was able to break the 10-hour barrier on this machine twice, but mostly it came in between 9 and 10 hours when running email, web browsing, Office apps, Acrobat and Zoom or Teams video meetings. As is so often the case, the maker’s estimates are optiimistic, but the unit brings enough oomph to last a bit longer than a typical workday anyway. That’s all to the good, as far as I’m concerned.

Pros and Cons for the Portege X40 M2

On the plus side, the unit is sturdy, good-looking, compact, and lightweight enough for easy backpack or briefcase transport. It’s also got decent battery life, a good-looking display, 2 Thunderbolt 4 USB-C ports, and full-size HDMI and RJ-45 GbE ports. On the minus side, mine came equipped with a modest 0.5TB Samsung OEM NVMe drive that failed to impress with its performance (on par with faster Gen3 or slower Gen4 circuitry), and its pair of 5 Gbps (USB 3.2 Gen 1) USB-A ports.  For office or home work, seems like a good Thunderbolt 4 dock would be a useful add-on, given that one USB-C port otherwise goes for charging at least some of the time.

If I were to buy one of these units, I’d probably go for the Ultra 7 model instead of the 5. Interestingly, I don’t see a 32GB option on this line’s product pages. Here’s my final net-net on this beast: a good choice for college students or office workers. Not enough oomph for developers or knowledge workers, though (the lack of Copilot+ support may not yet be telling for such folks, but will weigh more heavily in 2026 and 2027 as AI comes more into its own at the OS level). Check it out at the Dynabook Portege X40-M Series home.

Facebooklinkedin
Facebooklinkedin

Jabra Headset Goes MIA

Sometimes, I have to wonder about Windows. For the past three years and more, I’ve  unplugged my Jabra Engage 75 headset from my production desktop. (FWIW, I’ve also recently upgraded to an AMD Ryzen 7 5800X running Windows 11 24H2.) I then plug into my Lenovo ThinkPad P16 Gen 1 instead, whenever I need video for an onlne meeting. Today, when I did that very same thing, the device worked locally but would not engage with Zoom. While my Jabra headset goes MIA, I made three expensive attorneys wait for me to get my act together. Sigh.

When Jabra Headset Goes MIA, Then What?

It seems I never installed the Jabra Direct software on the P16. All of a sudden the device stopped interacting with Zoom. It was easily fixed — I visited the Jabra site, and downloaded and installed the latest Direct version, then made sure headset firmware was up-to-date. Now, everything is working OK.

What I don’t understand is why it stopped working in the first place. I have to guess that some recent Windows Update made a change to the way audio works, and somehow orphaned the headset running entirely on its own. But with its controlling software installed, and firmware updated, all is back to what passes for normal here at Chez Tittel.

Too bad I had to waste a no-doubt costly 20-25 minutes trying to make my headset work, when I should’ve been talking to the interviewing attorneys instead. If it wasn’t my birthday (just turned 73) I might be inclined to sulk. But I’ll simply say instead: that’s the way things go sometimes, here in Windows-World!

Facebooklinkedin
Facebooklinkedin

BlueScreenView Version Unknown Stymies WinGet

I guess it was predictable. Having worked through various version mismatch errors with WinGet, it seems inevitabled that a package focus might fail to report its version info entirely. That seems to be what’s going on with Nir Sofer’s otherwise excellent tool for inspecting Windows crash dumps. But, as you can see in the lead-in graphic, the program fails to report its own version info. Thus, BlueScreenView version Unknown stymies WinGet updates. Sigh.

Depicting BlueScreenView Version Unknown Stymies WinGet

One standard technique for solving WinGet version info issues is the tried-and-true uninstall-reinstall manuever. That said, its successes depend on the developer fixing version mismatches in the packages that WinGet stores in its database. As you can see in the lead-in graphic, that’s NOT what happens with BlueScreenView.

What you see in that graphic is a sequence of efforts to fix the unknown version info for BlueScreenView (BSV, for brevity):

1:  WinGet upgrade shows that BSV has a version number “that cannot be determined”
2-3: WinGet goes to work to uninstall, then reinstall BSV
4: A repeat of Winget upgrade shows that BSV’s version number remains unknown

Alas, this won’t be fixed until Mr. Sofer does something to address the version information stored in the package data. I’m sending him some feedback to that effect after I finish this blog post.

Let’s see what happens next. It’s always something, here in Windows-World. I enjoy digging into WinGet problems as they come up, so that’s what you often hear about from me. Cheers!

Facebooklinkedin
Facebooklinkedin

PowerChute Software Steps Functionality Back

I find myself wondering why, why, why Schneider Electric (parent company of APC, maker of my brand-new uninterruptible power supply, or UPS) switched to forced registration and login for its latest generation of software. Seems like that’s a step backward, not forward, as its PowerChute software steps functionality back. I ended up visiting MajorGeeks to download the old version (3.1.0) which I’m using quite happily right now. It serves as the lead-in graphic above, in fact.

Why Say: PowerChute Software Steps Functionality Back?

The key to the new PowerChute Serial Shutdown (PCSS) software is registering the UPS device and setting up an online account. In turn that requires scanning and uploading or manually entering a device ID and a product key value from a preprinted label attached to the device. You can’t access the software without going through that process.

My problem is there’s no such label on my device. I’m not quite sure how I got one without that data, but that’s my situation. I’ve contacted Schneider’s online support forums to see if somebody can help. But in the meantime I can’t log into PCSS without a valid account, and I can’t validate my account without registering my device.

Frankly, I don’t understand why PCSS won’t work at all without that validation step. The old sofware — as you can see above — works just fine without it. That’s the basis for my assertion that this software steps functionality back. I can understand why Schneider wants to keep tabs on its customers and keep track of their devices. As I said, I can’t imagine why the software won’t work at all without jumping through such hoops.

Go figure! Sometimes, things in Windows-World make little or no sense. Ditto for access management decisions from some equipment makers. Good thing the old software still works (it’s scheduled to retire in January 2026). Hopefully, I’ll get things straightened out a lot sooner that that.

Successful, But Protracted Support Call Fixes Things

I got on the phone with Schneider tech support. Turns out they’ve got another version of the software that doesn’t require registration to let PCSS run. It took a while for the tech support person’s email client to figure out how to get me that file. We ended up having to use a link on Google Drive because my HTML email client was apparently bollixing their ZIP file (I could tell she was using a Salesforce environment, because the link resolved somewhere in Salesforce-land).

This time, when I started to install PCSS, it welcomed me and asked for configuration settings right away. No login or validation required. Why do  I think this means this isn’t the first time the support folks have been down this road? It’s working now as it should be, but I must confess: I do like the old software version better. It told me more, in a more approachable form. Indeed, I prefer a native Windows app to a web-based interface for this stuff. But hey: that’s progress!

Along the way, I figured out I’d plugged my devices into the wrong outlets on the UPS (hence, the foregoing zero values). They’re in surge protected but not battery backed up outlets. I’ll switch that soon. Cheers!

 

 

Facebooklinkedin
Facebooklinkedin

Will BlueScreenView Go Black?

In upcoming versions of Windows 11, says Microsoft, the long-standing “Blue Screen of Death” will go black. That is, it will change color and appearance from its deep-blue, graphics- and text-laden format. It will transform to something sleeker and simpler, in pure black-and-white colors. According to Windows Latest, this change should appear in Windows 11 24H2 or 25H2 and “may not be backported to Windows 11 23H2.” All this given, I’m asking this question: “Will BlueScreenView go black?” Let me explain…

Unpacking the query: Will BlueScreenView Go Black?

To begin, let me identify BlueScreenView as a NirSoft tool, from Israeli programming dynamo Nir Sofer. It’s been around for over 15 years, and provides simple decodes for Windows mini-dump and crash dump files. It’s darned handy, in fact, if a BSOD (of either the black or blue variety) gets past you, and you didn’t record the STOP CODE error that provoked the crash, it will show it to you.

The afore-linked Windows Latest story works itself into something of a lather by observing that (a) the new black BSOD looks a lot like a post-GUI Windows Update screen (it does), and (b) that some Windows users may mistakenly see it as such and miss the STOP CODE for that reason. Here again, BlueScrenView should come in handy to help find and expand on those pesky codes.

What I want to know, however, is if Mr. Sofer will issue a new version of his program, and call it BlackScreenView instead. I’m guessing maybe yes, maybe no, depending on how much weight he puts on that change.

These are the kinds of things I wonder about as I putter around happily in Windows-World. Let’s see what happens, shall we?

Facebooklinkedin
Facebooklinkedin

WinTerm Windows 10/11 Divergence

Here’s something interesting — and purely temporary. My Windows 11 PCs and VMs are getting updates to Windows Terminal, but my Windows 10 PCs aren’t (yet). As you can see in the lead-in screencap that means there’s some WinTerm Windows 10/11 divergence currently happening. To the left, Windows 11 shows version 1.22.11751.0; to the right, Windows 10 shows 1.22.11141.0. An upgrade attempt on WinTerm for 10 says “No newer packages are available from the configured source” (which happens to be WinGet itself). What’s up?

Why There’s WinTerm Windows 10/11 Divergence

Simply put. MS is pushing the Windows Terminal upgrade to 11 before it gets around to doing likewise for Windows 10. It could happen in the next hour, day, or week. But it surely won’t take much longer than that.

Here’s what Copilot says:

The version difference you’re seeing—v1.22.1141.0 on Windows 10 versus v1.22.11751.0 on Windows 11—likely comes down to staggered rollout timing and platform-specific servicing.

Microsoft often releases Windows Terminal updates in waves, and while both versions fall under the 1.22 stable branch, the build numbers reflect incremental servicing updates. These can include bug fixes, compatibility tweaks, or minor enhancements tailored to each OS version. For instance, Windows 11 might receive a slightly newer build first due to broader feature support or integration testing, while Windows 10 gets a more conservative rollout.

It’s nice to get a decent explanation, and it helps me appreciate one thing that Copilot really is good at: summarizing and stating the MS party line on what’s going on when interesting things happen.

Eye of the Beholder

Of course, I recognize that what’s interesting to me is not interesting to everyone. Perhaps it’s not even interesting to that many others. But hey, it’s definitely a feature of the way things happen in Wndows-World. And if you read this blog, you already know I care a fair amount about that kind of stuff. Hopefully, you feel likewise — or what else would lead you here?

Here’s a shout-out to Shawn Brink at Eleven Forum, whose X tweet alerted me to this situation. See also the related news item. Thanks!

Note Added 6/26 (One Day Later)

And as I check the running instance of Windows Terminal on Windows 10 right now, it’s been upgraded. My guess is that Windows Store caught it on its usual light-night/early-AM update cycle. And sure enough, here’s visual proof:

Facebooklinkedin
Facebooklinkedin

NZXT H6 Flow Build Comes Together

OK, then. This weekend, I got the Asrock B550 motherboard and its AMD Ryzen 5800X CPU squared away in its case. As this NZXT H6 Flow build comes together, I’m understanding more about what current PCs look like and can do. The NZXT H6 Flow is a stunner (and a pretty good deal at ~US$110). But I’m still waiting for a few parts to completely finish things up. Let me explain.

As NZXT H6 Flow Build Comes Together, What’s Next?

I ordered the Asus Thunderbolt EX5 adapter for this PC. It eats an x16 PCIe slot, but delivers 2Thunderbolt 5 USB-C ports with up to 120 Gbps aggregate bandwidth. More importantly — to me, anyway — it’s licensed for Thunderbolt Share so I can finally try that app out.

I’m also gradually building up an archive hard disk for that system, to transport all the stuff I might want to access from my current production desktop to the new one. It’s been a long, slow process with a huge amount of data and a stupendous number of files involved. Thus, I’m deciding it may take two drives — one for documents and other data files, another for my massive digital music collection — which means one of them will have to plug in via USB. Still thinking…

I’ve got an Asus PCE-AC56 PCIe x1 802.11ac Wi-Fi adapter from the old build that I could plug into the new one. But shoot, a Wi-Fi 7 version (PCE-BE6500) costs US$80 these days and might be a better choice. It’s only a fallback anyway: I’m already using the built-in 2.5GbE RJ-45 wired NIC, and it’s working like a charm.

I did bump the memory up from 64 to 128 GB (cost me about US$125 DDR4-2666). It’s pretty snappy, and that gives me room for lots of VMs, which I intend to make more use of going forward, while cutting down on the number of physical PCs in my mini-fleet (current count: 11, with one soon to be decommissioned and 3 more charitably donated to the middle school marching band).

Ultimate Goal: Cutover from i7SkyLake to Flo6

My ultimate goal is to retire my current production PC. It’s built around an Asrock Z170 Extreme7+ motherboard and an i7-6700 Skylake CPU. The mobo made its debut in 2015, but I built the system either in 2016 or 2017. In any case, it’s provided at least 8 years of excellent service and is showing its age.

Funny thing that my “new” system is already 4 years old as I cut over. My attitudes — and my budget — have changed a lot since the days in the late 1990s and early 2000s when I built and tested DIY PCs for Tom’s Hardware. Now that I’m paying for everything, I’m squeezing those dollars much harder before I let go of them.

Hopefully, this “new” system will keep me running Windows for at least another 4 or 5 years before it, too, becomes obsolete. That’s just the way things go in Windows-World, where the relentless influx of newer, faster, better keeps washing older, slower, lesser technologies and hardware away. All I can say to comment is: At least I’m still here, overseeing those changes.

Facebooklinkedin
Facebooklinkedin

Database Mixup Prompts Bogus Update

There’s always something interesting going on with WinGet, the MS package manager for installing and updating Windows stuff. Yesterday, a database mixup prompts bogus update orders for Visual Studio 2022. Let’s look at what happened, so I can explain the nit-picky little details involved.

But first: there really is no update involved. In fact, the Visual Studio version numbers are identical: 17.14.6, as you can see in the lead-in graphic. Note that the same version number appears in the columns for both “Version” and “Available.”

Fixing Database Mixup Prompts Bogus Update

The devil for these particular details lies in the difference between the two strings. The info from the “Version” column comes from the local copy of the WinGet source. It includes the parenthetical phrase after the version number — “(June 2025).” The “Available” version info does not include that string. Thus, there’s a mismatch, even though they’re the same base version number.

Simply put, because the version numbers don’t match, WinGet blithely assumes they’re different. Technically, they are. But they differ because somebody erred in creating one version string or the other.

Who’s on the Hook for a Fix?

Why Microsoft, of course, because Visual Studio is their product. Thus, they’re responsible for the package data in the WinGet database. As you can see in the following screenshot, in fact, that fix is already in. It depicts this morning’s WinGet show  and WinGet list data for Microsoft.VisualStudio.2022.Enterprise. Note that the version number info now agrees completely. Fixed!

The previous discrepancy is gone. [Click image to view full-sized.]

For further proof, I ran WinGet upgrade –all –include-unknown. It shows that CrystalDiskMark and Edge need updates, but Visual Studio no longer appears. The mismatch is corrected, so it’s no longer incorrectly flagged for update.

I’m a huge fan of WinGet, not least because the team at MS that works on its software and data is on top of things. Good stuff!

Facebooklinkedin
Facebooklinkedin

Strange Crystal Dew World Hiccup

Yesterday, I noticed that both WinGet and PatchMyPC Home Updater hiccuped when trying to update CrystalDiskMark (8.0.6 to  9.0.0) and CrystalDiskInfo (9.6.3 to 9.7.0). This strange Crystal Dew World hiccup (that’s the home site for both apps) got me wondering if the developer had abandoned freeware versions of those tools for ad-driven (installer-based) or for-a-fee (MS Store) versions only. I’m please to report that my presumption was wrong, and new freeware versions for both programs are updating properly now.

What Caused This Strange Crystal Dew World Hiccup?

Apparently there was some delay between when the new version info got broadcast and when the Crystal Dew World website got updated. Indeed I saw web info (which serves as the lead-in graphic for the story) that led me to wonder if ad-driven (ZIP and Installer) or paid-for (Store) versions were the only remaining versions of CrystalDiskMark (CDM) and CrystalDiskInfo available.

This morning, however, when I went back to check again, things were different. I still see the same situation at Crystal Dew World (here’s a link to its CDM download which includes an installer named CrystalDiskMark9_0_0Ads.exe). But WinGet and PatchMyPC can both successfully upgrade these tools now (they threw “hash match fail” errors yesterday) and are proffering ad-free freeware versions that come from sourceforge (you can use WinGet Show CrystalDewWorld.CrystalDiskMark to reveal its database contents).

Updates Take Time to Propagate

I’ve seen similar things happen before — often, with MS facilities such as PowerShell and Windows Terminal — when an update emerges but packages and database contents don’t synch up. All in all, though, I’m glad that freeware, ad-free versions of these useful tools remain available. If they didn’t I’d have to find something else!

And, far too often, such things become necessary here in Windows-World. Not this time, apparently for CDM and CDI. Not yet, anyway… But the ad-oriented interface at Crystal Dew World strongly suggests it could happen if not now, perhaps later.

Facebooklinkedin
Facebooklinkedin