Skip to content
English
  • There are no suggestions because the search field is empty.

Folders and Paths Memtime Needs Access to in IT-Managed Environments

Memtime needs access to specific local folders and files to start and update correctly. Here's what that means for you and what to share with your IT administrator if Memtime is blocked.

Overview

Memtime stores application files and local runtime files on your computer so it can start, run, and update correctly.

In most environments, no special action is required from the user. However, in organizations with endpoint protection, application control, folder access restrictions, or other security policies, your IT administrator may need to allow specific Memtime folders and files. 


What this means for end users

If company security policies prevent Memtime from accessing required files or folders, you may notice that Memtime does not start, the application closes unexpectedly, or updates do not complete successfully.

This does not necessarily mean that Memtime is installed incorrectly. It may mean that your company’s security configuration is blocking a required Memtime path or executable.

If this is your case, you usually do not need to change any settings yourself. But you can share the "For IT administrators" section of this article with your IT team.


For IT administrators

Memtime requires access to its installation directory and local application data directory.

Please ensure that security tools, application control policies, and controlled folder access rules do not block the paths and executables listed below.

Installation paths

Depending on the system and installation type, Memtime is installed in one of the following directories:

  • %programfiles%\Memtime
  • %programfiles(x86)%\Memtime

In addition, Memtime stores essential files in the following local directory:

  • %localappdata%\memtime

Critical executable

The most important executable file is located here:

  • %localappdata%\memtime\user\core\core.exe

Memtime must be able to start this executable. Please note:

  • This file is regularly updated when new versions are available.
  • No policies should block or validate this file based on its hash.
  • If necessary, validation should rely on the file's digital certificate rather than the hash, since the hash will change with each update.

Required access

Please allow Memtime to read from and write to the required folders. Memtime needs access to:

  • The Memtime installation directory (%programfiles%\Memtime or %programfiles(x86)%\Memtime)
  • The local application data directory (%localappdata%\memtime) 

These paths should not be restricted or blocked, as Memtime needs to read from and write to them for proper operation.

Policy guidance

  • Do not block the Memtime installation directories.
  • Do not block %localappdata%\memtime\user\core\core.exe.
  • Do not rely on the file hash of core.exe for validation, because the hash can change with each update.
  • If validation is required, use the file's digital certificate instead of the file hash.

Important: Hash-based allowlisting can cause Memtime to be blocked after an update. Certificate-based validation is recommended when your security policy requires application validation.


Symptoms of restricted access

If Memtime is blocked by permissions or security policies, users may experience one or more of the following symptoms:

  • Memtime does not start.
  • The Memtime core process fails to launch.
  • Updates do not apply successfully.
  • Local files cannot be created or modified.
  • Memtime appears installed but does not run as expected.


Troubleshooting steps

For end users

  1. Restart Memtime and check whether the issue continues.
  2. If Memtime still does not start or update, contact your internal IT team.
  3. Share this article with your IT team so they can review the required paths and access rules.

For IT administrators

  1. Review endpoint protection, antivirus, EDR, application control, and controlled folder access settings.
  2. Confirm that the Memtime installation paths are not blocked.
  3. Confirm that %localappdata%\memtime\user\core\core.exe is allowed to start.
  4. Confirm that Memtime has read and write access to the required folders.
  5. If allowlisting is required, validate Memtime by digital certificate rather than file hash.


Need more help? 

If the issue continues after your IT administrator has reviewed the access requirements, contact support@memtime.com and include details about your setup, like company-wide policies, any security software, and any error messages shown when Memtime starts or updates.