Category Archives: WED Blog

Blinking Monitor Requires Nvidia Studio Driver

Yesterday, my production PC (Windows 10, i7-6700, 32GB RAM, 3070 Ti GPU) started the “blinking thing” again. As soon as I logged in, the right-hand monitor would go black then come back at irregular intervals. Previous episodes have responded to a driver update. But this time, no such update was handy. But my 3070 Ti runs either a gaming (for game play and high frame rates) or studio (for creative and production work) version. This time, fixing the blinking monitor required Nvidia Studio Driver to do its thing.

Why Is It That Blinking Monitor Requires Nvidia Studio Driver?

This issue has been popping up on my production PC since I switched out the 1070 Ti for the oversized 3070 Ti in January. I’m starting to wonder if my power supply may be having issues with the load on this system.

Reliability monitor doesn’t show any errors. But a dive into Event Viewer shows a Service Control Error 7031 that points to the Nvidia Local System Container at around the times I was getting the blink behavior. Since I’ve switched from the Gaming version of the driver to its Studio counterpart, the error has not resurfaced. Looks like it may be some kind of software glitch after all.

GeForce Experience lets you switch between the two driver flavors pretty easily. Simply click the vertical ellipsis to the right of the Check for Updates item and it gives you a radio button to pick one or the other, like so:

Fortunately for me, switching from”Game Ready” to “Studio” restored my system to proper operation. Good thing I’m not a serious gamer, eh?


Windows 11 Clean Install Overlooks Certain Drivers

OK, then: here’s a “new-ish” behavior in Windows 11 that I don’t love. Once upon a time, you could use the update function in Device Manager to search the Internet for device drivers. No longer: if a driver is absent, the “Update driver” function can’t find anything to use. That explains why Windows 11 clean install overlooks certain drivers. If they’re not in the driver store built into the ISO image, they’re simply unavailable.

If Windows 11 Clean Install Overlooks Certain Drivers, Then What?

Take my recently clean installed Lenovo ThinkPad X380 Yoga. I happened to notice a half-dozen items under “Other Devices” in Device Manager yesterday. “Hmmm” I thought to myself. “Looks like the installer didn’t find some drivers while bringing the machine up.” Too true, as it turns out!

Fortunately, none of what was missing was essential to the laptop’s operation. Thus, that meant identifying the missing drivers, then finding and installing them. At first look, I saw 7 such devices. A quick hop to the Lenovo Vantage app (the company’s maintenance-update platform, which generally works OK or better) took care of three of them.

On a whim, I looked up LifeWire‘s story on the best free driver updaters (Tim Fisher updated it on April 4, 2022). It gives Driver Booster 9 Free the best rating (but the free version only updates 15 drivers, then requires users to pay ~US$23 to get a paid-up, for-a-fee version). It found 24 (!) drivers in need of update, so I concentrated on updating those that showed up with a “Driver Missing” label in that program’s output. Once identified, I knew I could handle the others on my own.

Back in  the High Life Again . . .

Indeed, the free version of the program did the trick for me. You can see in the lead-in graphic from Driver Store Explorer (aka RAPR.exe) that I was able to update 7 drivers (they show outdated versions). Add in another 7 new drivers added to go from “missing” to “found” and my system is now fully up-to-date, with no remaining “Other” device entries. No Device Manager items with the yellow exclamation point, either.

The gurus at TenForums and ElevenForum generally recommend against driver scan/update tools. I generally concur. But this was a big enough kerfluffle that I was grateful for some automated search-and-update help.

I guess that means I’m willing to make an exception when the “don’t check the Internet for available drives” behavior in Windows 11 prevents the installer from providing a full slate of items. I understand why MS did this (to prevent driver changes from adversely affecting naive users). But as I said in my lead ‘graph: I’m not in love with this design decision and its impact on clean install completeness.

That’s life, here in Windows-World. I can live with it, and fix it myself, when I must. So that’s what I did. And now the clean install machine is nearly production-ready. Just a few more apps and applications to go!


22598 Insider ISO Download Available

That didn’t take long. Build 22598 in the Dev Channel made its debut on April 13 (yesterday). Today (April 14) it’s already available for download on the Windows Insider Preview Downloads page.  {Note: eagle-eyed reader and fellow WIMVP David H Johnson tells me the ISO and the WU version appeared at the same time.] The lead-in graphic above, shows 22598 Insider ISO download available. Of course, users must sign in with a valid Insider MSA (Microsoft Account) to gain access.

22598 Insider ISO Download Available: Grab It!

This was the source I used last weekend for the clean install on my “troubled” X380 Yoga. I ended up with an earlier version because of the timing. Nevertheless it worked like a charm. I’m in the habit of keeping ISOs together on my Ventoy drive, so I have going on 30 (mostly Windows OS) images all together on one easy-to-search external drive.

And because that drive is a USB-C/Thunderbolt 3 enclosure with a nominal 256 GB NVMe SSD inside, it does a reasonably good job of providing ready and quick access to its contents. The whole thing cost me about US$100 in late 2020 (you can buy the same thing for under US$75 now). It’s definitely proved its worth to me many,  many times since I put all the pieces together (read more about its innards in this December 2020 post: Interesting Single-Builder SSD Benefits.

Doing the Download Thing

After specifying my version and language in the download GUI, I grabbed a copy of the 22598 ISO from the web page. It took about 7 minutes to arrive in toto —  longer than most such transfers take me. Watching it make its way onto my C: drive, I can only speculate that traffic levels are higher than normal. Indeed a quick hop to showed Internet speeds all over the place on my local cable loop, ranging from a low of 250 Mbps to a high of 650 on my 940 Mbps (max speed) connection.

But once you have the ISO you can use it for DISM repairs, an in-place repair install, or even — as I did recently — a clean reinstall. Handy!


BitLocker Follies Follow Secure Boot

To qualify for Windows 11, a PC must support Secure Boot. It doesn’t necessarily have to be turned on. But if it is turned on, I learned last week that BitLocker follies follow secure boot like ducklings follow their Momma. In other words: if BitLocker is turned on for the C: (Windows boot/system) drive, it must also be turned on for the File History drive that Windows 11 uses as well.

What Does BitLocker Follies Follow Secure Boot Mean?

I learned this hard way when I tried to turn File History on for my Lenovo X12 Thinkpad PC. Because it had secure boot turned on, I had to enable BitLocker for the external drive upon which I targeted File History. This immediately got me to climbing an “interesting” learning curve.

While summiting that slope, I learned the following things:

1. You can’t manipulate an external drive’s BitLocker status through RDP. For security reasons, you must be directly logged into the target system. Sigh.

2. Turning BitLocker on requires setting a password to obtain or deny access to its encryption/decryption capabilities. This makes good sense, but gives me “just one more thing” to remember. Sigh again.

3. At first, BitLocker encryption looks fast. It got up to 84-85% complete in minutes. To my dismay and disappointment, the final 15-16% took HOURS to complete. By no coincidence whatsoever, space consumed on the drive is between 15 and 16%, too. It took the better part of 6 hours for the encryption to finish, in fact (0.71 TB worth).

4. Now, when I want to access the encrypted drive, I must first open it in Explorer, and unlock it by providing its password.

It’s All Good . . . I Hope

At least I now understand the necessary relationship between Secure Boot, BitLocker, and File History. I hope I don’t need to go a-troubleshooting soon. But if I must, I will. Stay tuned: I’ll keep you posted.





Clean Install Succeeds Where Beta Promotion Fails

For the past couple of Dev Channel builds, I’ve been trying — and failing — to get my Beta Channel test PC promoted to the Dev Channel. For Builds 22593 and 22581 the tap had been opened to upgrade from Beta to Dev Channel. But on my Lenovo ThinkPad X380 Yoga (8th Gen i7, 16 GB RAM and 1 TB SSD) it didn’t work. After many hours of dithering about, a clean install succeeds where Beta promotion fails. Let me explain…

Why Clean Install Succeeds Where Beta Promotion Fails

Wiping the primary system/boot drive was apparently the ticket to success. Given that I seemed to have mystery driver issues, starting over with a clean slate has finally set things right. And indeed, it was a rough and time-consuming ride along the way. Ultimately it took less than 35 minutes to perform the clean install itself. Alas, though, it always takes longer to put all the apps and settings back the way I want them from a clean slate. That’s life!

Interesting Lessons Learned

This is my first clean Windows 11 install since the new OS showed up in mid-2021. I had to be reminded that the BitLocker ID associated with the key needed to enable a USB-based install comes from the device. I spent a while trying to provide the wrong key, because I didn’t start by matching the Key ID value to the Device Name. Only then did I find and enter the right recovery key. Sigh.

I also learned that Norton’s external drive scan function takes FOREVER to complete. I let it run for 1:15 out of curiosity, but that was already too long for me to wait to move onto my next step. So I cancelled the scan (which took no time at all, thank goodness) and went onto the clean install.

Performing the clean install was remarkably quick. It included the option of defining a machine name near the tail end, too (something new to me). That was an opportunity I grabbed gratefully, and saved myself a bit of time moving ahead into post-install efforts.

Bottom line: I’m incredibly grateful to have this machine back where it needs to be. It’s nice not to have the mystery 0XC1900101 error hanging over my PC (and my head) any longer. I’d love to know what caused it, and how to fix it, but I never got enough data to make that happen. That said, it’s nice to know the “repair of last resort” — namely a clean install — still does the trick when other techniques come up short.


Various .NET Versions Facing EoS Soon

On April 4, an End of Support notice surfaced in  the MIcrosoft Message Center. Its initial text appears in the lead-in graphic for this story above. A quick summary of its contents is that various .NET versions facing EoS soon. The version numbers involved are 4.5.2, 4.6 and 4.6.1 runtime. MS recommends that affected PCs update to .NET Framework 4.6.2 before April 26, 2022. No updates or security patches will be issued for those versions after that date.

If Various .NET Versions Facing EoS Soon, Then What?

This is an issue only if certain applications still in use employ those older .NET versions, and they themselves haven’t yet been upgraded to use a newer one. As I look at the relevant folder in my production  Windows 10 desktop — namely:


these are the folders that I see

If I understand how this works correctly, all versions lower than 4.0 reflect older .NET versions currently installed on this PC. Thus by reading the version numbers for those folders you can see that 5 such versions are installed, from v1.0.3705 through v3.5.

On the other hand, if you display properties for any .dll file in the V4.0.30319 folder, you’ll see what version of .NET is currently present, to wit:The Product Version line reads 4.8.4084.0, and tells me that I’ve got the latest and greatest .NET version installed here, as well as the earlier versions already mentioned.

What To Do About Impending Retirements?

If you’re using no software that depends on earlier .NET versions, you need do nothing. OTOH, if some of your software does depend on them you must decide if you’ll keep using it and risk possible security exposure, or find an alternative that isn’t subject to such risk. For my part, I recommend the latter approach, unless there’s no other choice. And in that case, the safest thing to do would be to run such software in the MIcrosoft Sandbox as a matter of prudent security policy. ‘Nuff said!


Build 22593.1 Fails Beta Promotion

Drat! I’d feared this might happen, and it did. As you can see from the lead-in graphic, waiting for a new Dev Channel build on my second Lenovo Yoga X380 did no good. It, too, failed to upgrade with error code 0xC1900101. Thus, for that PC, Build 22593.1 fails beta promotion, just as with the previous build .

That leaves me with two potential paths to follow:

  1. Find a fix for, and repair the cause of the error
  2. Wipe the PC and use a current ISO to perform a clean install

I haven’t had much luck with Path #1, so I’ll probably give Path #2 a shot this weekend. I wish I knew what was causing the error.

Why Build 22593.1 Fails Beta Promotion

I am not alone in this error. Both Windows Report and The Windows Club have stories about this very error in their recent output. Reasons for this error vary, and can include the following:

  • Insufficient disk space on the target device to accommodate upgrade files and working space
  • Issues with non-essential peripherals (drives, scanners, and so forth)
  • Outdated BIOS
  • Incompatible device drivers
  • Third party AV or antimalware programs
  • “Software conflicts” with installed third party programs

As far as I can tell I may have a driver issue. But I can’t find proper details in the various log files to know for sure what’s up. I’m pretty sure I’m not subject to any of the other potential causes.

Clean Install Offers Easy (Potential) Out

Although there’s work involved after a clean install to bring the apps and applications back, this may be worth trying. I’ve spent hours and hours — unsuccessfully, so far — chasing after one or more errant drivers. I can get through a clean install in under an hour, once I have the ISO file built and ready to rock’n’roll.

Stay tuned! This promises to be interesting. . . I’ll report back as soon as I have some news.


Ventoy 1.0.73 Requires Interesting Contortions

When I saw a new version of Ventoy came out this morning, I immediately went to update my drive with the new software. It runs on an AData 256 GB (nominal) M.2 SSD inside a Sabrent NVMe enclosure. For some odd reason, the update function did not work properly. Digging into the log, I see the program had trouble writing the new EFI files to the Vtoyefi partition where the program does its boot magic. Indeed, installing Ventoy 1.0.73 requires interesting contortions for me to achieve success. I’ll explain…

What Ventoy 1.0.73 Requires Interesting Contortions Means

First, I backed up the contents of the Ventoy drive, which shows up as E: on my production desktop. Then I tried to use the Install function in the program to over-write the existing disk structures. No go. I switched over to a newer PC, where I was able to cable up using a high-speed USB-C cable into the Sabrent enclosure. Then, I performed a clean install of Ventoy 1.0.73 on the target drive. That worked!

Of course, then I had to go back to my production PC to restore the backup. The whole process ended up taking about half an hour to complete, of which time the bulk went to creating and then restoring a backup of the 28 ISOs in the Ventoy (E:) partition.

Speculation Reigns Supreme

I must confess I don’t know why the update function failed this time around. I’ve not seen this happen before with Ventoy. That said, I’m not surprised that a vintage-2016 PC with USB 3.1 drivers might have trouble with a device that works with USB 3.2 (and Thunderbolt 3) drivers. And indeed, when I hooked up to a device that supported those newer drivers, everything worked as expected.

That’s why I’m thinking something went weird with the USB drivers when the program attempted to rewrite the 32 MB FAT based EFI partition from which Ventoy works its magic. That’s the part that wouldn’t update on the older PC, but which installed flawlessly on the newer PC. If somebody else has a better explanation, please share. But when the next Ventoy update comes out, I’m going to run it from the newer PC. I’ll bet it runs faster that way, too, thanks to those newer — and faster — USB 3.2/Thunderbolt 3 drivers it uses.


Microsoft Catalog Goes HTTPS

Call it a factoid, or perhaps administrivia. Whatever you call it, this info come thanks to the eagle-eyed folks at  Indeed, it’s now clear that the venerable Microsoft Update Catalog is using the secure version of HTTP (namely, HTTPS) for downloads. The lead-in graphic shows lookup and resolution of yesterday’s CU preview URL for Windows 10 (KB5011543) by way of proof. When I say Microsoft Catalog Goes HTTPS, you can see it at the outset of the URL I pasted into Notepad, plain and simple.

If Microsoft Catalog Goes HTTPS, So What?

It’s 2022. HTTPS made its debut in 1994, in the earliest days of the web. It comes to us courtesy of Netscape from the same folks who brought us Navigator. And as far as I can recall, MS has been using HTTPS on its websites since the mid-2000s.

So why is MS making the catalog switch only now, either 28 or perhaps only 17 years later? The answer appears on a recent (April 1, 2022) Microsoft Docs page. It’s entitled “Site compatibility-impacting changes coming to Microsoft Edge.” Among other things it states that “downloading of files from HTTP urls will be blocked on HTTPs pages.”

I guess it just wouldn’t do, if Edge couldn’t download catalog entries for that reason. Note that the catalog itself has this URL for KB5011543: If the catalog download stayed at HTTP only, starting with v94 of Edge, it would no longer deliver the goods. And that kind of defeats its purpose, right?

So there’s your explanation. Enjoy the improved security, while you use any browser of your choosing. Cheers!


NonCNVi M.2 Wi-Fi Device Delivers LAN Access

It’s always the little things that jump up to bite you (or me, anyway). In today’s case, it was my blithe assumption that Intel Integrated Connectivity (aka CNVi) wouldn’t prevent the AX201NGW M.2 Wi-Fi card from working on my AMD B550/Ryzen 3 5800X build. Yeah, right! But when I replaced it with a no-name (REKONG) Media Tech MT7921K module (depicted in the lead-in graphic), Device Manager picked up that non-Intel hardware immediately. After a bit of driver fiddling, this US$29 (tax included) nonCNVi M.2 Wi-Fi Device delivers LAN access as it should. It does have interesting limitations, though . . .

Fiddling Means NonCNVi M.2 Wi-Fi Device Delivers LAN Access

At first, after plugging in the device, I saw only non-working BlueTooth and Network Adapter devices in Device Manager. This informed me that Windows couldn’t find the required drivers on its own. But a quick search on “Windows 11 drivers for MT7921K” quickly turned up what I needed. They’re available from Lenovo, as it turns out, with a separate .exe for each of Bluetooth and Wi-Fi.

As the owner/operator of half-a-dozen (or more) Lenovo laptops, I’m quite familiar with their self-installing drivers. After downloading and installing them, here’s what I see in Device Manager:

NonCNVi M.2 Wi-Fi Device Delivers LAN Access.DevMgr

With the right drivers installed, the BT components and the Wi-Fi interface all show up. Good!

Just a Few More Things

Wi-Fi behavior on desktops can be interesting. The interface has a tendency to turn itself off upon reboot, I’ve learned. I’m also trying to figure out why I can access the LAN (via the nearby Asus AX6000 router), but I can’t yet get Internet access through this interface. I have a wired GbE connection that works fine, but had hoped to switch over to wireless. So now, I’m researching those two issues in hopes of finding solutions soon.

A little more time put intro troubleshooting the M.2 Wi-Fi card tells me lots of interesting stuff:

  • The lack of an external antenna means the device doesn’t see that many wi-fi interfaces as it scans the airwaves. Thus, for example, it doesn’t see the Spectrum-supplied router in my bedroom closet (all of my laptops in the same office see it quite well).
  • The fastest throughput I can get on the device is between 250 and 300 Mbps (observed through a connection to
  • The 2.4 and 5 MHz connections to the “office router” are flaky in interesting ways: sometimes, I can access one or the other to get on the LAN, but don’t get Internet access. At other times one channel or the other will be inaccessible. Again, I attribute this to lack of an external antenna. My son has a PCIe 802.11ax adapter card with triple external antennae in his bedroom, and he gets up to 900 Mbps from the bedroom closet router, and up to 500 Mbps from my office router.

No External Antenna Is NOT a Plus

I’m increasingly inclined to observe that an M.2 Wi-Fi card makes sense only where close proximity to a WAP is available. It’s probably not a good idea for machines that do lots of heavy upload/download stuff, either. That’s kind of what I wanted to learn more about, so I’m not disappointed by this experience. I feel like I understand the capabilities and limitations of these devices much better now. I will keep my GbE wired connection going forward, too: the M.2-based Wi-Fi is not fast enough for my needs. If I’m ever *forced* to go wireless, I now understand that a PCIe device is my fastest option.