This is the page nobody wants to need. If encryption has visibly started - files renaming, extensions changing, a demand note on screen - what you do in the first five minutes decides whether it stays one PC's problem or becomes the whole office's.
Panic is the attacker's second tool. The natural reactions - clicking the note to read it, running every cleaner you own, rebooting repeatedly, plugging in the backup drive to check it - are mostly the wrong ones, and two of them actively spread the damage. The correct response is short, boring and physical. Learn it now, while you do not need it: disconnect, stop, preserve, report. Nothing in these five minutes requires technical skill, and everything technical comes after the bleeding has stopped.
Ransomware spreads sideways through networks and shared folders. Pulling the Ethernet cable or switching off Wi-Fi takes seconds and caps the incident at one machine. If it is a laptop on Wi-Fi, use the hardware switch or airplane mode if you can do it instantly - otherwise shut the machine down by holding the power button. A hard shutdown can lose the document you had open; leaving the machine connected can lose the file server. There is no contest.
If you manage an office: the same rule applies to the shared drive and server - isolate the affected segment first, investigate second.
Photograph the ransom note and any error screens with your phone - including any file names, addresses or IDs shown, without clicking anything. Write down when you first noticed it, what you were doing just before (an attachment opened, a download run), and which shared folders this PC could reach. That five-line note saves hours later, for IT, for the authorities, and for working out what else on the network needs checking.
Home users: call a trusted technician and describe exactly what you saw and did; do not let the machine sit connected "to show them". Offices: call your IT support or incident contact now, and start the list of systems that shared credentials or folders with this PC - those get checked before they get trusted. Recovery itself - clean reinstall, restore from the offline copy, credential changes on a clean device - is methodical work that starts once the machine is isolated. Speed matters in the first five minutes; after that, care matters more than speed.
See the test setup and the defences in action on the Technical Anshu channel, then come back and apply the settings on your own PC.
Watch Full VideoDisconnect it from the network first - that is the essential move. If encryption is visibly racing on and you cannot disconnect quickly, hold the power button and shut it down. A machine that is off and isolated can wait safely for expert help.
The countdown is pressure, not information - it is designed to make you pay before thinking. Attackers cannot delete your offline backup copy, and data restored from it does not depend on their timer. Isolate, preserve, report, and let the decision be made calmly by the right people.
Restore onto a cleaned or replacement machine, not onto the infected one - otherwise you may feed fresh files to a still-active infection and expose the backup in the process. Isolate first, clean or rebuild, then restore.