Windows File Recovery v. 0.1.20151.0 - hangs when recovering a certain file

Hi HerrWagner,

Thanks for raising your concern in Microsoft Community.

It sounds like your Windows File Recovery v. 0.1.20151.0 hangs when recovering a certain file. It could be caused by the wrong use of the command. You may refer to this article | Recover lost files on Windows 10 (microsoft.com) to get more details about performing the file recovery tool.

Feel free to post back if you need further assistance.

Best Regards,

Lynn Sun | Microsoft Community Support Specialist

-----------------------

* Beware of scammers posting fake support numbers here.

* Kindly Mark and Vote this reply if it helps, as it will be beneficial to more community members reading here.

Thanks for the answer. Maybe I'm doing something wrong, but I can't tell from the documentation that I doing something wrong or that I have forgotten something. In my opinion this is the correct command to restore data from a USB stick, I don't see any other mode that would help me.

From my point of view it should work and it's some bug. But I also cannot imagine that the Windows tool will get stuck forever and not give a message to the user or that the file can't be skipped. Especially because these tools like to run for hours and something like that shouldn't happen. So do I have to do something wrong?

HerrWagner,

The correct syntax of the command shown below for your easy reference:

Thx for replay again.

I'm sorry I don't understand. Since it's Fat32, i have to use the / extensive mode.

1.) The invoice example does not apply, because I generally want to restore all files.

2.) I don't just want to recover images from the document directory, its an regular USB-Stick. As mentioned, even if I only restore the images, the program stalls with a certain file. Therefore the assumption that it must be due to a certain .jpg file.

3.) As already mentioned, I don't see any filter option that could help me.

4.) What is the clue you want to tell me? If you think the syntax is wrong, please just tell me how the syntax is correct.

1.) I can restore files, pdf, jpg and png.

2.) BUT: The program obviously hangs on a certain .jpg file and simply does not continue. Thats the problem. I have no idea why it hangs or why you can't skip the file which is actually the main problem.

3.) I can certainly first recover all .pdf and .doc separately, but but you can't work like that. I can also restore the image files, but only to the point where the program hangs. I can't get to the files after that.

greetings

Hi HerrWagner,

All of the details in this link | Recover lost files on Windows 10 (microsoft.com) are just to make sure that you have used the tool correctly to restore.

At the same time, we must admit that no recovery software can 100% guarantee a successful recovery. It is recommended to cross-use it with other recovery softwares to increase the probability of recovery.

Thanks for your support to Microsoft and feel free to get back to us for any issues pertaining in the future.

Best Regards,

Lynn Sun | Microsoft Community Support Specialist

-----------------------

* Beware of scammers posting fake support numbers here.

* Kindly Mark and Vote this reply if it helps, as it will be beneficial to more community members reading here.

"At the same time, we must admit that no recovery software can 100% guarantee a successful recovery."

Would be nice if I got to the point at all ..

I would be happy if Microsoft at least guarantees that the program runs properly at all. I've never seen anything like that with competing products. Some of these are tools that some people have developed in their spare time.

The tool itself is well structured. Not exaggerated, actually does what it should, also sorts the file types into folders. You have to look at the commands, it is not self-explanatory. In certain points, it is better than the competing products. Would actually be a good basic tool and you wouldn't have necessarily use other software.

But it's relatively useless useless if you don't rely on it. You let the tool analyze the data carrier for a long time, then it starts to recover the files and at some point it simply hangs. Waste of time, you can use recuva or other tools right away. I think my problem shouldn't happen often, the tool seems to work in the most cases. As a customer / user, it just sucks when you waste hours because the program doesn't work properly.

Best Regards