ERROR_VIRUS_DELETED (0x000000E2) Fix – File Blocked by Security

1. Your Antivirus or Windows Defender is Overreacting (Most Common)

I see this all the time. A client calls me up, says “I downloaded the installer for QuickBooks 2023 and now Windows won’t let me open it – says it has a virus.” Nine times out of ten, it’s a false positive. Windows Defender or some third-party antivirus flagged the file because it looks like a virus, but it’s legit.

Before you do anything else, check the file on VirusTotal. Upload the file there – it’ll scan it with 60+ antivirus engines. If only 1 or 2 flag it (usually Defender or McAfee), it’s almost certainly a false positive.

Fix: Temporarily Disable Real-Time Protection

1. Open Windows Security: hit Windows + I → Update & Security → Windows Security → Virus & Threat Protection.
2. Under “Virus & threat protection settings,” click “Manage settings.”
3. Turn off “Real-time protection.” Windows will warn you – that’s fine. You’re turning it back on after you open the file.
4. Now try to open the file. Should work.
5. After you’ve opened it, turn real-time protection back on. Don’t leave it off.

Pro tip: If you’re paranoid (and you should be), scan the file with Malwarebytes or HitmanPro before opening. They catch real malware better than Defender.

Had a client last month whose entire print queue died because McAfee flagged a printer driver update. This fix got them back online in 5 minutes.

2. Corrupted System Files Triggering the Error

Sometimes the error pops up even when the file is clean. I’ve seen this after a botched Windows update or a drive that’s starting to fail. The system file checker (SFC) or DISM can fix it.

Fix: Run SFC and DISM

1. Open Command Prompt as administrator: hit Windows + X → “Command Prompt (Admin)” or “Windows Terminal (Admin).”
2. Type sfc /scannow and press Enter. Let it run – takes 10-15 minutes. If it finds corrupted files, it’ll replace them automatically.
3. After SFC finishes, run DISM: DISM /Online /Cleanup-Image /RestoreHealth. This fixes the system image that SFC uses.
4. Reboot your PC. Try opening the file again.

If SFC says it can’t fix some files, run DISM first, then SFC again. 90% of the time, that sequence clears it up.

3. The File is Actually Infected (You Need to Scan Properly)

This one’s less common in my experience, but it happens. If VirusTotal shows 10+ engines flagging the file, you’ve got real malware. Don’t try to open it – you’ll infect your machine.

Fix: Scan with a Second Opinion Tool

1. Download and install Malwarebytes (free version works). Update its definitions.
2. Run a full scan. If it finds the file as malicious, let Malwarebytes quarantine it.
3. Also run HitmanPro (trial works fine). It’s a cloud-based scanner that catches stuff Malwarebytes misses.
4. If both say it’s clean but Defender still blocks it, you’re back to cause #1.

Real story: I had a client who kept getting this error on a PDF attached to an email. Turned out the PDF had an embedded script that was legit malware. Malwarebytes caught it, Defender missed it. We blocked the sender.

Quick-Reference Summary Table

That’s it. Start with the antivirus check – it fixes 80% of these errors. If that doesn’t work, hit the system files. And if you’re still stuck, the file’s probably bad – delete it and get a clean copy from the source.