This will occur when using a recovery environment (WinRE, BartPE, and the like); unfortunately, it's that these environments, being extremely cut-down versions of Windows, do not have the needed components for Recuva to function properly, so basically, what you're seeing is:
You tell Recuva to recover files
Recuva asks the operating system to enumerate the file system
The recovery environment's OS, lacking the functionality to do so, returns no information
Recuva then has no information to display to you, the user
</li>
As such, there really isn't a way to fix this outside of running Recuva in a normal, fully working installation of Windows. If that can't be done on the computer, then you may need to make use of another recovery tool that can be used in a recovery environment, or that has its own recovery environment to work with.
<div class="ipsQuote_contents">
<p>
This will occur when using a recovery environment (WinRE, BartPE, and the like); unfortunately, it's that these environments, being <em>extremely</em> cut-down versions of Windows, do not have the needed components for Recuva to function properly, so basically, what you're seeing is:
</p>
<ul><li>
You tell Recuva to recover files
</li>
<li>
Recuva asks the operating system to enumerate the file system
</li>
<li>
The recovery environment's OS, lacking the functionality to do so, returns no information
</li>
<li>
Recuva then has no information to display to you, the user
</li>
</ul><p>
As such, there really isn't a way to fix this outside of running Recuva in a normal, fully working installation of Windows. If that can't be done on the computer, then you may need to make use of another recovery tool that can be used in a recovery environment, or that has its own recovery environment to work with.
</p>
</div>
Is this true for your products generally? I mean, e.g., if I'm in WinRE, will the portable CCleaner only scan and clean the WinRe registry on drive X: or can I force it to scan and fix problems on the system (c:\) registry? Thanks.