Recover files after Paragon HFS+ Corruption I have been using Paragon HFS+ to get write access to my Mac HFS+ partition from within Windows 8. Suddenly half the files in a directory have gone missing.

A few months ago I copied the files onto an external drive. On discovering the files were missing, I went to copy these old files back to the same directory that has been partially emptied by Paragon HFS+, using OS X Sierra Finder.

However, when I try to copy in the files from a backup, the copy stops, saying there is already a file with that name in the destination folder. Yet the file is not visible with OS X Finder or using the ls -a command.

This gives me hope that the files do still exist on the drive. Somehow, while they are found by the OS X copy command, they are hidden from ls, sudo ls -a, and the Finder GUI. So I cancel the copy, hoping to find a way of recovering the data.

Any ideas how can I recover my hidden files?

How might they be visible to the copy operation but invisible to ls -a?

I have been trying to get help from Paragon's customer support. After 4 days they told me to uninstall and reinstall their software - it is as obvious on my support call as it is here that that is irrelevant to the issue. After another 4 days Paragon told me their software drivers cannot be to blame as they do not write to disks. I can't stop working for a week, so by now I have had to re-create the files.

I was running Paragon's HFS+ software for just 13 days before this corruption happened, and this is the second bug I have tried to get support for (the first was the software refuses to register). Neither bug has fixes or solutions, and they have refused to refund, let alone help recovering my files.
HFSExplorer was able to see and recover some of the files, but most were missing.

Paragon did refund my purchase, after a few attempts at looking at the output of OS X repair commands which showed errors, which apparently they tried to reproduce, and my refusing to send them a dump of my hard disk. I have had no problems with their OS X product to access NTFS drives, and have used that much more extensively.