I just did and let it run for more than 3 hours. Still the same effect, except it went in couple of minutes to 99% (see the image) and hanged there. Recuva becomes unresponsive and the process must be killed in order to exit Recuva.
BTW, there's an error in that documentation. The debug log file resides in "C:\Users\<user_id>\" directory instead of the installation directory.
Glary undelete, instead, responds to cancel command, and then let's you try to restore the files it has found.
Recuva_log_1_30_435__6_9_2009_17_4_.txt
Recuva_log_1_30_435__6_9_2009_17_4_.txt