Windows 10: FIle History: Element not found when clean up old files since 2004/20H2

Hi,


this request is similiar to https://answers.microsoft.com/en-us/windows/forum/windows_10-files/file-history-element-not-found-error-on-windows-10/d7043300-9efe-4d83-ab6b-f71812981ca2


Other then he say, an In-place Upgrade did not solve the issue did from 2004 to 20H2.


I am using file history since it was introduced in Windows 8 and it was always working as expected until 2004 arrived.


This is my configuration:

• I am using a networkdrive connected with SMB, so the path to backup is \\diskstation\Sicherung ASRock
• The NAS is is a Synology Diskstation DS218+
• my settings are to backup every 1 hour does work and clean up files obsolote files automatically after 1 month does not work anymore
• I am only backup folders from my D: drive not the userfiles in the Default settings

So since file history does not delete files older than 1 month, when I want clean it manually, I get the "Element not found" error.


Troubleshooting steps:

• I stoped and enabled file history -> same issue
• I deleted the file history files and start again -> same issue
• I also delete all file history backup files and also reseted the file history with the help of that: https://www.tenforums.com/tutorials/54999-reset-file-history-default-windows-10-a.html -> same issue
• Today I did the In-Place upgrade. I used the official 20H2 MVS ISO file, started again a new file history from beginning and tried the option again -> but it's the same issue

So when we can expect a fix here?


No, I can't use the Feedback Hub, because it force me to enable Telemtry.

:)

 

Encountering "Element not found" on File History Cleanup

I have two machines that were updated from 1909 to 2004. One has had File History set up and running for years, starting in version 1607. Previously a Feature Update had stopped File History working, I had to stop using then reconnect the history drive before it would work again. I was impressed by the 2004 update, File History just continued working without a hiccup.

On that machine however many times I clean up versions it always says 'We didn't find any versions of your files that were that old'.


However, the other machine that updated to 2004 had never used File History before. When I set that up to use File History then try to clean up I get the same 'Element not found' message that you see.

 

File History: Element Not Found Error on Windows 10 May 2004

FWIW looks like there's confirmation that this is a 2004 bug:

Encountering "Element not found" on File History Cleanup - Windows 10 Help Forums

 

Encountering "Element not found" on File History Cleanup

Hello all,

Setting up File History here, and I am encountering an error that I wanted to post here and see if there's anyone that can assist.

I am running Windows 10 2004 and setting up a clean install of File History -- meaning no folders except for one with a file in it -- I get an error when attempting to run "Clean up versions" more than once:

"Could not clean up File History data -- Element not found."

(Note that the first time I click "Clean up versions" it results in a "We didn't find any versions of your files that were that old")

FWIW I encountered this issue with a full install/synchronization of my files, but even when I reduce the configuration to a simple folder with a file in it this error still occurs.

Is this a known issue? If I put more data/files in the folder and/or edit data that is in there, I still get this error. It makes me wonder if the catalog is already corrupt. Again this is from a clean install, already having wiped the FileHistory folder in AppData.

Any suggestions/insight here would be appreciated!

- - - Updated - - -

Alright, I have reproduced this on another 2004 machine on which File History was never activated. On this image I have screen capture installed, for your convenience:





In this case, I didn't get a "We didn't find any versions..." message, and it went straight to the error:





Is this a known/unknown bug in 2004, perhaps?

- - - Updated - - -

Wow I am surprised that no one has replied to this. Can someone with 2004 installed confirm that this does not happen to them? Thank you for any assistance you can provide to appeasing my sanity. *chuckle