Data Domain: BoostFS Lockbox Corruption After Windows Patching Causes Mount Failures

BoostFS mount operation fails with the error:
"The requested Lockbox entry could not be found."
Lockbox query operations fail with:
"Cannot initialize lockbox."
Lockbox credentials appear valid immediately after creation and can be successfully queried.
Following Windows patch installation and a system restart, lockbox file sizes change unexpectedly.
Existing lockbox entries become inaccessible after reboot.
Recreating the lockbox restores mount functionality until the issue reoccurs.

Engineering determined that lockbox files can become corrupted when Windows updates and system reboots occur after BoostFS installation on newly deployed systems. Although the lockbox is initially created successfully, the patching and reboot process may alter lockbox files, resulting in failed lockbox queries and unsuccessful BoostFS mount operations. The specific Windows patch responsible could not be conclusively identified.

Engineering recommended performing all Windows patching and required system reboots before installing and configuring BoostFS.

Recommended installation sequence
Deploy the Windows system.
Apply all required Windows updates.
Reboot the system as needed.
Install BoostFS.
Configure the lockbox.
Verify lockbox functionality and mount operations.

Following this sequence prevents lockbox files from being present during the patching and reboot process, helping maintain lockbox integrity and eliminating the observed mount failures.