- Veeam Support Knowledge Base
- Windows File Level Restore running from Remote Shell on Windows 10 failing unexpectedly
Windows File Level Restore running from Remote Shell on Windows 10 failing unexpectedly
| KB ID: | 2162 |
| Product: | Veeam Backup & Replication |
| Version: | 9.x |
| Published: | 2016-09-05 |
| Last Modified: | 2020-08-13 |
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
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:
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
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.
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.
Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Verify your email to continue your product download
We've sent a verification code to:
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!
Your feedback has been received and will be reviewed.