Why cant I use network drive mapped via WebDav for File History backup

I have mapped a folder on my NAS via WebDav protocol to drive Z: - it appears in File Explorer and I can read and write into it.

But when I try to use it for the File History in Windows 10, I get this error:



What am I doing wrong?

Berton said:

I'm a-wishing you'd have moved the error message panel [click drag title bar] enough to see the full path to the desired folder. And had mentioned that the XLS folder actually exists.

Well, I didn't want to show the actual address for my NAS server. (Even though it's password protected.)
The format of the URI that is used by the File History window is this:

Code:

\\account.Synology.me@SSL@5006\DavWWWRoot\ShareName

I created a root share just for this backup after I posted this question, thinking that maybe it was as issue. (before I was trying to use a non-root folder on a different share.)

And if I type it into the File Explorer, it opens up the root folder on my NAS and I can create files in it (that I can see on the NAS as well.)
Now what is the XLS file that you are referring to? Because that root folder on the NAS is empty.

Berton meant to refer to the ...\BACKUP\KLS folder, which must exist. It would help to see the complete FH window.

mngerhold said:

Berton meant to refer to the ...\BACKUP\KLS folder, which must exist. It would help to see the complete FH window.

I changed it to the root of another share. And yes, it does exist.

- - - Updated - - -

OK. Judging by the lack of replies, I conclude that Windows File History is a piece of junk. I'm looking for other versioning backup solutions.