Semaphore Timeout when mounting recovery points using Local Mount Utility (4038438)

Recovery points mount successfully using core UI but when using Local Mount Utility (LMU) you receive "TevoMountReplay failed with error -2147024775 (0×80070079 – The semaphore timeout period has expired".

Rapid Recovery users may see  "Core service cannot be reached. Please check the network connection and if the service is running."

The fix involves editing the Windows Registry to increase several timeout values.

⚠️ Important Warning: Editing the Windows Registry is risky. A mistake can cause system instability. It is highly recommended to back up your registry before you begin.

Step 1: Preparation

Before making any changes, you need to prepare the system.

1. Make sure any and all recovery points are dismounted from the Local Mount Utility.

2. Stop the LMU service on your server.

📍 Important: The following registry changes must be made on the computer where the Local Mount Utility (LMU) is installed and being used to mount the recovery points.

Step 2: Increase the LMU Connection Timeout

1. Open the Registry Editor.

   • Press the Windows Key + R, type regedit, and press Enter.

2. Navigate to the LMU User Settings.

   • Copy and paste the following path into the address bar at the top:

     HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\LocalMountUtility\UserSettings
     

3. Change the Timeout Value.

   • In the right-hand panel, find and double-click on CoreConnectionTimeout.

   • Change the Value data to 00:45:00. This increases the timeout to 45 minutes.

   • Click OK.

Step 3: Increase Driver Timeouts

Now, you'll increase the timeout for the underlying storage and disk drivers.

1. Navigate to the AAVDisk Driver Settings.

   • In the Registry Editor, go to this path:

     HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AAVDisk\Parameters
     

   • Find NetworkTimeout, double-click it, select the Decimal base, and change the value to 600000.

   • Find AsyncNetworkTimeout, double-click it, select the Decimal base, and change the value to 600000.

2. Navigate to the AAVStor Driver Settings.

   • Next, go to this path:

     HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AAVStor\Parameters
     

   • Repeat the same changes: Set both NetworkTimeout and AsyncNetworkTimeout to a Decimal value of 600000.

Step 4: Restart Services

The registry changes won't take effect until the related services are restarted.

1. Open Command Prompt as an Administrator.

   • Click the Start Menu, type cmd, right-click on "Command Prompt," and select "Run as administrator."

2. Restart the Driver Service.

   • Type the following commands, pressing Enter after each one:

     sc stop aavdisk
     sc start aavdisk
     

   • Note: If the start command fails, you will need to reboot the server.

3. Start the LMU Service that you stopped in Step 1.

4. Try Again.

   • You should now be able to mount the recovery point in the Local Mount Utility without the timeout error.