Ransomware Screen Freeze? Kill the Encryptor Before It Spreads

Your PC locks up and a ransom note pops up. Here's how to stop the encryption spread, kill the process, and recover files.

You're mid-spreadsheet when the screen flickers, the mouse stutters, and suddenly a full-screen note appears: "Your files are encrypted. Pay $500 in Bitcoin within 72 hours." The cursor still moves, but nothing clicks. File names are turning into gibberish. That's ransomware actively encrypting your drives. I've seen this hit a dental office and a small law firm — both times, the same panic. The good news? If you act in the first few minutes, you can stop the damage before it wipes your backups.

What's actually happening

Ransomware like LockBit or CryptoLocker grabs your files, encrypts them with AES, then drops a ransom note. The screen freeze isn't a crash — it's the malware locking the user session to keep you from interfering. Meanwhile, it's walking through your drives, encrypting everything it can reach. Network drives, attached USB, even cloud-synced folders if the sync client is running.

The root cause is always the same: something got executed that shouldn't have. A phishing macro, a malicious browser update, a fake invoice. But right now you don't care about the cause — you care about stopping the bleed.

Your move: kill the process, cut the network

First rule: don't pay. Second rule: don't reboot. Rebooting gives the malware a chance to load its persistence and resume encryption on boot. Instead, do this:

  1. Open Task Manager. Press Ctrl+Shift+Esc. If the screen is locked, press Ctrl+Alt+Del and choose Task Manager. If the ransom note covers everything, try Windows+Tab to create a new desktop (some variants don't block that).
  2. Find the suspicious process. Look for high CPU or memory. Common names: msos.exe, system32.exe (note the fake), decrypt.exe, or something random like a2f9k.dll.exe. Sort by CPU to see which one's hogging everything.
  3. End that process. Right-click and select "End task." If it won't die, use taskkill /F /IM processname.exe from an admin Command Prompt. If you can't even open CMD, try PowerShell from Task Manager's "Run new task" (hold Shift, click File, then Run new task — that bypasses some restrictions).
  4. Pull the network cable or disable Wi-Fi. This stops the malware from talking to its command server and from encrypting network shares. Do this even if the process is dead — some strains have a watchdog that restarts.
  5. Disable startup items. Open msconfig (Win+R, type msconfig) and uncheck everything suspicious. Or use Task Manager > Startup tab. This stops reinfection on next boot.
  6. Boot into Safe Mode with Networking. But hold on — before you reboot, grab a copy of the ransom note. You'll need the extension it appends to files (like .locked) to identify the strain later. Save it to a USB stick or write it down.

If it still fails after these steps

Sometimes the malware is a polymorphic beast that respawns. If you kill one process and another appears within seconds, you're dealing with a service or a scheduled task. Open services.msc and look for recently created services (sort by name, check dates). Also open Task Scheduler and look for tasks with weird names or triggers like "At startup" or "On idle." Delete anything that doesn't look legit.

If the screen is still locked, try booting from a Linux live USB (like Ubuntu). That gives you a clean OS without running Windows, so the ransomware can't execute. Mount your Windows drive and copy important unencrypted files (like .txt files that might have been missed) to an external drive. Then wipe and reinstall Windows. Yes, it's drastic, but if you can't stop the encryption, you might as well save what you can.

Real talk: I had a client whose server got hit while they watched. We killed the process, but because they had no offline backups, we still lost 3 days of patient data. The fix that saved them was a shadow copy. Check if System Protection is on: vssadmin list shadows. If you have any, you can try to restore files from there.

The recovery phase

After you've stopped the encryption, you need to figure out what strain you're dealing with. The ransom note usually names itself or a website. Look up that name on ID Ransomware — it'll tell you if there's a free decryptor available. Some old strains (like GandCrab) have decryptors from security firms. Newer ones (like LockBit 3.0) don't, so check before you pay.

Also check your shadow copies: right-click a file, go to Properties, look for the "Previous Versions" tab. If shadow copies exist, you might get your data back without any decryptor.

And here's the part I always stress: after you're clean, test your backups. Restore a few files from your cloud backup or external drive. If they restore, you're good. If not, figure that out before you need it.

Prevention so you never see that screen again

  • Disable macros in Office. Set it to "Disable all macros with notification" in Trust Center settings.
  • Block executable attachments in email. Use a filter that strips .exe, .scr, and .vbs attachments.
  • Keep backups on an external drive that's disconnected when not in use. Cloud is fine, but make sure versioning is on.
  • Update your software. Most ransomware exploits old Java or PDF reader flaws.

That's the whole game. Act fast, kill the process, cut the network, and pray your backups are solid. If you've got questions, run a scan with Malwarebytes or hit me up — I've seen every variant this decade.

Related Errors in Cybersecurity & Malware
0XC00D2722 Fix NS_E_DRM_ENCRYPT_ERROR (0XC00D2722) in 3 Steps 0X00000517 Fix ERROR_LOCAL_USER_SESSION_KEY (0X00000517) on Windows 10/11 0XC0130015 Fix STATUS_CLUSTER_NO_SECURITY_CONTEXT 0xC0130015 in Windows 0X80090321 SEC_E_BUFFER_TOO_SMALL (0x80090321) Fix for Windows

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.