Category Archives: Troubleshooting

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

Beta Build Resets Browser Default: Edge

Leave a comment

Notifications started popping like snack food when I logged into my Windows 11 Insider Preview Beta Channel PC this morning. You can see a whole string of them in the lead-in graphic. The generic and interesting error message is some variation of “An app caused a problem.” And bam! this Beta Build resets browser default: Edge is now in charge. Ask me if I’m happy about this. Answer: NO!!

Why Beta Build Resets Browser Default: Edge?

Good question! Google AI says:

An automatic default browser reset is a known issue in Windows 11 Insider Preview build 26120.6760. A potential workaround for this specific bug is to use the Settings app to manually re-select your preferred browser for all relevant file and link types.

But hey! I don’t have to like it, do I? I also went looking for a one-click reset tool, but couldn’t find anything useful. So off I hared to Settings > Apps > Default Apps, where I picked anything that came up Edge and changed it to Chrome. Sigh.

Here in Windows-World, it’s always something. Today it was an involuntary Edge default reset. I dealt with it, but I’d rather not have Windows 11 do that again for a while…

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
Backup/Restore, Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 10

Win10 Boot Follies Galore

Leave a comment

Here’s my situation. I’m still running the old i7Skylake with its 2015 vintage Asrock Z170 motherboard. That machine is running Windows 10 Enterprise. Thus, it’s not eligible for the ESU (Extended Security Updates) offer from MS to keep that machine alive for another year. “No problem,” I thought, “I’ll just clean install Windows 10 Pro, and take up the offer that way…” Instead, I’m dealing with Win10 boot follies galore, unable to boot to USB media to replace the current Windows image. It’s been heartbreaking…

Describing Win10 Boot Follies Galore

Copilot agrees that something is hinky with the UEFI on the Z170, and it’s preventing the PC from booting off a USB flash drive. So far, I’ve:

  • Turned off Fast Boot in UEFI, and discovered that toggling CSM (the compatibility support module that supports both MBR and GPT partitioning schemes) kills UEFI completely for UEFI version P7.60. Turns out that’s a known gotcha.
  • Built rescue and install disks on 8GB media to avoid FAT32 issues (using the usually reliable Media Creation Tool, and the still more dependable Macrium Rescue Media Builder)
  • Run those UFDs from USB 2.0 ports, on the off-chance that USB 3.x isn’t working for boot

So far, nothing has worked to install a different Windows 10 version on this PC. But I have a plan…

Bring Out the Heavy Guns

When all else fails while installing Windows, I’ve observed that disconnecting all non-boot drives, and replacing the boot media with a completely blank drive will sometimes work. I’ve got a 1TB Crucial T705 NVMe that I’ll prep in that way, and give it a try. IMO, it has a good chance of getting me over this hump.

I won’t have time to do this until the weekend. Stay tuned: I’ll follow up on Monday with a report on that experience. I’ve been bit on the hindquarters many times in Windows-World, but this bite kind of stings…

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

Dude! Where’s My Internet?

Leave a comment

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

Jabra Headset Goes MIA

Leave a comment

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
Insider stuff, Remote Desktop (RDP), Troubleshooting, WED Blog, Windows 10, Windows 11

Chasing RDP Login Takes Too Long

Leave a comment

OK then, I’ve hit my troubleshooting time-out. Now that I’ve switched over to the Flo6 5800X build for my production desktop, I’m keeping the i7Skylake up and running in parallel. Why? So I can grab or look up things I discover I need on the new build that are only available on the old. So far, that’s included some logins that didn’t make it into the Norton Vault (only stored in Firefox on the old PC, as it turns out), various files and some app configuration data I didn’t know I’d need. Only one small problem: I can’t RDP into the account where all the stuff I need lives. I can RDP into the i7Skylake on a local admin account, but I get an LSA error when I try to log into my primary account. Alas, chasing RDP login takes too long, so I’m using TeamViewer instead. Indeed, it came up on the first try.

Why Chasing RDP Login Takes Too Long

Something has gone weird with NetBIOS and/or Domain Name resolution for RDP into the i7Skylake. That’s why I can get in using a local account, but not the MSA for the primary account. I’ve tried everything Copilot and Google can tell me about fixing that, to no avail, including:

  • Flush DNS name cache
  • Editing hosts file
  • Turning off browse service
  • Trying cmdkey explicit access in Command Prompt

And a whole bunch more. At present, I’ve spent at least 4 hours trying to MAKE it work. But RDP stubbornly refuses to let me use my MSA to log into i7Skylake.

The TeamViewer Alternative: Armadillo Time

TeamViewer doesn’t use RDP for remote access. It’s got its own set of protocols and services to manage LAN and Internet-based connections. It took me all of 15 minutes to get everything downloaded, installed, configured and running. I was able to access i7Skylake using the MSA I wanted on the first try. Go figure!

Sometimes, the best thing about beating your head against the way is how good it feels when you stop. Here in Windows-World this is not an unfamiliar sensation. If anybody knows how I can fix my RDP issue, I’d love some added insight and info. But for now, I have lots of other things to do — including a big deadline tomorrow on a writing project — so I’m taking the alternate route. If you’re not familiar with Jim Franklin’s wonderful armadillo image of that same name, check it out courtesy of Coast Monthly (it serves as the lead-in image for a terrific story).

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

Inching toward Flo6 Cutover

Leave a comment

OK, then. I’m just about there. But it’s been a much wilder ride than I expected, as I keep inching toward Flo6 cutover. That is, I’m almost ready to put the 5800X Flo6 build where my i7Skylake PC is right now. I’ll also leave the i7Skylake running for a while to pick up missed bits and pieces, as they inevitably come up. Let me tell you what’s happened so far…

Steps Involved in Inching toward Flo6 Cutover

In my July 28 post, I listed remaining steps before I could switch from old production desktop to new production desktop. Those included:

  • MS Solitaire: turns out I had to find and run a recovery utility to figure out to which MSA my stats belonged. Only then could I bring up the right account. Took about half an hour: done.
  • Macrium Reflect: 9AM full backup configured and running. This turned out to be dead easy, compared to the other items. Took all of 5 minutes, then another 10 minutes to fire off daily backups.
  • PaintShop Pro: Turns out 2023 is as new as it gets. I didn’t need to buy a new version, but I had to decommission the install on the i7Skylake before I could install and activate the Flo6. Also took about half an hour, most of which was figuring out how the heck to log in. Eventually, I figured it out and got it done.
  • PDF reader: I couldn’t get Nitro Pro to send me an email to reset my password for love or money. That took half an hour. So I switched to Adobe Acrobat Pro. Murphy struck again! The default Acrobat Pro installer — the one on its primary download page — doesn’t work on Windows 11 (at least not on the Flo6 install). It took me almost an hour to find and use the company’s standalone installer instead. That worked, but sheesh: a PITA!

Ready to Switch…

It’s after 5 PM on July 31 (Thursday), so I’ll unplug everything for both systems, switch their locations, and plug them back in after lunch Friday. Hopefully everything will come up as it should. If not, I’ll report further in an addendum hereto. With finger crossed, I’m hustling through the morning so I can get this handled in the afternoon. Wish me luck!

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, Troubleshooting, WED Blog

Sez MS: 24H2 Most Reliable Windows Yet

Leave a comment

Here’s an interesting bit of Windows administrivia. On July 22, a spellbinding Windows IT Pro Blog post appeared. It comes from Monika Sandhu, the Senior Program Manager who runs the company’s Windows Resiliency Initiative. Unsurprisingly, it’s entitled Resilience in action for Windows devices. There’s lots of good stuff in this piece, but I want to focus on her claim: 24H2 most reliable Windows yet. What does this means, and why does she say it?

Why Is 24H2 Most Reliable Windows Yet?

You can see that paragraph from her blog post, reproduced as the lead-in graphic above. This assertion stems from MS telemetry that reports on unexpected restarts and related failure rates. Apparently, they’re down by nearly a quarter (24%) as compared to Windows 10 22H2.

As somebody who’s run a modest Windows 10 fleet (up to 12-15 desktops and laptops),  and who runs a similar-sized Windows 11 agglomeration right now, I can confirm her observation based on personal, if anecdotal experience. I don’t keep telemetry data around, but I do remember failure rates, restart problems, and so forth, across both Oses. For Windows 10, my experience goes back to October 14, when the first Technical Preview appeared. For 11, it goes back to June 2021. Over the interim, I’ve done dozens to hundreds of clean installs of both Oses, and hundreds of upgrades as well.

What Makes Windows 11 More Resilient?

I’ve seen the introduction of the reinstall now feature, which rebuilds whatever version of Windows 11 is running, including all current CUs, servicing stacks, and so forth. I’ve seen a demo of the Quick Machine Recovery facility which rebuilds the pre-OS-launch Windows startup/boot facilities. I believe this will work as MS describes it in actual deployment, too. And now, MS is talking about reworking the Startup Repair facility in WinRE (no doubt to match what QRM can already do).

So heck, yeah, I’m buying into this particular vision. In fact, I can’t wait to see QRM go into full production. I’m hoping it can save some butts the next time a Crowdstrike-like incident rears its ugly head. My thanks to Ms. Sandhu for sharing this info, and for injecting some hope that Windows-World could soon be a more resilient, less failure prone sphere to occupy. Let’s see what happens!

Facebooklinkedin
Facebooklinkedin
Hardware Reviews, Insider stuff, Recent Activity, Troubleshooting, WED Blog

NZXT H6 Flow Build Comes Together

Leave a comment

Allrighty, then. My “new” primary desktop build is almost completely done. I still have some software to install, and some file transfers from old to new to complete. But the hardware configuration is finished. As this NZXT H6 Flow build comes together, I’ve overcome some interesting hurdles and learned something I probably should have already known. Let me fill you in…

Deets: NZXT H6 Flow Build Comes Together

The case itself is perhaps the roomiest I’ve ever worked with. The split-level design  features the motherboard and plug-in elements above, with PSU, drive cage and cabling below. Very easy to work on, and far fewer cable routing shenanigans than I’ve ever run into before. Over the years — including a lengthy stint of motherboard, RAM and storage reviews for Tom’s Hardware in the early 2000s — I’ve probably built 100+ desktop and SFF PCs. From the perspective of ease and comfort, this one rules. First ever build, in fact, without cutting my fingers on the air cooler’s fins. Good-oh.

Here’s a BOM for the build, excluding the already-mentioned case [for which I paid US$110; other current prices in square brackets]:

  • Motherboard: Asrock B550 Extreme 4 (AM4) [US$185]
  • CPU: AMD Ryzen 7 5800X (8 cores/16 threads, 3.8 to 4.7 GHz, AM4, TDP 105W) [US$170]
  • GPU: NVIDIA 3070 Ti [US$600]
  • RAM: 128GB (4×32) DDR4-2666 [US$146]
  • NVMe: Sabrent Rocket Q 2TB[US$80], Samsung 990 EVO 4TB (2ndary)[US$200]
  • Hard disk: Toshiba DT01AC300 3GiB (2.72 TB in Explorer)[US$77]
  • Total system cost, not including monitors:  US$1,568

My ASUS Thunderbolt5 EX didn’t make the cut, because the B550 lacks a USB4/5 header for the device to plug into. Alas it won’t work without motherboard support. Sigh. I should have known, but there it is.

Issues Encountered and Overcome

The only build issues I ran into were:

  • Remembering how to re-insert the below-deck HDD cage. (A quick trip to YouTube took care of that in a hurry. Turns out to be a drop in, then slide up to lock into position kind of maneuver. Dead easy, once you see somebody else do it. Go YouTube!)
  • Getting the hard disk recognized in Device Manager. (None of my SATA devices showed up in Windows Device Manager or Disk Management. I used a temporary SSD-to-SATA device to ensure it was getting power (it got warm). So I knew it was a software issue. Thus, I was inspired to reload the “Standard SATA AHCI Controller:” right-click  the entry, Update driver, Browse my computer for drivers, Let me pick from a list…, reload the only entry showing. The plugged in SATA drive appeared immediately thereafter. Yay!

No drives appeared until I reloaded the standard SATA AHCI controller driver. Then, they popped right up.

Otherwise, this was a terrific, if time-consuming, experience. Because I must wear reading glasses now for close-in work (cataract surgery last fall), I had to give myself extra light and room for the build. I ended up taking over the island in our kitchen (covered with old towels) for the initial assembly, and then for final cable arrangement and clean-up. Except for the SATA HDD and the lack of USB4 support that knocked out the Thunderbolt5 EX, everything worked on the first try. Amazing!

IMO, things turned out extremely well. I’ll be switching over to this build sometime this week. Stay tuned: I’ll tell you more soon.

Facebooklinkedin
Facebooklinkedin