v25.6 (Ziggo Safe Online/OEM) - Sentry_Temp folder consumes 31GB

RonnyTNL

Is it normal this folder doesn't clean up after X GB?

Windows10x64 with F-Secure Endpoint protection.

ProgramData\Endpoint Protection SDK\common\sentry_temp == 31GB large.

Seems to contain all installers run on this machine after installing the product.

Can this folder be put in automatic maintenance and/or limited to X GB storage with FIFO or is there an option in the UI that I'm missing, my drive is becoming full.

Ukko

Spoiler Warning

Hello,

I am also only an F-Secure user. Just as my feedback until there is some proper response from official people.

My folder is about 1.5 GB. Not only installers. Some executables and libraries.

Are you sure that these "extra" 31 GB take up extra space? I mean, it could be hard links to files (and maybe they should not consume extra on disk) or something similar. Let's say the size of a folder or file is shown as such, but it is implied or taken from the "real" one. Although I don't know how long they would be stored (and how much space they would take up) if the original files were deleted. And in general, how long they are stored there.

JOnes

Before the F-Secure expert's comment:

"

You're encountering the sentry_temp folder—located under ProgramData\Endpoint Protection SDK\common\—which has ballooned to 31 GB with F-Secure Endpoint Protection version 25.6 (OEM). You’re wondering if this is normal behavior and whether it can be limited or auto-cleaned.

What Is sentry_temp and Why Is It Growing?

• Though documentation specific to F-Secure’s use is scarce, the sentry_temp folder is historically linked to antivirus engines—particularly Avira (and previously BullGuard)—where executables are moved into it and original locations replaced with redirects Malwarebytes Forums.
• In many applications, this folder holds installers or temporary files used during updates or scans.
• There’s no clear evidence it's limited by size or auto-cleaned. Even in older discussions, temporary files in F-Secure were meant to be removed cyclically, but this wasn't always consistent F-Secure Community.
• In a similar context, files in sentry_temp have caused issues when cleanup tools delete them—potentially breaking apps that rely on them Malwarebytes ForumsCCleaner.

Official Position & F-Secure Tooling

• The F-Secure Community hasn't provided a direct resolution for sentry_temp storage in version 25.6, though ameliorating performance improvements were promised with that release F-Secure Community.
• As of now, there’s no setting in the UI or documentation to impose size limits (e.g., a cap or FIFO cleanup).

Recommendations to Manage or Mitigate the Issue

1. Manually assess and clean if safe
   You may be able to delete older files manually—preferably when F-Secure is idle or disabled—though make sure not to remove any files required for currently running apps.
2. Use exclusion rules in your cleaning tools
   If you rely on third-party cleaners like CCleaner or BleachBit, exclude sentry_temp to prevent accidental deletion of files that may be in active use CCleanerMalwarebytes Forums.
3. Reach out to F-Secure Support
   Since version 25.6 includes improvements, it’s a good idea to report this issue directly in F-Secure’s support forums or via logs. The Community Manager, “Firmy,” often responds to such concerns F-Secure Community.
4. Monitor folder growth after clean reinstall or patch updates
   If possible, try uninstalling F-Secure using the standard app removal route (which should remove the SDK cleanly), then perform a fresh install. Confirm whether sentry_temp is regenerated—and see how big it grows over time F-Secure Community.

Summary Table

Concern	Insight
Why the folder grows	Likely stores executables/installers, historically used by Avira/BullGuard engines
Automatic cleanup available?	Not by default; old files may linger despite expectations
Risk of cleanup tools	Cleaning tools may break apps relying on files in sentry_temp
Management options	Manual cleanup, exclude folder in cleaners, contact F-Secure support
Pending improvements	F-Secure 25.6 included performance fixes—but no known storage cap feature yet

Final Thoughts

• Yes, it's not unusual for the sentry_temp folder to grow significantly—especially during active use or multiple installs.
• Since there’s no user-facing control for size or auto-cleanup, your best approach is to handle the folder manually and ensure it's excluded from automatic cleaners.
• For longer-term resolution, engaging F-Secure support and sharing diagnostics would be the most effective route."