1
00:00:00,000 --> 00:00:03,240
You know those prescription drug commercials that list so many side effects

2
00:00:03,240 --> 00:00:07,040
that the medicine actually sounds worse than whatever it was supposed to treat?

3
00:00:07,040 --> 00:00:11,720
Well, in the software world, we end up with the same thing more often than you might think

4
00:00:11,720 --> 00:00:16,880
where an update that's supposed to make your gadget work better ends up just breaking it.

5
00:00:16,880 --> 00:00:21,120
Here are four infamous examples of updates that went terribly wrong,

6
00:00:21,120 --> 00:00:25,120
starting with everyone's favorite operating system, good old Windows.

7
00:00:25,120 --> 00:00:28,200
Microsoft is certainly no stranger to royally cheesing off its users

8
00:00:28,200 --> 00:00:33,000
with the botched launches of Windows 98, ME, Vista, heck, even Windows 11,

9
00:00:33,000 --> 00:00:37,480
getting plenty of press coverage. But in 2012, there was a lesser-known glitch

10
00:00:37,480 --> 00:00:41,360
that frustrated lots of people at a very inopportune time.

11
00:00:41,360 --> 00:00:44,760
Microsoft pushed out an update to the .NET framework,

12
00:00:44,760 --> 00:00:47,920
which is basically a programming ecosystem for Windows

13
00:00:47,920 --> 00:00:53,040
to make writing programs easier. .NET was already infamous for botched updates,

14
00:00:53,040 --> 00:00:58,920
but this one was particularly egregious as it screwed up installations of TurboTax,

15
00:00:58,920 --> 00:01:03,480
an extremely popular program for preparing tax returns in the United States.

16
00:01:03,480 --> 00:01:09,800
Specifically, users that installed the bad update found it impossible to print out their tax forms.

17
00:01:09,800 --> 00:01:16,640
The kicker was that this update was pushed out just before April 15th, the US tax filing deadline.

18
00:01:16,640 --> 00:01:20,680
Fortunately, there was a pretty easy workaround, but seeing as this wasn't the first time

19
00:01:20,680 --> 00:01:26,120
a .NET update broke tax software, I can't imagine the however many thousands of accounts

20
00:01:26,120 --> 00:01:30,920
that use Windows were super happy about it. Moving on, we're gonna go to 2013

21
00:01:30,920 --> 00:01:36,360
when the PlayStation 3 ruled the console world. Gamers who owned a PS3 with a larger hard drive

22
00:01:36,360 --> 00:01:39,920
got a very rude surprise when Sony pushed a firmware update

23
00:01:39,920 --> 00:01:44,440
that bricked their systems entirely. Ironically, Sony promised that the update

24
00:01:44,440 --> 00:01:48,840
would improve system stability, but shortly after it was released,

25
00:01:48,840 --> 00:01:52,120
the botched update spawned a nearly 100 page thread

26
00:01:52,120 --> 00:01:55,920
on Sony's forums with people desperate for a fix.

27
00:01:55,920 --> 00:01:59,920
Of course, bad updates do happen and people might have been a bit more understanding

28
00:01:59,920 --> 00:02:04,680
if Sony hadn't made the situation worse by allegedly recommending that a user

29
00:02:04,680 --> 00:02:11,000
send off their crippled PlayStation for service at a cost of $100 out of pocket.

30
00:02:11,000 --> 00:02:15,480
Sony did at least push out a fix a couple of weeks later, but you'd think they would have learned something

31
00:02:15,480 --> 00:02:18,760
from the fact that they were just sued four years earlier

32
00:02:18,760 --> 00:02:23,160
for another update that also bricked a bunch of PlayStation 3s.

33
00:02:23,160 --> 00:02:28,680
Of course, there was one glitch that was a heck of a lot more alarming than a busted PS3 or some late tax forms.

34
00:02:28,680 --> 00:02:33,120
One very uncomfortable glitch occurred on the International Space Station of All Places

35
00:02:33,120 --> 00:02:38,600
also back in 2013. The ISS gets its own software updates on an annual basis,

36
00:02:38,600 --> 00:02:44,160
and during one of those routine updates, a bug took out the entire ground communication system,

37
00:02:44,160 --> 00:02:48,560
meaning that the ISS had no way to talk to mission control back on Earth.

38
00:02:48,560 --> 00:02:53,320
Not only that, one of the crew members reported that they lost access to other crucial data

39
00:02:53,320 --> 00:02:58,200
about how the spacecraft was functioning. Fortunately, they were able to get everything working

40
00:02:58,200 --> 00:03:02,440
later on that same day. Funnily enough, the ISS switched a bunch

41
00:03:02,440 --> 00:03:06,800
of the laptops on board from Windows XP to Debian Linux just a few months later

42
00:03:06,800 --> 00:03:12,120
for stability and reliability. I guess they didn't want to take any more chances.

43
00:03:12,120 --> 00:03:17,360
Finally, let's circle back to Sony for an update that was so bad, most people actually considered it

44
00:03:17,360 --> 00:03:21,720
to be a virus. Back in 2005, Sony's music division

45
00:03:21,720 --> 00:03:24,920
built digital rights management into their audio CDs.

46
00:03:24,920 --> 00:03:30,480
Not super surprising given how popular file sharing was becoming, but Sony went way too far

47
00:03:30,480 --> 00:03:36,000
by including software that actually updated the operating systems code to prevent users

48
00:03:36,000 --> 00:03:40,660
from copying songs. And these modifications were hard to reverse

49
00:03:40,660 --> 00:03:45,580
and created serious security vulnerabilities. Actually, that does kind of sound like a virus.

50
00:03:45,580 --> 00:03:49,920
So Sony had basically put root kits on millions of computers.

51
00:03:49,920 --> 00:03:55,040
But then when people found out about it, Sony's response was to release an uninstall program

52
00:03:55,040 --> 00:04:00,740
that didn't actually uninstall anything and just made the security problems worse.

53
00:04:00,740 --> 00:04:04,400
After multiple lawsuits, including one from the government of Texas,

54
00:04:04,400 --> 00:04:10,000
Sony was forced to relent and give customers up to $150 to fix any computer damage

55
00:04:10,000 --> 00:04:14,240
that their root kits caused. Ironically, Sony used copyrighted software

56
00:04:14,240 --> 00:04:19,360
as part of its root kit without permission, which is shocking, as I know there's never been

57
00:04:19,360 --> 00:04:23,520
any hypocrisy from Big Tech when it comes to protecting their bottom line.

58
00:04:23,520 --> 00:04:27,720
Subscribe! There's no way outro written, so, ha ha!

59
00:04:27,720 --> 00:04:28,920
That's the outro!