Windows 10 the future is here. What future?

Microsoft released the 2004 version of Windows 10 to its next consumers last night, saying it was «ready for widespread adoption» six months after its release.

The change of status means that this version of Windows 10, which was released by Microsoft in May 2020, is ready for installation by everyone. Prior to this stage, older Windows 10 users had to «search» for the update by checking for updates in Windows Update.

As of February 3, 2021, Microsoft he says: «Windows 10, 2004 version available for widespread adoption.»

For businesses this means they can upgrade to the next version of Windows 10 without any problems.

As for the daring ones who tried to upgrade in May 2020, let them beware. But because of these daring, Microsoft can make money from companies that pay to have the company’s operating system.

We could perhaps say that the free release of Windows 10 through Insiders channels, or through a upgrade offer that does not say end, is a win-win situation.

Is it?

The consumer gains a free operating system but if things do not go well he loses his peace. I could recall things you know (BSOD, file deletion, hardware incompatibilities) but I do not think it makes sense.

Everyone knows Windows from the good and the bad. The purpose of this post is not to blame an operating system that I rarely use anyway.

But Microsoft’s approach irritates me unimaginably. Approaching the tests by the general public for six months (whatever that means) to make a reliable operating system available only to those who pay.

However, Microsoft seems to be developing a faster update process for feature updates. The transition from Windows 10 version 2004 to 20H2 (2009 version) was much faster through an activation package. Both versions were basically the same and the activation package allowed the activation of new features that already existed. Microsoft used the same activation package to upgrade from Windows 10 version 1903 to version 1909.

Could these activation packages be used differently? Maybe. We see an operating system in two different versions containing different functions.

Recently, Microsoft tested another approach using the Windows Feature Experience Pack in the Windows Insiders Beta channel. It is intended to allow Microsoft to have feature enhancements in addition to major Windows 10 feature updates.

Are we in a new era of Windows 10? Maybe in a little while we will talk about two-speed Windows. Probably better to ask the question.

We already have Windows 10 two-speed.

The former are available to the general public, and the latter, (the good ones) for those who pay to have them. Why not have Windows 10 with more or less features?

On the future of Windows 10’s feature releases

Microsoft’s twice-yearly feature updates arrive every six months — whether users want them or not. The company needs to do something to make this upgrade process less disruptive and avoid patch fatigue.

• 
• 
• 
• 
• 
• 

Over the years, Microsoft has made a lot of changes in how Windows updates work as a result of the feedback from users. However, it has not made changes in the process that affects nearly all of us: the installation of twice-yearly feature releases. It still rolls out a release every six months — whether we want them or not. These feature releases are disruptive; I personally have to fix PDF printers for QuickBooks that get removed by the feature update and keep an eye on my workstations for other side effects. This twice-a-year process is tiring and because many of the security features and enhancements are only available with certain licensing models of Windows 10, such as Enterprise or Microsoft 365 E5, many users (including myself) do not see these new security features rolled out with each release.

All too often, I see people report that “a patch caused my printers to fail.” After asking for more information, I realize that the “patch” was actually one of the semi-annual feature releases. This blurring of the impact of monthly security updates and semi-annual feature releases prompts many to request information on how to stop the updating process. It’s not good when impactful feature releases cause users to fear the updating process.

The other day, I spotted a post in the Answers forum, that if true, is concerning: “I contacted the Dell customer support and thanks to them that I could restore my system,” the user wrote. “They advised me not to update my laptop till 2021 Feb., as there are serious bug[s] with the latest updates.”

How many times have I seen my own Surface device get a feature release offered up after my Lenovo laptop because of a blocking condition due to a driver. On a regular basis, I am asked whether it’s time to upgrade to Windows 10 2004 or even 20H2 and I look at the pending issues with concern (on top of anecdotal stories from IT admins and consultants who recommend staying on 1909). Microsoft just fixed the Thunderbolt SSD issue that was causing blue screens of death in the Nov. 30 preview update of KB4586853. (Many didn’t expect this would be fixed until next year.) And yet, there are still concerning issues with the 2004 and 20H2 releases.

Often, I see antivirus and security solutions that have not yet certified 20H2 for their platforms. For example, Sophos expects to soon certify its SafeGuard Enterprise as ready to be installed during an in-place upgrade even as Bitlocker is enabled on the device. McAfee also provides a rundown of known issues when upgrading between versions. Generally speaking, my rule of thumb for using antivirus software is to stay with Microsoft Defender if you receive or install feature updates soon after they’re released. If you use any other third-party antivirus, I recommend that you stay on older feature releases for at least several months after the latest version’s release. (FYI: A block is still in place for administrators who normally rename the admin account in their deployment process.)

Microsoft has provided a way to bypass any block it has in place by using a new group-policy setting. In Group Policy, go to Computer configuration>Administrative Templates>Windows Components, then Windows Update, then Windows Update for Business. Find the “Disable safeguards for Feature Updates” setting. This policy is available to Windows Update for Business devices running Windows 10, version 1809 or later that have installed the October 2020 security update.

I would only use this for testing purposes. For users stuck on Win10 1909 due to the issue with Conexant audio drivers, the only workaround now is to remove the Conexant drivers and proceed with the feature release process. (You will end up with generic Microsoft audio drivers.) If you don’t need the advanced features from your audio settings, this may be an acceptable option.

As of a few days ago, 20H2 use was still in single digits at less than 9%, per Adduplex. The majority of Windows 10 users are split between 1909 (36.4%) and 2004 (37.6%). Clearly, most Microsoft users do not rush to embrace the latest feature release.

It appears that Microsoft is responding. It recently announced that Insider builds will use a new process to release feature improvements. There is now a “Windows Feature Experience Pack” process that allows Microsoft to improve certain features and experiences independently of the operating system. “By testing this process first with Windows Insiders, we hope to expand the scope and the frequency of releases in the future,” the company said. “Eventually, Windows Feature Experience Pack updates will get folded into the already existing servicing process for Windows 10 and delivered to customers that way through Windows Update.”

I’ve done several surveys of what IT admins think about feature releases and most of them wish Microsoft would go to a one-per- year release cadence. It will be interesting to see whether the Feature Experience Pack process will be a way for Microsoft to do just that.

Bottom line: I’m glad Microsoft no longer force feeds Windows 10 feature releases like it used to. But I still feel this process of pushing mini service packs is disruptive, and causes too many issues. Here’s hoping that Microsoft realizes this and makes this process easier for everyone.

Microsoft accidentally confirms Windows 10’s future OS

It seems that Microsoft hasn’t given up on the idea of a unified Windows 10 experience and the company is still actively testing Windows Core OS for upcoming devices. If you’ve had any doubts about the existence of Windows Core OS, doubts can be settled as Microsoft has accidentally leaked new details of the unannounced operating system.

Windows Core OS is the leaner version of Windows that’s mean to be used in the Surface Neo as Windows 10X, Surface Hub 2, HoloLens, and, of course, it was also supposed to power Surface Phone ‘Andromeda’, but that changed later when Microsoft officials dumped Windows for Android.

Unlike Windows 8, Windows Core OS is not touch-centric as it has composers/adaptable shells for all form factors. The Core OS is being developed with a radically different way of interacting with computing devices such as desktops, laptops, dual-screen devices, Surface Hub, and Hololens.

The development of WCOS seems to be advancing with some surprising updates to old support documents that might be setting the stage for Windows 10’s modular operating system.

Although Windows 10X supports Win32 apps, questions have been raised in regards to classic Windows 10 features support on Windows 10X and Windows Core OS.

In a support document, Microsoft accidentally confirmed desktop fonts support for Windows Core OS and the document was quickly modified to remove mention of ‘WCOS’ and future devices.

“Please note: Not all of the Desktop fonts will be in non-desktop editions of Windows 10 such as Xbox, HoloLens, Surface Hub, future WCOS devices, etc,” Microsoft noted in the document.

We were able to uncover a now-edited page that confirmed desktop fonts for Windows Core OS and newer versions.

According to clues pieced together from preview builds and job postings, Windows Core OS is said to show up on PCs, laptops, Xbox, dual-screen tablets, multiple screen devices, Surface Hub, Mixed Reality headsets, and also the Internet of Things (IoT) products.

WCOS allows Win32, UWPs and PWAs to be installed and run via containers. In fact, Windows 10’s Core OS will be locked and stripped down, which should naturally improve performance and security.

What’s next for Microsoft’s Windows 10 in 2020

The next two Windows 10 updates, codenamed ’20H1′ and ’20H2′ reflect Microsoft’s new approach to split the major feature releases into two. The first update ’20H1′ would be a full-fledged update with new features, and the second update of the year will only contain improvements.

We’ve already had the first minor Windows 10 release ‘November 2019 Update’ last year and we’re now looking forward to the next two releases in 2020.

In addition to two new Windows 10 updates, Microsoft is working on a new version of the operating system called ‘Windows 10X’. Here’s what we know so far about Microsoft’s future plans for Windows.

Windows 10 20H1 ‘May 2020 Update’

Unlike November 2019 Update, there’s a grab bag of improvements and new additions in Windows 10 20H1, also known as version 2004 and May 2020 Update.

At this point with one month to go for its release, Windows 10 May 2020 Update feels stable and smooth. Still, there’s still plenty of time for Microsoft to fix any rare and last moment compatibility issues.

The name ‘May 2020 Update’ was recently spotted in the latest preview builds and Microsoft is also expected to publish the update in May.

The upcoming 20H1 feature update will focus on substantive improvements and as well as quality enhancements, including improvements to the existing features such as ‘Reset this PC’.

As of April, Windows 10 version 2004 update includes performance improvements, new Cortana experience, WSL 2, updated tablet experience, new optional updates page, improved driver compatibility, reduced CPU and Disk usage, new app icons, two new features in Task Manager, and more.

If this feature update hews to Microsoft’s usual schedule, it’ll drop in late April or early May.

Upcoming announcements from Microsoft’s Insider team will provide further hints about its exact release timeframe.

Windows 10 20H2 update

After 20H1 update release, we’re looking forward to minor 20H2 patch. As of April 2020, the upcoming 20H2 feature update focus appears to be only on quality enhancements, but there’ll be a few new features as well.

There are a few potential features from recent builds that are intriguing. For example, Windows Search is getting a new algorithm that will allow it to start the indexing process when you are not actively using the PC.

In this update, we’ll also see a number of minor tweaks to various UI elements. Interim beta builds also dropped further hints about what’s coming in this year or next year. For example, Microsoft has started working on its new volume control taskbar feature, modern disk management tool, and Control Panel removal plans.

The upcoming preview builds will provide further hints about what’s coming and we’ll continue to cover them in detail.

Windows 10X

As Microsoft moves toward the launch of the dual-screen Surface Neo, Microsoft is now actively testing Windows 10X in its internal branch.

In fact, the latest Windows 10 preview build include references to features of 10X such as the new Control Center.

According to the original schedule, Windows 10X is expected to become available for Surface Neo devices later this year.

It is worth noting that you’ll be able to dual-boot Windows 10 Pro/Home and Windows 10X on your traditional device through third-party tools. The laptop flavour of 10X is also being developed, but it won’t be announced until next year.