NVP-vProxy: Windows VM FLR Fails With "Error while browsing: 200: Error received from vProxy "could not get directory contents:"

vProxy File Level Recovery (FLR) for a Microsoft Windows VM fails with the following error:

Error while browsing: 200: Error received from vProxy "could not get directory contents: Unable to retrieve file list from 'host' (vm-moref) path 'path'"

The Windows VM does not contain Windows Distributed File System (DFS): NVP vProxy: Virtual Machine FLR Consistently Failing With "Could not get the directory content…"

This error can appear if the Admin Approval Mode (AAM) is enabled on the operating system. This prevents an administrative user from performing an FLR to the end user s profile. For any User Account Control (UAC) interactions, the administrator must wait for the mount operation to complete, and then access the mountpoint on the target machine.
 

There are three options available:

Option 1:

Perform the FLR from the NetWorker Web User Interface (NWUI). There is an option inside the FLR process called "run with elevated privileges." Check this option when performing the FLR. 

Option 2:

1. Initiate the FLR mount from the NetWorker Management Console (NMC):

 
 

 
 

You can browse to the needed folders/files and copy them to the Virtual Machine. Files can also be copied using xcopy : xcopy mountpoint_folder/file recover_destination /EH

3. When done, close the Recover Wizard in the NMC to disconnect the mount point.

Option 3:

Instant Access restores can also be used as an FLR workaround. This process is documented under: 

NVP vProxy: Perform VM FLR without vProxy FLR Agent