WEBVTT

00:00:00.040 --> 00:00:07.560
are we going to have to throw out 240 million PCS next year when Windows 10

00:00:05.080 --> 00:00:12.360
reaches end of life according to one It analytics firm that's how many computers

00:00:09.679 --> 00:00:16.920
are ineligible for a Windows 11 upgrade meaning they won't be getting security

00:00:14.120 --> 00:00:20.840
updates after October 2025 and while it's possible to pay Microsoft for

00:00:18.720 --> 00:00:25.640
extended security updates Slovenian company Acro security thinks it has a

00:00:23.039 --> 00:00:30.320
better and cheaper solution they call it zero patch and it's supposed to keep

00:00:27.760 --> 00:00:34.719
Windows 10 safe to use for at least 5 years Beyond October 2025 but how is it

00:00:33.480 --> 00:00:40.360
different from Microsoft's official Solutions what are strengths and weaknesses and how the heck does an

00:00:38.040 --> 00:00:43.559
outside company even figure out how to patch Windows security holes I mean it's

00:00:42.000 --> 00:00:46.680
not like Microsoft just leaves Windows source code laying around for anyone to

00:00:45.120 --> 00:00:50.399
look at before we go on I just want to say we're not affiliated or paid by

00:00:48.280 --> 00:00:54.520
acros in any way this is just cool information it turns out that not having

00:00:52.520 --> 00:00:58.320
the source code isn't a big deal for software Engineers who are good at

00:00:56.120 --> 00:01:02.120
reverse engineering once a vulnerability in Windows has been identified and

00:01:00.039 --> 00:01:06.439
Engineers can reproduce it they can track exactly how that data flows

00:01:04.320 --> 00:01:10.159
between different processes running on the PC and they can examine the code

00:01:08.479 --> 00:01:14.280
that's being executed using software tools after this tracking and inspection

00:01:12.400 --> 00:01:18.600
step the team then attempts to modify the original Windows code more on that

00:01:15.960 --> 00:01:22.479
shortly to plug the security hole although new vulnerabilities are found

00:01:20.159 --> 00:01:26.759
regularly with Windows many of them fall into known categories allowing zero

00:01:24.840 --> 00:01:30.560
patch to get fixes out the door in relatively short order but there's

00:01:28.759 --> 00:01:34.320
something about these fixes that is very interesting compared to official Windows

00:01:32.439 --> 00:01:38.680
patches and we'll tell you what that is right after we thank private internet

00:01:36.119 --> 00:01:42.880
access their VPN network expands across six continents and 91 countries that's

00:01:41.200 --> 00:01:47.119
all the good ones letting you access your local catalog of content from all

00:01:44.920 --> 00:01:51.360
over the globe VPN are like a little invisible tunnel for your online life no

00:01:49.719 --> 00:01:55.439
one especially your internet service provider or nosy third parties gets to

00:01:53.360 --> 00:01:59.039
see what you're up to your privacy belongs to you plus with just one

00:01:57.520 --> 00:02:03.360
subscription you can connect an unlimited number of devices to Pia

00:02:01.000 --> 00:02:07.200
really unlimited gz go check out Pia using our Link in the description for a

00:02:04.960 --> 00:02:11.840
special deal with a risk-free 30-day money back guarantee so what clever way

00:02:09.679 --> 00:02:16.280
has zero patch device to keep Windows updated instead of altering the original

00:02:14.280 --> 00:02:22.040
Windows system files that live on a drive zero patch instead Alters

00:02:18.640 --> 00:02:24.360
processes running in RAM across says

00:02:22.040 --> 00:02:28.879
this has a big Advantage if a patch that affects a running process for example a

00:02:26.560 --> 00:02:33.040
spreadsheet program is released the patch gets applied without the user

00:02:30.879 --> 00:02:37.480
having to reboot the PC or close the spreadsheet they're working on instead

00:02:35.080 --> 00:02:41.560
zero patch briefly stops the process and Alters a few bytes in memory which only

00:02:39.599 --> 00:02:45.360
takes a fraction of a second additionally attempting to alter Windows

00:02:43.560 --> 00:02:48.680
files would make the operating system think that there's a security issue and

00:02:47.280 --> 00:02:52.360
it wouldn't exactly be convenient to have your computer constantly think it

00:02:50.519 --> 00:02:56.959
has some kind of malware infection ironically caused by security patches so

00:02:55.239 --> 00:03:02.239
avoiding this approach altogether minimizes the chances that Windows would

00:02:59.480 --> 00:03:06.799
somehow how block the security fix is and if for some reason a patch messes

00:03:04.519 --> 00:03:12.080
something up or otherwise it needs to be unapplied de applied this can be very

00:03:09.760 --> 00:03:15.680
easily done simply by disabling zero patch which instantly removes any

00:03:13.640 --> 00:03:21.120
changes from memory without having to go through the process of deinstalling and

00:03:18.120 --> 00:03:23.560
update uninstalling but beyond these

00:03:21.120 --> 00:03:26.920
usability advantages across says zero patch is superior for certain

00:03:25.040 --> 00:03:31.360
vulnerabilities that Microsoft hasn't even addressed yet that is zero day

00:03:29.280 --> 00:03:35.760
attacks including for example security holes in authentication for large

00:03:33.239 --> 00:03:39.959
networks which Microsoft actually just stopped issuing patches for the point

00:03:38.159 --> 00:03:43.879
here is that not only is zero patch a solution to keep Windows 10 safe to use

00:03:42.080 --> 00:03:49.080
but the approach is also supposed to help with existing problems Microsoft

00:03:45.840 --> 00:03:50.760
either can't or won't fix indeed across

00:03:49.080 --> 00:03:55.319
has said that trying to fix the source code is much more timec consuming than

00:03:52.879 --> 00:03:58.239
zero patches handle it in RAM approach meaning they're actually supposed to

00:03:56.400 --> 00:04:01.840
push out patches faster than you'd used to be getting from Windows update

00:03:59.840 --> 00:04:05.799
butless we sound like we're Shilling for them again this was not a p video we

00:04:03.560 --> 00:04:10.519
have no affiliation with acros let's now talk about a key limitation to their

00:04:07.879 --> 00:04:15.360
solution unlike official Microsoft fixes zero patch can't touch problems in the

00:04:13.120 --> 00:04:20.239
kernel basically the underlying code of the operating system instead it'll patch

00:04:17.799 --> 00:04:25.160
issues in user space essentially the programs you can see running in task

00:04:22.120 --> 00:04:26.960
manager but the good news is that most

00:04:25.160 --> 00:04:31.759
critical issues that attackers could exploit are in user space so acros is

00:04:30.120 --> 00:04:36.039
pretty confident that zero patch will prevent Windows 10 from becoming

00:04:33.320 --> 00:04:40.759
unacceptably risky to use as the years go by still it's important to note that

00:04:38.600 --> 00:04:45.440
zero patch tends to focus on specific attack vectors meaning that despite its

00:04:42.919 --> 00:04:49.919
advantages it may not protect against the same range of attacks that the

00:04:47.800 --> 00:04:53.680
official Microsoft updates would if you want to give zero patch a try Acro told

00:04:51.960 --> 00:04:58.560
us that they're looking at extending support Beyond 5 years if demand is

00:04:55.880 --> 00:05:02.639
there but again the service is not free though it is nice for Microsoft to have

00:05:00.080 --> 00:05:06.520
a little competition are you planning to make your Windows 10 system last for as

00:05:04.840 --> 00:05:10.880
long as it can let us know down in the comments and if you'd like to learn a

00:05:07.960 --> 00:05:16.560
bit of history about how Windows XP lasted as long as it did go watch this

00:05:13.440 --> 00:05:16.560
video next