Remove Popotic ransomware from the system

Don't pay the ransom

Paying the ransom does not guarantee you'll get your files back. Major ransomware response studies consistently show that a meaningful percentage of paying victims either receive a non-working decryptor, only partial decryption, or no decryptor at all. Beyond that:

• Paying confirms you as a willing target - re-attack rates within 12 months are high
• Several ransomware groups have been sanctioned (US OFAC, UK OFSI). Paying these groups may be illegal under sanctions law in your country
• The ransom funds the next attack - on you or someone else
• Modern ransomware almost always exfiltrates data first, so paying doesn't get the leaked data back. Assume anything the malware could read was uploaded
• Decryptors, even when they work, often leave files corrupted because the encryption itself was buggy or rushed

The path below tries every legal, free recovery option first. Pay only as an absolute last resort, after consulting a lawyer and your country's cyber crime authority.

Disconnect from the network and log out of cloud storage

Pull the Ethernet cable and turn off Wi-Fi on the affected PC. If multiple computers share the network, do the same on every machine you suspect could be affected, including any servers and NAS units.

Then sign out of cloud storage clients (OneDrive, Dropbox, Google Drive, iCloud) from their app settings. If you can, pause the sync. Some ransomware uses the running sync client to push encrypted versions over your clean cloud copies.

Unplug external drives and USB storage

Safely eject any external drives, USB sticks, SD cards, and network-attached storage shares - then unplug them. If a drive was connected when the ransomware ran, the files on it may already be encrypted, but unplugging stops further damage.

Critically: don't reconnect any drive (including your most recent backup) to this PC until the ransomware is removed in Phase 3. Reconnecting an external backup to an actively-infected PC is the most common way that backup gets encrypted too.

Save the ransom note and a sample encrypted file

Copy the ransom note and one small encrypted file (under 1 MB) to a USB stick, or photograph the note with your phone. You'll need both for the variant identification step.

The ransom note is usually one of:

• A .txt file in every encrypted folder (typically HOW_TO_DECRYPT.txt, README.txt, or _readme.txt)
• An .html file with the same purpose
• A changed desktop wallpaper - photograph it
• A lock-screen interrupt that runs at startup - rarer

Identify the variant with ID Ransomware

From a clean device (your phone is fine, or another PC that wasn't on the affected network), visit id-ransomware.malwarehunterteam.com. Upload the ransom note and the sample encrypted file. The site identifies the variant family and tells you whether a free decryptor exists.

Boot to Safe Mode with Networking and download the scanners

Safe Mode loads only the minimal Windows drivers, which prevents most ransomware from auto-running while you set up the scanners.

Windows 11: open Settings → System → Recovery, click Restart now next to Advanced startup. After the restart, click Troubleshoot → Advanced options → Startup Settings → Restart, then press 5 or F5.

Windows 10: click the Windows logo, hold Shift, click the Power icon and choose Restart. From the Choose-an-option screen, click Troubleshoot → Advanced options → Startup Settings → Restart, then press F5.

Once Safe Mode has loaded, turn Wi-Fi back on and download Combo Cleaner (used in step 8) and Microsoft Safety Scanner (used in step 9). Save both installers to your Desktop, then disconnect Wi-Fi again before scanning.

Run Microsoft Defender Offline

Reboot to normal Windows. Open Windows Security → Virus & threat protection → Scan options. Select Microsoft Defender Antivirus (offline scan) and click Scan now. The PC restarts into a stripped-down environment and scans the disk before Windows fully loads.

Run a full Combo Cleaner scan

Run the installer you downloaded in step 6 and start a full system scan (not the quick scan). Let it complete, review what it detected, and apply the recommended actions. Combo Cleaner quarantines the ransomware executable and the registry / scheduled-task entries that re-launch it on reboot.

Run Microsoft Safety Scanner and re-enable Defender

Run Microsoft Safety Scanner (MSERT.exe) as a second-opinion full scan. The binary expires every 10 days so the copy you downloaded has the latest signatures.

Once it finishes, open Windows Security → Virus & threat protection → Manage settings and confirm Real-time protection, Cloud-delivered protection, and Tamper Protection are all on. Many ransomware variants disable Defender during the attack - this is where you switch it back on so the next attempt can't repeat the trick.

Check the No More Ransom Project for a free decryptor

Visit nomoreransom.org and search the Decryption Tools list for the variant name returned by ID Ransomware. The project is run by Europol, the Dutch Police, and security vendors - everything listed is legitimate and free.

If a decryptor exists, download it onto a clean PC, copy it across, and follow its instructions exactly. Decryptors usually want you to point them at a sample encrypted file plus its known unencrypted version (sometimes any image you previously had a backup of works).

Free decryptors exist for parts of the STOP/Djvu, GandCrab, REvil, Avaddon, Conti and Hive families, among others. Most modern variants don't have public decryptors - if yours isn't listed, that's expected; move to the next step.

Try Windows Volume Shadow Copies

Windows automatically creates Volume Shadow Copies of files when System Restore points are made or scheduled backups run. Most ransomware tries to wipe these (vssadmin delete shadows /all /quiet), but the deletion sometimes fails partially - especially if the running user doesn't have full admin rights. When it does fail, snapshots survive that contain pre-encryption versions of your files.

First, check what's there. Open Command Prompt as Administrator and run:

vssadmin list shadows

If you see entries listed, shadow copies survived. To restore from them:

• Built-in: right-click any folder → Properties → Previous Versions tab. Pick a snapshot dated before the infection and restore.
• Better tool for browsing: install Shadow Explorer (free). It shows all snapshots as a normal file tree and lets you copy out only the files you want.

Restore from cloud or external backup

If you have a backup that pre-dates the infection, this is the cleanest recovery available. Important precautions:

• Don't reconnect a backup drive until Phase 3 is complete. If the ransomware is still active, plugging in the backup encrypts it too.
• For cloud backups (OneDrive, Dropbox, Google Drive, iCloud), use the Version History feature to roll individual files back to pre-encryption versions.
• OneDrive specifically has a "Restore your OneDrive" feature: if it detected mass file changes, you can roll back the entire account up to 30 days. Sign in at OneDrive on the web, click the Settings gear, and choose Restore your OneDrive. Microsoft 365 subscribers also get ransomware detection alerts; non-subscribers get one free recovery.
• Verify the restored files open correctly before you delete the encrypted set. Test a few documents, photos, and any database / project files.

Try Recuva as a last-resort recovery

Recuva is a long shot, not a primary recovery tool. Most modern ransomware encrypts files in place - it reads the original, encrypts the data, and writes the encrypted bytes back to the same disk location. In that case, the original isn't deleted, just rewritten - and Recuva has nothing to find.

But for older or simpler variants that deleted originals before creating encrypted copies (rather than encrypting in place), Recuva can sometimes pull the originals from unallocated disk space. Worth trying as a last resort, especially before you use the disk much further.

If you try it:

• Stop using the disk as much as possible - every disk write reduces recovery odds
• Run Recuva from a USB stick, not from the affected disk
• Use Deep Scan mode (slower but the only mode worth running for this scenario)

Don't skip the steps above expecting Recuva to bail you out. It works in maybe 5-20% of cases, depending on the variant and how soon you try.

Report the attack to authorities

Even if your files aren't recovered, your report helps authorities track variants, attribute groups, and warn future victims. In some jurisdictions (especially the US and UK) early reporting can sometimes help recall a wired ransom payment via banking partners.

Save the report number - banks, insurers, and credit bureaus will ask for it. If you operate a business, you may also have legal disclosure obligations (GDPR in the EU, state breach laws in the US) that run on a 72-hour clock.

Plan 3-2-1 backups going forward

The single best defense against ransomware is a tested backup. Use the 3-2-1 rule:

• 3 copies of your data
• 2 different storage media (e.g., internal drive + external drive)
• 1 offline / air-gapped copy (an external drive that isn't always connected)

Recommended cadence:

• Daily: cloud sync (OneDrive, Dropbox, Google Drive) - convenient, but vulnerable if the ransomware reaches the sync folder. The Version History feature is what saves you
• Weekly: external drive that you connect briefly, then disconnect - the air-gap is what protects against ransomware
• Monthly: a second external drive stored off-site (different physical location) - protects against fire, theft, flood

Patch the entry point and monitor for 30 days

Most reinfections happen via the same vector that worked the first time. Until you've patched the entry point, watch for:

• Unusual disk activity, unexpected file modifications, or unfamiliar processes in Task Manager
• Unexpected reboots or new accounts you didn't create
• Defender or your antivirus turning itself off again

Common entry vectors and what to do about each:

• Phishing email with a malicious attachment - review email filters and train yourself / staff to recognise the patterns - see pcrisk's Phishing/Scam reference
• Exposed RDP with weak passwords - disable Remote Desktop from Settings → System → Remote Desktop if you don't need it. If you do, put it behind a VPN and require a long password plus MFA
• Unpatched VPN appliances or public-facing apps - check the vendor's advisories page and apply the latest firmware
• Cracked / pirated software - was the most common vector for STOP/Djvu in particular. Don't run software from torrent sites

Run a Combo Cleaner scan weekly for the first month. Update Windows, browsers, and applications aggressively.