Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Registry gets corrupted after installing Windows Update in Endpoint Encryption Full Disk Encryption (TMFDE)

    • Updated:
    • 24 Nov 2016
    • Product/Version:
    • Endpoint Encryption
    • Platform:
    • Windows 2008 Server R2

Under certain circumstances when running Windows Update on Windows 7 32 bit, the kernel can run out of memory (0 available memory).  This 0 memory situation is not a memory leak in Endpoint Encryption, but is the result of the OS over provisioning the kernel memory to Windows Update. When this high pressure memory situation occurs and the 4 KB of memory needed by Endpoint Encryption is unavailable, the OS will temporarily force Endpoint Encryption to abort the disk decryption process.

After the decryption process is forced to abort, the OS no longer receives the correct Registry data and the OS detects this as a Registry corruption and proceeds to initiate the registry auto-healing mechanism which in effect will cause the corruption resulting in "Errors found: Code 80080005 Windows Update encountered an unknown error.”

There will be an error in Windows System Event log:

Event ID: 7023

The Windows Modules Installer service terminated with the following error:

The configuration registry database is corrupt.

If you check the C:\Windows\Logs\CBS\CBS.log, you will find this error log:

Failed to initialize Trusted Installer. [HRESULT = 0x800703f1 - ERROR_BADDB]


When running Windows Update, the operating system can provision too much memory to Windows Update. This may cause the kernel to reduce to 0 available memory. With no available memory, Endpoint Encryption aborts the decryption process. From this point, Windows will be unable to read the correct Registry data. This version forces the kernel to re-allocate memory to Full Disk Encryption in high-pressure situations. With sufficient memory, Endpoint Encryption no longer causes Registry issues, so Windows Update continues to function properly.

To prevent this issue, it is strongly advised to upgrade the TMFDE agent with the following:

  • TMFDE 5.0 agents to at least build 5.0 patch 2 build
  • TMFDE 3.0.12/3.1.3 agents to at least build

To recover a corrupted registry database, backup all user data then do one of the following:

  1. Re-install Windows.
  2. Or follow these steps:

    1. Upgrade the TMFDE client.
    2. Submit a support case to request for a copy of a special Windows 7 setup CD according your FDE client version.
    3. Boot to the Windows ISO.
    4. Perform an In-Place Upgrade. You may refer to this Microsoft knowledge base article MS KB 2255099
    5. After the upgrade is finished, reboot the computer.
    6. Verify if Windows Update works.
Troubleshoot; Update
Solution Id:
Did this article help you?

Thank you for your feedback!

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.