Windows 10: Windows 10 FileHistory Bug

I cannot get my FileHistory to keep doing regular backups, it decides to stop backing up manually or automatically. In the even log I am given this message:

Unable to start a backup cycle for configuration

At this location

"C:\Users\Home\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Config"

I'm the latest version of Windows 10 with all updates, the FileHistory backs up to a external USB 3.0 hard drive

Latest Windows 10 updates, excluding the optional 2020-07 Cumulative Update Preview (KB4568831)

It should be noted I don't have a C:\Users\Home\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Config

folder or location I do have a

C:\Users\Home\AppData\Local\Microsoft\Windows\FileHistory\Configuration

Location with these 6 files in it

https://imgur.com/U3nrS7r

submitted by /u/suglow
[link] [comments]

:)

 

Bug > FileHistory/Credential Manager

Hi,

I don't know where to report this so please guide me.

I use FileHistory to back up all my Windows 10 PCs. Target backup location is a Synology NAS.

FileHistory uses the Credential Manager to log into the NAS and store the backup files. To me that's a huge problem and therefor a serious bug.

If I have to store credentials in Credential Manager for FileHistory to be able to store the backup everyone can access that backup data.

I should not be difficult for ransomeware to ask the Crendential Manager to browse the backup location and then encrypt it. It's pretty ironic that this is a valid scenario - you would think your FileHistory backup is where you restore all data from when it
has been encrypted - but that's not the case when the entire backup is encrypted.

I suggest that FileHistory uses it's own password vault instead of Windows Credential Manager. It's a huge flaw that the Credential Manager is being used for backup purpose and it defeats the purpose of having a secured backup when everyone can access the
backup files. The goal must be to only grant the backup client access to the backup location.

// peter

 

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.

 

FileHistory stops working

Hello

In have FileHistory backup not working correctly.

After my desktop backup for the portioned drives C: and D: stopped say 6 weeks ago. I have tried a number of suggestions from the form but have not got things working until yesterday 27/6/2020.

After using the same USB extension drive to back up my laptop which worked.

I tried the same usb derive with the desktop and found that by selecting the drive as new a new list of folders to be backedup was created only for drive C: and the FileHistory back up worked again.

Now IF I add any folder on derive D: to the backup list FileHistory stops working.

If I remove the D: related folder FileHistory works again.

When FileHistory stops working event viewer shows the 1st error message .

In the past when FileHistory didn't work EV showed both errors.

Unable to scan user librariles for changes and perform backup.

C:\Users\pflet\AppData\Local\Microsoft\Windows\FileHistory\Configuration\Config

File/directory was not backed up due to being encrypted or insefficent permissions.

D:\System Volume Information.

As enyone seen this?

Could this be the System volume information folder on D: ?

Can this folder be replaced / repaired ? I carn't see it being encrypted. Dont Know about permissions.

Thanks in advance. Paul