WEBVTT

00:00:00.000 --> 00:00:04.640
When Microsoft released Windows 10 in 2015, it was widely reported that the company was calling

00:00:04.640 --> 00:00:10.080
their newest operating system the last version of Windows, leading to widespread confusion and

00:00:10.080 --> 00:00:16.560
memory when the company proceeded to announce Windows 11 in 2021. It turns out the last version

00:00:16.560 --> 00:00:21.760
thing actually came from a throwaway comment by a Microsoft developer and not an official company

00:00:21.760 --> 00:00:28.320
statement. So is Windows 11 the last last version or will we be seeing a Windows 12 in the next few

00:00:28.320 --> 00:00:33.920
years? Prior to Windows 10, a new full-fledged version of the OS came out once every two or three

00:00:33.920 --> 00:00:38.960
years, but by the time 2015 rolled around, Microsoft no longer thought that this was a viable model.

00:00:38.960 --> 00:00:43.280
As computing was shifting more to applications that depended on the cloud, especially on mobile

00:00:43.280 --> 00:00:48.400
devices, Microsoft believed forcing its users to wait literal years for major updates was silly

00:00:48.400 --> 00:00:52.720
when people were used to getting updates on other platforms on a much more frequent basis,

00:00:52.720 --> 00:00:56.640
and I'm sure Microsoft didn't want to end up lagging behind in terms of compatibility

00:00:56.640 --> 00:01:01.520
with rapidly evolving technologies. So the company's strategy shifted to releasing multiple

00:01:01.520 --> 00:01:07.120
feature updates per year on Windows 10, giving users a gradual improvement to keep up with the

00:01:07.120 --> 00:01:12.400
times. And that seemed like a good idea, but a huge issue was that the improvements often weren't

00:01:12.400 --> 00:01:16.880
all that gradual. Not only did many users not get used to how often major changes were made to the

00:01:16.880 --> 00:01:22.240
OS, but updates were also cumulative. This meant that you couldn't pick and choose which features

00:01:22.240 --> 00:01:26.080
you wanted, and if a long period of time passed since you last updated your system,

00:01:26.080 --> 00:01:31.360
you'd get hit with a huge number of changes all at once. Although the changes themselves

00:01:31.360 --> 00:01:35.360
weren't all that bad, many users weren't happy with the frequency of them, especially larger

00:01:35.360 --> 00:01:39.840
organizations that had to manage large-scale Windows deployments for users who might not

00:01:39.840 --> 00:01:45.520
have been all that tech savvy. Now, this wasn't the only reason that Microsoft ended up releasing

00:01:45.520 --> 00:01:52.080
Windows 11, and putting out those major updates with an H in the name only once a year as a compromise.

00:01:52.160 --> 00:01:56.800
There were enough differences in Windows 11 to make it a full-fledged separate product,

00:01:56.800 --> 00:02:02.720
especially considering the beefed-up security requirements. But enough had changed overall

00:02:02.720 --> 00:02:08.400
from the original Windows 10 paradigm for the Windows 11 designation to make sense.

00:02:08.400 --> 00:02:13.120
But if Microsoft is fine with the annual update cadence and consumers end up being okay with it

00:02:13.120 --> 00:02:18.640
as well, is there a point to Microsoft coming out with the Windows 12? There have already been

00:02:18.720 --> 00:02:24.080
reports that Microsoft is indeed returning to their more traditional strategy of releasing a

00:02:24.080 --> 00:02:28.480
new version of Windows every three years. This is probably a tacit admission on Microsoft's part

00:02:28.480 --> 00:02:33.600
that the whole Windows as a service idea didn't completely take off. But beyond just that,

00:02:33.600 --> 00:02:38.560
not sticking with one version of Windows for the rest of time makes sense for a couple of reasons.

00:02:38.560 --> 00:02:42.560
As we saw with the controversy over TPM requirements for Windows 11,

00:02:42.560 --> 00:02:47.200
hardware requirements are going to keep changing in the future. At some point, newer standards

00:02:47.200 --> 00:02:52.320
will become necessities instead of nice to have. And once a Windows update requires some

00:02:52.320 --> 00:02:57.280
major hardware change, it would be much more confusing to consumers if an update to the same

00:02:57.280 --> 00:03:02.960
Windows version simply did not work in their existing hardware. Going back to a new full-fledged

00:03:02.960 --> 00:03:08.560
Windows version every three years also gives consumers more of a choice as to whether they

00:03:08.560 --> 00:03:14.160
want to drastically change how they interact with their computer. And for administrators

00:03:14.160 --> 00:03:18.160
in large organizations, they might have really good reasons to stick with what they have, whether

00:03:18.160 --> 00:03:23.040
that's a need to run older software or the fear that migrating to a new version of Windows would

00:03:23.040 --> 00:03:27.680
cause chaos and calamity among the rank and file of their company. Although Microsoft has gotten

00:03:27.680 --> 00:03:32.400
plenty of criticism for forced updates, upgrading to an entirely new version of Windows has always

00:03:32.400 --> 00:03:37.920
been completely optional and remains so to this day. Right now, most folks in the industry are

00:03:37.920 --> 00:03:43.440
expecting Windows 12 sometime in 2024, but we don't have much information as to what it would look

00:03:43.760 --> 00:03:48.560
outside of possibly adding battery and Wi-Fi indicators at the top of the screen to make

00:03:48.560 --> 00:03:53.600
the experience slightly more phone-like. Hopefully, exciting changes will be coming for those of us

00:03:53.600 --> 00:03:59.600
using a desktop, like the ability to move the taskbar again. Oh, please, God, give me that back.

00:03:59.600 --> 00:04:03.440
Thanks for watching. Like, dislike, check out our other videos like this one where Riley