Category Archives: Windows 11

Insider stuff, Recent Activity, USB devices, WED Blog, Windows 11

WTC = What the Clunk?

Leave a comment

I bought my first hard disk back in the late 1980s. If memory serves it was a 300MB drive with 8″ platters. It cost about US$1,000. It attached via SCSI to a Macintosh SE desktop, with its 9″ CRT (512×342 resolution). Why tell you all this? Because that old drive was literally a clunker: as it started, or read data, or shut down it would emit a series of thunks and clunks you could hear in the next room. I just added a Seagate IronWolf 12TB NAS drive to my production desktop. This morning as I booted up I found myself saying WTC = What the Clunk? as it started up for the day.

Why I’m Saying WTC = What the Clunk?

I just looked up the innards of this new spinning disk. It’s got 8 platters, each with 2 heads and a total of 1.5GB of capacity. And  those heads and platters are sealed into a helium filled chamber to keep them as quiet as possible. Even so, spinning up apparently takes some mechanical oomph because I heard at least a trio of discernible clunks as the unit spun up this morning.

It had been so long since I’d heard those sounds, I’d forgotten what they sounded like. Now, I’m reminded of what I used to listen to all the time nearly 40 years ago: a steady series of thumps, clunks and thunks as big disks went about what — by today’s standards — can only be called “small business.” Fortunately, as the IronWolf goes about its much, much bigger business it only emits an occasional sound. If I use my imagination, I can hear it as a chuckle at the depth of my disk drive recollections.

I won’t even go back to the earlier days when I worked on Data General and DEC PDP minicomputers that used 14″ platters. Those came (and went) as removable disk packs. They made some industrial strength noise, for sure, in the days before Windows-World came along. But that’s a whole ‘nother story…

Facebooklinkedin
Facebooklinkedin
Insider stuff, Remote Desktop (RDP), WED Blog, Windows 11

Remote Desktop Connection LSA Error

2 Comments

Over the past couple of years, I’ve noticed that establishing an RDP session from my primary desktop to other PCs sometimes fails under specific circumstances. I’m researching a story about this for Mayank Pamar at WindowsLatest, so keep an eye out for that opus. It’ll probably hit next week. When I attempt to get into some of my Windows 11 PCs (the only kind of physical PC I have any more), my login will occasionally be refused if I use a Microsoft Account (MSA). Indeed I’ll see a Remote Desktop Connection LSA error that reads “The Local Security Authority cannot be contacted.”

What Causes Remote Desktop Connection LSA Error?

Interestingly, there are a number of possible causes. Some are easy to fix, others fall on third parties. Here’s a partial list:

  • OS can’t validate credentials, particularly MSA logins (the most common and obvious reason, but one users cannot easily fix themselves)
  • Secure channel negotiation (to exchange credentials) fails
  • Time sync or DNS resolution fails
  • Credential policies are somehow misconfigured

Time sync and DNS stuff is probably the most approachable, so they’re worth trying. For the former that means Settings > Time & Language > Date & time > Sync now (under Additional Settings). For the latter, it’s only meaningful if using manual DHCP assignment, in which case Setting > Network & Internet > Ethernet or Wi-Fi > Edit DNS Settings > define preferred and backup DNS server addresses. Most users will get their DNS server assignments via DHCP.

The other items are a bit more convoluted. I’ll get to them in my upcoming story. Here in this brief blog, I’ll “leave them as an exercise for the reader” in the classic ploy used to avoid heavy lifting in so many, many textbooks I’ve read over the years…

A Typical (and Useful) Workaround

If I can’t get into a PC using my MSA, I’ll set up a local account on the affected machine with admin privileges and use that to RDP into the machine instead. This might cause issues on machines where you want or need access to account-speicific files or data (e.g. the associated C:\users\<name> folder hierarchy). But otherwise it works OK. In a small and unscientific survey of my local fleet, I’ve had to do this on just under half the machines (4 out of 9), most of which are running Insider Preview releases (and thus, have their foibles).

Here in Windows-World, if you can’t do things the way you want to, you must sometimes do them some other way. Obtaining RDP access to some of my test and experimental PCs puts me in those shoes from time to time. So it goes!

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

Wi-Fi Kernel Dump Error Is Neutrino-Like

Leave a comment

Here’s something interesting I’ve never seen before. The other day, I was trying to update the recently re-awaked ThinkStation P3 Ultra. Among the many items in the queue, through Lenovo Vantage, was an Intel Wireless LAN Driver. Indeed the same driver also showed up in the Intel Driver and Support Assistant. Despite repeated efforts through both facilities, the driver update always failed. This morning, I observed traces of those failures in Reliability Monitor. This Wi-Fi Kernel dump error is neutrino-like in that it registers in Relimon, but doesn’t diminish the Reliability Index (see the lead-in graphic).

More on Why a Wi-Fi Kernel dump error is neutrino-like

The error code in the Relimon details cite to the following string:LKD_0x41A1_Netwtw08!unknown_function. Online research tells me two useful things about this info:

1. It’s tied to Intel’s wireless driver (confirms what I’d suspected)

2. the LKD stands for Live Kernel Dump, indicating that Windows detected a hardware-related fault serious enough to provoke a snapshot of the error, but that it did NOT crash the system

The lack of a crash explains why Relimon imposes no charge on its Reliability Index even though the event is labeled “Critical” of type “Hardware error.” Shoot! I didn’t even know this was possible. Very interesting!

What About that Wi-Fi Driver?

A quick peek into Device Manager showed me that the Wi-Fi 6E AX211 160MHz driver was throwing a “device cannot start (Code 10)” error. Because both Lenovo Vantage and Intel DSA weren’t fixing things, I decided to go clean and start over. I right-clicked the device in DevMgr, then selected Uninstall from the pop-up menu. After a reboot, I visited the Lenovo Downloads & Software page, entered the Serial# for the P3 Ultra, and grabbed the latest Wi-Fi driver package. After installation, DevMgr obligingly reports that “The device is working properly.” Problem solved!

I figure when two update tools both choke on a driver, it’s time to remove the offending software, download, and try again. Here in Windows-World, even drastic measures need the added protection of “fingers crossed.” Thus, I’m glad that strategy worked.

 

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

Generic Keys Speed Clean Install

Leave a comment

I just wrote a story for the AskWoody newletter. It’s entitled Why Starting Fresh with Windows 11 Beats an Upgrade. It’s premium content, though, and behind a paywall so you can only see it if you sign up for a subscription. I think that’s worthwhile. but you’ll have to decide for yourself. But in thinking through what’s involved in a clean install, a key early screen demands a valid key to continue (there are workarounds). In this context, I recall that generic or setup keys also work. See the lead-in graphic.

If You Have Them, Generic Keys Speed Clean Install

Generic product keys, aka, default setup keys — may be used during a clean install of Windows. Indeed, the same keys work with 10 and 11. These keys are generic because they won’t activate Windows. But if you’re clean installing on hardware that’s already been granted a digital activation, the Microsoft activation servers should recognize your machine after you get to the desktop, and take care of that automatically.

Here’s a list of generic keys, courtesy of Copilot:

Of course this is an image so a link is helpful to actually grab such 25-char strings. MS doesn’t maintain them in one place, but you can find them at ElevenForum.com through their tutorial “Generic Product Keys to Install or Upgrade Windows 11 Editions.”

Handy to have around, so good stuff indeed. Hats off yet again to the master of Windows mysteries, Shawn Brink (chief MVP and maven for the ElevenForum site). He’s a real treasure for those of us who live in Windows-World. Thanks again, Shawn!

Facebooklinkedin
Facebooklinkedin
Cool Tools, Device drivers, Recent Activity, Troubleshooting, WED Blog, Windows 11

MS Mouse Driver Delirium Done

Leave a comment

I’m still finding my way into a more perfect configuration on my “new” production PC . It is actually built around nearly 5-year-old technology, recently updated and expanded into a new NZXT Flo 6 case. Yesterday, I noticed something minor but annoying that I’ve seen before: my wireless mouse cursor was lagging, which means the tracking followed behind my hand movements. I *HATE* that. I also know that when it happens, it’s mostly owing to transceiver interference or driver issues. Because I’ve placed the transceiver high above my desk, I keyed in on driver issues. And sure enough, activating the MS Mouse and Keyboard driver put paid to my MS Mouse driver delirium.

How I Cured My MS Mouse Driver Delirium

I’d already downloaded and installed the MS Mouse and Keyboard Center drivers on this PC. What I hadn’t done, based on what I first saw in Device Manager (see lead-in graphic) was to make sure that the Mouse and Keyboard Center’s mouse driver was actually in use. Indeed, when I checked, it was running the generic “HID-compliant device” driver in the first position in the driver list on display in the screencap. Go figure!

To my surprise, the system asked for a reboot after I updated the mouse driver. Copilot tells me it’s because

The HID-compliant driver is a low-level, class-based driver. [That means r]eplacing it with a vendor-specific driver…often involves swapping out kernel-mode components that are actively in use.

That totally makes sense. And after said restart, the mouse lag problems disappeared completely. Thank goodness things sometimes work the way they should. That’s enough of a novelty here in Windows-World to earn my genuine gratitude. Now I can work and play without waiting for the cursor to catch up with me. What a relief!

Facebooklinkedin
Facebooklinkedin
Device drivers, Insider stuff, Recent Activity, Troubleshooting, USB devices, WED Blog, Windows 11

Safely Eject Gets Weird When Swapping Drives

2 Comments

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
Copilot+ PCs, Insider stuff, Recent Activity, WED Blog, Windows 11

SFF Copilot+ PCs Remain Scarce

Leave a comment

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 Neo50q Tiny (Snapdragon) 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…

Note Added 9/24: Oops! Wrong One..

As you can see in the lead-in graphic, I’d originally landed on the Lenovo ThinkCentre M75q as a Copilot+ SFF PC. Closer examination researching this topic yesterday showed me, it’s not. It lacks sufficient NPU oomph to qualify as such. But that’s when I discovered that indeed Lenovo DOES have an SFF Copilot+ PC — namely the ThinkCentre Neo 50 (Snapdragon) Tiny now mentioned at the head of this story. I guess I got my minis mixed somehow. Glad to fix it, though…

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

Windows 11 Does Multi-Monitors Right

Leave a comment

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
Cool Tools, Insider stuff, Recent Activity, WED Blog, Windows 11

Careful With App Defaults

Leave a comment

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
Insider stuff, Recent Activity, WED Blog, Windows 11, Windows Update

25H2 Enablement Blazes on Lenovo AIO9i

1 Comment

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