The reason why the file explorer shows "KAMIKAZE" is because there's an HTML file in every system folder, including the root of the drive, that replaces all the UI inside the file explorer frame. Of course it got replaced with the word "KAMIKAZE".
I'm honestly shocked that Win98 restarted in the normal way. I'm fairly certain that the dialog calls some DLL routine with RUNDLL32 to initiate shutdown.
RUNDLL32 is just a helper program that can execute functions from DLLs (and technically only those that are designed for it). The shutdown window belongs to Explorer and any libraries used by it couldn't be overwritten.
@@D0Samp in this case, explorer.exe init's shutdown from the user shell interface "USER.EXE" since it is loaded first into memory and can't be overwritten.
@@DayreaverNoFake Okay I just revisited this video and saw this. I scrolled pretty far down and eventually found the comment you're talking about. I actually don't know if I stole this or not because I barely remember writing this comment and you can't even tell because they both say "2 years ago" So maybe I did, who knows? :)
I tried to write a file infector in C a few years ago. It could successfully infect some programs, but it only worked on Windows XP and crashed frequently. File infectors are hard to get right, apparently. At least malware failing can still be very entertaining.
And sadly file infecting annoyers aren't much of a thing anymore. Too hard to do, and no money for the author. That's why everyone moved to Trojans, ransomware, and other forms of malware.
i'd imagine trying to get the software/files/whatever to still function after injecting your own code into them is a recipe for disaster unless you really know what you're doing
I like how at 10:51 you can already see the system font falling apart, it's quite subtle at first - it no longer showed some of uppercase characters in the window title bar!
Prime example at 11:50 of what happens if you kill both fontdrvhost.exe processes, you get nothing but icons and no text. Everything will go back to normal with a simple logout/login.
Brilliant, as always. You can start typing the executable name in a focused explorer window to get to it quicker. Takes way less than scrolling through the directory :)
I appreciate the first warning dialogue, that has to be a power trip,ime "hey im going to fuck you up but only if you ask for it, I could fuck you up, if you dared me"
The fact that this virus was written in C means it should be excused of it's glitches and bugs, from programming C++ I believe that C is very difficult and can make you think that the compiler is broken even though it is fine. And besides, the way it manages to hijack the system like it does impresses me
What are you talking about? Tons of highly stable programs are written in C and C++, including almost all of Windows (and many prominent Microsoft apps). If there are any bugs that's entirely down to the author not knowing the language and its quirks well enough or just plainly being a bad programmer. If anything C is significantly easier to learn than C++, albeit probably a bit harder to use, but nothing a good programmer couldn't deal with
@@BenKerman This is just my experience. I've only used it for less than a year and while programming I occasionally find random bugs, such as the compiler erroring out stating that the cause is within the compiler (as opposed to the line which triggered that error). It is possible that the author has just as much experience as I have (if not a bit more) plus they likely haven't thoroughly tested it as well. Thus leading to a buggy program.
@@Jobby_Jamesit's probably more a function of it being very difficult to debug while it's actively running and overwriting itself. It's also possible the virus was designed to work correctly to patch a particular PE (portable executable I.e. .exe file) file with a particular header, but cannot dynamically patch by interpreting each header and correctly patching only what it needs to (dynamically changing code section size, program entry point, etc.). If I get bored tomorrow I might find a sample and reverse engineer it to check my theory
i love/miss the simple and very efficient/productive/snappy interface of 98 with the sounds and all. Miliseconds to do anything. Now the FRIGGING CONTEXT MENU HAS A SCROLLBAR WWTTFFFFFFFFFFFFFFFFFFFFFF
@@Aura_Mancer shut the heck up, linux is one of the worst OSes ever, where almost nothing works out of the box and everything is just irritatingly incomplete. The entire OpenSource community is a big fat cargo cult.
@@dimitar4y That hasn't really been true for quite a while. Not to mention the fact that your only alternatives are something which is even *more* restrictive (OSX), out of date and vulnerable as hell (Windows 7-), or which is loaded with bloatware and *literal spyware* (Windows 10+).
@@dusklunistheumbreon linux has plenty of vulnerabilities and outdated/restricted libraries, and half the libraries/software are bloatware that requires other bloatware that requires other bloatware that requires a version that doesn't exist, in order to compile, in a bash script that isn't annotated with vague hidden errors. Only mentally ill liberals use linsux.
This thing doesn't really scream "written in C" to me. Rather, after some pretty much bare level reverse engineering, it screams "poorly modified from CIH". Not only does it use very similar (read: nigh exactly the same) code for setting up the sidt ring0 vulnerability up (which plausibly could have been in another zine explaining it, in fact in doing research I actually found another page describing it from the era that used original code to explain it), it actually uses the exact same interrupt number as CIH (which... is a bit less plausible to have been duplicated, to be nice about it.) Couple that with extremely hacky modifications to the file infection code (which is also mostly taken from CIH), and you have Kaze. As an aside, Caw also re-uses the CIH code for entering ring 0 and seemingly file infection, but its instability can be pretty much boiled into one thing: the author removed a ton of sanity checking when entering ring0 (including checks for if the virus was already resident...... yep.), which typically causes it to attempt going resident more than once...
"Thank you for joining me here yet again. It really means a lot to me" genuinely could not live with myself if i missed a video. Still thinking about a video where you referenced "hope I don't lose my EverQuest details" because i still play that game lmao
I have a question about the Kaze virus. Is it able to affect a running process? I'm not really sure where or what processes are in Windows so I figured I'd ask. If it can't then the Notepad process should never been affected by the virus and only the file on disk.
Hey Dan, a while ago i was scrolling through your videos and there was lots of “safety” videos. (one of the topics was illegal street racing) Whatever happened to those?
I was always curious how viruses managed to infect files. Now I know that for interpreted command and programming languages (such as VBS, JavaScript, BAT, Macros, Python, maybe SQL files [but propably it wouldn't be able to edit another files from the script and spread through mere database and would need executable/script in order to infect SQL]) it's quite simple - you just add commands or functions at the end of the file and hook it up for execution. Pretty straight-forward. I'm sure I'd be able to make JS or PHP infecting virus with my current developer knowledge. Yet I wonder how it is able to infect compiled programs (EXE, JAR, APK etc. etc.). Yet I have no idea how a program could attach its code to the compiled executable, my guesses are de-compiling the code and attaching itself to the main function (like public static void main() in Java after decompiling), using reflection mechanism (again, one of my first ideas when I think how to infect java executables) or decompiling executable to the assembly code in order to attach itself (AFAIK mainly in the DOS era). I am very curious from the technical point of view how infection process works and messes with the execs.
A compiled exe is just a list of instructions, right? I figure it would be easy enough to just throw in your own list of instructions and then when the program gets there it just starts running them. No idea how you’d do that without crashing or without hindering the original app functionality…
@@JKTCGMV13 Yeah. It's just a list of instructions (a machine code, to be exact) but different languages compile the sources to the machine code [or bytecode like in Java or C# cases and deritatives like Kotlin or F#] in a different way (well, even different compilers for the same language do it differently). I think it would be relatively easy (without knowledge of machine code architecture and featuers) to infect execs designed in the same programming language as the virus. After a brief research I found that one could disassembly (revert machine code to assembly code) executable thus providing a way to inject its code to the infected file. Propably thats the main way of infecting files, still requiring a lot of knowledge, not only about language that hacker uses and how it's assembled but also about the assembly and machine code itself.
You don't need to go as far as decompiling. Exe files contain metadata that tells which parts of the file are executable, which are data, their sizes, where they should be loaded in mem, where execution should start, etc. This, paired with the fact that a exe file generally has a lot of empty space is enough to infect it. It's possible to patch the executable to have it execute arbitrary code when it starts, or look for specific sequences of instructions that are common and patch those.
I suppose if he used one of those SD-or Flash-card readers you plug into an old computers IDE-interface instead of a mechanical harddrive, he could have images of fresh installs ready to just easily copy to an SD- or Flashcard, but I think he does it manually with diskettes for DOS or CD’s for Windows.
i know that he historically (and probably still) did not; during the now deleted ampdan1 viewer special 2, he showed off how he had his windows 98 key memorized, so he had to do it by hand.
Dan mentally struggled with asking his viewers for submissions of malware. The fact that some of the samples did end up in the wild was pretty alarming as well to say the least. He has no desire to reopen submissions.
I completely agree with the captions on 4:24, modern BSoDs ain't very informative, even a software like BlueScreenViewer is not helpful, I used to have BSoDs with completely different error codes while my drivers and hardware are completely OK (as I guess). Nobody even on Microsoft forums were able to help me.
Use Winaero Tweaker and you can restore the NT 3.1 blue screens that were used all the way up through NT 6.1 (Windows 7) that were replaced in NT 6.2 (Windows 8.0)
When i heard December 7 i felt chills down my spine... December 7 is the day i first deactivated my deviantart account when i thought it was a good idea to attack some questionable artists
@@RedPawner hmm…I guess you realized that the NSFW stuff is more common than anything else on DA lol, there’s a way higher demand for it than safe art imoe. Still, that’s a very random thing to bring up 😂
>video is 15 minutes long
>starts with dan immediately talking about how horribly the virus is written
it's gonna be one of those videos isn't it
it's like "when viruses fail: the movie"
hello squimpus! i like your art
What are you doing here, *criminal-ly* underrated analog horror creator!
The best kind of videos.
Man I literally went from wendigoons video to this. Love your content man!
The virus corrupting itself actually makes it true to it's name :)
Wind?
My bad, I failed to watch 20 seconds before commenting.
Exactly.
Kamikaze virus. Takes out the system and itself with it...
this is the biggest takeaway for sure.
For anyone not aware, December 7th was the day that Japan attacked Pearl Harbor, which is the connection to the "kamikaze" part
A date which will live in infamy.
A date which will live in infamy
the divine wind
@@betaversion9654 bruh
@@imveryangryitsnotbutter hehehe
What an uncharacteristically polite virus asking you for permission before attempting to do anything untoward.
It was probably just an experiment from some student
The reason why the file explorer shows "KAMIKAZE" is because there's an HTML file in every system folder, including the root of the drive, that replaces all the UI inside the file explorer frame. Of course it got replaced with the word "KAMIKAZE".
I'm honestly shocked that Win98 restarted in the normal way. I'm fairly certain that the dialog calls some DLL routine with RUNDLL32 to initiate shutdown.
Maybe it's loaded in RAM?
RUNDLL32 is just a helper program that can execute functions from DLLs (and technically only those that are designed for it). The shutdown window belongs to Explorer and any libraries used by it couldn't be overwritten.
@@D0Samp in this case, explorer.exe init's shutdown from the user shell interface "USER.EXE" since it is loaded first into memory and can't be overwritten.
The feature of the virus corrupting itself is definitely making it true to it's name!
stolen comment?
@@DayreaverNoFake Unfortunately not. I cant even find the other comment that you're talking about.
@@realausome the comment says "The virus corrupting itself actually makes it true to it's name :)", i dont know if it was posted before or after
@@DayreaverNoFake Okay I just revisited this video and saw this. I scrolled pretty far down and eventually found the comment you're talking about. I actually don't know if I stole this or not because I barely remember writing this comment and you can't even tell because they both say "2 years ago"
So maybe I did, who knows? :)
I tried to write a file infector in C a few years ago. It could successfully infect some programs, but it only worked on Windows XP and crashed frequently. File infectors are hard to get right, apparently. At least malware failing can still be very entertaining.
Bruh das sad
Yeah, file infection is one of those things that are hit or miss, because of how stuff gets run and interpreted around.
At least Trojan is a thing.
And sadly file infecting annoyers aren't much of a thing anymore. Too hard to do, and no money for the author. That's why everyone moved to Trojans, ransomware, and other forms of malware.
i still need to revisit mine
i'd imagine trying to get the software/files/whatever to still function after injecting your own code into them is a recipe for disaster unless you really know what you're doing
this feels like a strange thing to mention, but that low humming background ambient noise in this is really calming.
I like how at 10:51 you can already see the system font falling apart, it's quite subtle at first - it no longer showed some of uppercase characters in the window title bar!
- called "kaze"
- doesn't run on the n64
Prime example at 11:50 of what happens if you kill both fontdrvhost.exe processes, you get nothing but icons and no text. Everything will go back to normal with a simple logout/login.
I just wanna take a moment to appreciate the CC going on in this video. Made it just a little bit more fun.
The CC messages are so sweet. Thank you for making these videos, they're very enjoyable!
Brilliant, as always. You can start typing the executable name in a focused explorer window to get to it quicker. Takes way less than scrolling through the directory :)
:O Enderman!
Cool you are interested in dan as well as me! Sub is for both of you!
And also, you know, these videos are in a average PC person of 2000
You always could've.
The 2 compoot removers
Seeing these back-to-back brings back a ton of nostalgia for how amazing Windows XP looked and felt after the 95/98/Me design
2:39 LMAO " contact the system administrator.... hold on thats me... i dont know how to fix this???"
I appreciate the first warning dialogue, that has to be a power trip,ime "hey im going to fuck you up but only if you ask for it, I could fuck you up, if you dared me"
I LAUGHED SO HARD WHEN THE C DRIVE SAID KAMIKAZE
11:56
Danooct1: There seems to be something missing,
Homestar Runner: Your computer needs wouds.
7:14 I am glad that you are here, and I am grateful that I can be here to enjoy your videos.
The fact that this virus was written in C means it should be excused of it's glitches and bugs, from programming C++ I believe that C is very difficult and can make you think that the compiler is broken even though it is fine. And besides, the way it manages to hijack the system like it does impresses me
What are you talking about? Tons of highly stable programs are written in C and C++, including almost all of Windows (and many prominent Microsoft apps). If there are any bugs that's entirely down to the author not knowing the language and its quirks well enough or just plainly being a bad programmer. If anything C is significantly easier to learn than C++, albeit probably a bit harder to use, but nothing a good programmer couldn't deal with
@@BenKerman This is just my experience. I've only used it for less than a year and while programming I occasionally find random bugs, such as the compiler erroring out stating that the cause is within the compiler (as opposed to the line which triggered that error). It is possible that the author has just as much experience as I have (if not a bit more) plus they likely haven't thoroughly tested it as well. Thus leading to a buggy program.
@@Jobby_Jamesit's probably more a function of it being very difficult to debug while it's actively running and overwriting itself.
It's also possible the virus was designed to work correctly to patch a particular PE (portable executable I.e. .exe file) file with a particular header, but cannot dynamically patch by interpreting each header and correctly patching only what it needs to (dynamically changing code section size, program entry point, etc.). If I get bored tomorrow I might find a sample and reverse engineer it to check my theory
i love/miss the simple and very efficient/productive/snappy interface of 98 with the sounds and all. Miliseconds to do anything. Now the FRIGGING CONTEXT MENU HAS A SCROLLBAR WWTTFFFFFFFFFFFFFFFFFFFFFF
If you aren't into gaming, try linux. Kubuntu can be similar to Windows, and is very snappy.
Even if you're into gaming, Linux works just fine now.
Steam Proton allows you to run pretty much any game without needing to bother with WINE
@@Aura_Mancer shut the heck up, linux is one of the worst OSes ever, where almost nothing works out of the box and everything is just irritatingly incomplete. The entire OpenSource community is a big fat cargo cult.
@@dimitar4y That hasn't really been true for quite a while.
Not to mention the fact that your only alternatives are something which is even *more* restrictive (OSX), out of date and vulnerable as hell (Windows 7-), or which is loaded with bloatware and *literal spyware* (Windows 10+).
@@dusklunistheumbreon linux has plenty of vulnerabilities and outdated/restricted libraries, and half the libraries/software are bloatware that requires other bloatware that requires other bloatware that requires a version that doesn't exist, in order to compile, in a bash script that isn't annotated with vague hidden errors. Only mentally ill liberals use linsux.
7:13 np :) Also only channel I put cc on. Really like the idea of thanking viewers without cluttering the video itself with actual video edits.
Kaze:*kills solitude*
Solitude:*dies*
danooct1:*revenge mode activated*
Kaze: *makes suicide in windows xp*
7:43 made me realize that I need a floppy clicker
This thing doesn't really scream "written in C" to me. Rather, after some pretty much bare level reverse engineering, it screams "poorly modified from CIH". Not only does it use very similar (read: nigh exactly the same) code for setting up the sidt ring0 vulnerability up (which plausibly could have been in another zine explaining it, in fact in doing research I actually found another page describing it from the era that used original code to explain it), it actually uses the exact same interrupt number as CIH (which... is a bit less plausible to have been duplicated, to be nice about it.) Couple that with extremely hacky modifications to the file infection code (which is also mostly taken from CIH), and you have Kaze.
As an aside, Caw also re-uses the CIH code for entering ring 0 and seemingly file infection, but its instability can be pretty much boiled into one thing: the author removed a ton of sanity checking when entering ring0 (including checks for if the virus was already resident...... yep.), which typically causes it to attempt going resident more than once...
Kaze, that name sounds familiar.
Thank you..for providing the content professionally
glad you're still making these vids after all these years
"Thank you for joining me here yet again. It really means a lot to me" genuinely could not live with myself if i missed a video. Still thinking about a video where you referenced "hope I don't lose my EverQuest details" because i still play that game lmao
wow, this new upload schedule is awesome
I love this 2001-like style of these videos, kinda showing what an user that got it would do (or an IT dude explaining it)
It's a good day when you upload Mr. virus man.
Never forget that you are appreciated. We just wish you'd post more videos :P
Happy that you are still uploading :)
The XP font thing reminds me of when I accidentally deleted my selected UI font in Linux and had pretty much the exact same effect
I love the sound that the Win98 machine makes. So relaxing.
I absolutely adore the wallpapers.
Have you ever thougt of doing a 10hr video of recorded disk drive seeking noise? That would be awesome.
Really love the CC on the recent videos! Gives me a good chuckle.
Back once again, bringing you a classic Win32 Virus. Enjoy.
Always looking forward to this content 😊
13 years and he’s still going wow
Nice to see a virus that works on two different OS, the payload was crazy
It probably also works in NT 4.0, 2000 and ME. It possibly has another crazy payloads for those versions.
World: destroyed
Solitaire: still playablr
Danooct1: YES
Just before Windows XP restarts I can see a glimpse of the BSOD
I love his voice and the subtitles
Plan on using Windows 2000 in future videos?
How the fuck did this even spread far enough to be found by malware researchers? Lmao
I know right, probably got directly submitted or someone dropped into Kazaa folder.
welcome back king
8:31 can't you just type calc to find it quick? or was that not a thing yet in xp?
Nope not yet! that was introduced in Vista. However you can just use calc.exe in the run dialog as C:\Windows\System32 is in the PATH
Oh wow meme master watching dannoct1 amazing
lol we thought u knew better kmlkmljkl
I have a question about the Kaze virus. Is it able to affect a running process?
I'm not really sure where or what processes are in Windows so I figured I'd ask.
If it can't then the Notepad process should never been affected by the virus and only the file on disk.
the computer might've bsoded when it reset but it was prob so fast you didnt see it.
try redoing it with automatic restart on failure disabled.
this is actually how kaze emanuar makes all the chaos64 hacks
Kaze.. that name reminds me of the time when I played roblox and I saw a noob that had a display name with "Kaze" and he was rlly kind 🗿
"Congraturation!"
Your computer got 風邪！
2:30 my school's computers displayed that message so many times, so I can see the message text hasn't changed at all even since Windows 98
*sad cat meme for calc*
Your spoiling us dan.
Yo, a Super Mario 64 modder?
*runs Kaze* where are my Super Mario 64 mods.
huh, huh, huh, huh,
Been a while since I've seen this guys videos
Hey Dan, think we'll ever see classic Mac malware make an appearance on your channel?
Hey Dan, a while ago i was scrolling through your videos and there was lots of “safety” videos. (one of the topics was illegal street racing) Whatever happened to those?
What did the virus do to Windows XP's fonts?
I was always curious how viruses managed to infect files. Now I know that for interpreted command and programming languages (such as VBS, JavaScript, BAT, Macros, Python, maybe SQL files [but propably it wouldn't be able to edit another files from the script and spread through mere database and would need executable/script in order to infect SQL]) it's quite simple - you just add commands or functions at the end of the file and hook it up for execution. Pretty straight-forward. I'm sure I'd be able to make JS or PHP infecting virus with my current developer knowledge. Yet I wonder how it is able to infect compiled programs (EXE, JAR, APK etc. etc.). Yet I have no idea how a program could attach its code to the compiled executable, my guesses are de-compiling the code and attaching itself to the main function (like public static void main() in Java after decompiling), using reflection mechanism (again, one of my first ideas when I think how to infect java executables) or decompiling executable to the assembly code in order to attach itself (AFAIK mainly in the DOS era).
I am very curious from the technical point of view how infection process works and messes with the execs.
A compiled exe is just a list of instructions, right? I figure it would be easy enough to just throw in your own list of instructions and then when the program gets there it just starts running them. No idea how you’d do that without crashing or without hindering the original app functionality…
@@JKTCGMV13 Yeah. It's just a list of instructions (a machine code, to be exact) but different languages compile the sources to the machine code [or bytecode like in Java or C# cases and deritatives like Kotlin or F#] in a different way (well, even different compilers for the same language do it differently). I think it would be relatively easy (without knowledge of machine code architecture and featuers) to infect execs designed in the same programming language as the virus.
After a brief research I found that one could disassembly (revert machine code to assembly code) executable thus providing a way to inject its code to the infected file. Propably thats the main way of infecting files, still requiring a lot of knowledge, not only about language that hacker uses and how it's assembled but also about the assembly and machine code itself.
You don't need to go as far as decompiling. Exe files contain metadata that tells which parts of the file are executable, which are data, their sizes, where they should be loaded in mem, where execution should start, etc. This, paired with the fact that a exe file generally has a lot of empty space is enough to infect it. It's possible to patch the executable to have it execute arbitrary code when it starts, or look for specific sequences of instructions that are common and patch those.
I wonder if Dan reinstalles DOS/Windows 98/XP manually after every video with real PC or uses some special tools to install OS fastly.
I suppose if he used one of those SD-or Flash-card readers you plug into an old computers IDE-interface instead of a mechanical harddrive, he could have images of fresh installs ready to just easily copy to an SD- or Flashcard, but I think he does it manually with diskettes for DOS or CD’s for Windows.
i know that he historically (and probably still) did not; during the now deleted ampdan1 viewer special 2, he showed off how he had his windows 98 key memorized, so he had to do it by hand.
@@SoulcatcherLucario Why was it deleted?
Hey Dan, will you ever bring back Viewer-Made Malware or is it gone for good? Just a question.
Dan mentally struggled with asking his viewers for submissions of malware. The fact that some of the samples did end up in the wild was pretty alarming as well to say the least. He has no desire to reopen submissions.
@@PsychoFizz ah okay. Thanks for letting me know!
@@shirleydotxml my pleasure! Enjoy the rest of your day
I would make a joke of things breaking in your videos, but I think thats already a must :p
rip Solitaire, you will be missed
"Soap Bubbles, the inferior version of bubbles... is still there"
lmfao
I appreciate the added comments in the captions lol
Yeah Baby! That’s what I’ve been waiting for! Thats what it is all about!
WOOOOO
Hey man, could you try out the .ssoi ransomware? Just got my computer infected and I wanted to cope by seeing you try it. Thanks.
thank you dan, very cool!!! seriously
Imagine using that computer still after windows 11 is released
What a bummer. No blue sceen of death.
Actually, at 13:25, it did for a fraction of a second and then rebooted...
That droning sound makes this video feel so ominous.
I completely agree with the captions on 4:24, modern BSoDs ain't very informative, even a software like BlueScreenViewer is not helpful, I used to have BSoDs with completely different error codes while my drivers and hardware are completely OK (as I guess). Nobody even on Microsoft forums were able to help me.
Use Winaero Tweaker and you can restore the NT 3.1 blue screens that were used all the way up through NT 6.1 (Windows 7) that were replaced in NT 6.2 (Windows 8.0)
god, this was from a year ago? I thought it was from ages ago
why did you do older videos (but not bad videos!)
shoutouts to simpleflips
Kamikaze indeed
Where's Rogueamp? :(
Heh it's fitting to be called kamikaze since it kills itself when it infects everything.
10:00 Filesytem is still there lol
Only the real ones see the messages in the captions ❤
When i heard December 7 i felt chills down my spine... December 7 is the day i first deactivated my deviantart account when i thought it was a good idea to attack some questionable artists
r/oddlyspecific
Elaborate?
ok
Wait wha-
@@Dragoneer From august to december 2015 i harassed deviantart artists for drawing no no art
@@RedPawner hmm…I guess you realized that the NSFW stuff is more common than anything else on DA lol, there’s a way higher demand for it than safe art imoe. Still, that’s a very random thing to bring up 😂
Nice Video!
10:51 I see some font corruption!
kaze reminds me of sm64
me when emanuar
Amazing
12:48 someone's gonna remove the "a" from agai so it sounds like "gay" and make a ytp with it
HIDDEN FILE EXTENSIONS?! WHAT KIND OF MONSTER!??!?!
Shonan no Kaze
13:26 if you pause quick enough you can see a BSOD
That WinXP settings window with no text is how 99% of Windows users see these kinds of windows
Source: am the computer guy in my family
13:25 Wow, if you watch the video in 0.25 speed, you can see the computer BSOD!
Twisted Metal
Bro nice streak…