Category Archives: Windows OS Musings

Mild Microsoft Update Health Tools Mystery

An interesting item is bubbling up in user forums  lately. Lots of Windows 10 PCs — including some of mine — have seen a new-ish, intriguingly named application show up. This story’s lead-in graphic shows it in second place. In fact, I’d say we’re facing a mild Microsoft Update Health Tools mystery. Typical questions include “What is it for?” and “When is it used?”

Cracking a Mild Microsoft Update Health Tools Mystery

A Microsoft Docs “Questions” item links the utility with update KB4023057 .  A corresponding support page mentions all Windows 10 versions, including 20H2. (It’s dated October 2020.) I’ve seen posts at answers.microsoft.com as far back as August 2020. It, too, references that same KB article.

That article says the update delivers “reliability improvements to Windows Update Service components.” It also says it:

includes files and resources that address issues that affect update processes in Windows 10 that may prevent important Windows updates from being installed. These improvements help make sure that updates are installed seamlessly on your device, and they help improve the reliability and security of devices that are running Windows 10.

Some Interesting Notes about KB4023057

There are 5 bulleted items (and a sub-note) the Support Note. All make fascinating reading. I reproduce them verbatim. (For brevity, I prune “This update may” or “This update will” ):

  • …  request your device to stay awake longer to enable installation of updates.

    Note The installation will respect any user-configured sleep configurations and also your “active hours” when you use your device the most.

  • … try to reset network settings if problems are detected, and it will clean up registry keys that may be preventing updates from being installed successfully.
  • … repair disabled or corrupted Windows operating system components that determine the applicability of updates to your version of Windows 10.
  • … compress files in your user profile directory to help free up enough disk space to install important updates.
  • … reset the Windows Update database to repair the problems that could prevent updates from installing successfully. Therefore, you may see that your Windows Update history was cleared.

Invitation to Conspiracy Thinking?

Go back, and read the forum traffic. Or, search Google for “Microsoft Update Health Utility.” Sadly, it reveals suspicion among community members. Indeed, some fear it helps MS forcibly update older Windows installs. In fact, MS does this already. Others don’t trust MS update orchestration. They’d rather control updates themselves. Still others worry about unwanted side effects or unusable PCs after forced updates.

Gosh! While these things are possible, I see nothing untoward at work here . Instead, I see MS staging repair tools in advance for update issues on Windows 10 PCs should they manifest. Aside from lacking user controls, I see them no differently than built-in update troubleshooters. In fact, I’m a devoted user of Shawn Brink’s Reset Windows Update tutorial and its accompanying batch file. It’s gotten me past 95% of all WU problems I’ve seen. That’s why I’ll gladly keep using it.

No Cause for Alarm

As far as I can tell, there’s not much to see here. Admittedly, Update Health Tools is a small surprise. But its Support Note offers good explanations. Thus, I’m OK with this tool. Nor should you worry, either. Rather, it looks like good software engineering.

Better yet, the Update Health Tools can handle update issues on their own, sans user input or guidance. That sounds like a blessing, even if in disguise. And FWIW, it’s missing  from Insider Preview releases. That tells me it aims squarely at production PCs outside IT umbrellas. That means mostly home and small business users. Thus, it should benefit those who need it most.

I’m coming out in favor of the Update Health Tools. I hope we’ll learn more about them from Microsoft soon. In the meantime, if you don’t like the tool, you can choose to uninstall it. I’m leaving it alone myself. If I’m right about it, it may come in handy someday.

Facebooklinkedin
Facebooklinkedin

Windows 10 LTSC Lifetime Gets Halved

OK, then. It must be something in the air. I blogged here about the Long Term Servicing Channel (LTSC) version of Windows 10 about two weeks ago. And today, I just saw — courtesy of the always vigilant Mary Jo Foley (MJF) at ZDNet — that MS is cutting LTSC support life from 10 to 5 years. This starts with the next release as explained in a Windows IT Pro blog post. (See below for a key snippet.) Fore sure, the big takeway is that Windows 10 LTSC lifetime gets halved, as of 21H2.

Why Windows 10 LTSC Lifetime Gets Halved?

The best answers for inevitable follow-on questions appear in a quote from the aforementioned blog post. Here ’tis:

Today we are announcing that the next version of Windows 10 Enterprise LTSC and Windows 10 IoT Enterprise LTSC will be released in the second half (H2) of calendar year 2021. Windows 10 Client LTSC will change to a 5-year lifecycle, aligning with the changes to the next perpetual version of Office. This change addresses the needs of the same regulated and restricted scenarios and devices. Note that Windows 10 IoT Enterprise LTSC is maintaining the 10-year support lifecycle; this change is only being announced for Office LTSC and Windows 10 Enterprise LTSC. You can read more about the Windows 10 IoT Enterprise LTSC announcement on the Windows IoT blog.

Two important take-aways:

1. Happily, this change synchronizes Windows 10 Enterprise LTSC and Office LTSC release timing.

2. Even better, Windows 10 IoT Enterprise LTSC is NOT affected. It stays on a 10-year schedule.

Apparently MS understands full well that, once deployed, IoT devices are best left alone as long as possible. Happily, Windows 10 Enterprise LTSC and Office LTSC are synching up, because they’re likely used in tandem. Thus, both benefit from the same release cycle. In most cases, five years is in keeping with typical technology refresh cycles (which usually run 5-7 years).

Plus çe change…

The complete French aphorism translates “The more things change, the more they stay the same.” Indeed, it seems that MS isn’t afraid to tweak long-term servicing options, to better meet customer needs. My guess: making customers upgrade LTSC Office without upgrading the OS  simultaneously could be less than helpful. Therefore, it makes sense that MS would synch things up where the two are likely used together.

On another front, MJF and I both see a bit of ‘suasion possibly at work in this change. Here’s what she says on this in her story:

Microsoft execs have tried to dissuade customers from using LTSC versions of Windows 10 as a way to avoid regular feature updates. (More than a few customers do this.) They’ve emphasized that the intent of LTSC releases is to support mission-critical systems that can’t or shouldn’t get regular updates.

In today’s blog post, officials said they also found that many customers who installed LTSC versions for their information worker desktops “found that they do not require the full 10-year lifecycle.”

Given that the typical refresh cycle is less than 10 years, I’d have so say “No kidding!” to her final observation. I concur!

Facebooklinkedin
Facebooklinkedin

21H1 Hits Beta Preview Channel

The lead-in graphic for this story shows some big news. That is, the Feature update to Windows 10, Version 21H1 is now available. This applies to Windows Insiders in the Beta Insider Preview channel, I hasten to add. And indeed, the foregoing item showed up on my Beta Channel test machine this morning. Hence the proclamation that 21H1 hits Beta Preview channel.

When 21H1 Hits Beta Preview Channel, Then What?

There are two kinds of implications for this occurrence. One is technical, and the other is a matter of historical analysis and implication. On the technical front, this means that the upcoming 21H1 is more or less locked down. That is, what we see in this preview release is also pretty much everything we’ll see in any upcoming public release. On the historical front, public releases typically have followed previews somewhere from 4 to 6 weeks after the preview appears. That puts initial public release of 21H1 somewhere between March 18 and April 1, by my reckoning.

Upon reflection, I kind of like an April 1 date (April Fool’s Day).

The Beta Channel Upgrade Experience

The screencap you see at the head of this story is the one that appeared on my Beta Channel test PC. For up-to-date Beta Channel PCs, this update is undoubtedly an enablement package that simply turns on features already present in the Insider Preview OS.

Why say “enablement package?” I say that because it completed the pre-reboot portion of the install in under two minutes on a Surface Pro 3 (vintage 2014) machine. The “Working on Updates” portion was pretty speedy, too (less than a minute). And the post-reboot drill took about 30 seconds (just a hair slower than a normal rebooot, in other words).  You won’t have to spend much time twiddling your thumbs while waiting for this “feature upgrade” to install!

I’m jazzed to understand that 21H1 is in the offing, and should be making its way into public release somewhat sooner than I’d expected. My congrats and thanks to the #WindowsInsiders team in general. Take a read of Brandon Leblanc’s Announcement post for more Insider info.

Facebooklinkedin
Facebooklinkedin

Windows Release Health Gets MS Makeover

Thanks to the always-vigilant Mary Jo Foley, I learned yesterday that a key Windows dashboard has a new look. When I say Windows Release Health gets MS makeover, I mean the web page that reports on Windows 10 issues and conditions is snazzed up. It not only covers releases back to 1607. It also provides pointers galore. You’ll find links to information about releases, updates, OS deployment and the Windows lifecycle. You can see  this in the lead-in graphic for this story, in fact.

So What If Windows Release Health Gets MS Makeover?

MJF tweeted that this “new and improved” layout “looks nice” and brings “lots of Win 10 resources in one place.” I concur. This reworked page makes it easy to keep up with all mainained releases  from one dashboard. This one’s definitely worth bookmarking, and visiting regularly.

Here’s a summary of what’s in the page header shown in the graphic. I also list releases for which known issues, release notes, “What’s New” info, and so forth, are available:

Versions of Windows on this page include 20H2, 2004, 1909, 1809, 1803 and 1607.  That final item comes courtesy of LTSC, which uses this version as a still-current base.

MS did a nice job on this effort. Hats off for consolidating lots of useful info, and making it easy to find. Once again: bookmark this one!

Facebooklinkedin
Facebooklinkedin

Likely Windows 10 LTSC Usage Scenarios

In yesterday’s post, I explained the role of the Semi-Annual Channel (SAC). Indeed, it’s the most apt Windows 10 release for everyday use in most cases. In that discussion, the Long-Term Servicing Channel, aka, LTSC also came in for mention. I’ve just participated in an interesting TenForums thread on this topic. It raises the question of how to get an ISO for this channel, for which I helped find an answer. It also raised a broader question: LTSC, What is it, and when should it be used? This leads in turn to likely Windows 10 LTSC usage scenarios.

What Are Likely Windows 10 LTSC Usage Scenarios?

The preceding link is a 2018 Windows IT Pro Blog post from John Wilcox, He’s a “Windows-as-a-Service” evangelist at Microsoft. In that post he explains (and illustrates) one major LTSC use class:

devices purchased with Windows 10 IoT Enterprise pre-installed. Examples … include kiosks, medical equipment, and digital signs, i.e. use cases where devices are commonly treated as a whole system and are, therefore, “upgraded” by building and validating a new system, turning off the old device, and replacing it with a new, certified device.

He also goes on to explain for such systems that Microsoft

 designed the LTSC with these types of use cases in mind, offering the promise that we will support each LTSC release for 10 years–and that features, and functionality will not change over the course of that 10-year lifecycle.

Understanding the LTSC Release Cadence

MS deliberately slow-walks LTSC releases to the delivery stage. Wilcox explains that a new release is created on a three-year cycle. In fact, “each release contains all the new capabilities and support included in the Windows 10 features updates … released since the previous LTSC…” Thus, LTSC releases use a year to identify themselves. Recent examples include Windows 10 Enterprise LTSC 2016 and 2019.

Changing Times vs. No Change

Wilcox is pretty adamant that only those scenarios where no change is anticipated over a system’s useful life are truly suitable for LTSC. That means: no new peripherals, no new applications, no new devices and capabilities. Anything different is a strong argument to use the SAC instead. Embedded or dedicated systems often qualify, but little else fits that bill. End of story.

[Note Added February 10:] 2022 LTSC Preview

Good timing. Just saw a notice at TenForums that a new Preview Build 20292 for LTSC 2022 is out: get all the details at the Announcing item. Glad to see MS is still at work on what’s next for LTSC. Be sure to check it out, if this is in your wheelhouse.

 

 

 

Facebooklinkedin
Facebooklinkedin

Pondering Microsoft Viva Introduction

OK, I admit it. I’ve been biting my lip since last week, when MS briefed MVPs about this upcoming milestone. Now that they’ve made an official announcement, I can share my thoughts and reactions. (That’s also where the nifty graphic comes from.  I doubled it up for a better WordPress look.) All this goes to explain why today I’m pondering Microsoft Viva introduction. Potentially,  it means much for modern digital workers everywhere — including me (and you too, dear reader).

When Pondering Microsoft Viva Introduction, Don’t Get Carried Away

Q1: What is Microsoft Viva?
A1: It’s an “Employee Experience Platform,” aka EXP “built for the digital era.” It is designed to bring together “knowledge, learning, resources, and insights into an integrated employee experience…
Further, it “… builds on Microsoft Teams to empower people to be their best, from anywhere.” See the Official Announcement Blog.

Q2: Name the four faces of the Viva EXP?
A2:  They’re repeated in the next graphic. You’ve got Viva Insights, Viva Topics, Viva Learning, and Viva Connections.

Pondering Microsoft Viva Introduction and its four major components.
Pondering Microsoft Viva Introduction and its four major components, we see Insights, Topics, Learning, and Connections.

Of Insights, Topics, Learning and Connections

The emerging scoop on these Teams-based facilities goes  like this:

  • Viva Connections allows an organization’s leaders to shape in-house cultures and mindsets. It also invites employees to help build “an inclusive workplace.” Further, it “helps everyone succeed by giving people a curated, company-branded experience that brings together relevant news, conversations, and other resources.” More at Viva Connections Blog.
  • Viva Insights wants to help people form better work habits, achieve improved work/life balance, and find focus. Using AI (I’m guessing of both global and local varieties) this tool offers  insights to individuals, managers and leaders. They’re described as “personalized and actionable insights that help everyone in an organization thrive.” Mo’ info at Viva Insights Blog.
  • Viva Learning creates a centralized learning hub within Microsoft Teams. There, people can “discover, share, assign and learn from content libraries available across the organization.” “[M]ake learning a natural part of your day” is the goal. MS says it “seamlessly connects into the day to day for our 115 million daily active users in Teams.” Futher deets from Viva Learning Blog.
  • Viva Topics uses AI to provide its users “with knowledge and expertise in Microsoft Teams and the Microsoft 365 apps they use every day.” Based on Teams and Graph, it seeks to “deliver knowledge directly through the Teams users experience later this year.” At present it “has [already] reached general availability for our commercial customers.” Oh, and here’s the link to the Viva Topics Announcement (no blog just yet, I guess). This is the area that, as a Windows Insider MVP, interests me most.

Big Trouble in Little China

…is a delightfully awful 1986 throwaway movie starring Kurt Russell and Kim Cattrall. It also humorously restates my mild concern, understanding now how much MS knows about us through Teams. And then, how much more we’re all going to know about ourselves and each other through that same nexus.

This could might be the best thing that’s ever happened to productivity workers. Or, it might be the first sign that SkyNet is getting itself together to subjugate wee, slow, puny humans. Should be fun to see which way this particular mop flops, eh?

Stay tuned! We’ve all got a lot to ponder as the next step in the man/machine interface takes another small step into the future. Personally, I’m jazzed…

Facebooklinkedin
Facebooklinkedin

Remembering Santayana’s Dictum Win10-Wise

I learned this one as “Those who fail to learn from history are doomed to repeat it.” Turns out that upon checking Santayana’s aphorism, it’s actually “Those who don’t know history are destined to repeat it.”  But when it comes to remembering Santayana’s dictum Win10-wise, I was forced to re-learn an important lesson today. Let me explain…

What Remembering Santayana’s Dictum Win10-Wise Means

A funny thing happened to me today: I installed KB4598291 but it didn’t show up in Update History nor in its Control Panel counterpart under Programs and Feaures. Why was this? Because I’d wandered off the update track to force my test PC ahead to 19043.XXX builds using a series of linked DISM statements. Sigh.

Today, I learned why that’s a BAD IDEA. When I realized that something was amiss, I learned that things were further out of whack than I’d dreamed possible. The hack meant that I could no longer use the tried-and-true “in-place upgrade repair install” technique to return my test PC to some semblance of normality.

That Key Doesn’t Work. Try Another…

I used UUPdump.ml to build a customized install ISO for 19042.789. But when I tried to run same on my “unofficial” 19043.782 machine, the installer asked for a Windows 10 key before it would proceed. None of the following worked:

  1. The generic Windows 10 Pro key
  2. The actual key for the current install, as elicited by Showkey Plus
  3. A still active MAK key for Windows 10 Pro I purchased from Crayon, Inc. in 2018

Ouch! I was in trouble. Fortunately, i was able to restore a backup from a time when this test PC was still on the regular Beta/Release Preview build track. Once I’d done that, I was able to catch up and bring the PC up to build 19042.789, as shown in the lead-in graphic for this story.

The Moral of the Story

I’d been warned by friends and colleagues that wandering off the usual Insider Preview track is OK for experiments, but not for ongoing use. Now I know why: once you hit the next Cumulative Update (as I did today) the off-track releases will get weird in a hurry. My advice: learn from my mistake, and don’t go there, unless it’s on a throwaway VM. I now understand that’s how I should have played that, too. Live and learn!

 

Facebooklinkedin
Facebooklinkedin

My Insider Preview Working Routine Revealed

On January 18, I reported here that the Insider Team at MS renewed my Windows Insider MVP (WIMVP) status for 2021. Since that renewal came through, I’ve been keeping an eye on my daily activities and taking notes. Now, I’m prepared to share a mini-expose. It’s what I call “My Insider Preview working routine revealed,” as in the title for this story. I’ll explain what it means, what I do, and how much time it takes to stay involved in the program.  Here goes…

Digging In: Insider Preview Working Routine Revealed

There are 5 major activities involved in the Insider Preview working routine, as far as I can tell. I’ll enumerate them first, then provide some details and ruminations.

  1. Dealing with Insider Preview releases
  2. Reporting on installation and use experiences
  3. Researching news and reports related to Insider Preview Releases
  4. Participating in the WIMVP community
  5. Raising awareness for Windows 10 plus related tools and utilities

1. Dealing with Insider Preview releases

I watch all the release channels — namely Dev, Beta, and Insider Preview, with at least 2 test machines devoted to each channel. Every time a new release comes out, I go through a specific drill, as follows:

  • Download and install the release
  • Observe any issues, hiccups or out-of-baseline behaviors during the install and initial trip to the desktop
  • Perform post-install clean-up, which consists of deleting Windows.old, running file cleanup, and making a fresh backup of the new version in Macrium reflect
  • Report on experience and findings at TenForums.com in the News forum and, if necessary, in the Installation and Upgrade forum
  • Check Event logs and Reliability Monitor for out-of-the-ordinary stuff
  • Report anything interesting or noteworthy to Feedback hub

As occasional updates to IP releases emerge, I repeat the steps above except for post-install clean-up, though I may run DISM /online /cleanup-image /analyzecomponentstore to see if any install packages need cleaning up in the wake of the new update. Sometimes they do, and sometimes they don’t.

I do about 6 of these a week on average, where each one takes anywhere from 15 minutes to an hour if everything works as it should. Sometimes, troubleshooting can take an hour or more, as when troubleshooting installation failures. Right now, for example, I’m dealing with a Bug Check 0xA IRQL_NOT_LESS_OR_EQUAL stop error on Build 21301 on one of my test machines.  I may not get this resolved until after dinner tonight because I have three deadlines to meet today (this article, a story for ComputerWorld, and a blog post for ActualTechMedia).

2. Reporting on installation and use experiences

Once I get the IP release installed and cleaned up, I start using it from time to time. As I observe its behavior and try out commands, programs, apps and utilities, I report any issues I encounter to Feedback hub. This depends a lot on my overall workload and may involve only 10 minutes on some days, and an hour or two on others. Varies a lot.

3. Researching news and reports related to Insider Preview Releases

I read the Windows 10 coverage on at least a half-dozen sites daily to keep up with current events, reported bugs and issues, emerging features and rumors of same. I also keep a partial eye on Microsoft business and tech news, as well as PC software and hardware industry news. This takes me at least an hour a day; longer if I get interested in something and start tracking stuff down. My daily visits include WinAero.com, Windows Latest, MSPowerUser, NeoWin, OnMSFT, Ghacks, ZDNet, Windows Central, and TenForums.com (where I try to read all new threads every day).

4. Participating in the WIMVP community

I belong to the WIMVP Yammer group, and scan its posts daily. We have weekly meetings to discuss Windows 10 topics which I sometimes attend (but not always). When we have online meetings — as we will later this morning — I try to attend those pretty regularly. I make a point of attending our conferences, and used to enjoy the physical ones. Now, like everybody else, I get what I can from their online/virtual counterparts, and look forward to when traveling for a real meet-up is once again possible. This takes me an hour or two a week on average, with 2-3 full days for conferences.

5. Raising awareness for Windows 10 plus related tools and utilities

I’m always on the lookout for good Microsoft-built or third-party tools, utilities, scripts, and whatnot. As I find them, I write about them in my daily reporting, and try to get articles placed to write about them in more detail and depth. You can get an inkling of what I do from my end-of-last-year story here Top 3 2020 Utilities. This is about the most fun I get to have in this role, but seldom takes more than an hour or two a week, sometimes less.

I also give an annual Windows 10 presentation at the Spiceworks SpiceWorld conference, and try to pick up other speaking and presenting gigs as they make themselves available. If you want me to talk about Windows 10 stuff at your conference and I don’t have a conflict, I’d be happy to oblige. Contact me through Ed Tittel Contact Info, where you’ll find an email form that goes straight into my inbox.

Facebooklinkedin
Facebooklinkedin

Pondering Windows Experience Pack Updates

I’m still at the point where it’s all sinking in. Thus, I read with interest at WindowsLatest this morning that “Microsoft is testing another new Windows 10 Experience Pack update.” I went to check update history on one of my Release Preview machines (the Surface Pro 3). And sure enough, I see a corresponding update to match the Experience Pack version info from Settings → System → About shown in the lead-in graphic. That’s got me pondering Windows Experience Pack updates in general, and hoping we’ll see them put to work for something more … err … substantial that screencap tweaks in the near future.

Pondering Windows Experience Pack Updates.update-history

While Pondering Windows Experience Pack Updates, I Hope for More Action

Once I learned that KB4601906 was in the picture for this change, I jumped first to the Microsoft Catalog to see if it was there. No such luck. Likewise, as is often the case, a search on KB4601906 through Google turns up lots of third-party hits, but nothing from MS itself. Clicking on the link in update history, however, is another story. That gets me to an MS Support item named January 12, 2021—KB4598242 (OS Builds 19041.746 and 19042.746). That takes me to a blurb on the wrong Knowledge Base article. A direct search for “KB4601906” at MS Support turns up … nada.

Of course, I learned what I could from WindowsLatest and other similar items from TenForums and other places. @Brink reproduces the Windows Insider blog item that finally sheds a little light on the subject. In that item, Brandon LeBlanc says

We are improving the reliability of screen snipping experience, especially with apps that access the clipboard often.

More importantly, near the end of his post, he goes on to say

…we are testing this new process out with Insiders to deliver new feature improvements to customers outside of major Windows 10 feature updates. Right now, we are starting out with a really scoped set of features and improvements. Over time, we hope to expand the scope and the frequency of releases in the future.

No News Is … No News

I get it now, and think I already understood this. MS is working with the Windows Experience Pack as a way to deliver new feature improvements without resorting to a semi-annual feature upgrade. They’re still testing and haven’t done anything serious or significant with this yet. But they will, someday. Soon, I hope. Stay tuned!

 

Facebooklinkedin
Facebooklinkedin

Build 19043 Becomes Likely 21H1 Candidate

The rumors started flying yesterday, first at WindowsLatest. But I couldn’t find evidence through the data they provided to back that up in the Windows registry. Then, this morning Sergey Tkachenko at WinAero.com came out with some more tangible proof in the form of registry key/value names to demonstrate that 21H1 action is afoot. I’m now inclined to agree that Build 19043 becomes likely 21H1 candidate for a Spring release.

Strong Hints Mean Build 19043 Becomes Likely 21H1 Candidate

In his story, Tkachenko proposes a string value  of Microsoft-UpdateTargeting-ClientOS vb_release_svc_prod3 10.0.19043.782 for an ultimate value of the Microsoft-Windows-21h1Enablement key. Just for grins, I searched on that value, and found nothing like it in either of my Release Preview (Build 19042.782) test machines.

Careful reading of his post leads me to  this analysis. Because 19041 became 20H1 and 19042 20H2, he’s guessing that 19043  matches up to 21H1. But so far, I’ve seen no hard evidence to support this assumption. That said, I do believe he may be right. I’ve seen nothing whatsoever to contradict equating 19043 with 21H2, either. And indeed, it is shared by many other Windows followers online.

How Much Longer Before We Know?

If you believe poster “moinmoin” at WindowsModder.de, an enablement package could appear as soon a next Patch Tuesday (February 9).  And if not then, he says, surely on or before the following Patch Tuesday (March 9).

It all depends on how this latest Release Preview update goes within the Insider Preview population that downloads and uses KB4598242. This test of the enablement package’s stability and usability, based on telemetry from its installers, could have a major impact on when 21H1 sees the light of day. If things go well, and no major issues or errors manifest, then sooner. If contrariwise, then later. We’ll see!

[NOTE}: To get the complete details on the Registry information from the lead-in photo from this story, right-click that image and select “View Image” (Firefox). Or, use your browser’s syntax to view the image by itself. Then you can read the values on-screen. HTH.

OK, Then: It’s Settled (January 24, 2021)

Thanks to a sequence of DISM commands that German-speaking Windows wizard “moinmoin” has shared at DeskModder.de, we now know how to “upgrade” PCs running Insider Beta or Release Preview channel build 19042.782 (or higher, presumably). I share all those details in a new article here entitled 19043 aka 20H1 Early Try-out How-to. I’d have to say this locks in the 19043/20H1 nomenclature conclusively, unless MS introduces a seismic shift in naming conventions between now and when 21H1 goes public.

Facebooklinkedin
Facebooklinkedin