Category Archives: Windows 11

Windows 22H2 Upgrade Recalls Windows Past

Holy Ebeneezer! I had a major shot of deja vu yesterday. In preparing for son Gregory’s lightning home visit for Turkeyday, I found myself updating the B550 Ryzen 7 5800X PC I built to mirror the one he took to school with him in late August. Try as I might, I couldn’t get Windows 11 updated to 22H2 on that system using only Windows Update. My subsequent contortions in completing that Windows 22H2 upgrade recalls Windows past. I’ll explain…

How Windows 22H2 Upgrade Recalls Windows Past

Going back to the days of Windows 3.X, I can remember countless upgrade installs to transition from an older to a newer Windows version. That drill goes something like this for as far back as I can recall:

1. Run setup.exe from install media (first diskettes, then CDs, then DVDs, then streaming downloads)
2. Perform all the steps of the upgrade process: GUI-based install, reboot, then post-GUI install with 2 or 3 reboots along the way
3. Download and apply updates from Windows Update
4. Repeat Step 3, ad nauseam ad infinitum, until no more updates are available

I can remember when the time required to complete steps 3 & 4 took waaaaaaaaaay longer than the time required for the first 2 steps. And, especially in the days of reading physical media, that initial time frame was nothing to sneeze at.

Since Windows Vista/7 Everything Is Changed…

That was roughly the era during which physical media gave way pretty much entirely to online downloads and access. Since those versions emerged, the time to install or upgrade Windows has also dropped from a typical 45 minutes to an hour, to something more like 18 – 25 minutes. And MS is doing a much, much, much better job of slipstreaming updates into official image downloads these days, so the seemingly endless sequence of updates that followed a clean install or an upgrade even for Windows Vista and 7, is now much less intense and onerous.

But yesterday, I got a chance to taste what I hadn’t experienced in quite a while. I went through three rounds of updates on 21H2 before I realized WU wasn’t going to upgrade it to 22H2. Then, I visited the Download Windows 11 page and ran the Installation Assistant (depicted in the lead-in graphic above). That got my PC to 22H2. Then I ran another two rounds of updates (the first brought half-a-dozen items to that PC, the second only one).

That got the B550 Ryzen PC current with Windows 11 22H2. It wasn’t exactly like the “good old days,” really. But it was close enough to jog my memory about the way things used to work when dinosaurs roamed the earth and 16 MB was a HUGE amount of RAM.

Facebooklinkedin
Facebooklinkedin

No Remote WinSAT No Batteries

In following up on yesterday’s memory training item, I started messing about with WinSAT. For those not already clued in, WinSAT stands for Windows System Assessment Tool. As it turns out, such assessment depends on steady, reliable power and “close to the metal” access to the PC it’s assessing. That’s why, I believe that MS says “You cannot run formal assessments remotely or on a computer that is running on batteries.” (Using WinSAT). Hence the assertion: no remote WinSAT no batteries.

If No Remote WinSAT No Batteries, Then What?

A formal assessment on WinSAT runs a whole battery of checks. You can still do feature-by-feature checks remotely (just not the whole thing). Here are the results of WinSAT mem over a remote connection to one of my 2018 vintage Lenvo X380 Yoga ThinkPads:

No Remote WinSAT No Batteries.rem-mem

A single feature check — mem, or memory — does work remotely.

But if I run the whole suite (WinSAT formal) in the same PowerShell session, I get an error message instead:

No Remote WinSAT No Batteries.rem-formal

Going formal with WinSAT “cannot be run remotely…”. No go!

Such things lead to head-scratching from yours truly. I can kind of get it because it’s undoubtable that the remote connection is going to affect results reported because of the time involved in remote communications. But why allow checks one-at-a-time, but not all-at-once? MS is mum on this subject, so I’m not getting any insight there. It could be that singleton checks add relatively little overhead, but that cumulative effect of an entire suite of same adds noticeable delay. Who knows?

Facebooklinkedin
Facebooklinkedin

P16 Posts Mysterious Memory Training Message

OK: here’s a new one on me. This weekend, I updated the UEFI on the Lenovo P16 Mobile Workstation. Along that update path, the P16 posts mysterious memory training message. Something along the lines of “the screen will go dark for 2 minutes while the system performs memory training.” I’d not enountered this terminology before so I was taken aback. Turns out it’s a well-known thing, tho…

Learning Ensues When P16 Posts Mysterious Memory Training Message

Apparently memory training — or as Lenovo calls it in the P16 Maintenance manual: “memory retraining” — can happen after hardware changes or following UEFI updates. Online research eventually led me to a document that explained what’s going on. It’s called DDR4 SRAM: Initialization, Training and Calibration, and it’s darned informative. In fact, it’s worth a read-through for those interested in going beyond the basics I’ll present here.

For my purposes, it was enough to know the following:

1. Device or firmware changes can affect memory timing and performance
2. Training uses an iterative approach to altering timing values
3. It converges on settings that provide a workable trade-off between speed (faster performance) and stability (fault-free memory access)
4. If your motherboard uses JEDEC timings, training/retraining is not usually required (or performed)

In fact, it’s a lot like what I used to read at Tom’s Hardware about over-clocking PC memory back in the late 1990s. Start from a safe setting, increment and try. If it works, increment again. Repeat until a failure occurs. Back off to the preceding increment. Done!

Changes Sometime Cause (Re)Training

The bottom line is that what I was entirely normal. I’d either never seen or never noticed such warnings before, but they’re typical following hardware (usually RAM module swap-outs) or firmware (including UEFI) changes. Now I know. And it gave me a good excuse to download and read around the maintenance manual for the P16. That’s always fun, too.

Facebooklinkedin
Facebooklinkedin

Windows 8.1 EOL January 2023

Here it comes, I guess. MS is reminding Windows 8.1 users that its end-of-life (EOL) is imminent. With Windows 8.1 EOL January 2023 just around the corner, what else is MS saying? Find out in their Support article entitled “Windows 8.1 support will end on January 10, 2023.” Intentionally or not, it includes some amusing stuff. It also speaks to their philosophy and stance regarding Windows 11.

After Windows 8.1 EOL January 2023, Then What?

The afore-linked MS support article actually calls the transition that will occur on January 10, 2023 “end of support.” But because most readers know what EOL means I used it here. MS also recommends upgrading Windows 8.1 devices “to a more current, in-service, and supported Windows release.”

If Statcounter is correct, as of October 31, 2022, Windows 8.1 held a desktop market share of 2.45%. MS also puts the size of the combined Windows 10 and 11 device or OS instance population at 1.5B. That’s in keeping with Earthweb’s total count estimate from August 2022 of 1.6B. Statcounter grants Windows 10 and 11 combined 86.71% of the global desktop tally. By my reckoning, therefore, that puts the possible number of 8.1 devices at just over 42M.

Upgrade to Windows 11 on a New PC

MS also recommends for Windows 8.1 devices that don’t meet Windows 11 hardware requirements, that users “replace the device with one that supports Windows 11.” Indeed, it makes sense when refreshing PC hardware to go as modern and forward leaning as possible.

In fact, Windows 8.1 made its public debut (GA) on October 17, 2013. This date calculator tells me that was 9 years, 1 month, and 1 day ago as of today, November 18, 2022. That makes it almost inevitable that hardware purchased on or before the 2013 date doesn’t meet Windows 11 hardware requirements. The Gen8 “boundary date” actually falls in 2017-2018 time range.

What Happens to 8.1 After EOL (or EOS)?

MS won’t be offering an ESU (Extended Security Update) program for Windows 8.1. Thus it will no longer receive technical support, software updates, and security patches or fixes. According to WinAero, “Microsoft’s own products including Office 365 and the Store app will stop working.” That should be enough to convince most business users that it really is time to get off that bus.

For me, some of the humor in this otherwise doleful situation comes from Windows 8 and 8.1 general marketplace fate. It was never that popular to begin with, nor did it ever enjoy the kind of uptake in business that XP, 7 and Windows 10 achieved. To think that as many as 42M devices may be affected by this impending retirement is mostly a testament to how enormous the total Windows market really is. And to think it’s dwarfed by a factor of 3X or greater by smartphones is truly mind-boggling.

Even so, prodding a device population of 42 million onto Windows 11 and new PCs could be a boon to the sagging PC market. At a modest average price of $1K per unit (low for a business class PC nowadays, but higher for home/casual users) that’s a cool $42B in sales. It comes pretty close to “real money,” in my book.

Shout-Out to Sergey Tkachenko: the WinAero story cited in the concluding section of this story originally led me to the MS Support item that provides its focus and impetus. Thanks, Sergey!

Facebooklinkedin
Facebooklinkedin

VM SSD Speed Falls Off

What did I expect, I wonder? I’ve been digging more deeply into VMs on the amazing Lenovo P16 Mobile Workstation. (It’s got an i9-12950HX, 2TB PCIe x4 SSD, 128GB RAM, Quadro RTX A5500, and Windows 11 22H2.) Most of the time, the VM runs almost indistinguishably from the physical OS. But various IO metrics tell a different story: most tellingly, VM SSD speed falls off measurably. That applies both to the Virtual C: drive inside the VM, and when accessing external USB4 storage devices from the VM.

How Much VM SSD Speed Falls Off

By most metrics, it’s 2X or more. To be more specific, CrystalDisk-Mark results for the C: drive are about half across the board versus the internal Kioxia SSD. For the all-important random read/write 4K single thread, it’s worse than that (2.5X to 3X). Worse still, large file copies to external USB drives fall off a cliff: typical rates of 250-280 MBps fall to 60-70 MBps. This is shown from File Explorer inside the VM in the lead-in graphic above. Here’s a comparison from the physical machine:

VM SSD Speed Falls Off.phys-copy

Notice: USB speed is at least 4X faster on a physical PC vs. a VM.

Let’s Get Physical…

This actually provides an interesting justification for running certain workloads on physical rather than virtual PCs — namely, that IO and completion times can be dramatically affected. But given the convenience, flexibility and open-ended nature of VMs, this is not likely to matter that much except for highly specialized workloads where time is worth more than money.

Fascinating stuff, though — and great fun to play with. Check out the Get a Windows 11 development environment page at MS.

Facebooklinkedin
Facebooklinkedin

Repair Upgrades PowerShell

Here’s something I didn’t know before. Or at least, I never tried it. Just recently (November 8) MS released a new 7.3.0 version of PowerShell to GitHub. I’ve been upgrading my various systems since, slowly but surely. This morning I learned that opting for Repair upgrades PowerShell. Let me show you what that means.

Showing How Repair Upgrades PowerShell

On some PCs, winget upgrade may not show the new PowerShell as an option. (I’ll use my Lenovo Yoga 7i as an illustration because it manifests such behavior.) You can see it’s running version 7.2.7 and that PowerShell does not show up in the output from winget upgrade below:


If that’s the case, here are the steps to using repair to upgrade PowerShell on such PCs:

1. CTRL-Click on the link that reads https://aka.ms/powershell. This opens the MS PowerShell Documentation page.
2. Click on the “Download PowerShell” button at the upper right. This takes you to the GitHub Latest release page for PowerShell (7.3.0, as I write this, but updated as new versions emerge). Then close all open PowerShell sessions.
3. Scroll down to assets and download the installer file for your PC (for most readers the 64-bit MSI is the right choice: PowerShell-7.3.0-win-x64.msi)
4. Run the microsoft self-installing (MSI) file to start PowerShell installation. Step through all the installer prompts. If the Repair option comes up, select it (shown in the lead-in graphic for this story). It will run and “fix” the current installation.

At the end of this process, you’ll have a working upgrade to version 7.3.0. Cheers!

What About Winget Upgrade Microsoft.Powershell?

Gosh! That works too but finishes strange. Let me show you, in the following screencap (click on image to view full-sized):

The output doesn’t actually confirm a successful install of PowerShell 3.7.0. It shows a progress bar, and a status of “Starting package install…” Then it transitions to a command prompt. In the background, the new version is installed and running. But because you’ve got a 7.2.7 window open, you don’t see the 7.3.0 label until you close the old window and open a new one.

It’s always something, right?

Facebooklinkedin
Facebooklinkedin

Windows 11 Beta Channel Gets Improved Task Manager

Finally! I’ve been reading about — and seeing — cool changes to the Task Manager in Windows 11 for weeks and weeks. But only with Build 22623.891 for all of its users, Windows 11 Beta Channel gets improved Task Manager. What does this mean? Take a look at the lead-in screencap (and others below) and I’ll tell you more…

Woo-hoo! Windows 11 Beta Channel Gets Improved Task Manager

Let’s start with the lead-in graphic. Among the several improvements Task Manager now makes easily accessible in the 22623 fork of the Beta Channel, I can finally produce the Dark Theme. That’s what you see in that graphic, which makes for a more dramatic (but also visually sensible) set of CPU utilization graphs. Previously, this kind of thing was only accessible through ViveTool tweaks (which I avoid as a matter of practice).

What else is in there? You can search for processes by name in various Task manager panes (processes and details). The next screencap shows the results of a search for the ubiquitous svchost process in the Processes pane (notice it’s smart enough to map part of the .exe name to the related process names: cool!).

Windows 11 Beta Channel Gets Improved Task Manager.search

Notice that “Service Host” appears in nearly all of the elements shown as search results. Very helpful!

According to this story at WinAero from Sergey Tkakchenko, you can search on process name, ID or publisher with good results. That certainly worked for me.

One more thing: turning on “Efficiency mode” in Task Manager is now a right-click option from the Details pane. This lets users lower runtime priority to boost power efficiency, while upping stability risks. My example (e.g. the Chrome web browser) is an example of something you probably would NOT wish to run in this mode. For real.

Efficiency mode is easy to set, but should be approached with some caution.

I’m not sure I truly understand when or why to use Efficiency Mode (presumably on a tablet or laptop on battery power) but I’ll do some investigating and experimenting and see what’s up with that. Stay tuned! Should be fun…

In the meantime, I’m delighted to finally be able to see and exercise these Task Manager facilities for myself. If you have access to a Beta Channel Insider Preview, it’s worth updating to Build 22623.891 to see for yourself.

Facebooklinkedin
Facebooklinkedin

Ready-to-Run Eval Windows 11 Development VMs

MS offers free downloads of ready-to-run Eval Windows 11 Development VMs (virtual machines). They incorporate a copy of Windows 11 Enterprise, Visual Studio 2022 edition, Windows Subsystem for Linux (WSL), and Windows Terminal. They’re ready to run in developer mode, right “out of the box” as ’twere.

MS makes them available, free, for the following hypervisors:

  • VMWare
  • Hyper-V
  • VirftualBox
  • Parallels

Just for grins I downloaded the Hyper-V incarnation, and spent an enjoyable hour getting it installed and running yesterday, along with some exploration and investigation. The lead-in graphic shows the head of the download page for all this stuff.

Grab Ready-to-Run Eval Windows 11 Development VMs

I was able to bring up the VM simply by opening it in Hyper-V and using the “default switch” for the networking option. It’s just that easy to get it up and going. No kidding. But…

As I explored the new runtime environment I did find some limitations. Turns out the default install in Hyper-V does not resolve TPM issues. There’s a whole raft of “Generation 2 VM Security Issues” about which I had been blissfully unaware.

I’m going to need to work through those issues so I can try again. Why? Because if I want to keep the VM around as more than a transitory eval, I have to be able to upgrade to 22H2 (the download is 22H1). And here’s what the Windows 11 Installation Assistant currently has to say about that:

Upon running the PC Health Check on that VM, I’m informed that no TPM is detected. No TPM, no upgrade. This can be fixed: I see numerous recipes to make that happen. I’ll try them soon.

More Fun Than…

In the meantime, I’m having a gas running VMs on the P16 Mobile Workstation (with 128GB RAM, a 24-core i9 12th Gen CPU, and so forth). Honestly and for the first time, ever, I can’t tell any diff between running a native OS and a VM. It’s awe-inspiring. I’ll keep digging in, and reporting more, but if you too wish to play, visit the download page. It’s a pure joy to mess around with!

Facebooklinkedin
Facebooklinkedin

PowerToys File Locksmith Works Well

Starting with version v0.64.0, released on November 2, the PowerToys collection added File Locksmith to its mix.The tool’s own built-in description is sparse. It reads: File Locksmith is “…[a] Windows shell extension to find out which processes are using the selected files and directories.” Doesn’t sound like much but can be handy. Indeed, I learned that PowerToys File Locksmith works well this weekend. Let me explain…

Why Say: PowerToys File Locksmith Works Well?

As I tried to work through an update process for a desktop tool, I got an error message showing three instances of svchost.exe were impeding installation. Remember: File Locksmith is a “shell extension.” In this case, that means you can right click “stuck” files in File Explorer and then choose the “Who’s using this file?” menu option that appears.

This brings File Locksmith into the picture, wherefrom you can choose an “End Task” button for associated files that show up in the listing. Furthermore, you can see detail about each running process, so you can even match up process IDs inside Task Manager to make sure you “end task” only when and where you should, and leave other stuff alone.

PowerToys File Locksmith Works Well.fl-output

The offending items were various DLLs. They run within svchost processes so multiple programs can share access to them.
[Click image for full-sized view.]

This made my job pretty easy. All I had to do was end the offending tasks so the installation could complete. It did so pretty much immeditately after I told it to try again. And it ran to successful conclusion.

Warning: Because ending tasks for shared DLLS can leave certain important facilities inaccessible after such a move, I also restarted Windows after the update was done. You know: just to be on the safe side…

But gosh, File Locksmith made this sometimes vexing and onerous task easy and straightforward. I have to laugh about this too, though. Here’s why: earlier versions of PowerToys itself were prone to experiencing install delays owing to running items. These included dll host processes that required manual closing in Task Manager. Thus, it’s glaringly obvious how the developers figured out such a tool could be helpful — at least, IMHO.

But it’s here, it works, and has already proved useful in helping me update a utility included in my Startup items, and generally running in the Windows background. If it worked for me, it should do likewise for you. Enjoy!

Facebooklinkedin
Facebooklinkedin

Samsung Printer Is Now HP

Boy! The interesting things one can learn when updating drivers are legion. Case in point: I learned I needed an update for the Samsung Easy Printer Manager program. Upon searching for same, I found myself directed to HP (!) Customer Support. Indeed, that’s where the latest version of said utility now resides. You can see a screencap of that download page at the head of this story. Looks like my Samsung printer is now HP,  in name and in fact.

If Samsung Printer Is Now HP Then What?

HP is the former division of Hewlett Packard that now sells PCs and printers, as well as peripherals. To give you an idea of how long this has been going on, this press release bears a November 1, 2017 date. Whoa: talk about missing that bus by a mile…

When HP closed the deal they did so for US$1.05B. They also acquired a portfolio of 6.5K patents, and “a workforce of nearly 1,300 researchers and engineers with expertise in laser technology, imaging electronics, and supplies and accessories.” I guess that means buying an official laser toner cartridge (I still have a spare in my utility closet) will cost even more than it did the last time I looked. I found the product page, but I can’t find a price (looks like I might have to set up an account). Amazon references an “HP Store” and offers same for US$76, so that’s not too pricey. OK then: it’s all good.

Plus çe Change…

That’s French for a saying that roughly translates: “The more things change, the more they stay the same.” The technology landscape is chock full or mergers, acquisitions, spin-offs and divestitures. I have to laugh about this one, because I’m definitely coming late to that particular party. But at least, I had no trouble finding an updated version of the software I needed. And it works, too!

And that’s the way things go, here in Windows-World, from time to time.

Facebooklinkedin
Facebooklinkedin