Category Archives: Insider stuff

Fighting Off Update OCD

I’ve been whipping my PCs into shape, preparing for a trip away from home. I’ll be OOO for all of next week, attending a legal process in Waco. Naturally, before I go, I’m making sure all the PCs here — especially production ones — are entirely up to snuff. I must be getting close to my goal, because I’m currently fighting off update OCD. Let me explain…

What Fighting Off Update OCD Really Means

As you can see from the SUMo listing for my production desktop (in the lead-in graphic above), I still have three items that appear to be obsolete or outdated. At least one of them is a false positive.

I just checked on FileZilla. And while no update was available yesterday, one is  indeed available today. Fixed! Here’s how I found that out just now by asking the app to check for updates:

Fighting Off Update OCD.FileZilla

When I checked yesterday inside the app: nada. Today I found — and installed — 3.60.1. Notice: It bears today’s date (6/1/2022). Go figure!

When I check on status for voidTools Everything (sometimes called Search Everything), it still reports itself current. That’s good enough for me, so I’ll quit looking for the putative version that SUMo recommends. Here’s what the program tells me when I tell it to check for updates:

Fighting Off Update OCD.everything

If the auto-checker says “OK,” I’ll take it at its word.

The last item is the sometimes tricksy Intel ® PROSet Adapter Configuration Utility. It’s easy to go round and round on this one. I’ve learned to search on the first two digits of the version number — that is, 27.3 — along with the utility name at If it comes up, I’ll try it; if not, I’ll wait until next time around. I did find such a version, and thus I downloaded and installed it.

Two False Positives, One Gone

Even though I got to a new version of FileZilla, it wasn’t new enough to satisfy SUMo (it shows up in the app as version rather than, despite its own self-labeling). But that’s close enough for me.

AFAI can tell, there is no such Everything version as — or at least, I couldn’t find it. Again, given the auto-updater’s response in the application, good enough for me.

Downloading and installing the file did clear the PROSet warning, though. Again: good enough for me.

I’ll waste no more time obsessing, and let my OCD find something else to obsess about instead. Basta!


Settings Accounts Presents Subscriptions Info

I’ve been reading about it for months, but until Build 25126 (Dev Channel) I never saw it. But finally, I can see the Services & Subscriptions info for my logged-in MS in Settings → Accounts. Hence my claim that Settings Accounts presents subscriptions (and product) info, as shown in the lead-in graphic.

Until this finally hit my Dev Channel test PCs, I’d been accustomed to a “pointer display” like the one shown in the next screencap (from a production Windows 11 PC running Build 22000.708). It just provides a quick link to the logged in MSA’s “Microsoft Account” web page, with its subscriptions, rewards and other details.

What Does Settings Accounts Presents Subscriptions Info Deliver?

It means you can see your purchased products, subscriptions and services right inside Settings, without having to jump onto the MS website. But that seems to be about it. To manage services or subscriptions, the website is the place.

For purchased products, it shows product name and purchase date. For subscriptions, it shows product name, and pending expiration/renewal date. For expired subscriptions and other such data, little reminders appear in the initial Settings Accounts screen, as shown above. It’s handy, but it’s neither earth-shattering nor life-changing.

Other Lesson Learned

I was reminded, while conducting this exercise, that you have to ADD other accounts. Indeed, even MSA based ones must go to the list of authorized users for them to login. Even to a a Windows 11 PC. That finally allowed me to see multiple accounts when I used the CTRL-ALT-DEL key combo to bring up the “Switch user” option on the pop-up menu.

I did this so I could check the info from the perspective of multiple accounts. I also had to (temporarily) turn off the security setting “Allow Windows Hello logon only” so I could get in to a newly-added account that didn’t yet have that stuff set up.

Sigh. Live and learn (or remember), I guess…


Manual OneDrive Update

Late last week, SUMo (Software Update Monitor) informed me that the version of OneDrive on the home-from-school PC was outdated. It didn’t update itself, nor did any of my usual update tools handle this item either. Thus, I found myself asking: “How do I perform a manual OneDrive Update?” The answer, quite fortunately, is: “Easy!”

Working Through Manual OneDrive Update

If you right-click the OneDrive cloud symbol in the taskbar notification area, a menu appears. Click “Settings” from that menu (shown in the lead-in graphic for this story).

Next, click the “About” tab at the upper left of the resulting OneDrive window. If you the click on the version number in the “About Microsoft OneDrive” pane (boxed in red below), it takes you to the OneDrive release notes page.

The Build number clues you into what’s running on the target PC.

From there, you can compare the version number for the installed version (shown in your UI) and the “Last released build” under  the “Production ring” heading on the web page. If the numbers agree, you’re up to date. If the on-web version is higher numbered than the local one, click the link to download the OneDriveSetup.exe file. You need only double-click that file to bring your OneDrive version current. Easy-peasey!

Ordinarily, OneDrive takes care of itself just fine. But if you find a PC with an out-of-date version — even a way out-of-date as on the former school laptop — this technique will catch you up quickly and easily. Cheers!


School PC Catch-up & Cleanup

Earlier this week, the school year ended. Thus, I regained access to my Lenovo X390 Yoga laptop, which my son used as his in-school PC. As such things go, it wasn’t in terrible shape. But it had missed out on plenty of updates, including the upgrade to Windows 11. With all that effort behind me now — and a couple of interesting war stories to share — here’s the tale of a school PC catch-up & cleanup.

Tales of  a School PC Catch-up & Cleanup

I was pleasantly surprised with the machine’s state upon its return. It wasn’t even that dirty. A quick wipedown with a wet-wipe sufficed to get the fingerprints and etcetera gone. A microfiber cloth did likewise for the screen and keyboard deck.

But boy, did it need a LOT of updates. And then there was the Windows 11 upgrade, which brought me face-to-face with at least one recurrent RDP gotcha, amidst some other interesting stuff.

What Didn’t Need an Update?

I ended up using three tools to cover most of the application updates. Of course,  a visit to the Microsoft Store did likewise for the apps on this PC. Those three tools were KC Softwares Software Update Monitor (SUMo), PatchMyPC, and the built-in PowerShell winget utility. In the end, all 16 applications installed on the PC were updated, along with 54 (!) apps via the MS Store. Wow!

It was on the OS side of things where life got more interesting. After I caught up on the Windows 10 installation on the X390, I noticed that numerous prior upgrade attempts to Windows 11 had failed. Upon essaying same, I quickly realized why: Start10 was installed on that machine.

The MS installer apparently now requires that Start10 be uninstalled before the upgrade can proceed. Interestingly, earlier versions would let it through. (I had a couple of machines where Start10 would happily run on Windows 11, in fact). Uninstalling the application required some Task Manager shenanigans. I had to kill its parent process. That’s because uninstall otherwise requires a reboot and the upgrade install process was ready to fire off if the hurdle could be cleared.

A Few Bumps on the Upgrade Road

Then came the Windows 11 upgrade, which proceeded without issues this time. However, once again I could not use an MSA (Microsoft Account) to RDP into the upgraded PC. I had to set up a local account (with admin privileges). I also had to use the PC’s IP address as the target, because the machine name wouldn’t resolve. That’s interesting, because the names DO resolve in Nirsoft’s NetBScanner, as shown here:

School PC Catch-up &

As you can see both RyzenOfc and DinaX390 resolve inside NetBScanner, but neither name resolves inside RDP. Weird!

I’ll be filing feedback hub reports on those glitches later today. That’s it for now on “The Return of the School PC.” More will follow as I observe and learn more along the way…

Note Added 1 Day Later

I have gotten machine names to resolve on both problem PCs now. The Ryzen PC was affected by the recent lightning strike, and lost its network sharing settings and name resolution upon the next reboot. After running DISM /restorehealth and turning RDP off, then back on, it started working again.

On the X390, after I used RAPR to forcibly delete obsolete and duplicate drivers, then rebooted, the name resolution starting working there again, too. They now show up in positions 2 and 4 in the following set of File Explorer network PC icons:

I still can’t log into either machine using RDP with an MSA (Microsoft Account). Thank goodness the local account workaround (admin level accounts only, please) still does that trick! I’m guessing this is a separate issue and will report it to Feedback Hub accordingly.



Lightning Storm Prompts Network Rework

My son, Gregory, graduated from high school on Tuesday night. After we got home a big line of thunderstorms rolled through, and we experienced a quick half-dozen power interruptions. It wasn’t enough to toast anything, thank goodness. But that lightning storm prompts network rework here at Chez Tittel. Long story short, I’ve added a new GbE switch. I’m also keeping an eagle eye on my Asus AX6000, currently serving purely as a Wi-Fi Access Point (WAP) on my LAN.

Why the sudden vigilance and rework? Because the network starting crashing constantly the day after the T-storms rolled through. I think I’ve got things under control now, but only time will tell. For a while, though, I grew increasingly convinced the AX6000 had been damaged: the network stayed up with it out of the loop, and started crashing when it was added back in. After a factory reset and a recopy of the old configuration, though, it seems to be back in the pink. Perhaps the firmware got discombobulated?

If Lightning Storm Prompts Network Rework, Then What?

As I said before, I’m watching my network more closely than usual right now. My attempted cure — a factory reset on the WAP — seems to be holding up so far. I’m thinking about adding a second UPS to my office, so I can plug my networking gear in. This will not only let it run for a while on battery power, it will also provide added circuit protection.

What with family activities and a fast press at work right now, I’m definitely not down for extended, ongoing network troubleshooting. Hopefully my fix will hold. If not, I will purchase a new WAP. I may also swap out my two 8-port GbE switches for a 16-port model with more professional features. Given that time is money, I’d rather spend a little extra in exchange for improved reliability and availability.

And, that’s the way things go here in Windows-World, especially when the T-storms start rolling through…


22621 Takes RTM Role

OK, then: I was pretty much on the money yesterday when I speculated about Windows 11 22H2. A May 24 Windows Hardware Compatibility blog post — shown as the lead-in graphic above — totally confirms this. Indeed, Build 22621 takes RTM role for OEMs in the run-up to its release later this year.

If 22621 Takes RTM Role, Then What?

Here’s a quote from my May 24 piece Windows 11 21H2 Hits Broad Deployment:

As I’ve already reported on May 16, Beta Channel Build 22621 is very likely to RTM as 22H2 in a short while. That makes 22H2 GA likely in September or October.

The lead-in graphic (see red boxed text) confirms that Build 22621 is the “Windows 11, version 22H2 certfication build.” That makes it the starting point for the images that OEMs will build to load onto machines sold after the 22H2 GA date whenever that might be.

And, as for that date, later on in the afore-cited Windows HCL blog post it says:

Partners looking to achieve compatibility for systems shipping with Windows 11, version 22H2 Release may use drivers for components that achieved compatibility with Windows 11, Version 21H2 until Sept 5th, 2021

To me that puts GA date sometime after September 5, and seems to confirm my speculation that this would occur in September or October of this year. Unless something unforeseen occurs — and it could — September 6 is suddenly looking possible. Stay tuned, though: as usual, I’ll keep tracking this and let you know what I learn.


Windows 11 21H2 Hits Broad Deployment

Does anybody else see irony in this? If you check the lead-in graphic for this story, you’ll see it captures the header of the Windows 11 known issues and notifications document. The section I show is dated May 17. It reads (in part): “Windows 11 is designated for broad deployment.” Thus, when I claim that Windows 11 21H2 hits broad deployment that’s almost verbatim.

So, where’s the irony? We’re taking about 21H2. It has an RTM date of June 24, 2021, and a GA date of October 5, 2021. This is late May 2022. As I’ve already reported on May 16, Beta Channel Build 22621 is very likely to RTM as 22H2 in a short while. That makes 22H2 GA likely in September or October. To me, the irony is strong. As the older version gets fully broadcast, the new one is entering the pipeline, heading in the same direction.

What Windows 11 21H2 Hits Broad Deployment Means

Simply put, this means MS is not longer withholding an upgrade offer of Windows 11 21H2 to any qualified PCs. Previously, they’d been holding back on machines with known issues such as device or driver incompatibilities. Now, it’s open season for anyone with an eligible PC. In part, this tells business users that “Windows 11 is ready for prime time.”

This comes at roughly the same time that Panos Panay delivered a Computex keynote in which Windows 11 figures strongly. In that address, he touted Windows 11 in a string of superlatives. Windows 11, he avers, is MS’s highest rated, highest quality OS ever, with faster business adoption than “in any previous version of Windows.”

Interestingly, Panay also mentioned that “Windows 10 had that great moment” (emphasis mine). He went on to say that “But Windows 11 in its moment …[is]…driving in the right direction for our customers every day.” Paul Thurrott interprets this to mean “…you shouldn’t expect any meaningful updates to Windows 10 going forward.” FWIW, I agree.

Too Much Windows 11 Drama

Lots of news outlets online are expressing dismay and disbelief in reaction to Panay’s keynote. I’m not upset, and I think I understand what’s going on. Panay is working to move the business base to dig into 11 and to get the long, slow, deliberate migration process going. Given that business usually waits for the first “real upgrade” to a new OS to start its processes forward, I see this more an an announcement that “The upgrade is coming. Time to get serious about migration.” more than anything else.

Hyperbole is to be expected in trade show keynotes. I see a more serious and not at all sinister purpose at work. Call me naive, or even a Polyanna, but this looks like a calculated wake-up call to me.


X12 Hybrid Tablet 25120 Issues Continue

OK, then, I just updated from Build 25120.1000 to 25120.1010 on both of my test machines. In what’s becoming an emerging pattern, the X380 Yoga sailed through the process. OTOH, the X12 Hybrid tablet PC did not. Hence my assertion that my X12 Hybrid Tablet 25120 issues continue unabated. They’re weird, but they don’t last long. Let me explain…

Why Say: X12 Hybrid Tablet 25120 Issues Continue

This time around, I saw similar weirdnesses with 8GadgetPack after the reboot to the desktop on 25120.1010. But because I RDP’ed into that PC anyway, it looks like things fixed themselves as a result of that maneuver. Makes me wonder if my earlier repairs were really necessary. I’m killing my RDP session right now to check the desktop locally…

Indeed, everything looks normal from both a local and an RDP vantage point. But getting to the desktop this time around was time-consuming. The post-GUI restart took 25-30 minutes to complete vs. a more typical 5 minutes or 20. Post-GUI seemed to take the same amount of time, though — about 5 more minutes.

Where Things Get Weird

In fact, the post-GUI reboot didn’t complete until AFTER I’d disconnected the Thunderbolt 3 dock I use on that PC for external storage and a wired GbE connection. Once the PC got to the desktop, I reconnected the dock. Immediately, the OS recognized the dock and its drives. As the following graphic shows, it also reports what it sees correctly:

X12 Hybrid Tablet 25120 Issues Continue.winver

Eventually, after disconnecting the Thunderbolt dock, post-GUI reboot completes, as does the update

Of course, there’s only one way to show my possible diagnosis is correct. When the next CU or upgrade comes along in the Dev Channel, I’ll disconnect the dock before I start that process. If it completes normally, that’ll demonstrate the dock is a potential culprit. If I still have problems, I’ll know it’s something else. Stay tuned: I’ll let you know. It’s interesting and weird, whatever it is…


Build 25120 Shenanigans Continue

I’m still finding my way into the “new regime” for the Dev Channel in Windows 11. A couple of days ago, MS dropped Build 25120 (here’s that announcement). I’ve been playing catch-up ever since, with a number of interesting issues popping up. In true Whack-a-Mole style, I’ve been able to fix everything so far. But no sooner do I whack one than another pops up, which is why I assert that Build 25120 Shenanigans continue. Let me explain…

Which Build 25120 Shenanigans Continue?

Yesterday, I described issues with the Thunderbolt dock and its attached peripherals (unplug/re-plug fixed that one). I also described how 8GadgetPack disappeared, and required a re-install AND a repair for a successful resuscitation.

Later that afternoon, I ran into an interesting gotcha, described in this Twitter thread “Dude! Where’s my Control Panel?” Suffice it to say that I couldn’t search inside the start menu, which proved hugely frustrating. A DISM restorehealth operation and a File Explorer restart set things back to rights for that one. FWIW, I also ran SFC /scannow but it found nothing in need of repair.

I can now say with confidence, based on recent, painful personal experience, that typing program names into the Start Menu search box beats the pants off figuring out and using command line equivalents! Until I fixed that glitch, I was NOT a happy camper.

What’s Next?

I can’t say for sure, but I’m pretty sure I’ll keep finding and fixing stuff as the series of Dev Channel releases find their way onto my test PCs and VMs. I’m getting a good education on minor glitches and gotchas and their associated fixes, that’s for sure. All I can say to MS and the WindowsInsiders team is: “Keep them moles a’comin.” I’ll keep whackin’ ’em as they pop up, for sure!



Dev Channel PC Shows Potential Thunderbolt Issues

OK, then. Life has just gotten a little more interesting here at Chez Tittel. Briefly: I had trouble remoting into the X12 Hybrid yesterday. Ditto this morning, when I decided to troubleshoot the PC. Turns out the initial attempt at installing Build 25120 failed, with a familiar and possibly driver-related error code. And while the second upgrade attempt succeeded, that Dev Channel PC shows potential Thunderbolt issues. Let me explain…

Dev Channel PC Shows Potential Thunderbolt Issues: More Info

The lack of a network connection clued me into the seeming culprit. When I visited the X12 hands-on, I saw I was connected to the LAN via Wi-Fi. Not necessarily bad, but the machine has a Thunderbolt dock with a (previously working) GbE wired connection. It wasn’t working. Nor were other peripherals plugged into the dock.

So I unplugged the dock, then plugged it back in after a half-minute wait. Presto! Everything was working as normal once again, including my wired RDP connection. I can only presume that the driver issue reported in the first failed upgrade attempt was Thunderbolt related. I’m also  starting to wonder if my dock isn’t having power or connectivity issues, because this is not the first time this has happened — the dock going bye-bye — recently.

Promised Dev Channel Instability Is Manifesting, Too…

When the Insider releases for Dev and Beta Channels forked earlier this month, MS warned of potential or increased instability in the Dev Channel. I’m not complaining, but I am seeing same now on Build 25120.

8GadgetPack is definitely hosed on the X12 (but works perfectly on the X380 Yoga — go figure!). I’m making my bug reports and trying various fixes. As I’ve said before, I’m getting a feeling that this venerable software’s days on Windows 11 may be numbered. I’ll keep you posted about that.

Otherwise, I’m just feeling my way into the latest OS release. I’m hopeful that such kinks as I discover will be worked out. But yea or nay, I’ll let you know. Stay tuned!

Note Added 15 minutes later: Another reinstall of 8GadgetPack, and another manual repair does the trick on my X12 PC. GadgetPack appears to be working again. Having now had trouble on one of each of my two Dev Channels PCs after the past two upgrades I’m wondering if this will become a recurring theme in post-upgrade processing. More to come on this subject, I’m sure!