NoVirusThanks OSArmor: Complete Guide to Hardening Your Windows System

Troubleshooting NoVirusThanks OSArmor — Common Issues & Fixes

1) OSArmor blocks a legitimate app (false positive)

• Fix: Open OSArmor GUI → Rules → Whitelist process. Add the full executable path and parent-process exceptions if needed.
• Tip: Test after adding; if issue persists, restart OSArmor service.

2) OSArmor prevents installers or updaters from running

• Fix: Temporarily disable the specific protection (e.g., “Block installers with double extensions” or “Block unsigned processes”) in Rules, run the installer, then re-enable the protection.
• Alternative: Add the installer EXE to the whitelist.

3) OSArmor shows “Protections turned off” or trial expired

• Fix: Ensure you’re using a version that matches your license (paid versions require a license). Reinstall a supported free version (older free builds exist) or enter a valid license key.
• Tip: Backup your OSArmor config before reinstall.

4) High CPU or unexpected resource usage

• Fix: Update to the latest OSArmor release from the official site. If problem remains, open OSArmor → Settings → disable nonessential logging or experimental features, then restart service.
• Diagnostic: Use Task Manager or Process Explorer to confirm OSArmor service is the source.

5) Conflicts with other security software

• Fix: Temporarily disable one product at a time to identify conflict. Prefer running OSArmor alongside antivirus/EDR in compatibility mode — add mutual exclusions for each other’s service/exe where safe.
• Caution: Only add exclusions after verifying they are necessary.

6) OSArmor service won’t start

• Fix: Run Services.msc → locate OSArmor (or OSArmorDevSvc) → set to Automatic, then Start. If it fails, reinstall Visual C++ redistributables (2015–2019) and reinstall OSArmor.
• Logs: Check Windows Event Viewer (Application/System) for service error codes.

7) Rules not applying or changes not saved

• Fix: Run OSArmor GUI as Administrator when editing rules. After changes, click Apply and restart the OSArmor service.
• File-permission check: Ensure the account has write access to OSArmor’s config folder (Program Files\NoVirusThanks\OSArmor…).

8) USB or removable-drive protections blocking legitimate devices

• Fix: In Rules, add trusted USB processes/executables to the whitelist or disable the specific removable-drive blocking rule. Reconnect device after changes.

9) Windows updates or system components blocked

• Fix: Temporarily disable the related OSArmor rule, perform Windows Update, then re-enable rule. If Windows components are blocked persistently, add Windows update-related executables (e.g., wuauclt, svchost) to trusted list only if safe.

10) How to gather helpful diagnostics

• Enable OSArmor logging (Settings → Logging), reproduce the issue, then collect:
  • OSArmor logs
  • Windows Event Viewer entries
  • Exact executable paths and parent process names
    Share these with NoVirusThanks support or community forums for faster resolution.

When to contact vendor/community

• If rule edits, whitelists, service restart, and reinstall do not fix the issue, open a support request at novirusthanks.com or post on reputable forums (BleepingComputer, Wilders) including logs and steps already taken.

If you want, I can generate the exact whitelist rule syntax for a specific executable — give me the full path and parent process.