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.

Facebooklinkedin
Facebooklinkedin

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.

Facebooklinkedin
Facebooklinkedin

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…

Facebooklinkedin
Facebooklinkedin

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!

 

Facebooklinkedin
Facebooklinkedin

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!

Facebooklinkedin
Facebooklinkedin

Kindle Update Problem Solved

Huh! In past discussions of update handling tools such as PatchMyPC and SuMO, I’ve complained about the difficulties that keeping Kindle up-to-date posed for me. Ha! Ha! The joke’s on me this time, because there really is NO such problem. There are a few wrinkles, however, even though I now find my Kindle update problem solved. Let me explain…

How I Got My Kindle Update Problem Solved

As it turns out, Kindle will happily update itself for you. But you have to go about it the right way. And you must keep at it until you get to the latest version. This requires understanding how Kindle update works, which is something it took me some experimenting to learn. Let me share:

1. As you can see from the lead-in graphic for this story, Kindle includes an automatic update feature amidst its various options. That said: YOU MUST LAUNCH the Kindle for PC application before the update function will run. Duh!

2. Kindle does not automatically or necessarily update to the latest and greatest version. It seems to update incrementally from the current installed version to the next available version. That just happened on my X12 Hybrid Tablet, where it took me from version 1.34.63103 (Jan 2022) to 1.35.64251 (Apr 2022), even though version 1.36.65107 (May 2022) was also available.

3. If you find yourself trailing behind the latest and greatest version after an auto-update, open and close the Kindle for PC application again. This will repeat the auto-update process. In my case that got me caught up. My guess is that this could take multiple iterations for those running more seriously out-of-date Kindle for PC versions.

This sure beats my previous approach, which had me visiting the Amazon store to “buy” (it’s free) whatever version was current then, and then to install it over the older version on my target PC. This is a whole lot easier…

The Secret: Run the App!

All this said, the secret to keeping Kindle for PC updated is to run the app as part of your update check cycle. Because the default setting is to “Automatically install…” as it shows in the lead-in screencap, the software does the rest. Wish I’d known this sooner, but glad to know it now. Case closed!

Now, if only Nitro Pro worked the same way I’d be free of my last hold-out “must update manually” program. Sigh.

Note Added One Day Later

As the following screencap shows, the PowerShell winget command is “smart” enough to update Kindle without opening the app. Check this out!

Another great reason to use winget for updating Windows PCs: it will update Kindle without opening the app!
[Click image for full-size view.]

Facebooklinkedin
Facebooklinkedin

Finding New Windows 11 Shutdown Dialog Box

Here’s an interesting bit of administrivia. Upon reading at OnMSFT that MS had snazzed up its Dev Channel dialog box for Windows 11, I went looking for same. That proved a bit more challenging than I initially expected. But I eventually got past finding new Windows 11 Shutdown dialog box, and made it appear. It serves, in fact, as the lead-in graphic for this very story (see above).

It Was Tricky, Finding New Windows 11 Shutdown Dialog Box

The usual method is to employ the Alt+F4 keyboard shortcut. But on my Lenovo X12 hybrid tablet PC that did precisely nothing. Then I found a source with something like this tell-tale sentence:

On some laptops it may also be necessary to press the Function (Fn) Key as well.

That turned out to be just the trick I needed to get the keyboard shortcut to work. Indeed, it’s what allowed me to produce — and then screen capture — the lead-in image for this story.

What IS New in Dev Channel Shutdown Dialog Box?

It’s kind of hard to tell just from the screenshot what’s new. For comparison, here’s what the Windows 10 version looks like:

Notice it prominently features the Windows 10 logo at the top of the dialog box. Notice also its corners are squared, not rounded. AFAIK that’s about it for what’s new.

That said, in keeping with a sparer and more spacious UI in Windows 11, it’s a bit easier on the eyes. IMO it’s also a bit easier to read and understand. For me, the learning came from producing the dialog box more than its contents. But hey, that’s why I have so much fun messing around with Windows. Cheers!

 

Facebooklinkedin
Facebooklinkedin

Could Build 22621 Be RTM Version?

With some consistency and frequency, most of my go-to Windows news sources report the same thing. That is: the latest Beta Channel Build 2221, is likely to go out to OEMs as the “Release to Manufacturing” (RTM) version for Windows 11. This raises the question “Could Build 22621 be RTM version?” I’m inclined to believe it might be, so please let me explain why. . .

Repeat: Could Build 22621 Be RTM Version?

Here are my reasons for believing that indeed, 22621 could be an RTM candidate if not THE RTM candidate for Windows 11:

Timing: MS has promised a 22H2 Windows 11 release, which means sometime between July 1 and December 31, 2022. Given that the usual delay from RTM to public release varies from as little as 12 to as long as 20 weeks over the life of Windows 10, a similar range seems likely for 11 as well. Given 22621 came out on May 11, that would put general availability between July 27 and September 21. This makes good sense to me. OEMs need time to get their collective acts together, and to get ready to deploy new images for the next feature update on their (mostly) consumer grade equipment.

Insider Channel Divergence: As I reported here on May 12, 22621 represents the divergence of Beta and Dev Channel Insider versions. MS forked the Insider channels so it could concentrate on the next Feature update in the Beta Channel, while working on future features for a presumptive 23H2 release in the Dev Channel. Stands to reason they’d have forked when they were getting close enough to recognize a possible RTM in the Beta Channel.

22621 Announcement blog post: Combine the opening statement of “small set of fixes” with “preview experiences that are closer to what we will ship to our general customers” and you get something pretty much like a “closing in on RTM” impression from this post.

Winver Label: look it says right in the lead-in graphic “Version 22H2.” What more do you want by way of (potential) proof?

It’s Not a Sure Thing, But…

Indeed, MS will make changes to 22621 as and when user telemetry indicates a need for same. That goes double if bug reports start proliferating. But, absent such spurs to additional action and related changes, 22621 seems pretty close to what is probably already going into OEM intake processes. Stay tuned: I’ll keep you posted as things develop from here!

Facebooklinkedin
Facebooklinkedin

8GadgetPack Repair Fail Fixed

I had an “Oh no!” moment yesterday. After upgrading my Lenovo X12 tablet to Dev Channel Build 25115, I went through the usual post-upgrade drill. Because the installer always kills fave tool 8GadgetPack, developer Helmut Buhler has created a run-once repair tool that restores gadgets to working order afterward. It shows up as Restore Gadgets on the desktop, and must be double-clicked to run. For the first time ever, I experienced an 8GadgetPack repair fail yesterday. Ouch!

[NOTE] The Restore Gadgets script shows up in Recycle Bin in the lead-in graphic because it’s smart enough to delete itself once it runs.

What made it an “Oh no!” moment was that I feared it meant the demise of Gadgets from Dev Channel desktops once  and for all. Gadgets were obsoleted back in the Windows 7 days, ostensibly for security reasons (though I’ve never run  into, nor heard of, actual Gadget-related exploits). And for a time after the upgrade, all of my attempted repairs didn’t work.

How I Got 8GadgetPack Repair Fail Fixed

This only affected one of my two Dev Channel PCs, as it turns out. Once I realized the repair was bollixed on the X12, I tried it on the Lenovo X380 Yoga. Worked like a charm! That was comforting, because I knew it was something with the X12 itself, and not a general failure.

Here’s what I tried before coming up with the actual fix itself:

1. Re-ran the repair tool (no go).
2. Re-ran the repair tool with elevated privileges (didn’t do it)
3. Downloaded and ran the 8gadgetpack.msi file from 8gadgetpack.net (no luck there, either)

But when I tried #3, I got an error message that said to go to Control Panel → Programs and Features and attempt repairs from there. When the right-click menu for 8GadgetPack popped up, it included a “Repair” option. And when I ran the repair that way, it worked. Go figure!

Upon Closer Inspection…

In trying to figure out what happened, I opened up Reliability Monitor and looked at the day’s error and event reports. Sure enough, 8GadgetPack appeared in the form of a couple of Warning messages.

Something about running the repair tool from the desktop led to what ReliMon reports as an “unsuccessful application reconfiguration.” Apparently, the same problem does not apply to running it within a Control Panel item. Thus, I learned a new workaround and brought my beloved 8GadgetPack back from unnecessary oblivion. Other fans of ever-handy Windows Gadgets should be cheered thereby as well. Good stuff!

Facebooklinkedin
Facebooklinkedin

Windows 11 Dev Beta Channels Diverge

OK, what had been joined is now put asunder. Yesterday, Windows 11 Dev Channel went to Build 25115, and Beta Channel to Build 22621. This means that the two Insider Previews are now different. In fact, when Windows 11 Dev Beta channels diverge, it means they have different goals. According to WindowsLatest, 22621 represents a big push toward the first feature update for Windows 11. OTOH, 25115 shows that MS is still pushing forward into future releases looking into 2023 and the “next” feature update upcoming.

When Windows 11 Dev Beta Channels Diverge, Then What?

Among other things, this explains why MS broadcast an email warning to Dev Channel Insiders last week that “unstable and buggy preview builds will soon begin rolling out in the Dev Channel” (source: WindowsLatest,  May 8). In other words, the Dev Channel is returning to its primary role as a “first exposure” to new features, functions, and whatnot making its way into limited circulation for testing and feedback. Frankly, I’m looking forward to this.

As for the Beta Channel, it’s gearing up for progressively more locked down snapshots of what will become the 22H2 release for Windows 11. Thus, it should become an increasingly accurate rendition of the next production Windows 11 release. Again: I look forward to this, too.

You can see the Winver output from these two different versions in the lead-in graphic for this story. The Dev Channel release (Build 25115.1000) is to the left.The Beta Channel release (Build 22621.1) is to the right.

Fun and Foibles A’Comin…

With a more freehwheeling and experimental take on Windows 11 coming to the Dev Channel, life is about to get more interesting. Who knows? There may be bugs or hiccups to detect and report, and trouble to shoot. That’s why I signed up for the Insider program, and why I’m looking forward to more new stuff ahead. Sure, there may be instability and bugs. But that’s a good thing in the interests of getting things out there, and then getting them right. Cheers!

Facebooklinkedin
Facebooklinkedin

Author, Editor, Expert Witness