Clear, practical technology insights BSOD Code Lookup · Windows Error Code Lookup · Wi-Fi Troubleshooting · PC Troubleshooting Checklist

Fake Virus: Troll Friends by Creating a 'Fake' Virus on Notepad

Get a clear overview of Fake Virus: Troll Friends by Creating a 'Fake' Virus on Notepad, why it matters, and what readers should know.

Table of Contents

This updated guide examines Fake Virus: Troll Friends by Creating a 'Fake' Virus on Notepad and organizes the essential facts, background, and practical takeaways in clear American English.

Why not try to troll your friends with 'viruses', try creating a fake virus then send it to your friends. Surely your friends will have to 'roar' when they know their computer is infected with 'fake virus'.

In the article below, Network Administrator will guide you how to create fake virus to troll your friends with Notepad. The steps are extremely easy.

Note : This method does not apply to Macbooks.

Fake Virus: Troll Friends by Creating a 'Fake' Virus on Notepad — contextual image 1

Step 1:

Open a new Notepad.

Fake Virus: Troll Friends by Creating a 'Fake' Virus on Notepad — contextual image 2

Step 2:

Copy and paste the code below into Notepad:

Set WshShell = WScript. CreateObject ("WScript. Shell")

strName = wshShell. ExpandEnvironmentStrings ("% USERNAME%")

x = msgbox ("Critical: Your system is severely affected by multiple threats. To abort all processes, press 'Abort'. To Scan again, press 'Retry'. To continue all processes, click 'Ignore'.", 2 + 16, "Virus found by Windows Defender ©")

WScript.sleep 2000

msgbox "Sytem failure in% WINDIR%", 48, ERROR

WshShell. Run "cmd"

WScript.sleep 200

wshshell.sendkeys "cls"

WScript.sleep 200

wshshell.sendkeys "{ENTER}"

WScript.sleep 200

wshshell.sendkeys "A"

WScript.sleep 200

wshshell.sendkeys "r"

WScript.sleep 200

wshshell.sendkeys "e"

WScript.sleep 200

wshshell.sendkeys ""

WScript.sleep 200

wshshell.sendkeys "y"

WScript.sleep 200

wshshell.sendkeys "o"

WScript.sleep 200

wshshell.sendkeys "u"

WScript.sleep 200

wshshell.sendkeys ""

WScript.sleep 200

wshshell.sendkeys "s"

WScript.sleep 200

wshshell.sendkeys "c"

WScript.sleep 200

wshshell.sendkeys "a"

WScript.sleep 200

wshshell.sendkeys "r"

WScript.sleep 200

wshshell.sendkeys "e"

WScript.sleep 200

wshshell.sendkeys "d"

WScript.sleep 200

wshshell.sendkeys ","

WScript.sleep 200

wshshell.sendkeys ""

WScript.sleep 200

wshshell.sendkeys strName

WScript.sleep 200

wshshell.sendkeys "?"

x = msgbox ("?", 4)

wshshell.sendkeys "{ENTER}"

wshshell.sendkeys "cls"

wshshell.sendkeys "{ENTER}"

if x = 6 Then

WScript.sleep 200

wshshell.sendkeys "G"

WScript.sleep 200

wshshell.sendkeys "o"

WScript.sleep 200

wshshell.sendkeys "o"

WScript.sleep 200

wshshell.sendkeys "d"

WScript.sleep 200

wshshell.sendkeys ","

WScript.sleep 200

wshshell.sendkeys ""

WScript.sleep 200

wshshell.sendkeys "y"

WScript.sleep 200

wshshell.sendkeys "o"

WScript.sleep 200

wshshell.sendkeys "u"

WScript.sleep 200

wshshell.sendkeys ""

WScript.sleep 200

wshshell.sendkeys "s"

WScript.sleep 200

wshshell.sendkeys "h"

WScript.sleep 200

wshshell.sendkeys "o"

WScript.sleep 200

wshshell.sendkeys "u"

WScript.sleep 200

wshshell.sendkeys "l"

WScript.sleep 200

wshshell.sendkeys "d"

WScript.sleep 200

wshshell.sendkeys ""

WScript.sleep 200

wshshell.sendkeys "b"

WScript.sleep 200

wshshell.sendkeys "e"

WScript.sleep 200

wshshell.sendkeys "."

WScript.sleep 200

wshshell.sendkeys "."

WScript.sleep 200

wshshell.sendkeys "."

wshshell.sendkeys "{ENTER}"

WScript.sleep 100

wshshell.sendkeys "exit"

WScript.sleep 100

wshshell.sendkeys "{ENTER}"

End If

if x = 7 Then

WScript.sleep 200

wshshell.sendkeys "N"

WScript.sleep 200

wshshell.sendkeys "o"

WScript.sleep 200

wshshell.sendkeys "?"

WScript.sleep 500

wshshell.sendkeys ""

WScript.sleep 200

wshshell.sendkeys "."

WScript.sleep 200

wshshell.sendkeys "."

WScript.sleep 200

wshshell.sendkeys "."

WScript.sleep 200

wshshell.sendkeys "Y"

WScript.sleep 200

wshshell.sendkeys "o"

WScript.sleep 200

wshshell.sendkeys "u"

WScript.sleep 200

wshshell.sendkeys ""

WScript.sleep 200

wshshell.sendkeys "s"

WScript.sleep 200

wshshell.sendkeys "h"

WScript.sleep 200

wshshell.sendkeys "o"

WScript.sleep 200

wshshell.sendkeys "u"

WScript.sleep 200

wshshell.sendkeys "l"

WScript.sleep 200

wshshell.sendkeys "d"

WScript.sleep 200

wshshell.sendkeys ""

WScript.sleep 200

wshshell.sendkeys "b"

WScript.sleep 200

wshshell.sendkeys "e"

WScript.sleep 200

wshshell.sendkeys "."

WScript.sleep 200

wshshell.sendkeys "."

WScript.sleep 400

wshshell.sendkeys "{ENTER}"

WScript.sleep 100

wshshell.sendkeys "exit"

WScript.sleep 100

wshshell.sendkeys "{ENTER}"

End If

WshShell. Run "cmd"

WScript.sleep 500

wshshell.sendkeys "dir"

WScript.sleep 100

wshshell.sendkeys "{ENTER}"

WScript.sleep 1000

wshshell.sendkeys "dir"

WScript.sleep 100

wshshell.sendkeys "{ENTER}"

WScript.sleep 2000

wshshell.sendkeys "cls"

WScript.sleep 40

wshshell.sendkeys "{ENTER}"

WScript.sleep 40

wshshell.sendkeys "prompt deleting cookies."

WScript.sleep 40

wshshell.sendkeys "{ENTER}"

WScript.sleep 40

wshshell.sendkeys "cls"

WScript.sleep 40

wshshell.sendkeys "{ENTER}"

WScript.sleep 2000

wshshell.sendkeys "prompt deleting Users."

WScript.sleep 40

wshshell.sendkeys "{ENTER}"

WScript.sleep 40

wshshell.sendkeys "cls"

WScript.sleep 40

wshshell.sendkeys "{ENTER}"

WScript.sleep 2000

wshshell.sendkeys "prompt deleting drive 'C:'."

WScript.sleep 200

wshshell.sendkeys "{ENTER}"

WScript.sleep 40

wshshell.sendkeys "cls"

WScript.sleep 40

wshshell.sendkeys "{ENTER}"

WScript.sleep 1000

x = msgbox ("Are you sure you want to permanently delete all directories, files, and subfiles in the environment variable: '% ALLDATA%'?", 4 + 32, "C:")

WScript.sleep 2000

wshshell.sendkeys "prompt deleting system 32."

WScript.sleep 70

wshshell.sendkeys "{ENTER}"

WScript.sleep 40

wshshell.sendkeys "cls"

WScript.sleep 40

wshshell.sendkeys "{ENTER}"

WScript.sleep 1000

wshshell.sendkeys "exit"

WScript.sleep 200

wshshell.sendkeys "{ENTER}"

WScript.sleep 4000

msgbox "Just kidding:)"

Fake Virus: Troll Friends by Creating a 'Fake' Virus on Notepad — contextual image 3

Step 3:

Proceed to save the Notepad file again. You can save Notepad to any name you want, but the extension must be ".vbs". For example, you can save Notepad to fakevirus.vbs.

In the Save as type item you select is All files.

Fake Virus: Troll Friends by Creating a 'Fake' Virus on Notepad — contextual image 4

Step 4: Create a Shortcut

Right-click any space on the Desktop, select New => Shortcut , then click Browse and find the Notepad file location that you saved.

Name the shortcut with something you can easily remember, such as Magic Box Game.

Fake Virus: Troll Friends by Creating a 'Fake' Virus on Notepad — contextual image 5

Step 5: Edit Shortcut

Right-click the shortcut you just created, then click Properties . On the Properties window select Change icon., change the Shortcut icon with an icon that you think will catch the eye "victim" trolled by you.

Fake Virus: Troll Friends by Creating a 'Fake' Virus on Notepad — contextual image 6

Step 6: Some tips and warnings

- You can turn off the program any time you want by opening Task Manager (press Ctrl + Alt + Delete), then select the Process tab and finish "wscript.exe" .

- Click on any window or exit the Command Prompt window while the program is running that may cause an error to randomly open any file on the Desktop.

Fake Virus: Troll Friends by Creating a 'Fake' Virus on Notepad — contextual image 7

Refer to some of the following articles:

  • Your Windows 10-based computer has a virus, this is a fix
  • Windows Defender is disabled or inactive, this is a fix
  • 9 tips to protect your computer safely from virus attacks

Good luck!

FAQ

What is Fake Virus: Troll Friends by Creating a 'Fake' Virus on Notepad about?

It provides a structured overview of fake virus, explains the main context, and highlights practical takeaways for readers.

Why does this topic matter?

Understanding the main concepts helps readers evaluate the issue, avoid common mistakes, and make better-informed decisions.

How should readers use this information?

Use the guidance as a practical starting point, confirm details that may have changed, and follow current product, safety, or security recommendations.

Discussion

Reader Comments 0

Sign in with email or Google to join the discussion.