WEBVTT 00:00:00.160 --> 00:00:08.960 Everybody knows that more is better. More RAM means more programs can run at 00:00:05.520 --> 00:00:11.599 the same time. More GPU power means more 00:00:08.960 --> 00:00:16.160 FPS in your games. And more mother-in-laws means more time spent 00:00:13.920 --> 00:00:21.359 with family. There are downsides. Well, mine is great. But in a world where 00:00:18.800 --> 00:00:26.400 malware is seemingly more dangerous than ever, it would only be logical to assume 00:00:23.519 --> 00:00:31.519 that more antivirus software is going to keep her more safer, right? I mean, why 00:00:29.039 --> 00:00:36.000 not? It used to be that running even one antivirus package would significantly 00:00:33.680 --> 00:00:40.879 impact your PC's performance. But these days, computers are so much faster that 00:00:38.719 --> 00:00:46.239 Windows includes its own AV software that most people probably don't even 00:00:42.640 --> 00:00:49.600 notice is running. So, could we run two, 00:00:46.239 --> 00:00:52.879 three, or 10 antivirus tools to create 00:00:49.600 --> 00:00:54.719 the safest PC on the internet? That's 00:00:52.879 --> 00:00:59.199 what we're here to find out with some help from our sponsor, Threat Locker. 00:00:57.120 --> 00:01:03.039 Threat Locker is a totally different way to keep your entire business network 00:01:01.359 --> 00:01:10.880 safe, but we'll talk more about that later. For now, spoiler alert, more is 00:01:06.400 --> 00:01:10.880 not always better. Let's see how that 00:01:17.320 --> 00:01:24.000 goes. Let's kick this off with a good old-fashioned boot time test. In front 00:01:22.000 --> 00:01:30.640 of me are two virtually identical systems with Core i5 processors, 16 gigs 00:01:26.640 --> 00:01:33.920 of DDR5 memory, an RTX 3050GPU, and a 00:01:30.640 --> 00:01:35.759 terabyte of fast NVMe storage. Both have 00:01:33.920 --> 00:01:40.799 a fresh install of Windows 11, and all the latest drivers. But there's one key 00:01:37.920 --> 00:01:46.560 difference. This one relies solely on Microsoft's antivirus. Not that one, 00:01:44.079 --> 00:01:50.720 Microsoft Defender. As for the other, well, we just plum had a hard time 00:01:48.960 --> 00:01:55.040 choosing between all the options, especially with all of the inbreeding 00:01:52.560 --> 00:02:03.200 between AV companies these days. Did you know that Avast, Avera, AVG, and Norton 00:01:59.840 --> 00:02:05.600 are all the same company? Gen digital, 00:02:03.200 --> 00:02:11.599 look it up. And they don't just share ownership. Norton and AVG actually use 00:02:08.879 --> 00:02:16.800 Avast's AV engine these days. And a ver's engine gets used even by third 00:02:13.599 --> 00:02:18.560 parties like VMware and F-Secure. Uh, 00:02:16.800 --> 00:02:25.440 this one's booted by the way. Couldn't help noting that. This one not so 00:02:22.040 --> 00:02:28.319 much. Is it still going? Anyway, the 00:02:25.440 --> 00:02:32.319 TLDDR is we got confused. So, we crammed our second system full of as much 00:02:30.080 --> 00:02:36.200 antivirus software as she would take and still connect to the internet. What's 00:02:33.840 --> 00:02:43.200 the final count? I think 14. 14. My goodness. 00:02:40.239 --> 00:02:48.080 And it's booted. Hold on. I have another fun one for you, though. Let's see how 00:02:45.120 --> 00:02:48.080 long they take to shut 00:02:48.920 --> 00:02:55.519 down. Wow, that one's done 00:02:52.280 --> 00:02:58.160 already. Let's read some more lines. Ah, 00:02:55.519 --> 00:03:04.480 yes. React to boot time. Oh, I can tell you all the antiviruses we have. Total 00:03:00.800 --> 00:03:10.159 AV, Panda, Malware Bites, Quick Heal, 00:03:04.480 --> 00:03:13.599 Avast, AVG, Adaware, ESET, Avira, Forct, 00:03:10.159 --> 00:03:16.120 Heimdoll, Komodo, Clam, AV, and of 00:03:13.599 --> 00:03:20.400 course, good old-fashioned Windows Defender. It is worth noting that a 00:03:18.400 --> 00:03:24.560 couple of them do have reduced runtime protection when others are 00:03:22.440 --> 00:03:27.440 detected. And I guess I'll talk about our sponsor real quick here because 00:03:25.680 --> 00:03:31.120 we're still waiting. Uh, it's worth noting, by the way, our sponsor, Threat 00:03:29.120 --> 00:03:34.799 Locker, doesn't really compete with any of the antivirus software that we're 00:03:32.560 --> 00:03:38.959 showing off today. Threat Locker stops more than just malware. They even block 00:03:37.200 --> 00:03:43.040 unapproved applications on your network with application allow listing. That 00:03:41.200 --> 00:03:46.879 means that aside from being protected, your team can't be lured away from that 00:03:44.879 --> 00:03:51.120 important report for a quick round of Battro during business hours. Okay, 00:03:49.280 --> 00:03:54.799 finally, let's boot them back up and see how these systems feel. Let's start with 00:03:52.879 --> 00:03:58.319 our control computer. Yep, that's file explorer. Yep, that's the system tray. 00:03:56.720 --> 00:04:02.159 If I wanted to launch Steam, it seems like that'll happen in a perfectly 00:04:00.159 --> 00:04:06.720 reasonable amount of time. Now, let's move over here where Oh my goodness, I 00:04:03.840 --> 00:04:09.040 already have a popup to dismiss. Okay, file 00:04:11.640 --> 00:04:16.320 explorer. This is a modern Core i5. That 00:04:15.120 --> 00:04:25.639 was pretty quick for that one, actually. I mean, the system tray was still responsive. How long does it take to 00:04:19.919 --> 00:04:25.639 launch Steam, though? Ah. Oh. 00:04:27.960 --> 00:04:33.560 Oh. Oh my god. This poor system. Look at 00:04:32.479 --> 00:04:39.840 them all. Malware bite 6%. Komodo 4 Vera 00:04:39.960 --> 00:04:45.240 4%. Is Steam still launching? 00:04:46.000 --> 00:04:51.680 It'll take a while. 00:04:49.000 --> 00:04:56.160 Wow. Okay. I knew it was going to be bad. I didn't think it was going to be 00:04:53.600 --> 00:05:01.360 like using my Windows 98 machine. I thought it would be uh this is awful, 00:04:58.240 --> 00:05:03.360 but it's oh this is awful. And the funny 00:05:01.360 --> 00:05:07.759 part is when we're not doing anything, the usage of all these doesn't seem that 00:05:05.440 --> 00:05:11.280 bad. It's just that that's the whole thing, right? When they're idling in the 00:05:09.520 --> 00:05:15.840 background, they're fine. But it's as soon as you start to do anything that 00:05:13.360 --> 00:05:22.080 they're actively continuously monitoring what's going on and making sure that 00:05:17.440 --> 00:05:22.080 it's okay and the system resource usage 00:05:22.280 --> 00:05:27.560 goes oh my god did you see how long that 00:05:25.520 --> 00:05:32.560 took to maximize boy that's crazy. Can Can I see 00:05:30.639 --> 00:05:36.880 yours? Yours should be fine. Yeah. Mine works like a computer. This shouldn't 00:05:34.080 --> 00:05:40.720 slow the GPU, isn't the Do you see that? That's terrible. 00:05:38.320 --> 00:05:44.960 What the That is not the screen capture, guys. No, that's live happening 00:05:43.199 --> 00:05:50.000 in person. That's wild. It's It's not even using 00:05:47.199 --> 00:05:54.720 that much. No, it's at like 10%. Okay. What's yours? What's yours? One to 2%. 00:05:53.120 --> 00:05:59.759 And this is way worse than you think because you might say, "Oh, what? It's 00:05:57.280 --> 00:06:04.199 using 10 times as much resources. That's to be expected." But I think it's more 00:06:01.840 --> 00:06:12.400 than that because yours is using 1% of like 1 and a half GHz. Mine is 00:06:08.160 --> 00:06:14.560 using anywhere from 5 to 10%. But my CPU 00:06:12.400 --> 00:06:18.479 is clocked way higher. Yeah. And I don't know if that's, you know, linear or 00:06:16.560 --> 00:06:24.360 anything, but it's clear that my resource usage is more than it appears. 00:06:21.919 --> 00:06:31.360 You're almost double the RAM, too. Oh, dude. How's my sto My storage seems 00:06:27.280 --> 00:06:33.600 okay. Yeah, but I bet my storage becomes 00:06:31.360 --> 00:06:38.080 a complete disaster as soon as I try to launch a program. So, let's both launch 00:06:35.759 --> 00:06:42.800 Edge and look at the average response time. 3 2 1 click. Oh, okay. That didn't 00:06:41.440 --> 00:06:46.280 work. Okay, let's launch File Explorer. Let's launch File Explorer. Okay, ready? 00:06:44.479 --> 00:06:52.440 3 2 1 click. So, you went up to 00:06:48.759 --> 00:06:55.919 7. Yeah. Okay. No, that was 00:06:52.440 --> 00:06:58.960 fine. Copilot. Let's launch Copilot. 3 2 00:06:55.919 --> 00:06:58.960 1 Click. 00:06:59.840 --> 00:07:08.160 Yeah, my storage is not hit that hard. I mean, it takes forever to do anything, 00:07:05.759 --> 00:07:11.360 but it seems to be more down to the CPU that's struggling. Is this ever going to 00:07:09.759 --> 00:07:18.880 launch? Did I click it? Yeah. Oh, dude. Yeah. Look, I got the spinny wheel. Oh, yeah. There you go. Wow. You want to see 00:07:15.520 --> 00:07:21.520 worse? Plug in the USB key. Really? 00:07:18.880 --> 00:07:27.680 Where did they go? Oh, that makes sense. They're going to lose their 00:07:24.039 --> 00:07:30.400 minds. Okay. And so the race is how long 00:07:27.680 --> 00:07:34.240 it takes for the folder to open. Well, just just see what happens when you plug 00:07:31.599 --> 00:07:40.800 it in. Top USB 3 port here. Sure. Okay. Three, two, one. 00:07:37.520 --> 00:07:44.840 Okay. Mine opens up. Oh, yeah. I got it. 00:07:40.800 --> 00:07:44.840 I got it. Okay. 00:07:46.520 --> 00:07:52.000 What? Look at my CPU usage. They all 00:07:50.400 --> 00:07:55.919 want to scan it for threats. You better let it do it. Oh, it's got Oh. Oh. Oh, 00:07:53.919 --> 00:08:00.960 good. gravy. Just say yes to a few of them. Oh, no. No. Oh, wait. Some of them 00:07:58.000 --> 00:08:10.560 don't even ask me. Yep. They just start. Oh, no. So, my poor USB drive is at 95% 00:08:06.879 --> 00:08:12.720 utilization right now. Even my NVMe SSD 00:08:10.560 --> 00:08:18.319 is registering. You were 30% CPU there a second ago at 3 00:08:16.000 --> 00:08:21.840 GHz. Okay. You want me to click yes? Click yes to a couple of them. That'll 00:08:20.000 --> 00:08:25.879 give you some time to talk. Back before Al Gore invented the internet, the 00:08:23.840 --> 00:08:30.879 primary way to exchange data was sneakeret. And the fight against malware 00:08:28.720 --> 00:08:36.399 depended on knowing what that malware looked like on your disc or in your 00:08:33.440 --> 00:08:41.839 system memory. Early PC antivirus suites then relied on databases of signatures 00:08:39.120 --> 00:08:46.800 for known malware. So if your AV tool didn't know about a virus, it probably 00:08:44.480 --> 00:08:51.200 wouldn't protect you from it. And it was a lot more work to get new signatures 00:08:49.440 --> 00:08:55.440 than just clicking update and downloading them from the internet. Of 00:08:53.360 --> 00:08:59.760 course, the damage a virus could do back then was also quite a lot more limited. 00:08:57.839 --> 00:09:04.640 We weren't exactly banking online back in 1987. It wasn't until the '90s then 00:09:02.560 --> 00:09:08.880 that antivirus turned into a serious industry. With the arrival of the 00:09:06.640 --> 00:09:13.839 internet, PCs were interacting with each other like never before. And the problem 00:09:11.200 --> 00:09:19.040 is that most desktop software really wasn't ready for the dangers of this new 00:09:16.640 --> 00:09:24.640 level of connectivity. Looking at you, Outlook Express. Antivirus creators then 00:09:22.240 --> 00:09:29.360 embraced having an easy way to get updates of these signatures or 00:09:26.959 --> 00:09:34.880 definitions to their users. But then at the same time, virus writers found new 00:09:32.080 --> 00:09:39.720 vectors of attack. email, Microsoft Office macros, Java, VBScript, and they 00:09:37.680 --> 00:09:45.040 exploited them with new types of malware, often more quickly than 00:09:42.000 --> 00:09:47.680 researchers could hope to respond to. Is 00:09:45.040 --> 00:09:52.800 this still running? All right, more history, then. We started the '90s with 00:09:50.320 --> 00:09:57.800 maybe a few hundred known viruses in the wild, and by 1999, the AV test database 00:09:56.320 --> 00:10:03.839 had nearly 100,000 entries. AV makers like FPROT 00:10:01.519 --> 00:10:08.240 tried to get out ahead of this rapid fire virus development with the first 00:10:05.920 --> 00:10:13.279 use of heristic detection as we might recognize it today. That is analyzing a 00:10:11.040 --> 00:10:17.760 program's behavior to recognize potential threats even if that malware 00:10:15.600 --> 00:10:23.720 has never been seen before. But signatures were still a big piece of the 00:10:20.240 --> 00:10:26.560 detection puzzle. And I mean big. By 00:10:23.720 --> 00:10:32.959 2005, AV Tests database had more than tripled to almost 340,000 entries. And 00:10:30.000 --> 00:10:38.600 the worst part is that was nothing. In 2007 alone, another 5 million unique 00:10:36.640 --> 00:10:45.200 malware samples were added to the database. It went parabolic and it's 00:10:42.160 --> 00:10:47.279 only gotten worse. So, yeah, it was easy 00:10:45.200 --> 00:10:51.920 to rag on Norton and friends, and they did make it real easy. But between 00:10:49.680 --> 00:10:56.720 massive databases of potential threats and the need to protect from more and 00:10:54.320 --> 00:11:02.279 more vectors of attack, it's no wonder that antivirus packages kept using more 00:10:59.040 --> 00:11:05.279 and more system resources causing system 00:11:02.279 --> 00:11:07.920 slowdowns. And that was with just one of 00:11:05.279 --> 00:11:12.160 them running. Let's try gaming on our system with 14 AVs. We haven't even 00:11:09.839 --> 00:11:16.640 finished scanning this USB drive yet. Yeah, sure. Let's game. We did so many 00:11:14.959 --> 00:11:21.279 takes while this was sitting here scanning. 00:11:19.279 --> 00:11:28.079 I have 270 FPS. You're sure these systems are safe? I have 294. Oh, wait. 00:11:25.360 --> 00:11:34.200 Gaming might be totally okay cuz it's not burdening our 00:11:29.480 --> 00:11:37.600 GPU and our storage was actually doing 00:11:34.200 --> 00:11:40.959 fine. Yeah, my RAM usage is way higher. 00:11:37.600 --> 00:11:43.040 4 gigs higher and my CPU usage is 00:11:40.959 --> 00:11:47.600 substantially higher. But this is interesting. I'm at a higher speed 00:11:45.279 --> 00:11:52.399 though. Yours is turboing higher, probably because it's less burdened. But 00:11:50.000 --> 00:11:57.760 the FPS is nearly identical. We just seem to be GPU bound. Yeah, that's 00:11:55.519 --> 00:12:02.720 interesting. I think it might be because we're running RTX 3050s. These are 00:12:00.079 --> 00:12:06.240 pretty low GPUs. Look at the process count 00:12:04.720 --> 00:12:09.240 and the threads. You have double the threads. 00:12:09.519 --> 00:12:16.399 That is wild. So, I think the only reason this isn't 00:12:14.000 --> 00:12:22.399 impeding my gaming performance is that our GPU is just not powerful enough. I 00:12:20.000 --> 00:12:26.880 mean, we're getting 230 frames a second. Yeah, but we're just we're not revealing 00:12:24.480 --> 00:12:30.480 we're we're GPU bottlenecked. Yeah, clearly I have plenty of CPU left 00:12:29.120 --> 00:12:34.480 over to run all this crap in the background. I think we might need a 00:12:32.399 --> 00:12:40.839 couple higherend GPUs. I'll be right back. He brought us 5080s. We can't plug 00:12:37.279 --> 00:12:40.839 these into our PSUs. 00:12:41.519 --> 00:12:47.360 You didn't bring the 12 pin. Really? They don't include it anymore? Well, I 00:12:46.079 --> 00:12:52.560 guess this is an opportunity to talk about our sponsor, Threat Locker. They take a different approach to keeping 00:12:50.320 --> 00:12:56.480 your company's network safe. Following zero trust principles, Threat Locker 00:12:54.560 --> 00:13:00.800 proactively blocks everything by default, only allowing what you decide 00:12:58.880 --> 00:13:04.320 is absolutely necessary for your team to be productive. This approach means 00:13:02.480 --> 00:13:07.839 Threat Locker doesn't require a lot of system resources. And it does more than 00:13:06.480 --> 00:13:12.800 just limit which applications can be run. Elevation control allows standard 00:13:10.240 --> 00:13:16.880 users to run specific applications with local admin privileges without ever 00:13:14.959 --> 00:13:20.639 having that unnecessary privilege as a user. And threat locker detect 00:13:18.880 --> 00:13:24.959 continuously monitors the behavior of trusted and untrusted applications and 00:13:23.120 --> 00:13:28.800 will automatically respond based on the rules created by your IT specialists. 00:13:27.200 --> 00:13:32.399 These policies are enforced in milliseconds whether or not your 00:13:30.399 --> 00:13:37.440 endpoint is connected to the internet. Do you see this? What the 00:13:35.600 --> 00:13:42.560 mine? No. No. This has got to be a driver issue. It's got to be a driver issue. Maybe my drivers didn't auto 00:13:40.320 --> 00:13:48.000 install or my drivers probably took so long to autoupdate to the new card that 00:13:45.440 --> 00:13:50.720 they that they haven't updated yet. Startup scan and pro. Oh my god. Oh, 00:13:49.600 --> 00:13:55.600 your internet was off when you you booted up, too, cuz the cable fell out. Okay. Yeah, that's probably the issue. 00:13:53.600 --> 00:14:01.880 Okay. Okay. Okay. Okay. It was a driver issue getting new ones installed. It's 00:13:58.320 --> 00:14:03.839 freaking warm. Great hoodie. Terminally 00:14:01.880 --> 00:14:09.360 online. But I'm too warm to wear it right now. Here we go. Holy, 00:14:06.920 --> 00:14:13.519 dude. We're still in the loading screen and I'm pretty sure my CPU usage is 00:14:11.199 --> 00:14:17.360 higher than last time. It's not good. I'll tell you that much. Cuz I'm at 00:14:14.800 --> 00:14:22.000 1,000 FPS in this loading screen now. Y I think this is going to impact it more. 00:14:19.199 --> 00:14:24.959 My clock speed is lower than it was compared to yours. I think 00:14:24.000 --> 00:14:30.079 it's still going to be pretty respectable. I think so to be clear. 00:14:27.440 --> 00:14:35.839 Wow. Let's let it settle in a little bit because you never know. Here, let's walk 00:14:32.160 --> 00:14:38.560 up the stairs. All right. So there is no 00:14:35.839 --> 00:14:42.399 doubt that if you have enough overhead, you can 00:14:39.800 --> 00:14:45.839 absolutely impact the ability to run games at maximum performance. You're 00:14:44.000 --> 00:14:52.480 about 20 frames lower than me, but realistically, we're looking at an RTX 00:14:48.880 --> 00:14:54.720 5080, right? Yeah. And I'm only running 00:14:52.480 --> 00:14:59.040 about 20 FPS lower than you. It's really not bad in a pretty CPUbound game. With 00:14:57.440 --> 00:15:03.079 all of that said, it's very clear that these AV programs are heavy enough to 00:15:01.279 --> 00:15:07.600 run that they can impact system performance, which isn't to say that 00:15:05.360 --> 00:15:12.399 they're unnecessarily bloated. They're just doing a lot. Let's go back to our 00:15:10.160 --> 00:15:17.920 history lesson. First introduced by McAfee in 2008, cloud-based antivirus 00:15:15.760 --> 00:15:23.360 uses kind of the best of both worlds. Heristic detection to identify the 00:15:20.240 --> 00:15:26.320 behavior of suspicious files and 00:15:23.360 --> 00:15:31.279 constant checking against a continually updated online database of threats, 00:15:28.880 --> 00:15:36.880 taking advantage of the spread of always on internet connections. It was a really 00:15:33.920 --> 00:15:42.000 good idea, but Microsoft was about to upset the game board. After years of 00:15:39.920 --> 00:15:47.839 ruthless attacks from Apple targeting Windows's security, Microsoft acquired 00:15:44.880 --> 00:15:52.399 giant anti-spyware in late 2004 and quietly started work on what would 00:15:49.360 --> 00:15:54.399 become Microsoft Defender Antivirus. 00:15:52.399 --> 00:15:59.519 Starting with Windows 8, Defender was enabled on Windows PCs by default, 00:15:57.040 --> 00:16:04.320 switching itself off if a third party AV tool was installed. And over the years, 00:16:01.920 --> 00:16:10.320 Defender has evolved to the point where those third party AV tools are less 00:16:06.959 --> 00:16:12.880 likely to feel needed. As of 2024, more 00:16:10.320 --> 00:16:17.519 than half of American users use built-in antivirus protection like Microsoft 00:16:14.880 --> 00:16:22.639 Defender or Apple's XProtect. And of those that use a third party solution, 00:16:19.360 --> 00:16:24.399 only about half use a paid product. As a 00:16:22.639 --> 00:16:28.639 result, recent years have seen significant consolidation in the 00:16:25.839 --> 00:16:32.639 antivirus market. Intel bought McAfee back in 2010 only for it to end up in 00:16:30.720 --> 00:16:36.560 the hands of Advent International, a private equity firm that is rumored to 00:16:34.160 --> 00:16:41.560 be eyeing Trend Micro as well. And we mentioned Gen Digital earlier, formerly 00:16:38.639 --> 00:16:45.680 Norton, who now owns four major AV brands. Other major brands have shifted 00:16:43.920 --> 00:16:49.920 their sites to corporate clients with NextG Endpoint Protection and Management 00:16:47.680 --> 00:16:54.000 Solutions, leaving the home market to lesserk known antivirus solutions, some 00:16:51.920 --> 00:16:57.600 of which we installed here today. Before we go, then let's see how they handle 00:16:55.600 --> 00:17:00.320 this little selection of malware that we've prepared for them. Oh, we're going 00:16:59.199 --> 00:17:06.160 to intentionally infect them. We're going to remove the Ethernet. Oh, you did. Oh, no. You didn't. Are we? 00:17:04.480 --> 00:17:08.959 I mean, they should be safe, right? They should be fine. Oh, this makes me deeply 00:17:07.760 --> 00:17:12.799 uncomfortable. Jordan, they're mostly just test files. Okay. Mostly. Okay. 00:17:11.120 --> 00:17:19.839 What do you want me to Oh, threat blocked. Hey, the system 00:17:17.240 --> 00:17:23.679 works. Maybe. Oh, potential threat block. Oh, infected file move to 00:17:22.079 --> 00:17:27.839 quarantine full. I mean, maybe you are safer. Maybe I am 00:17:26.160 --> 00:17:32.240 safer. Nothing happened here yet. I feel safer. Okay. What am I supposed to try 00:17:29.679 --> 00:17:36.799 to do? Ah, whatever you want here. Open up the danger zone. Open the danger 00:17:33.520 --> 00:17:38.120 zone. Okay. Jokes. Yeah. Run something 00:17:36.799 --> 00:17:42.799 in there. It'll be fine. Oh my god. Avoid.exe. Threat blocked. Good. Oh, 00:17:40.640 --> 00:17:46.720 it's gone. Good. It's gone. Boom. Just like that. How about Vista? 00:17:45.200 --> 00:17:51.760 Cannot access. It's still freaking out in the bottom corner here. It's malware 00:17:48.400 --> 00:17:54.960 stopped. Windows chilled Windows. I'm 00:17:51.760 --> 00:17:57.039 It's working. 00:17:54.960 --> 00:18:00.799 Chilled Windows cannot access. Oh, dude. I think I think it's just removing. Oh, 00:17:58.559 --> 00:18:04.880 there we go. I finally got a popup. Threats found. Yep. 00:18:03.440 --> 00:18:09.039 Okay, so it's stopping me from doing it, too. Also working. 00:18:07.120 --> 00:18:13.440 Mine's a lot more calm about it. They're working. Yeah. 00:18:11.840 --> 00:18:17.360 And that was even after I told them, hey, look, don't bother scanning this 00:18:14.880 --> 00:18:22.000 thing. Yeah, that's pretty cool. The point today was not to answer, you know, 00:18:19.760 --> 00:18:26.000 which of these antivirus suites is the best? That was not what we set out to 00:18:23.440 --> 00:18:31.039 do. What we set out to answer was, is more better? The answer is no. Pick one 00:18:28.880 --> 00:18:36.720 good tool for real-time monitoring. And then if you must run additional tools, 00:18:33.360 --> 00:18:38.559 just run them as single time scans. And 00:18:36.720 --> 00:18:41.520 don't discount Microsoft Defender. I mean, it did work against all these 00:18:40.080 --> 00:18:45.200 threats. Found the problems here, even if it might not find every threat. And 00:18:43.760 --> 00:18:50.240 if you want enterprise or business protection, you're going to want to check out something entirely different, 00:18:48.559 --> 00:18:54.320 like from Threat Locker, who sponsored this little experiment. We're going to have a link to them in the video 00:18:52.880 --> 00:18:59.120 description. If you guys enjoyed this video, uh maybe you like the vibe of how 00:18:56.799 --> 00:19:04.480 many USB devices can you plug into one computer. That was a lot of well, it was 00:19:01.200 --> 00:19:04.480 pain, but also fun.