RUNLOCALAIv38
->Will it run?Best GPUCompareTroubleshootStartLearnPulseModelsHardwareToolsBench
Run check
RUNLOCALAI

Independently operated catalog for local-AI hardware and software. Hand-written verdicts. Source-cited claims. Reproducible commands when we have them.

OP·Fredoline Eruo
DIR
  • Models
  • Hardware
  • Tools
  • Benchmarks
TOOLS
  • Will it run?
  • Compare hardware
  • Cost vs cloud
  • Choose my GPU
  • Prompting kits
  • Quick answers
REF
  • All buyer guides
  • Learn local AI
  • Methodology
  • Glossary
  • Errors KB
  • Trust
EDITOR
  • About
  • Author
  • How we make money
  • Editorial policy
  • Contact
LEGAL
  • Privacy
  • Terms
  • Sitemap
MAIL · MONTHLY DIGEST
Get monthly local AI changes
Monthly recap. No spam.
DISCLOSURE

Some links on this site are affiliate links (Amazon Associates and other first-class retailers). When you buy through them, we earn a small commission at no extra cost to you. Affiliate links do not influence our verdicts — there are cards we rate highly that we don't have affiliate relationships with, and cards that sell well that we refuse to recommend. Read more →

© 2026 runlocalai.coIndependently operated
RUNLOCALAI · v38
  1. >
  2. Home
  3. /Learn
  4. /Courses
  5. /Local AI on Windows
  6. /Ch. 11
Local AI on Windows

11. Antivirus Considerations

Chapter 11 of 15 · 20 min
KEY INSIGHT

Antivirus real-time scanning is the most common cause of slow model downloads and intermittent binary execution failures on Windows. Adding exclusions for model storage and binary directories eliminates the problem entirely.

Windows Defender (built into Windows Security) scans files on first access. For large model files (7 GB+), this causes two problems: download speed drops to 20-30% of available bandwidth while Defender scans the file in real time, and the first inference run is slow because the binary gets rescanned. In worst cases, Defender quarantines the Ollama or LM Studio executable, which silently breaks the tool with no visible error message.

Check Windows Security exclusions:

Get-MpPreference | Select-Object -ExpandProperty ExclusionPath

Add exclusions for known safe directories:

# Exclude Ollama model storage
Add-MpPreference -ExclusionPath "$env:LOCALAPPDATA\Ollama\models"
# Exclude Ollama program directory
Add-MpPreference -ExclusionPath "$env:LOCALAPPDATA\Programs\Ollama"
# Exclude Docker data directory
Add-MpPreference -ExclusionPath "C:\ProgramData\docker"
# Exclude WSL2 VHDX file
Add-MpPreference -ExclusionPath "$env:USERPROFILE\AppData\Local\wsl"

Third-party antivirus (Kaspersky, Bitdefender, Malwarebytes) has similar real-time scanning behavior. Most support "gaming mode" or "resource-intensive application" exclusions that pause scanning during active use. Setting an exclusion for the entire model directory is the most reliable solution.

Ollama binary signatures may not be trusted by Windows SmartScreen on first run. If SmartScreen blocks the installer, use:

Start-Process -FilePath "C:\path\to\OllamaSetup.exe" -ArgumentList "/S" -Verb RunAs

The /S flag runs the installer silently. If SmartScreen still blocks it, right-click the .exe, Properties, unblock, then run.

Local verification checkpoint

Run the smallest example from this chapter in a local workspace and record the package version, runtime, data path, and observed output. If the result depends on model size, vector count, CPU/GPU backend, or available memory, note that constraint beside the exercise so the lesson remains reproducible.

EXERCISE

Run a large model download with Ollama, time it, then add the model directory to Windows Defender exclusions, delete the downloaded model with ollama rm, and time the same download again. Compare the two download durations.

← Chapter 10
Path Configuration
Chapter 12 →
WSL2 Troubleshooting