Windows File Level Restore running from Remote Shell on Windows 10 failing unexpectedly

KB ID: 2162
Products: Veeam Backup & Replication
Version: 9.x
Published:
Last Modified: 2016-09-08

Challenge

You are trying to start Windows File Level Restore running from Remote Shell on Windows 10 but it fails unexpectedly with a general error:

User-added image

In the log files (C:\ProgramData\Veeam\Backup\FLRSessions\Windows\FLR__<vm_name>_\VeeamAgent.MountVm.Client.log) you may observe following error code:

[05.09.2016 18:30:14] <  4728> mnt| Virtual space {b7ac05db-bfce-41fb-8d5c-780993e049de} was destroyed
[05.09.2016 18:30:14] <  4728> mnt| VeeamFCT driver communication library was deinitialized
[05.09.2016 18:30:14] <  4728> drv| ERR |CVeeamFCTDriver::FileMount: Failed to mount file 'C:\WINDOWS\system32\config\systemprofile\aoivmtwx.mot\veeamflr-0000417000007499-0000.flat'.
[05.09.2016 18:30:14] <  4728> drv| >>  |Details: FctVsAddFile() : HRESULT = 0x80070003
 

Cause

Windows environment variables for local system (SYSTEM) are missing or not set.

Solution

You need to recreate missing values in the following registry key on Windows with Remote Shell running: 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment 

Name: TMP 
Type: Expandable String Value 
Value: %SystemRoot%\TEMP 

Name: TEMP 
Type: Expandable String Value 
Value: %SystemRoot%\TEMP

Afterwards please restart Windows.

0 / 5 (0 votes cast)

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Orphus system