Xangle
Xangle Portal
Sign in

Product

Xangle Camera Server

Speed & throughput

Optimization

Reduce capture, transfer, processing, and delivery delays by checking the whole path from camera to output.

Windows Defender exceptions for capture folders

Windows Defender real-time protection can inspect files while they are being created and modified. This matters most for large RAW+JPG captures, where hundreds of files may arrive at the same time.

Why add an exception

Camera Server writes incoming transfer data directly into the dataset folder as chunks arrive. Defender may inspect those files during the transfer or when they are closed. That inspection can add disk and CPU pressure, delay write callbacks, and extend the transfer.

An exception for the active dataset parent folder prevents Defender real-time scanning of files under that path. It does not disable Defender everywhere and does not cover files written to other locations.

Add the exception

  1. Open Windows Security.
  2. Select Virus & threat protection, then Manage settings.
  3. Scroll to Exclusions and select Add or remove exclusions.
  4. Choose Add an exclusion, then Folder.
  5. Select the parent folder used for Camera Server datasets, for example C:\Users\info\xangle\cameraserver\datasets.
  6. Confirm that the exact active dataset and any Camera Server staging folder are beneath the excluded path.

The same setting can be checked from an elevated PowerShell window:

Get-MpPreference | Select-Object -ExpandProperty ExclusionPath

Folder exclusions reduce protection for that folder. Use them only for a trusted local capture directory, not for Downloads, shared folders, or a broad system path.

What our test demonstrated

We ran four matched 168-camera RAW+JPG captures, alternating the folder exception on and off. Every run produced 334 files and approximately 4.27 GB of data.

Folder exception Average total time Average transfer time
Enabled, two runs 30.800 s 29.899 s
Disabled, two runs 35.956 s 34.895 s

Without the exception, the transfer was approximately 5 seconds slower, or 14% slower, in both averages. The runs also showed higher CPU usage and substantially more aggregate write and queue pressure without the exception. Network throughput was nearly identical, so the difference was not explained by a faster network run.

This is strong evidence that real-time scanning affected this workload. It is not a promise of the same improvement on every computer: scanner versions, other security products, storage hardware, file sizes, and background activity can change the result.

When to use it

Use a capture-folder exception when:

  • the directory is a trusted, local SSD workspace;
  • RAW or RAW+JPG transfers show high disk activity, write latency, or queueing;
  • repeated tests show slower transfers with real-time scanning enabled;
  • the folder is not synchronized by OneDrive, Google Drive, or another cloud service.

Do not use an exception as a substitute for investigating a failing SSD, a congested network, an unstable camera branch, or a third-party security product. Keep the exception limited to the capture workspace and review it if the dataset location changes.