Category Archives: Recent Activity

Installing Build 27802 Throws Memory Error

Here’s a new one on me. Last Friday, as I was installing the latest Canary Channel upgrade, the installer threw an error code that I’d not seen before. That code is 0x8007000e; its output from the Microsoft Error Lookup Tool (err_6.4.5.exe) appears as the lead-in graphic above. That error occurred during the GUI portion of the install. And it occurs to me that while installing Build 27802 throws memory error, it might have been because I was running WinGet in parallel, installing other stuff at the same time. I’m guessing was a self-inflicted thing…let me explain.

Self-Inflicted: Installing Build 27802 Throws Memory Error

The recommendation that comes with this error, is to restart the PC and try again. As soon as I did that — without added activity on the side — the upgrade installed successfully with no further errors along the way. As I look back on what got updated during my first botched attempt, I see that some fairly intense items were involved. Most notably, it included Visual Studio, for which a typical install is usually around 50GB in size. I can see where trying to juggle both on a 2021 vintage laptop (Lenovo ThinkPad X12 Detachable Tablet with 16GB RAM) might cause resource issues.

Anyway, the proof’s in the observation that a second attempt worked. That’s probably because I didn’t try to multi-task while the GUI install was underway. The only reason I haven’t done this to myself before is that you can’t do anything to the PC except let the installer run, during the post-GUI phase!

27802 Takes a While to Complete, Too

I couldn’t help but notice — because I perforce went through the process twice on the X12 — that the upgrade process to this latest build takes some time to complete. Normally, a Canary Channel upgrade finishes in under half an hour. This time around, the whole process — including download, GUI install, and post-GUI install — took about 75 minutes to complete from desktop to desktop.

At least I now know I should leave my PCs (mostly) alone while the GUI phase of a Windows upgrade is underway. I wonder what my next creative abuse of the runtime and installer will teach me? There’s always something new and interesting to learn, here in Windows -World!

 

Facebooklinkedin
Facebooklinkedin

PatchMyPC Updates 9 Apps Today

Gosh: I don’t see this very often. On the Lenovo ThinkStation P3 Ultra just now, PatchMyPC Updates 9 apps today. You can see them in the lead-in graphic. The whole thing took less than 4 minutes to complete. My appreciation for this handy update tool knows no bounds!

OK PatchMyPC Updates 9 Apps Today: Next?

The full name of the tool is Patch My PC Home Updater. (I’ll call it PMPC for brevity here). With 516 apps in its library, PMPC is not as comprehensive in coverage as is WinGet or the MS Store (2,600+ packages in the former, and over 60,000 in the latter). But it’s completely automated, incredibly easy (and fun) to use, and — for some odd reason — almost always faster than running the same installers in PowerShell or the Command Prompt.

Indeed, PMPC is also less careful or respectful of running apps than WinGet. It cheerfully stops web browsers (and other apps) to update them, then restores their previous runtime context. In WinGet, you will often either be unable to update a running browser (e.g. Chrome) or you’ll have to relaunch it manually (e.g. Edge or Firefox).

It’s a handy tool, and comes in a variety of commercial forms that work with Autopilot and InTune, among other patch and update management systems. As with WinGet, you can also use it to install and uninstall the items in its library as well. Highly recommended, and a treat to use.

Facebooklinkedin
Facebooklinkedin

So Long, ThinkCentre M90a Gen5 AIO

Allrighty, then: I’m packing up the Lenovo All-in-One for return to North Carolina. It’s been fun, but it’s time to say “So long, ThinkCentreM90A Gen5 AIO.” As I’m readying the unit for return, I’ll also file this blog post by way of final thoughts and farewells to this doughty device. Overall, it’s actually quite fast and capable.

Adieu & So Long, ThinkCentre M90a Gen5 AIO

Overall, I like the performance and compactness of this All-in-One. As I said before, this unit would make a great office/cubicle PC; ditto for college students looking for a dorm room desktop. It would, however, make sense, to spend ~US$500 less for 8GB RAM and 256GB SSD with no optical drive, then add more memory and a second SSD at market prices to match the pricier configuration. That’s because, as configured, this unit costs around US$2K (i7-14700, 1TB SSD, 32GB RAM, Windows 11 Pro, optical drive).

I also don’t understand why Lenovo didn’t provide Thunderbolt 3 or better ports — ideally, USB4 compliant ones — in this AIO. It comes equipped with numerous USB-A ports and a single USB-C (8 in all). Alas, they top out at 10 Gbps USB 3.2 Gen 2 speeds (2 of those, plus another 6 USB 3.2 Gen 1 5Gbps ports, all of the Type A variety).

An AIO Past Its Peak?

Though the CPU is a speedy 20-core model (8 P-cores for 16 threads, 12 E-cores for a total of 28 threads altogether), no NPU means this unit is not Copilot+ capable. Those wishing to exercise Windows 11 24H2’s more advanced AI capabilities can’t do so on this PC. I’m also a bit vexed at the lack of high-speed USB as well. But if those things don’t play into your users’ computing needs, this is  a solid, work-ready PC. If I were going to buy one myself, though, I’d look for refurb deals or discounts from Lenovo or other resellers.

The display is gorgeous (2880×1800) and supports refresh rates as high as 160MHz. It’s a treat to look at, and work with. I also hooked it up to a 34″ external Acer monitor, and the Intel 770HD chipset had no issues driving its built-in 24″ display at the same time. It made for some impressive and watchable screen real estate. Yes, I know: that plays against the compactness factor, but I was curious! HWiNFO output for the built-monitor serves as the lead-in graphic here.

As the unit heads back to the reviews team, I find myself wondering what Lenovo might send my way next. Stay tuned: I’ll tell you all about it. Can’t wait!

Facebooklinkedin
Facebooklinkedin

Free Macrium Update Conundrum

OK, then: I’m chuckling. I’ve noticed for the past two months that while Macrium Reflect Free (v8) notifies me updates are available, it never downloads them. Then, I used one of my two remaining paid-for v8 licenses and presto! v.8.8.8325 is now available for download. That poses a free Macrium Update conundrum — namely, are they or aren’t they? So I asked Copilot about company policy on updates for that free version.

Here’s what it told me:

Yes, Macrium has stated a policy regarding updates for the free version of Macrium Reflect. As of January 1, 2024, Macrium Reflect Free v8.0 no longer receives feature, compatibility, or bug fix updates. Security patches were provided until that date, but no further changes are made to the v8 Free code base.

You can continue to use Macrium Reflect Free, but to receive updates and new features, a paid license is required.

Timing the Free Macrium Update Conundrum

Again, I’m chuckling because I’ve managed to go nearly two full months before catching this on my various testbed PCs. That’s also a clever use of notifications from Paramount Software (the makers of MR). It let me know — somewhat more slowly than I’m sure they intended — that my old free licenses were orphaned.

Now that I’ve updated as many of them as I can, I need to figure out how many MR version X licenses I’m actually still using. I’ve sent at least 3 or 4 such machines back to Lenovo after installing paid-up versions on them. I need to reclaim them so I can use them for other such machines as and when they show up here at Chez Tittel.

And now, at least, older members of my mini-fleet can get their Macrium updates on. Boy howdy: Isn’t that just the way things go here in Windows-World from time to time? Keeping up isn’t a full-time chore, for sure, but it does require paying a certain amount of attention…

 

Facebooklinkedin
Facebooklinkedin

Recent RDP Hiccups Confirmed

I’ll be darned. It isn’t often that my local minor Windows gotchas make the news. But there they were this morning on Windows Latest: Windows 11 24H2 RDP hangs on login, RDP session connecting issues reported. For at least the last month or so, I’ve had RDP sessions hang on the login screen, and stay stuck there. Now that I think upon it, the client on the “other side” must’ve been some version of 24H2 (Canary, Beta, Release Preview or Production). That’s why I say: recent RDP hiccups confirmed.

What to Do When Recent RDP Hiccups Confirmed

In my case, this turns out to be a minor enough gotcha that I’ll keep doing what I’ve already been doing. Of course, now I can start waiting — and looking — for some relief from MS. Turns out that if you close the hung RDP session and reconnect to that client, the connection works 90+% of the time. That’s good enough for Windows work here at Chez Tittel.

I have, however, noticed that the Remote Desktop app is less subect to the hiccup (though still not completely immune). I can’t function with remote access of some kind. That’s because I’ve got 6 Windows 11 PCs in my office, and 3 more upstairs. And you guessed it: all are running Windows 24H2 of some kind by now.

A Group Policy Fix May Do the Trick

WindowsLatest also reports that changing the value for a particular node in the Windows Group Policy tree can fix this issue. That node is:

Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections

Open Select network detection on the server. Next, make sure that value is set to Enabled, then give it a value of  Turn off Connect Time Detect and Continuous Network Detect.

According to the story, that should fix things, with no reboot required. Let’s see … goes off to check … seems to work as described. At least, the half-dozen connections I just tried all came up, sans hiccups. I’ll see how things go longer term and report back here if anything fails in the interim.

Facebooklinkedin
Facebooklinkedin

Lenovo Q3 Results Support Refresh Year Notions

The world’s biggest PC maker — Lenovo, that is — just reported results for the third quarter of its fiscal year (ended Dec 31). It shows approximate growth in revenues and profits over Q3 for the previous fiscal year. One phrase from the report (PDF) caught my eye: “Commercial sales benefited from the Windows 11 refresh, with premium workstation sales spearheading demand recovery…” Hmm, could it be possible that these Lenovo Q3 results support “refresh year” notions for 2025? You bet!

How Lenovo Q3 Results Support Refresh Year Notions

Back on January 6 I posted about the MS supposition that AI additions to Windows 11 plus Copilot+ PCs could turn 2025 into The Year of the Windows 11 Refresh (that’s a link to their blog on this topic as well as a good summary). As the biggest player in the PC market, Lenovo’s latest quarterly numbers certainly plays into this picture. And it does so in a way that speaks for the “refresh year” idea, rather than against it. Could MS actually have a clue?

I cribbed the lead-in graphic for this story from Paul Thurrott’s coverage of this topic: Lenovo Revenues Jump 20 Percent to $18.8 Billion. It shows how the number have fared over the past 5 quarters, with a dip from Q1 to Q2 in that series, but steady growth and recovery since then.

What Else Could Speak to Refresh?

It is interesting to see how next-ranked PC players numbers either further support this notion, or call it into possible question. Copilot says that means HP, Dell and Asus (Apple holds spot#4, but I’m pretty sure they’re not much into playing the Windows 11 refresh game).

HP’s Q4 24 results show a 1.7% jump YoY (nowhere near Lenovo’s ~20%), but they do cite “steady progress in Personal Systems and Print.” Dell’s overall revenues and earnings declined over 2024, as did the number of units it shipped that year (39.1M vs. 61.8M for Lenovo, 53M for HP, and 17.9M for Asus). Asus was up 8.8% YoY in PC sales, and their strong showing in PC sales helped contribute to their success.

Nothing Entirely Clear Yet, Yea or Nay

Lenovo’s results are the only ones that mention the refresh phenomenon explicitly. But if it pans out further, I expect we’ll hear more from other OEMs, too. Stay tuned: I’ll keep you posted.

 

Facebooklinkedin
Facebooklinkedin

WinGet Installs Neofetch Directly

OK then, I’ve had a little more time to research and think about yesterday’s blog post, which seized upon the Chris Titus install/update/tweak PowerShell script as a way to get Neofetch installed on Windows. It most assuredly works, but there are easier ways to get this done. Indeed, with the right knowledge and syntax, WinGet installs Neofetch directly. Here’s the syntax:

WinGet install Neofetch

You can see that in the lead-in screengrab. It shows that WinGet knows about a package named neofetch-win with an associated ID of nepnep.neofetch-win. Indeed, that turns out to be the key to finding this project at GitHub. Turns out that nepnep39 is the developer’s handle, and neofetch-win is the name of this GitHub project.

Why WinGet Installs Neofetch Directly

TLDR answer: because the developer has created a package definition for neofetch-win that’s known to WinGet. Indeed, I got the simplest possible syntax shown in the lead graphic from the GitHub project’s README file. Who knew? A lot of people, apparently (he thanks visitors for 50K downloads in March 2024). But alas, not yours truly until yesterday. Sigh.

There’s another way to use WinGet to install Neofetch, also shown in the lead-in graphic, albeit indirectly. You can use the ID mechanism as well, to wit:

WinGet install --id nepnep.neofetch-win

This approach specifically calls out the package by its full ID string, as registered in the WinGet package database.

Even GitHub Provides More Ways

If you visit the “Latest” release page for neofetch-win at GitHub (1.2.1 as I write this), you’ll also find links to an .exe file and an MS Installer (.msi) file there. They work, too, to provide access to this nifty little tool from the UNIX/Linux world.

Where there’s a will to use WinGet, it’s often possible to find a way to exercise same. In this case, I simply needed to find the right handle. It must’ve been too obvious for me, but now I know how to get there from here. And so do you… But heck, based on nepnep39’s March 2024 thankyou, maybe you already did.

Facebooklinkedin
Facebooklinkedin

MS Seemingly Drops Intel Gen7-10 24H2 Support

Whoa! Maybe even “Double Whoa!!” Look closely at the recently updated Microsoft Learn Windows Hardware Developer document Windows 11 Version 24H2 supported Intel processors. Careful examination shows that MS seemingly drops Intel Gen7-10 24H2 support. That’s right: everything from Gen 7 (Kaby Lake; 2016 mobile/2017 desktop) to Gen 10 (Comet Lake; 2017 for both mobile and desktop) is absent from that list. I’m concerned, and so are lots of other industry followers and reports (e.g. WinAero, Tom’s Hardware, Eleven Forum, and so forth). Can this be true?

Really!? MS Seemingly Drops Intel Gen7-10 24H2 Support

Initially, I wondered if this could be an error or oversight. But apparently, it’s a deliberate strategy aimed at OEMs. Indeed, a Windows Latest item dated today (2/17/2025) explicitly debunks this notion: No, Microsoft is NOT dropping Windows 11 support for Intel 8th, 9th, and 10th Gen chips. Though the absence of these items prompted plenty of speculation that Gen 7-10 were falling off the 24H2 table, here’s what that item states:

…first…Microsoft has renamed the document to mention the Windows 11 24H2 release. Second, the list of supported processors does not include “8th gen, 9th gen, and 10th gen Intel” chips. This led some people to believe that older Intel chips are no longer officially supported for “Windows 11 24H2.”

In response to this belief, Windows Latest asked MS directly and got this added clarification:

In a statement to Windows Latest, Microsoft confirmed that Windows 11 hardware requirements hadn’t changed since 2021.

I’ll also observe that the first paragraph of this Learn item states “…released and future generations of processors which meet the same principles will be considered as supported, even if not explicitly listed.” Guess what? That includes the “missing” Intel Gen7-10 CPUs, dear readers.

Windows 11 for AI vs. Other Flavors

Apparently MS is steering OEMs toward Intel CPUs that provide the necessary NPU and other items necessary to qualify for Copilot+ classification. It’s another logical, if vexing, consequence of the “Year of the Refresh” that MS is promoting for OEMs that want to support 24H2 fully and completely. Go figure: it seems to be something of a tempest in a teapot!

Facebooklinkedin
Facebooklinkedin

Waiting On Next NVIDIA Studio Driver

Oho!  A new NVIDIA Game-ready driver is out. As you can see in the lead-in graphic this one’s numbered 577.42. But if you’ve been reading this blog of late, you already knew that both the January 30 Game-Ready AND Studio drivers gave my dual monitor rig fits (get the gist from this Feb 5 item). Hence, my response to the new driver is below tepid. Instead, I’m waiting on the next NVIDIA Studio Driver to come along. I hope my optimism that it might fix dual monitor gotchas is justified. We’ll see…

Why I’m Waiting On Next NVIDIA Studio Driver

The January 30 update included both Game-Ready and Studio driver version. Alas, both also exhibited the same unwanted behaviors on my dual-monitor setup. The left-hand monitor didn’t want to wake up from sleep, and I had to use a combination of two techniques to bring it back to life:

  1. Use the WinKey-Ctrl-Shift-B key combination (shortcut) to reload the graphics driver
  2. Use the Ctrl-Alt-Del “three-fingered-salute” to bring the desktop back to life

Shoot! I like it a lot better when I just hit a key, or click the mouse, and the PC wakes up on its own shortly thereafter. Neither of the preceding 572.16 versions were so obliging, which is why I rolled back to version 566.36. I don’t plan on updating until a new Studio version comes out (and I’ll be sure to back up 566.36 for re-use, should I need it back).

Facebooklinkedin
Facebooklinkedin

WU: How Long Is Too Long?

Here’s a Windows road I’ve been down many times. Indeed, it’s the kind of road, as in Robert Earl Keen’s excellent song, that “goes on forever…” It’s the road you walk on when WU hangs during download, GUI install, or post-GUI install. I read with amazement this morning in an ElevenForum thread that some poor soul waited THREE HOURS on a stuck install before asking for help. Ouch! Of course this raises the question with WU: How long is too long when things get stuck?

For me, the TLDR; answer is “10-15 minutes.” I just don’t have the patience to wait much longer. And FWIW, I’ve only seldom seen something that’s been stuck that long succeed after such a delay.

In WU, How Long Is Too Long Depends on You

At some point, the stuckee realizes that nothing is going to change, no matter how much longer one waits. That’s the point at which one must bite the bullet, and restart the stuck PC. Holding down the power button for 10 or more seconds until the PC shuts down will usually do it. Sometimes, however, one must either power off the PSU (desktops) or take more drastic steps (e.g. disconnect battery or wait for it to drain completely on a laptop).

Surprisingly, in the dozens of times I’ve had to do this when stuck in the past 5 years or so, the aftermath has mostly been positive. Often, Windows will simply pick up where the stuck update left off and finish up from there. Sometimes, it will roll back to the pre-install state instead.

Only in a handful of cases has the affected PC refused to boot correctly. When that happens, it’s time to pull out your rescue media and perform an image restore to your last known,good, working image backup. You have one of those, right? I’ve learned the answer to that question had better be “Heck, yeah. Let’ s go!”

Overcoming The Worst Case Scenario

No image backup and no working PC can be problematic. Hopefully, you’ve got at least some important stuff backed up someway, somehow (OneDrive, maybe?). You’ll either find a way to run a repair install (works sometimes) or you’ll have to choose between a clean install or a factory reset. Hopefully, it won’t come to that. I haven’t had to go there but once or twice in the 30-plus years I’ve been running Windows. Hopefully, your odds and experience will be the same. Good luck!

Facebooklinkedin
Facebooklinkedin