Category Archives: Windows 11

Safely Eject Gets Weird When Swapping Drives

Go figure: I had to grab some or all of 7 different SATA drives to complete file transfers from the old production PC to the new. Mostly, this meant waiting for Teracopy (a bulk transfer utility I highly recommend). It aced the job of moving files from my old drives to the new 12TB Ironwolf. Along the way I learned something interesting — namely, that Safely Eject gets weird when swapping drives. At least it gets weird when using dual-drive caddies. Let me explain…

How Safely Eject Gets Weird When Swapping Drives

Safely Eject appears in the System Tray (aka Notification Area) of the taskbar as a teeny-tiny USB Flash Drive icon, as you can see in the lead-in graphic. Turns out it’s a quirk of the chipsets used to bridge multiple SATA drives through a single USB connection that coming back after an eject doesn’t always work.

Here’s what happened on my 5800X Flo6 production rig and the ThinkPad P16 Gen 1 Mobile Workstation. No drives in the caddy showed up after ejection, then disconnect/reconnect of the USB cable. As Copilot says “After eject, the bridge may not reinitialize that port properly.” A reboot typically fixes such problems, but that got vexing given that I had to work my way through 7 drives in all.

Suggested Mitigations

Courtesy of Copilot, I worked my way through a couple of possible mitigations. Turns out the ASMedia driver wasn’t in use, so it wasn’t a possible culprit, either.

The right technique involved a multi-step combination of commands and physical actions:

Step 1: Unmount the drive to be removed from the caddy using the mountvol <drive-letter> /p command (e.g. mountvol e: /p)

Step 2: Turn off the power on the caddy. For one caddy that meant using the power switch, for the other it meant unplugging the power input from its brick.

Step 3: Wait 5-10 seconds for the device to reset completely.

Step 4: Power the caddy back on, possibly with one or two new drives inserted, after removing one or two old ones. Wait for those drives to get initialized, then show up in File Explorer. Proceed.

This worked properly on both the P16 and the Flo6 PCs. Safely eject is fine for single-drive devices (of which I have more than a dozen). But I now know that using the mountvol command, plus cycling the power around drive swaps, is the right way to keep my dual-drive devices working as they should.

Here in Windows-World, the path to proper device function has its occasional twists and turns. For my dual-drive caddies, this particular turn is worth making…

Facebooklinkedin
Facebooklinkedin

SFF Copilot+ PCs Remain Scarce

Last year, I really got my hopes up when ARM announced a developer’s kit version of a small form-factor (SFF) PC with Snapdragon X. Alas, it never materialized. I’ve also read about plans from numerous vendors to offer mini but mighty PCs of this type, including Geekom and ASUS. But right now, SFF Copilot+ PCs remain scarce. In fact, I can find only two for sale presently: the Lenovo ThinkCentre M75q Gen 5 (AMD) and the MSI Cubi NUC AI+ 2MG (Intel).

Why Do SFF Copilot+ PCs Remain Scarce?

I speculated about this when ARM announced, delayed and then canceled its own SFF SnapdragonX based model. Looking at the enclosures for the 2 aforementioned models, I’m still leaning that way. Mostly, in fact, it has to do with support for only 1 or 2 USB-C ports (typically 40Gbps/Thunderbolt 4/USB4).

Thus, there’s a nearly inescapable add-on expense when buying such a unit — namely, a TB4 or TB5 dock, most of which cost from US$350 to over $500. That’s a big bump in cost, cubic volume, and complexity for PCs designed to be affordable and, above all, compact.

I’m Interested, But Is the Market?

Because of the need for more ports, power, connections and displays, I have to believe the general marketplace finds current Copilot+ SFF PCs unappealing. It’s one thing to get useful capability in a compact and reasonably powerful package. It’s another thing entirely to have to turn around and spend from 44 to 63 percent of the purchase cost on a TB4/5 dock to get all the ports and connectivity modern office workers need.

If these OEMs build such SFFs, will buyers come? Initial excitement and plans said “Yes.” Subsequent actual product offerings, options, and limited choices say “Maybe” at best. Too bad: I like the category and what it brings to the desktop. I may be in a (small) minority, though…

Facebooklinkedin
Facebooklinkedin

Windows 11 Does Multi-Monitors Right

I’ve been living the life of a native Windows 11 user on my production desktop — the newer, Ryzen 7 X5800 based PC — for a couple of months now. One thing I’ve noticed is that Windows 11 handles multiple monitors with great alacrity and aplomb. IMO, Windows 11 does multi-monitors right, in several important ways. Let me elaborate…

Why Say: Windows 11 Does Multi-Monitors Right

To begin with, I didn’t need to engage in Display settings shenanigans on my dual-monitor desktop setup. At all. Indeed, Windows 11 correctly detected and arranged both of my displays during its initial bootup. I didn’t have to do anything to get them working in extended mode (to use left- and right-hand devices as a single logical desktop with proper mouse tracking all the way across). In Windows 10, this requires manual intervention and setup.

It gets better. Updating NVIDIA graphics drivers is likewise much better behaved. On Windows 10, post-install, all windows moved onto the primary display. Remote desktop sessions appeared in full-screen windows that needed to be maximized to show a top-center control bar. On Windows 11, windows reappear where they resided prior to the update, and RDP sessions remain as previously set.

GPU driver stability also seems to be improved. On Windows 10, I often had to deal with “display blink” — a phenomenon that caused either my left- or right-hand display to blink on and off every few seconds. So far, I’ve been through three NVIDIA update cycles on Windows 11 with nary a sign of such misbehavior.

All’s Well…

It may still be too early to proclaim success or improvement, but I’m doing those things anyway. So far, display handling in Windows 11 is better behaved and more predictable than it was on Windows 10. Should things change, I’ll be sure to report on issues I encounter. But so far, it’s been a refreshing breeze to work with multiple monitors on Windows 11. Fingers crossed that things keep going in the same way for the foreseeable future!

Facebooklinkedin
Facebooklinkedin

Careful With App Defaults

I’ve always got PCs coming and going here at Chez Tittel. That means laptops, mostly, with an occasional All-in-One or SFF desktop to keep things interesting. Further, that means setting up Windows to work the way I want. Too bad, then, that Edge isn’t inclined to make way for other Web-focused defaults (e.g. Chrome). Even when I pick Chrome as the default browser, Edge keeps popping up for other stuff. The lead-in graphic shows why I’ve learned to be careful with App defaults. Indeed, it shows Edge remains the default for .mhtml files (MIME encapsulation of aggregate HTML documents) even after Chrome gets the default pick.

Why Be Careful With App Defaults?

Elsewise, items opened in other MS apps will open in Edge rather than Chrome.  In this case, Outlook handles a lot of .mhtml files for links and Web items embedded in email messages. Those still go to Edge. The right way to do this is to click Settings > Apps > Default Apps > Google Chrome.  On that page, make sure Chrome gets associated to all file types you want it to handle.

In my case, I just made sure everything on the foregoing Settings page that used to show Edge as the default now shows Chrome. A hopefully obvious corollary to this exercise is that setting Chrome as the default browser in Windows 11, is not sufficient to make it take over for all Web-related items. Hopefully, that’s now fixed!

Just another happy day in Windows-World, living on the edge (horrible pun not just intended, but enjoyed).

Facebooklinkedin
Facebooklinkedin

25H2 Enablement Blazes on Lenovo AIO9i

I’m working with a Lenovo Copilot+ PC review unit these days: it’s a snazzy Yoga All-in-One AIO9i. It comes equipped with an Intel Core Ultra 7 258V (8 cores: 4 each P-cores and E-cores/8 threads), integrated Intel Arc 140V GPU, 32 GB LPDDRx-8533, Hynix OEM PCIe x4 NVMe SSD, and more. It also has Windows 11 Pro for Workstations installed. I’m not sure what makes this PC so fast, but 25H2 enablement blazes on Lenovo AIO9i.

Details: 25H2 Enablement Blazes on Lenovo AIO9i

How fast? The whole process, after opting into the Release Preview channel on the Insider program, took under three minutes to complete. That means:

  • Downloading the enablement package (under 30 seconds)
  • Running the GUI-based portion of the update (under 30 seconds)
  • Reboot and post-GUI update handling (under 40 seconds)
  • Resume desktop through lock screen and login (under 10 seconds)

There are lots of reasons why this is so fast. For one. the enablement package itself is svelte (under 1MB in size). That’s because MS has already included most of the code in earlier updates, and the enablement package — as the name indicates — simply turns such stuff on. As Copilot puts it, earlier “monthly cumulative updates (LCUs) have quietly staged the new features in a dormant state.” It continues: “The enablement package simply flips the feature flags — no need to download or install new core components.”

Other contributing factors to speed:

  • No drive revalidation, no app compatibility scans, no migration of user profiles
  • As the preceding bulleted list observes, this process requires only one update to complete
  • No rollback staging or recovery partition updates are included, to reduce disk I/O and system prep times

Indeed, inspection of $WinDrive (C:) shows no Windows.old partition, as one might usually find after a version uplift. Likewise, Disk Cleanup finds only 1.53 GB of files to clean up in the upgrade’s wake. That’s much less than the more typical 25-30GB on production Windows 11 systems here at Chez Tittel when transitioning from 23H2 to 24H2, for example.

Wow: Just Wow!

I’m not sure that Windows for Workstations made any difference here, either. Despite this version in place, it doesn’t use advanced features — e.g. ECC RAM and ReFS — that might speed things up. I think this is just one very lean, mean and fast enablement package. It’s worth enrolling a test PC in the Insider Program, Release Preview Channel just to check it out for yourself. Speedy!

 

Facebooklinkedin
Facebooklinkedin

Quiet Labor Day Return

Hello, there! Today’s my first day back at work since I took off with my family to get son Gregory moved into his Hollywood CA dorm. He’s concluding his film school studies with a semester at Emerson’s campus on Sunset Boulevard, with a dorm move-in on 8/23. We had an epic trip with stops at Las Cruces, NM and Phoenix, AZ on the way to LA from 8/20-22. We spent 2 days in Hollywood, 2 in Santa Barbara, and 2 more in Culver City. Then, we covered the same route in reverse from 8/28-30. I expected lots of catch-up Windows work this weekend, but I got a quiet Labor Day return instead. Let me explain…

What Makes For a Quiet Labor Day Return?

Apparently, Windows-World mostly held its breath while we were gone. I was expecting lots of updates via winget, PatchMyPC, Intel DSA and so forth after 10 days away. Instead, I observed update counts in the following (surprisingly low) ranges:

  • Winget: 3-10 items
  • PatchMyPC: 1-2 items
  • Intel DSA: 0-2 items
  • Lenovo Vantage: 0-2 items

Indeed, I saw the highest counts on machines that I’d left idle 2-3 days before leaving town. That puts the unchecked period north of two weeks on such machines, and shows low update deltas for the time period involved. The lead-in graphic shows 10 winget items on the Lenovo ThinkPad P16 Gen 1 Mobile Workstation. It had the most pending updates, with the Dynabook Tecra taking the number 2 winget spot with 7 items.

Note Added 1 Hour Later

When I visited my sole remaining Windows 10 physical PC — the i7 Skylake I’m still running in tandem with my 5800X production PC — it looked more like what I’d expected for all machines. Here’s the skinny:

  • Winget: 18 items
  • PatchMyPC: 5 items
  • Intel DSA: 0 items
  • WU: pending restart for KB5064794 and KB5063842

Again: that’s 25 items altogether, and more like what I thought I’d see across the board. That said, here at Chez Tittel Windows 10 is slowly shuffling off the scene…

Now What?

With all my Windows PCs — 10 in all — now caught up, it’s time to get back into the working groove. I’ve got a couple of assignments this week, including one for TechTarget, one for ComputerWorld, and another for Actual Tech Media. Things pile up when you’re off having fun (and driving 3K+ miles)! My return to Windows-World wasn’t as labor intensive as I’d guessed, which makes it a nice Labor Day surprise. In this case, quiet is good!

Facebooklinkedin
Facebooklinkedin

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

Dude! Where’s My Internet?

Whoa! I had an amusing but vexing hiccup on the new Flo6 Ryzen 7 5800X system when I sat down to work this morning. The Internet was dead, dead, dead. I could ping localhost but nothing further. It got me thinking about the absurdist epic starring Ashton Kushner and Sean Wm Scott. That prompted the tongue-in-cheek question “Dude! Where’s my internet?” I must speculate, and laugh, at what I think is the answer. Let me explain…

Why Expostulate: Dude! Where’s My Internet?

Everything looked OK when I sat down at the machine. But as soon as I tried to access any online resources, those requests went nowhere. And, of course, they took quite a while to time out to tell me there was no there on the other side of the connection.

I checked the cable TV signal (still there, which means out inbound broadband is working). I checked the wireless PCs (still there, which means at least the fallback to the boundary device WAP is working). Soon it became apparent: the Flo6 PC was the source of my woes. I’m not seeing any errors in Reliability Monitor so I’ll make an educated guess.

Waking Up Is (Sometimes) Hard to Do

The Flo6 had been asleep when I sat in front of it this morning. My best guess is that yesterday’s update somehow mucked with the wake behavior for the unit’s Realtek Gaming 2.5GbE Family Controller. So I reloaded the driver, and then unchecked the box under Power Management that reads “Allow the computer to turn off this device to save power.” From sad experience, I’ve learned this can turn into “LAN doesn’t work after waking from sleep” errors.

And gee: doesn’t that sound just like what happened to me this morning? It also demonstrates quite convincingly that here in Windows-World, some mornings start better than others. I’ll let you decide what kind of morning I was having today. I think I already know!

Facebooklinkedin
Facebooklinkedin

Thunderbolt 5 Era Is Finally Dawning

It was nearly two years ago — September 12, 2023, in fact– that the Thunderbolt 5 specification made its debut, including a prototype. But the road from prototype to “tech for sale” has proved long and somewhat fractured. Cables, docks, and peripherals started to show up about a year later (e.g. Kensington SD5000T5 Dock). Gaming laptops blazed the way on the PC front, with the Razer Blade 18 the first to offer TB5 ports as an optional upgrade (April 2024). And as I write this screed in August, 2025, it looks like the Thunderbolt 5 era is finally dawning for real. Let me explain…

Why Say: Thunderbolt 5 Era Is Finally Dawning?

When Thunderbolt 5 (of which USB4 v2 is a subset) first showed up about 12-16 months ago in shipping products, it was a kind of exception. Initial offerings were costly, or provided as added-cost options. Now, they’re starting to appear as standard ports on higher-end  laptops. That still means gaming devices, mostly, though business/developer platforms and high-end mobile workstations are also getting in on the fun.

You can see the specs for the MSI Vector 16 HX AI A2XW in the lead-in graphic. It retails for right around US$3,700 at Amazon. Its CPU goes to 24 cores (8 P-cores, 16 E-cores), includes 64GB RAM, a 4 TB NVMe SSD, and various mobile NVIDIA GPU options. It also offers 2 Thunderbolt 5 USB-C ports. It’s even Copilot+ capable. Kind of a beast, actually…

I see another MSI model available similarly equipped, plus one each Gigabyte and ASUS laptops (all offer 2 TB5 ports except for the ASUS, which offers a singleton). What’s missing from this picture? How about HP, Lenovo, Acer, Dell or Microsoft Surface models?

When Will Things TB5 Heat Up for Real?

When the aformentioned bigger players jump firmly onto the TB5 bandwagon. I expect that could happen later this year, or early next year, after vendors get the OEM bits from Microsoft for Windows 11 25H2. It’s coming soon — probably in October — so we may see more than a dawning in the near term.

I’m surprised that it’s taken this long, and that uptake hasn’t been what I would call either aggressive or enthusiastic. Could it be that most ordinary PC users and laptop buyers simply don’t care about or don’t need the higher performance and greater bandwidth that TB5/USB4 v2 provide? Maybe so.

I’ll keep watching, and keep chiming in on what I see. I’m still waiting for somebody to send me a review unit with TB5 ports, so I can put an entire device chain to work, including dock, monitors and external NVMe storage devices. Will somebody at MSI, Gigabyte, or ASUS take the hint? I reviewed all your stuff back in the day when I was building PCs and sussing out laptops for Tom’s Hardware. Why not let me pick up where I left off now, with a TB equipped laptop?

Facebooklinkedin
Facebooklinkedin

Copilot Unpicks Local RDP Access

On my sole remaining 2018 vintage Lenovo ThinkPad X380 Yoga, I’ve been fighting RDP connectivity issues. It’s running Windows 11 24H2 Insider Preview Beta Channel Build 26100.4946. All of a sudden, I couldn’t RDP into the machine at all. MSA-based access is still stuck on a Local Security Authority (LSA) access problem. But just now, Copilot unpicks local RDP access so I can use a local admin account to access it remotely. Phew!

Grinding Through as Copilot Unpicks Local RDP Access

Something was odd about the local account setup that didn’t sit right with RDP. Even though I’d set the account up with a password, that selfsame account did not have the PasswordRequired value field set to “True.” Turns out that RDP requires this setting before it will allow any account to connect.

Copilot cheerfully took me through some PowerShell syntax that didn’t work. Then it had me run the Command Prompt alternative that finally did the trick:

net user Actname YourSecurePassword123! /active:yes
/passwordreq:yes

Obviously, I used the actual account name for the Actname placeholder, and the real password for that string. But indeed it worked. And when I made my next login attempt, I was finally able to get back into that machine.

A Word of Warning

When I asked Copilot why this might have happened it informed me that this build “introduced a wave of under-the-hood changes” into Windows 11. Specifically, in the area of identity handling where “Insider builds often tweak how MSAs and local accounts are handled — especially in relation to login tokens, SID bindings, and credential providers.” That’s confirmation of what I’ve long suspected, because I’ve found myself unable to login to RDP using an MSA numerous times.

But this is the first time I’ve also been blocked for a local account as well. I’m just glad Copilot could steer me in the right direction to get a local connection working again. Even though my test and experiment PCs are mostly in the same office as my production desktop, it’s so much more convenient to access everything from the same keyboard, mouse and display setup. For me, RDP is an essential work tool. Bugs me to no end, when it doesn’t work right, as it does occasionally break down here in Windows-World. Sigh.

 

Facebooklinkedin
Facebooklinkedin