Tag Archives: featured

MS Makes LTSC Sole Windows Server Release Channel

July 29, 2021 Ed Tittel Leave a comment

When you think about it, here’s a sensible move. Windows Server is the kind of platform that organizations want to stand up, get right, and leave alone. There’s little need for personalization, and it doesn’t need desktop tweaks. In fact, Server is really a background thing. It holds up the “you ask, I answer” side of client/server. architecture. Then, too, MS put containers and microservices under the Azure umbrella. That’s why, I think, that MS makes LTSC sole Windows Server Release channel.

Why MS Makes LTSC Sole Windows Server Release Channel

A July 26 Microsoft Docs item spells things out. It’s entitled Windows Server release information. This quote explains things (emphasis mine):

The Semi-Annual Channel in previous versions of Windows Server focused on containers and microservices, and that innovation will continue with Azure Stack HCI. With the Long-Term Servicing Channel, a new major version of Windows Server is released every 2-3 years. Users are entitled to 5 years of mainstream support and 5 years of extended support. This channel provides systems with a long servicing option and functional stability, and can be installed with Server Core or Server with Desktop Experience installation options. The Long-Term Servicing Channel will continue to receive security and non-security updates, but it will not receive the new features and functionality.

Organizations can migrate if and when compelling new features emerge. It’s arguable this change makes a virtue of necessity. Why say that? Most organizations upgrade servers no more often than once every 2-3 years (or longer) anyway.

On balance, I think this is a good move. For developers, it means building, testing and maintaining fewer releases . That is good news for everybody. Developers can build more cool new stuff. Admins face less busy work. This means shorter, simpler scheduled updates. And because updates often happen over long weekends, it means more holiday time with family and friends. That’s a real win-win!

Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 10

21H2 Preview Experiences After Two Weeks

July 28, 2021 Ed Tittel Leave a comment

I’ve got one lone test machine running the “other path” for older Windows hardware — namely the 21H2 Feature Update released on 7/16/2021. Here, I recite my 21H2 Preview Experiences after two weeks. While I’ve not encountered any show-stoppers, the Reliability Monitor report that appears above says it all. As is not untypical for new release forks, this one’s got some minor gotchas.

Summarizing 21H2 Preview Experiences After Two Weeks

I’ll start with a list of all errors reported in the foregoing Reliability Monitor screencap.

Date	Source	Summary
16-Jul	Windows	Hardware error
17-Jul	Windows Update Medic Service	Stopped working
	Search application	Stopped working and was closed
	Search application	Stopped working
18-Jul	Windows Desktop Gadgets	Stopped working
21-Jul	PWA Identity Proxy Host	Stopped responding and was closed
	Windows Desktop Gadgets	Stopped working

Upon examination, the error sources mostly originate from Windows itself. Only Windows Desktop Gadgets (which occurs twice) is a third-party app. The rest of the stuff is OS components, hardware, or built-in Windows apps.

IMHO, this kind of behavior is typical for a new release fork. It indicates a shakeout from current preview status on the way to something more stable. It’s only July and the release probably won’t happen until October, so there’s still plenty of time to get things right. If what I’m seeing right now is any indication, what needs fixing is mostly minor stuff.

I would say this augurs well for those who plan to upgrade to 21H2 on production PCs. If your PCs won’t meet Windows 11 upgrade requirements, they should be able to run Windows 10 until EOL in October 2025 without too much fuss or bother. Good stuff!

Insider stuff, Recent Activity, Troubleshooting, Updates, WED Blog, Windows 11

Vexing Windows 11 Antimalware Platform Update Issues

July 27, 2021 Ed Tittel Leave a comment

Right now, I have two PC dedicated to Windows 11 testing and learning. Just recently, I discovered some vexing Windows 11 Antimalware platform update issues. The short version is: one of my PCs is up-to-date. It’s no longer subject to Automatic Sample Submission reset to off following each restart. Alas, the other remains stubbornly stuck on an earlier Antimalware platform release. None of the update options available work, so I can’t get no relief. Let me explain…

Fighting Vexing Windows 11 Antimalware Platform Update Issues

First, let me be clear. This is a known and documented Windows 11 issue. It’s been around since the initial release hit. Indeed, a fix exists: when the Antimalware Platform version gets to 4.18.2107.4 or higher, the problem disappears. For the record that problem is depicted in this story’s lead-in graphic. After every reboot, the Automatic Sample Submission feature for virus uploads in Defender is turned off. The feature is easy to turn back on, until the next reboot. OCD OS maintainer that I am, the workaround isn’t enough for me. I want it fixed, for good, now.

Here’s the vexing part. WU hasn’t yet deigned to update the antimalware engine behind the scenes. Ditto for the Protection updates option in Windows Security. There’s a registry hack documented on a related ElevenForum thread. There’s even a manual Defender update download that’s supposed to take the Antimalware engine release to 1.2.2107.02. It comes in a file named defender-update-kit-x64.zip. Alas, inspection of said update file shows the Antimalware engine to be 4.18.2015.5. It’s too old to fix the issue, in other words. Thus, no relief just yet, shy of a permanent registry hack.

The Perils of Perfectionism

Yes, I could hack the registry to turn this off. But I’d have to unhack it again when the fix finally shows up on the X380 Yoga that’s affected. I’m going to have to wait for WU to get around to providing me the latest antimalware engine on its own, or find a newer manual update. Alas, that’s the way things go sometimes, here in Windows-World. Oddly, I find myself hoping for a new Windows 11 build, in hopes the latest antimalware engine will be part of its contents. Stay tuned: I’ll let you know how all this shakes out.

Note Added August 4: Update Came!

Thanks to long-time and active TenForums and ElevenForum user @Cliff S, I learned this morning that Antimalware Client Version 4.18.2107.4 arrived via WU. Checking my own previously stuck test machine, I saw it too, had gotten this update. And now, my PC no longer reverts to Automatic Sample Submission=Off after each reboot. Fixed!

I’ve also determined this version is available through the Microsoft Update Catalog. Search for KB4052623, and grab the correct version, if WU doesn’t come through for you.

Letters from the Ed, Recent Activity, WED Blog, Windows 10, Windows 11, Windows OS Musings

Next LTSC Is 21H2 Based: Windows 11 Follows Later

July 23, 2021 Ed Tittel Leave a comment

In a July 15 Windows Experience Blog post, MS VP John Cable writes that in “the second half of 2021” the next version of the Windows LTSC will hit. Here’s a quote: “…we will also launch the next version of the Windows 10 Long-Term Servicing Channel (LTSC) based on version 21H2 at the same time.” A recent “Ask Me Anything” (AMA) session said a “next LTSC” after that would use Windows 11. Hence my assertion: the next LTSC is 21H2 based, Windows 11 follows later.

Next LTSC is 21H2 based Windows 11 Follows Later. How long?

Good question. Take a look at a list of LTSC Windows 10 releases. I include my guess for the upcoming one:

1. Windows 10 Enterprise LTSC 2015 1507   07/29/2015
2. Windows 10 Enterprise LTSC 2016 1607   08/02/2016
3. Windows 10 Enterprise LTSC 2019 1809   11/13/2018
4. Windows 10 Enterprise LTSC 2021 21H1   11/??/2021

The gaps vary. It starts with just over a year (1 → 2). The next is over 2 years (2 → 3). That latest goes up to around 3 years (3 → 4). Recent history argues it will likely hit in two or three years. A lot depends on features that Windows 11 offers and Windows 10 does not. Equally important: how much they matter for deployments likely to use the long-lived LTSC code base.

Why Use a Windows LTSC Release?

In its LTSC explainer in Microsoft Docs, MS works hard to distinguish LTSC from other release channels and to identify typical usage scenarios (italic text is quoted verbatim):

Important

The Long-Term Servicing Channel is not intended for deployment on most or all the PCs in an organization. The LTSC edition of Windows 10 provides customers with access to a deployment option for their special-purpose devices and environments. These devices typically perform a single important task and don’t need feature updates as frequently as other devices in the organization. These devices are also typically not heavily dependent on support from external apps and tools. Since the feature set for LTSC does not change for the lifetime of the release, over time there might be some external tools that do not continue to provide legacy support. See LTSC: What is it, and when it should be used.

The latter document calls out a “key requirement … that functionality and features don’t change over time.” These include medical systems like those used in MRI and CAT scan devices, industrial process controllers, and air traffic control systems. All such systems are costly, complex, and relatively isolated from public networks.

My gut feel is a long wait doesn’t matter that much for LTSC deployments. Because they’re so specialized and focused. engineers will build around whatever’s available when they put LTSC to work. When it gets used, the Windows OS isn’t really important: the function and capabilities of the overall system in which LTSC is embedded is what really matters.

Insider stuff, Recent Activity, Updates, WED Blog, Windows 11

Beta Channel Update Has Uncertain Timing

July 22, 2021 Ed Tittel Leave a comment

I always have troubles with patience. That goes double when I know a PC will run Windows 11, but hasn’t gotten the upgrade offer just yet. I’m talking about my second Lenovo ThinkPad X380 Yoga unit. It had been on the Release Preview Channel. But two days ago, I bumped it up to the Beta Channel in hopes of getting the Windows 11 upgrade. Because this Beta Channel update has uncertain timing, I’m not sure when this PC will get the offer. Here’s the irony: I have a second, nearly identical X380 unit (they differ only in the SSD installed) that’s been running Windows 11 since Day 1 on the Dev Channel.

Does Trickle-out Mean Beta Channel Update Has Uncertain Timing?

As you can see in this story’s lead graphic, Beta Channel PCs should be getting “these Windows 11 builds…” So far, this particular X380 Yoga is hanging back on Windows 10, Build 19043.1149. I’m eager to get the machine onto the new OS, but I want to see how long this is going to take to happen.

My track record on such things is far from stellar. I’ve forcibly upgraded many machines to new Windows 10 versions when upgrade offers were slow to appear. That raises the question: Can I wait long enough for WU to do its thing? Or will I succumb to the fatal allure of instant upgrade and do it manually?

I do want to understand how things will work in the Beta Channel. But I’m having trouble waiting on the system to catch up with me. Let me try another reboot and see if that will help … goes off to make that happen … Nothing doing.

Stay tuned. I’ll be back (soon, I hope) to tell you that WU has come through, or to confess that my patience wore out and I used an ISO to perform an in-place upgrade to Windows 11. One way or the other, I’ll get there, I promise!

Insider stuff, Recent Activity, Tips, Tricks and Tweaks, WED Blog, Windows 11

Confusing Windows 11 Scissors and Trashcan

July 21, 2021 Ed Tittel Leave a comment

Sometimes, I have to laugh at myself. Yesterday, in cleaning out my Downloads folder on a Windows 11 test PC, I noticed that clicking the Scissors icon didn’t delete selected files. Duh! That’s the job of the Trashcan icon, as I figured out a little later using mouseover tactics. By confusing Windows 11 scissors and trashcan icons, I showed myself that minor mistakes can stymie routine file handling tasks. Sigh.

If Confusing Windows 11 Scissors and Trashcan, What Next?

Before I figured out my category/identification error, I found another quick workaround to delete files. By clicking “More options” at the bottom of the first right-click menu, another more familiar menu appears. It’s more or less the Windows 10 menu transplanted into Windows 11, like so:

A second menu has the familiar text entry to make my choice more obvious: Delete appears three up from the bottom.
[Click image for full-sized view.]

As is nearly always the case in Windows (including 11), there’s more than one way to get things done. When one fails (or operator error leads to unwanted outcomes), another way can lead to success. My next step would be to turn to the command line, had this alternate path not led to the desired results. It’s always good to keep working at things until they get solved. That goes double when my silly mixup led to an initial lack of success.

As I learn new UIs and tools, this kind of thing happens from time to time. Call them Windows follies or funnies if you like. For me, it’s just another day, and another lesson learned, here in Windows-World!

Letters from the Ed, Recent Activity, Updates, WED Blog, Windows 10, Windows 11, Windows OS Musings

Are Over Half-a-Billion Windows 7 PCs Still In Use?

July 20, 2021 Ed Tittel Leave a comment

The old saying goes: “The numbers don’t lie.” Alas, I’ve been messing with numbers long enough to know that they don’t always capture the whole truth, either. Please indulge me for a moment, while I make a case for the size of the Windows 7 PC population. Warning! That case leads to the question that headlines this item: Are over half-a-billion Windows 7 PCs still in use? Sounds a bit high, as numbers go, so I’ll lay my reasoning out.

Why Ask: Are Over Half-a-Billion Windows 7 PCs Still in Use?

According to NetMarketShare.com, the platform version numbers for Windows 10 stand at 57.85% of desktops, versus 24.79% for Windows 7. MS has recently asserted that 1.3B active monthly users run Windows 10. Using that as a baseline, I calculate that if this number is accurate, there must be just over 557M Windows 7 PCs in use by proportion. How many of these are VMs, and how many are physical PCs is anybody’s guess.

Let’s say that 2 of 3 Windows 7 instances run on physical PCs just for grins. That would mean 557M Windows 7 OS instances translate into around 371 million devices running this now-obsolete OS. Recall that EOL for Windows 7 hit on January 14, 2020, 10.25 years after it debuted on October 22, 2009. These machines will be prime candidates for Windows 10 upgrades, because in all likelihood most of them will be unable to meet Windows 11 hardware requirements.

Another Question Comes to Mind…

As I tweeted last Friday, this raises another question. That question is: Will Windows 11 hardware requirements spur an uptick in Windows 10 installs, as older Windows 7 PCs get a “last and final” upgrade? Personally, I’m inclined to believe the answer is “Yes.”

Here are my reasons for so believing:
1. Because Windows 10 EOL is October 14, 2025, that buys time for home and business (mostly small business) users to save up for a hardware refresh to make themselves Windows 11-ready.
2. It reflects common practice in upgrading, where many users — again, especially those in SMBS — deliberately trail the leading edge of Windows releases in the name of improved stability, reliability and understanding.
3. It’s always easier and cheaper (at least, in terms of current cash flow) to defer upgrades and hardware purchases until later, rather than to act sooner. That said, it gives more time for planning, lets others do the hard work of pioneering, and offers greater comfort in making changes at a time of the buyer’s choosing.

How all this actually plays out remains to be seen. If my numbers have any bearing on what’s out there in the real world, things could get interesting. I have to believe the big OEMs — Lenovo, Dell, HP, and other players (Acer, Asus, LG, and so forth) — are pondering this closely and carefully. I’m betting that PC sales will remain strong until 2026 and beyond, though probably not at pandemic levels, as the workplace returns to more customary modes of operation. Stay tuned: I’ll keep you posted.

Recent Activity, Software Reviews, Updates, WED Blog, Windows 10, Windows 11

Windows App Update Blues

July 17, 2021 Ed Tittel Leave a comment

OK, then. I just got back from a nearly two-week hiatus (see yesterday’s blog post for a trip report). For the past day and a bit more, I’ve been catching up my 10 PCs. In part, that means updating the apps on those machines. Indeed, this experience has me singing the “Windows App Update Blues.” They’re nicely illustrated in the lead-in graphic for this story, which shows two apps on my primary production PC that lack built-in update facilities despite widespread proliferation and use (Kindle) and a pricey paid-for license (Nitro Pro).

Why Sing Those Low-Down Windows App Update Blues?

It’s nearly inconceivable that Amazon, that paragon of modern software efficiency and might, doesn’t include an updater for the Kindle reader. Ditto for Nitro Pro, which makes me shell out over US$100 for updates to this powerful and otherwise handy PDF tool on a more-or-less yearly basis.

Updates are not that simple on either side. For Kindle on PC, I have to visit the “free Kindle app” page at Amazon. Because I stay logged into the site, clicking “Download for PC & Mac” brings a file named KindleForPC-installer-1.32.61109.exe to my PC. Then, I have to run the installer, and it gets updated. Thankfully, this does not require me to remove the older version manually by way of post-install cleanup. Question: why can’t I get an update through the usual Help → About sequence typical for most Windows apps?

Nitro Pro has a “Visit our website” link on its Help → About pane. I guess that’s intended to streamline the manual update process. But each time I have to upgrade, I have to remember to visit the Downloads page via the website’s page footers, and manually download the latest version. While Amazon is at least kind enough to rename its updates so you can tell them apart, all four versions of Nitro pro 13 share the same filename: nitro_pro13.exe so only file creation dates distinguish them from one another. Then, something called “Nitro Pro SysTray” blocks installation until I instruct the installer to shut it down manually. After that, things work their way to proper completion. It, too, cleans up older versions (thank goodness).

But the Question Lingers: Why Manual?

I’m still not happy that I have to run this stuff down on my own and run updates manually. I hope somebody at Amazon and Nitro notices this item, and takes appropriate action. Given that most programs do this automatically, why can’t their apps do the same?

Letters from the Ed, Recent Activity

Vacation Return Means Posts Resume July 19

July 16, 2021 Ed Tittel Leave a comment

In case you haven’t noticed, I’ve been silent since July 5. That’s because the family and I took off on a great summer driving vacation on July 6 and just got back last night. I can now report that our vacation return means posts resume July 19 here at edtittel.com. Here’s a quick peek at our ambitious and sometimes tiring visiting/driving schedule:

Day  1  Round Rock     Big Spring, TX
Day  2  Big Spring     Albuquerque, NM
Day  3  Albuquerque    Colorado Springs, CO
Day  4  Colorado Spgs  Breckenridge, CO
Day  5  Breckenridge   Durango, CO
Day  8  Durango        Taos, NM
Day  9  Taos           Amarillo, TX
Day 10  Amarillo       Round Rock (home)

If Vacation Return Means Posts Resume July 19, What Happened?

I had several peak culinary experiences, including the best chicken fried steak (EVER) at the Settles Hotel in Big Spring, TX. Also really enjoyed a french dip at Seasons Restaurant in Durango on some truly wonderful local whole-grain bread. And a not-to-be-missed “meat coma” at the Big Texan Steak Ranch & Brewery in Amarillo.

We drove three thrilling and sometimes scary mountain roads. Two in Colorado included Highway 9 into Breckenridge and Highway 550 (including the famous “million dollar highway”) into Durango. In New Mexico, HIghway 104 from Las Vegas to Tucumcari bid a beautiful end to our mountain driving adventures.

We rode the Durango to Silverton narrow gauge train, and saw the magnificent and amazing Mesa Verde National Park near Durango. We also walked lots of mountain and/or tourist town main streets, drinking in the scenery and the mix of locals and visitors there.

All in all, it was a great adventure. All of us — Dina, Gregory and myself — had a great time. 10 nights away from home and 7 different hotels later, we gladly slept in our own beds last night.

Random Trip Highlights

We set a new “record MPG” in Dina’s E250 Bluetec diesel on this trip: 56 MPG riding a very long downhill stretch on I-70 from Vail to Grand Junction, CO. For the whole trip, we averaged just under 43 mpg, which reflects a large fraction of uphill driving.

In Colorado Springs, we stayed at the fabulous Broadmoor. Everybody should be so lucky at least once in their lives. It was amazing! The Settles Hotel in Big Spring proved a surprisingly good reason to visit that small Texas hamlet, the Rattlesnake Queen notwithstanding. I had at least four good bowls of chili on the trip, and an outstanding “Chile Colorado” in Mancos, CO on the way back from Mesa Verde National Park to Durango.

All in all, it was a terrific trip. Lots of beautiful scenery, interesting activities, and many, many miles covered (well over 2,000). Suitably refreshed and reinvigorated I’ll be covering my usual Windows topics on Monday. Stay tuned!

Insider stuff, Recent Activity, Tips, Tricks and Tweaks, WED Blog, Windows 11

WhyNotWin11 Offers PC Health Check Alternative

July 5, 2021 Ed Tittel Leave a comment

Some Windows users are purists by deliberate choice. Given the option of a Microsoft and a third-party too, they’ll take the MS route every time. I am no such purist. I appreciate good tools, whether from Microsoft or another (reputable) source. Thus, I’d like to observe that the GitHub project WhyNotWin11 offers PC Health Check Alternative. Indeed MS has temporarily taken down its tool. PC Health Check is available only from 3rd-party sources, such as TechSpot right now. Thus, WhyNotWin11 has the current advantage.

Why Say WhyNot11 Offers PC Health Check Alternative?

Though PC Health Check has been out of circulation for a week or so, WhyNot11 got its most recent update on July 3. Visit its Latest Release page for a download (version number 2.3.0.5 as I write this). You can also update the previous version 2.3.03 by downloading the latest SupportedProcessorsIntel.txt file and copying it over the previous version in the %Appdata%\Local\WhyNotWin11 folder.

Note: on my PC, that’s
C:\Users\\AppData\Local\WhyNotWin11\SupportedProcessorsIntel.txt.

WhyNotWin11 Is More Informative, Too

This story’s lead-in graphic shows the information that the third-party tool displays about target PCs. It provides a complete overview of which requirements are met (green), which aren’t listed as compatible (amber), and which are missing or disabled (red). This is more helpful than the output from PC Health Check. See it output below:

PC Health Check only briefly explains part of what’s at issue, and tersely at that.

While the message above does explain the “the processor isn’t supported,” it also fails to note the absence (as I know it to be on this PC) of a Trusted Platform Module (2.0 or any other version). WhyNotWin11 notifies users about both conditions directly and obviously.

IMO, easy access and operation, and more information about the target PC all make WhyNotWin11 a superior choice over PC Health Check. At least, for the purpose of finding out why a machine will (or won’t) upgrade to Windows 11. PC Health Check does offer other capabilities that users may find helpful, including (questionable) info about backup and synchronization, Windows Update checks, storage capacity consumption and startup time. I’m not arguing against use of the tool, when it returns to circulation. I’m merely suggesting that for the purpose of evaluating PCs for Windows 11 upgrades, WhyNotWin11 does a better job at that specific task.