Are you seeing this on Windows 10, without the Anniversary Update installed yet? (How to check, using the 'ver' command.)
If so, it is likely this issue, and should be fixed by forcing the Windows 10 Anniversary Update to install. (It seems it has not yet installed for everyone, for some reason.)
It can also be fixed by disabling the File History shell extension (details in the 2nd thread I linked), if you are unable to install the Anniversary Update for some reason.