Category Archives: Troubleshooting

Uncovering Create Dev Drive Gotcha

Yesterday, I blogged about a real, but apparently small, performance boost for ReFS volumes vis-a-vis NTFS ones. While I was undertaking that testing, I switched a USB4 NVMe from NTFS to ReFS to keep everything else the same. I’m pretty sure that’s the best way to isolate file system differences because port, cable, enclosure and drive all remained the same. Along the way, I found myself uncovering “Create Dev Drive” gotcha. Let me explain.

Uncovering Create Dev Drive Gotcha:
Two Create Dev Drive Buttons

If you attach an unallocated drive to a Windows PC, then navigate to System > Storage > Disks & Volumes, you’ll not only see the “Create Dev Drive button” at the top of that UI pane as shown in the lead-in graphic. Should you scroll down to said unallocated drive, you can evoke a different Create Dev Drive button by clicking on the down-caret for “Create volume” like so:

Here’s the gotcha: if you use the upper Create Dev Drive button, everything works as it should. But if you use the lower one, the create operation fails every time, and reports it fails because the drive is read-only. Here’s what the Settings UI looks like after that error:

Something odd and interesting apparently happens when you use this button instead. I’m reporting this to Feedback Hub. Here’s that link, if you’d care to upvote: Create a dev drive button doesn’t work.

Clean-Up and Fix

Once you do this to yourself, you need to clean things up before you can set things up correctly using (only) the upper “Create Dev Drive” button. You must open Disk Management and delete the RAW volume you’ll now see there (right-click, and select Delete Volume… from the pop-up menu). Then you can return to Settings > System > Storage >Disks & volumes and do it right this time. Enjoy!

One more thing: the Dev Home app is a great place to get started when creating an ReFS volume. It does the Settings navigation for you and drops you right where you want to be. Just remember: it only works when you select the upper, general “Create Dev Drive” button, NOT the lower, device-specific “Create Dev Drive” button. I have no idea why this is so, but that’s the way it seems to work at present. Mysteries like these are what keep me forever fascinated with the wrinkles in Windows-World.

 

Facebooklinkedin
Facebooklinkedin

Chkdsk /f Fixes DISM Issues

Here’s an interesting item. As part of routine maintenance, I ran DISM /online /cleanup-image /analyzecomponentstore on the P16 Mobile Workstation this morning. Imagine my surprise when it threw  “Error 2; The system cannot find the file specified.” at about 80% complete. I’d never run across this one before. But a Google Search soon revealed that this happens when DISM encounters a corrupted entry in the component store. MS Answers also reported that, nearly always, chkdsk /f fixes DISM issues of this kind. So that’s what I tried: as you can see from the lead-in graphic, it worked!

How Chkdsk /f Fixes DISM Issues

This particular disk scanning operation repairs any corrupted files it finds, if it can. That has me wondering if sfc /scannow might not have had the same salutary effect. I think that’s at least possible, so I’ll have to try it next time around. The only follow-on is that repairs to the C: drive (especially for the kinds of files that DISM cares about) must run while the Windows OS image is not in use. That means scheduling that check and repair during boot-up before the OS takes over operation of the PC (that is, while the boot loader is running things).

Thus, I had to reboot the P16, and watch the check run as a pre-boot task (large white text against a black screen). Here’s a capture from inside a Hyper-V VM (otherwise, it’s challenging to grab boot-time screens from Windows).

Once that repair had completed, I was able to run the previously inoperative DISM command without trouble. Every now and then, one gets lucky in Windows-World. This time, the repair worked just like it was supposed to. Good stuff!

 

Facebooklinkedin
Facebooklinkedin

Morning Black Screen Recalls Pending Reboot

On September 10, NVIDIA release its Game-Ready driver, version 561.09. At its conclusion it asked for a reboot. “Oh yeah,” I thought, “I’ll do that later.” It’s happening a LOT later than I planned, nearly 8 days on. If you look at the uptime info in the lead-in graphic you’ll see I’ve somehow managed no reboots since then. But, for the last two days this PC’s monitors have stayed dark when I’ve tried to wake it up first thing in the morning. Alas, that morning black screen recalls pending reboot, which I apparently MUST do (soon).

Note: I’ve been able to bring the desktop back from the black screen state on each of the past two days by striking CTRL-ALT-DEL at the keyboard, then canceling out of the Security Options screen that pops up. Good thing to know, in case this ever happens to you.

How Morning Black Screen Recalls Pending Reboot

Normally, when I click a mouse button or hit a keyboard key when my PC is sleeping, it starts right up. Both yesterday and today, though, I get black screens on both monitors with no cursor. Experience informs me that this is 95+% likely caused by a graphics driver issue. And as I think about it, I dimly recall installing 561.09 last week, then never following up with a reboot. If you do the math on the uptime field from WinFetch in the lead-in graphic, it was last updated on September 9,  around 3:09 PM (thanks timeanddate). Thus, it hasn’t been updated since the GPU driver got updated.

I’ve also noticed graphics running a bit slower and jerkier lately, too. It all adds up: I should’ve remembered to reboot the same day I updated NVIDIA graphics driver. But it may be too late to go back, but it’s not too late to reboot right now. And sure enough, when I do, no more black screens on startup, nor after waking from sleep (which I forced from Power > Shutdown > Sleep through the Start Menu to check).

Go figure. I should know better. This not-so-gentle reminder does the trick to help me remember this time. Isn’t that just the way things sometimes go in Windows-World?

Facebooklinkedin
Facebooklinkedin

Choosing USB Power Ports Properly

I should have known. I put the Lenovo ThinkPad X12 Gen 1 hybrid tablet back into service yesterday. Indeed, I had a ThinkPad Universal Thunderbolt 4 Dock sitting right next to  the device. “No problem,” I thought to myself “I’ll hook up to one of these USB-C ports and I won’t need to rustle up its 65W brick.” Wrong! Just as it’s essential to choose USB-C ports for their bandwidth ratings when attaching storage devices, ditto for choosing USB power ports properly when seeking a charge. Let me explain…

Why Choosing USB Power Ports Properly Matters

I show the rear view of the TB4 dock in the lead-in graphic. Turns out that only the TB4-rated ports (the leftmost block of two is to the right of the DC power input connected) deliver more than 10W via USB-C. The others are rated 10 Gbps too, while TB4 gets the coveted 40 Gbps rating.

I knew things were off when the BIOS told me that the PSU wasn’t delivering an acceptable amount of power as the X12 started booting up. “Doh!” I reflected, “it’s important to read the fine print on the USB-C connectors to make sure they have the power lightning bolt and plug into those.” And sure enough,  if I zoom in on the detail on the two left-most USB-C ports on the back, the lightning bolt is pretty visible on each one.

Left: lightning bolt above; right: below. 100W available from each one, as per specs.

It pays to check before plugging into USB-C. If you can’t see or don’t know, it never hurts to RTM. As soon as I figured out what I was doing, in fact, it all made sense. Just another perfect day in Windows-World, right? Cheers!

Facebooklinkedin
Facebooklinkedin

StartMenuExperienceHost.exe Knocks ReliMon Over

When searching for Windows blog topics, I occasionally drop in on Reliability Monitor (aka ReliMon). FYI, it’s actually a special version of the more general-purpose Performance Monitor (PerfMon). This morning, I saw what I can only describe as a bad-to-worse stability index chart. See the lead-in graphic. Upon examination, I concluded that StartMenuExperienceHost.exe knocks ReliMon over with daily errors. Ouch!

Handling StartMenuExperienceHost.exe Knocks ReliMon Over

Digging into the details, I see this element present every day (multiple times on some days) for 16 of the past 17 days. That’s a new personal record for me, and it’s interesting. Why? Because this system hasn’t been giving me any obvious trouble, repeat SMEH errors notwithstanding. (Hope that abbreviation is obvious…)

So naturally I went looking for enlightenment about SMEH and the related MoBEX error that occurs for each instance in the detail page. Unsurprisingly, I found a registry hack to address the issue at TenForums.com from well-known VIP member Samuria. Apparently, it involves a well-known permissions inheritance issue for values inside the

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

key. I’ve applied the fix Samuria recommends, and will observe ReliMon over coming days to see if it helps.

The Enduring Value of Internet Community

Though one must exercise caution in picking up and running with fixes from the Internet, there are gradations of trust and merit in play, too. Because I’ve been an active member of TenForums for years and have seen many, many useful tips from Samuria over that entire interval, I’m comfortable with following his advice. That makes this a “safe fix” IMO. But if you have a recent backup handy, and know how to restore it, you can always get back to where you started. That’s my fallback position, and I’m sticking with it. Cheers!

I’ll keep you posted as I see if this helps … or not. Stay tuned!

Sept 13 follow-up #1: No dice, but…

I got a comment from fellow TenForums VIP OldNavyGuy that told me two things: he tried the reghack and it didn’t work for him. He also build a new user profile and moved over to that, then killed the old one. He reports that did away with the ongoing torrent of StartMenuExperienceHost.exe errors. I’ll try it sometime, and see.

Facebooklinkedin
Facebooklinkedin

Intel 13-14 Gen CPU Issues Unfolding

In tech news over the past 2-3 weeks, there’s been some serious CPU stuff revealed. As updated in this recent Windows Central item, PCs with Intel’s 13th and 14th generation CPUs (Raptor Lake and Raptor Lake Refresh, respectively) are prey to a microcode bug. Units with a TDP of 65W or greater can run excessive voltage under some conditions. This can cause crashes and BSODs. On July 26, in fact, Tom’s Hardware reported a scary observation. It said “13th Generation Raptor Lake processors have a return rate [4X] higher than … the previous generation”  (copy abbreviated). There’s the basis for my claim to see Intel 13th-14th Gen CPU issues unfolding.

What Intel 13-14 Gen CPU Issues Unfolding Means

If you’ve got PCs or laptops with such CPUs inside, you’ll need to keep an eye on them. Intel plans to issue a microcode fix sometime soon. When it’s available, you’ll want to schedule that update sooner rather than later. I’d also recommend that owners think about  underclocking as a form of insurance against possible problems that normal voltage level operations might otherwise cause.

Indeed, for those with 13th Gen Raptor Lake devices, you’ve been dodging trouble for some time now. The already-cited Tom’s Hardware story, mentions that “the first sporadic reports of CPU crashing errors surfaced in December 2022 and grew to a crescendo by the end of 2023.” You’ve been warned!

For more info on underclocking, this wikiHow Tech story “Underclock Your Computer Hardware: 2 Easy Ways” looks like a good place to start.

No Raptor Lake Exposure Here…

I have to chuckle as I report that the PCs and Laptops at Chez Tittel aren’t subject to this reported exposure. Because its worst-case consequences could require replacing a CPU, that’s a very, very good thing. I was concerned about my workhorse test PC, a well-equipped Lenovo P16 Mobile Workstation Gen 1. But a quick trip to CPU-Z (which you can use on your PCs to suss out relevant details) showed it running an Alder Lake 12th Gen Intel CPU. I was totally relieved to see that this morning (see lead-in graphic).

Facebooklinkedin
Facebooklinkedin

Disappearing Printer Gets IP-based Fix

This weekend, we went out looking at new housing developments. To prepare for our quest, I went to print street addresses for model homes in Liberty Hill and Georgetown (two small towns north of here). But when I tried to fire off a print job to the Samsung networked printer next to my desk, Devices and Printers told me it was offline. I’ve learned to recognize it as a sign of driver corruption, so my disappearing printer gets IP-based fix. Let me explain…

Why Say: Disappearing Printer Gets IP-based Fix?

My Samsung ML 2850 is old enough that it does not support the Microsoft Universal Print drivers. I have to load a bespoke device driver to make it work. In turn, that means automated discovery of this network attached printer doesn’t work right, either. That’s why you see the IP address info for the device below in the lead-in graphic (courtesy of Advanced IP Scanner). I use the Add a Printer option that depends on its IP address instead.

The drill is familiar and runs something like this:

1. Notice the Printer is offline
2. Basic troubleshooting doesn’t help
3. Right click the icon in Devices and printers, select delete
4. Use the Add a printer dialog to start the process going
5. Click the “Printer I want isn’t found” option
6. Click the use IP address or hostname on the next pane
7. Use the printer’s IP address to install the current driver

This actually takes longer to explain than it does to execute. But it does work, and it seems I have to do this once every three months or so. I guess that’s the outcome of using a 10-year-old printer (that still works like a champ, BTW). Windows has left it behind, but it still keeps chugging along. Kind of like your humble author, I guess…

Windows 11 Proves More Friendly

Just for grins, I tried discovering the Samsung ML 2850 from a Windows 11 host on the same network. At first, it couldn’t see that device, either. But when I clicked the radio button labeled “My printer is a little older. Help me find it.” the Samsung device did turn up. I had to know enough to select the Microsoft PCL6 Class driver (which handles the interface between the Samsung and the Universal Printing stuff). But once I did that, everything worked as it should. Seems like MS has made Windows 11 rather more printer friendly than I expected (and friendlier even, in this case, than Windows 10). A pleasant surprise indeed!

Facebooklinkedin
Facebooklinkedin

Calc Key Follies Fixed

Here’s an interesting one. I have a Microsoft Comfort Curve 4000 ergonomic keyboard (and two more in my parts closet: I LIKE them). Lately, though, when I press the “Calculator” (Calc) key on the very top row of long, narrow silver keys at furthest right something odd occurs. Calc shows me a “blank face,” as you can see in the lead-in graphic. Basically it’s just a big blue block of nothing much. Attend, and I’ll explain I I got these Calc key follies fixed.

For the record, I don’t *want* to see the blank face of Calc. I want to see the keypad so I can use the darn thing, like so:

Multiple Methods Get Calc Key Follies Fixed

I discovered these methods partly by searching the web, and partly by experimentation. There are three of them, to wit:

Method 1: Close Calc, then hit the Calc key again. This one’s my favorite so it’s my go-to now. It involves the lease effort and goes fastest.

Method 2: Open the Calc app from the Start Menu. Even though pressing the Calc key shows a blank face, visiting the Calculator app through Start always works. It takes added mouse clicks, though. Until I figured out Method 1 by experimentation, this was my go-to method.

Method 3: Go to Settings > Installed Apps, click on the ellipsis for Calculator, Click the Advanced Options button, scroll down to Reset, then click the Repair button. That’s 5 mouse clicks and a bit of scrolling. Waaaaaaay too long for me, but it does do the trick. But then the question is: why does this condition keep coming back, even after an app reset? I think I know the answer: read on, please.

Special Keys Require a Custom Driver

The Comfort Curve 4000 keyboard has a whole row of elongated, narrow silver keys that use special, driver-based, context-sensitive macros. These do things like jump to the home screen, open a search window, open email, access the volume controls (up and down), and so forth. And yes, at far right you can see the Calc key that’s been acting up lately. They occupy the top row from left almost to the numeric keypad at right, as shown here:

My best guess is that something in the driver is losing its proper connection to the Calc app so that when the key is pressed once, it gets close to launch but not all the way there. Fortunately, it’s relatively easy to get the Calculator working as I’ve described.

But gosh, aren’t these little foibles fascinating? It’s a bit of a pain to run into them, true. But it’s a blast to figure out what’s happening and why, and then to find fixes or workarounds. Just another day here in Windows-World!

 

Facebooklinkedin
Facebooklinkedin

Intermittent Mouse Needs New Battery

I have a kind of love-hate relationship with mice. Because I work on a desktop PC by choice, I’m more or less forced to use a USB-attached pointing device. I’ve switched back and forth between wired and wireless models because their weaknesses sometimes vex me. For the wired meese, the wire tends to snarl up with other cables on my desk. For wireless models, what frosts my jowls is intermittent or imprecise cursor stuttering or movement. I started to experience that on my current mouse this morning: a usually unflappable (and wireless) Microsoft Mobile Mouse 4000. Then I noticed a dimly pulsating red indicator light atop the device. Oho! This intermittent mouse needs new battery to work properly.

Why My Intermittent Mouse Needs New Battery

According this MS Community thread, the light is a battery life or status indicator. When you plug a new battery in, it shows green for 5 seconds, then turns itself off. Ditto when you power the mouse back on. When the battery is starting to fail, it shows red for the same interval upon power-up. And when battery levels are going critical — that is, it’s about to die — the dim red pulsations begin. Good to know!

We shop at Costco, so we always have lots of batteries around. As soon as I swapped out the old AA for a new one, I got the green glow for 5 seconds. Now it’s dark again. And presto! The mouse is no longer stuttering, and it’s tracking exactly where I want it to go. Yay!

The Best Issues Get Quick, Easy Fixes

Working with PCs in Windows-World means there’s always something in need of fixing or figuring out. Once you identify an issue, the troubleshooting process begins. Over my decades working with this stuff, I’ve learned to appreciate problems that are easy to recognize, diagnose and fix. Today’s successful battery swap definitely falls in that category, even if another one bits the dust as a result.

Facebooklinkedin
Facebooklinkedin

Pondering Post-Hurricane Internet Outages

The old saying in my home state of Texas is “If you don’t like the weather, wait 5 minutes. It’ll change.” Things took a turn for the worse on Monday and Tuesday, when Hurricane Beryl tore through the Gulf cost then Houston. At one point, over 2M locations (households or businesses) had no electricity. That number is still about 1.2M as I write this screed according to PowerOutage.us. One unexpected effect caused most Internet Service in Austin, Dallas, Houston and San Antonio to fail from about noon Tuesday until after 7PM that day. As a member of an affected household, it has me pondering post-hurricane Internet outages.

Fortunately, our 5G service stayed up and continued to provide Internet access. So I was able to limp along during the outage, using my iPhone 12 as a hotspot for minimal connectivity. Failing over from a nominal GbE link to something that delivers 5 MBps if we’re lucky stings, though.

If Pondering Post-Hurricane Internet Outages, Think Failover

Until last year, I had a Inseego MiFi M2100 mobile hotspot through my Verizon account. I kept it around as a fallback when the pandemic hit, because we had to have Internet access, guaranteed, while my son was attending high school remotely. He’s off to college now, and we’re doing our best to cut recurring expenses — like most American families nowadays. So we dropped the hotspot when we switched over from Verizon to Spectrum for cellphone service last year. The iPhone isn’t quite as robust as the MiFi device, but it does the job in a pinch.

Looking at news coverage of Tuesday’s Internet outage, Spectrum is quoted as saying it arose from “a third-party infrastructure issue caused by the impact of Hurricane Beryl.” My guess is that an Internet POP/peering location got flooded, or lost power, and backup generators couldn’t or didn’t pick up the slack. The afore-linked story also tells me that the affected area also included Laredo, San Antonio, the Rio Grande Valley, and Corpus Christi.

Resilience Matters

As somebody who makes his living at least partly thanks to Internet access — I use it for research and learning, for business communications, to obtain and deliver work assignments, and a whole lot more — ongoing access is essential. I’m glad I could use the iPhone as a failover device, but it definitely battered my productivity.

It’s enough to get me thinking about doubling up on fiber-optic coverage, and bringing in the AT&T Uverse fiber service alongside Spectrum’s CATV-based GbE service for redundancy’s sake. The question then becomes: it it worth the extra expense? I’ll have to think on that…

 

Facebooklinkedin
Facebooklinkedin