I've got a bat right there that can destroy any computer, 100% guaranteed

>>16568 >anyone knows how to create a .bat file that kills computers? Something like this?: @echo off :uji start goto uji exit What this code basically does is to open a "Command Prompt" window, hide the text output (or at least I think that's what the @echo off was for), open another console window and jump to the second line creating an infinite loop. I can confirm that it works on Windows XP, but I don't know if it still works on newer versions of Windows.

>>16568 the only way to "kill" a computer via software is to make it overheat or to flash a corrupt firmware. both of those risks have been mitigated on modern PCs. thermal throttling has been figured out, and motherboards wont accept an unsigned BIOS update. if you are a super hacker maybe you can forge the BIOS signature somehow. fucking up someone's operating system installation doesn't "kill" the computer.

>>16568 Any modern operating system is going to protect itself from the user doing something REALLY stupid. You may get >>16802 's fork bomb to work. That's a sensible attack. However, running any commands that will actually harm Windows requires running the batch file as Administrator.

>>16568 >open notepad >write "start" 10 times >copy/paste LOTS of times >save file as [fake name].bat >open properties and give it a fake icon too >hilarity ensues This batch file just opens the command prompt window for as many times as you copy/paste "start" until the PC crashes. For maximum effect give it a misleading name and disguise it as another program. I did this in the highschool computer lab, replacing Internet Explorer with an identical looking .bat bomb

>>17003 I just tried this on my pc, it still works without needing to run as admin. Modern computers can open cmd a lot of times, so make sure to copy/paste for like 5 minutes and NO TYPOS or it will stop the program prematurely. Have fun.

>bat Max you can get is make his computer crash with a forkbomb