How to resolve performance issues incurred because of the check for encrypted legacy SafeBoot Content Encryption 2.x files

Technical Articles ID: KB81615
Last Modified: 2022-09-12 20:42:58 Etc/GMT

Environment

File and Removable Media Protection (FRP) 5.x

For FRP supported environments, see KB81149 - Supported platforms for File and Removable Media Protection.

Problem

You see performance degradation when you delete files if FRP is installed on the client.

You might also see performance issues when you:

Copy data
Save data
Delete operations that occur in the background

Cause

When you perform actions on encrypted files with FRP, the product checks if the files were encrypted with the legacy SafeBoot Content Encryption 2.x version.

The check takes processing time from the computer. This action can impact the performance, especially when it involves data sets that contain many files.

Solution

This behavior is expected. To work around this issue, see the Workaround section below.

Workaround

Disable support for legacy SafeBoot 2.x files.

CAUTION: This article contains information about opening or modifying the registry.

The following information is intended for System Administrators. Registry modifications are irreversible and could cause system failure if done incorrectly.
Before proceeding, Technical Support strongly recommends that you back up your registry and understand the restore process. For more information, see the Microsoft Windows registry information for advanced users article.
Do not run a REG file that is not confirmed to be a genuine registry import file.

IMPORTANT: Before you perform these steps:

The workaround is advised only for environments where FRP has been newly installed. It is not for environments that retain legacy SafeBoot Content Encryption 2.x files.
Make sure that there are no files still encrypted with legacy SafeBoot Content Encryption 2.x. When this optimization is enabled, version 2.x encrypted files are no longer readable by an FRP client.
Upgrade to FRP.

Use the following steps to disable support for legacy SafeBoot 2.x files:

To disable support for SafeBoot 2.x files, create the following registry entry:
1. Click Start, Run, type regedit, and then click OK.
2. Navigate to the following location:
  
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MfeEEFF
3. Create the following DWORD type registry key names and set both values to 0:
  
  Disentangle
  Version2Exists
4. Exit the registry.
Restart the computer.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

How to resolve performance issues incurred because of the check for encrypted legacy SafeBoot Content Encryption 2.x files

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Title

Title

Knowledge Center

How to resolve performance issues incurred because of the check for encrypted legacy SafeBoot Content Encryption 2.x files

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Choose your region

Title

Title