Zabezpečení

Jak bezpečně nastavit výjimky v antiviru

Ruce kontrolující nastavení antiviru a kontrolní seznam zabezpečení vedle notebooku

Antivirus software sometimes blocks a file or application that you need for legitimate work. It may identify a build tool, internal script, business utility or newly downloaded installer as suspicious even when the file is safe. This is commonly called an antivirus false positive.

The correct response is not to switch off protection or exclude an entire drive. The safer approach is to investigate the detection, confirm that the item is trustworthy, and create the narrowest temporary exception that solves the problem. This guide explains how to set antivirus exclusions safely on a personal computer or work device, while keeping protection active for everything else.

Understand when an exclusion may be justified

An exclusion tells security software not to inspect a specified file, folder, process or other location in the usual way. The exact options vary by product and operating system. The security cost also varies: excluding one known executable is usually narrower than excluding the folder in which many programs and documents are stored.

A possible exclusion may be reasonable when:

  • a trusted application is repeatedly blocked and the vendor or developer confirms that the detection is incorrect;
  • you have checked the file’s origin, digital signature and expected contents;
  • the application is required for a specific business, engineering, development or administrative task;
  • you understand exactly what the proposed rule will bypass; and
  • you can monitor and review the rule later.

An exclusion is not a general solution for slow performance, an unknown warning or software that refuses to install. First check whether the security product has a recommended update, repair option or false-positive reporting process. A detection may also indicate that an installer, plug-in or downloaded document has been tampered with.

Do not add an exclusion merely because a pop-up is inconvenient. Treat every request to disable scanning as a security decision, especially on a computer used for customer data, financial information, design files, source code or company accounts.

Confirm that the file or application is trustworthy

Before changing a setting, identify precisely what was blocked. Record the file name, full path, detection name, application version and the action taken by the antivirus product. A vague message such as “the program is not working” is not enough information to justify an exception.

Use this verification sequence:

  1. Check the source. Prefer the software publisher’s official download channel, a known business supplier or an internal distribution system. Be cautious with files received through unsolicited email, file-sharing links, forums or repacked installers.
  2. Check the path. A legitimate application is more credible when it is in the expected installation location. A similarly named executable in a temporary download folder, a user profile subfolder or an unusual system location deserves additional investigation.
  3. Check the publisher. On supported systems, inspect the file’s properties and digital signature. Confirm that the signer is the expected publisher and that the signature is valid. A signature is useful evidence, but it does not prove that the file is safe in every situation.
  4. Compare the file. If the publisher provides a checksum or hash, calculate the hash of your copy and compare it carefully. Do not rely on a copied value from an untrusted page.
  5. Check for a current version. Look for a newer installer or update. A false positive may already be corrected in a later release, while an old version may contain a real vulnerability.
  6. Seek a second assessment when needed. For an important or unusual file, ask the software publisher or your IT administrator to investigate. Do not upload confidential business files to an online scanning service unless your organisation permits it.

Never treat a warning from a colleague, an online comment or a search result as proof of safety. If the file is cracked, modified to bypass licensing, or obtained from an unofficial source, do not create an exclusion. Remove it and obtain legitimate software instead.

Choose the narrowest possible exclusion

The safest antivirus exclusion is specific, documented and limited in time. The available rule types differ, but the general order of preference is to exclude one known file or one narrowly defined application component rather than a broad location.

Exclusion scope Typical use Relative risk Recommended approach
One exact file A verified executable repeatedly identified as a false positive Lower, but not zero Prefer this when the file path and purpose are stable; document it and review it
One specific process A trusted application that creates or opens temporary working files Medium Use only when you understand which activity the process can access
A dedicated application folder A controlled folder containing a known tool and its required components Medium to high Use only when a file-level rule cannot solve the issue; keep the folder restricted
A user profile, downloads folder or project root General convenience or performance improvement High Avoid; these locations commonly receive untrusted files
An entire drive or all security scans Broad troubleshooting or permanent performance changes Very high Do not use as a normal remedy

When the security application offers a choice between excluding a file, folder, process or extension, choose the option with the smallest effect. Avoid extension-based exclusions such as ignoring every file with a particular format. A malicious file can use the same extension as a legitimate work file.

Use a dedicated folder only when the application genuinely requires it and when you can control what is placed there. Do not allow email attachments, browser downloads or unknown scripts to enter that folder. If several people use the computer, consider whether they can write to the excluded location. A writable excluded folder can become a convenient place for malicious software to hide.

IT professional verifying a software file and checksum before creating an antivirus exclusion

How to add an exclusion safely

Menu names differ between security products and operating systems, so use these as vendor-neutral steps rather than exact button names. Sign in with an authorised account, and avoid changing centrally managed settings on a business device without approval.

  1. Open the antivirus settings. Find the area for protection, threat detection, scanning or exclusions. Do not use a system-wide switch that disables real-time protection unless your administrator or the vendor’s support instructions require it for a tightly controlled test.
  2. Record the current configuration. Note existing exclusions, the date, the user who manages them and the reason for the change. This makes accidental over-exclusion easier to detect.
  3. Create one rule. Select the exact file or narrowly defined process that was investigated. Type or browse to the verified path carefully. Check for similar names and confirm that you are not selecting a parent folder by mistake.
  4. Add a clear note. Include the application name, publisher, reason, date, person responsible and planned review date. If the product does not support notes, keep the information in your IT or password-management documentation according to your organisation’s policy.
  5. Keep protection active elsewhere. Do not disable web protection, email scanning, automatic updates or other security layers simply because one item has an exclusion. The names and available controls depend on the product.
  6. Test the required task. Start the application and perform the smallest test that confirms the problem is resolved. Do not download unrelated files or leave the system broadly unprotected for troubleshooting.
  7. Scan the item separately if possible. After the rule is created, use the product’s available manual or on-demand scan options where appropriate. Remember that an excluded item may receive different treatment during scanning.
  8. Watch for new behaviour. Unexpected network connections, newly created executables, repeated detections or changes to the file’s publisher should trigger a review. Remove the rule while investigating.

Test the exclusion from a standard user account where possible. If an application needs administrator rights, treat that as a separate privilege decision rather than granting broad permissions to make the warning disappear.

Practices that reduce protection

Several common shortcuts create more risk than they solve:

  • Excluding a whole drive: this can leave operating-system files, applications and personal documents outside normal inspection.
  • Excluding Downloads or temporary folders: these are common destinations for files from the internet and email.
  • Excluding all scripts or archives: legitimate and malicious content can use the same file types.
  • Excluding the antivirus program itself: this can interfere with detection, updates, self-protection and repair.
  • Disabling real-time protection permanently: this removes a major layer of defence instead of addressing one identified item.
  • Copying a rule from another computer: paths, software versions, users and threat exposure may be different.
  • Adding a permanent exception for an old installer: installers are often downloaded, reused or replaced, so an exception can outlive its original purpose.

Security tools should normally be allowed to protect themselves. If two security products conflict, follow documented vendor guidance or ask an administrator to resolve the conflict. Do not assume that excluding one product from another is harmless.

Review and remove exclusions regularly

Every exclusion should have an owner, a reason and a review date. Review the list after software updates, operating-system changes, employee role changes and security incidents. Remove rules for applications that have been uninstalled, replaced or no longer need special handling.

For a home computer, a simple monthly or quarterly check can prevent forgotten exceptions. For a business, include exclusions in change management or endpoint security reviews. Compare the list with installed software and investigate rules that have unclear names, broad paths or no documented owner.

Remove an exclusion when:

  • the application vendor has released a corrected version;
  • the file has moved or been replaced;
  • the project or business need has ended;
  • the publisher or file hash has changed unexpectedly;
  • the rule is broader than the current task requires; or
  • you cannot explain why it exists.

After removal, update the antivirus software and run an appropriate scan. If the same trusted file is detected again, repeat the verification process rather than recreating a broad rule. A recurring detection may need investigation by the software publisher.

Which security product fits this approach?

Exclusions are a configuration practice, not a reason to choose a product solely because it appears to block fewer files. A good security routine keeps protection active, makes exceptions visible and allows you to investigate false positives carefully.

Situace Possible product choice Why it may fit
One person uses Windows, Mac or Android devices and wants a recognised security platform ESET HOME Security Essential The listed product supports Windows, Mac and Android, with a one-year licence for one device
A household or individual needs coverage across several device types Bitdefender Total Security The listed product supports Windows, Mac, iOS and Android, with a one-year licence for five devices
A household needs a multi-device security product across major desktop and mobile platforms Norton 360 Deluxe The listed product supports Windows, Mac, Android and iOS, with a one-year licence for five devices

These product details describe platform and licence scope, not a promise that every setting or exclusion type is identical. Always check the current product documentation before applying a rule. Organisations with centrally managed devices should also follow their internal security policy and endpoint-management controls.

Genuine licences for ESET HOME Security Essential, Bitdefender Total Security and Norton 360 Deluxe are available from KEYFORREST with instant electronic delivery. Check the current product page for the exact platform, device count, licence term and version before ordering.

Často kladené otázky

Should I exclude a file that my antivirus identifies as a false positive?

Only after verifying its source, publisher, path and, where available, checksum. Ask the software publisher or IT administrator for help when the file is important or the evidence is unclear.

Is it safer to exclude a file or its folder?

Excluding one verified file is generally narrower than excluding a folder. A folder rule can protect every file placed there from normal scanning, including a later malicious file.

Can I exclude my Downloads folder to stop repeated warnings?

No. Downloads commonly contain files from the internet, so excluding the folder can remove an important protection layer. Investigate and handle the specific file instead.

How often should I review antivirus exclusions?

Review them regularly and after software, user or security changes. At minimum, remove rules as soon as their documented purpose ends.

What should I do if a trusted application is still blocked?

Update the application and antivirus software, confirm the detection details, and contact the application publisher or your administrator. Avoid creating a broader exclusion without new evidence.

author-avatar

O autorovi Marios Chaidousis

Marios Chaidousis je specialista na software a licence se zaměřením na Autodesk (AutoCAD, Revit, Inventor), Microsoft (Office, Microsoft 365, Windows, Windows Server, SQL Server), Adobe a bezpečnostní software. Pomáhá inženýrům, profesionálům a firmám vybrat správnou licenci a využít software naplno.LinkedIn · Facebook · Instagram