Windows 10: FileHistory backup

Regarding FileHistory backup drive, if I select "Stop using device" can I still use the same external hard drive by selecting "Add a drive"?

:)

 

FIleHistory: some folders are not backup up anymore

Preamble: I have been used FileHistory to backup my folders and files on a network drive since long.

All backup up folders where included in the Library, therefore I nave used the Backup Contro Panel to include other folders in the backup list.

Up to yesterday everything was working fine.

Yesterday I used the Backup Control Panel to see what was happening if I was adding folder "C:\User\Paolo" to the list of included folders.

Shame on me ..

Since then FileHistory stopped backing up all folders, with one exception: the special folder "Download" which is the only one in my Library to be located in drive D:\ (that is, outside C:\User\Paolo)

Removing the folder C:\User\Paolo from the included didn't work.

Restoring Windows to a previous restore point did not solve the issue.

Starting a new backup on a different network drive did not work.

The final solution was to both

• remove all files located in C:\Users\Paolo\AppData\Local\Microsoft\Windows\FileHistory\Configuration
• start a new backup in a new folder/network drive

I hope that sharing this will help others with the same issue.

Paolo

 

Windows 10 Backup / FileHistory

I had a backup drive using FileHistory in Windows 8.1. After having upgraded to Windows 10 however the the Backup option in settings is not doing what I want it to at all!!!

It doesn't allow me to choose which folders to backup and which to exclude. However many times I change these it always reverts to the default setting of backing up everything with no exclusions.

FileHistory was a very useful feature of Windows 8.1 and I would like to be able to do the same in Windows 10. Please help.!

 

Bug: Windows 10 (build 14393.693) FileHistory when using hidden network share as backup destination

Okay. Seems like it's impossible to report a bug as a standard consumer. I don't wanna call Microsoft supporter or anything - I just want to say that I've found a bug.

It's pretty simple to reproduce.

1. You have to have a FileHistory running using a network location as backup destination.

2. Disconnect the backup share (like move the folder so FileHistory cannot find it anymore).

3. Setup a new network share but make the new share hidden (so you have to use $ to browse it)

4. Enter FileHistory configuration

5. Configure FileHistory to use the new share - browse your way in \\someserver\share$\

6. FileHistory now asks you if you want to move previous FileHistory to the new location. Click Yes.

7. FileHistory now fails. Note that when you have clicked Ok to the fail dialog the screen shows your new network backup destination. BUT there's no $ in the path. The FileHistory process is kind of halted and you cannot start it, because the new destination
does not exist (due to lack of $ in path).

8. To workaround, reproduce step 4-5 but in step 6 click No to move previous FileHistory.

9. Now the label has the new network path has the $ in its destination and the FileHistory is now working.