file history - element not found

David Backhouse 60

file history - element not found. Any solutions yet?

I am getting the error message on both Windows 11 and Windows 10 PCs.

Daisy Zhou 28,391 Reputation points Microsoft Vendor

2023-07-28T02:04:35.93+00:00

Hello David Backhouse,

Thank you for posting in our Q&A forum.

To better understand your question, please tell us what you are doing then you see the message "file history - element not found"?

Also, would you please attach the screenshot with "file history - element not found"?

If you have any question or concern, please feel free to let us know.

Best Regards,
Daisy Zhou
David Backhouse 60 Reputation points

2023-07-28T07:44:11.3066667+00:00

OK - this is an issue with many many mentions on various websites including on Microsoft (where there are at least three instances on Feedback). Generally the answer seems to be that this is a bug somewhere in the File History program/clean-up option, which occurs in both Windows 10 and Windows 11. The easiest way to initiate the problem is to run "FhManagew.exe -cleanup 30" from a PowerShell (Admin) window.

As previously noted I have tried all the sfc /scannow and DISM options - mulitple times on both Windows 10 and 11 PCS - no faults identified. Both computers are fully up to date - Windows/drivers, etc.

I have tried switching the file history from the NAS to a local folder - no improvement (and which would anyway invalidate the purpose of File History!).

I have tried deleting all the File History folders (on PC and on NAS) and restarting the whole process, including having to reset all the configuration for excluded folders, etc. Again no improvement, same issue continues.

The consensus seems to be that Microsoft has discontinued support for File History and is not going to fix the problem. Clarification on this would be welcome so we know whether to continue raising the issue or give up and find an alternative back-up solution. Whilst noting that OneDrive is NOT an alternative since it will simply have synchronised any inadvertent deletions, corrupted files, etc.

For information:

Edition Windows 10 Home, Version 22H2, Installed on ‎23/‎10/‎2020, OS build 19045.3271, Experience Windows Feature Experience Pack 1000.19041.1000.0
Daisy Zhou 28,391 Reputation points Microsoft Vendor

2023-07-28T08:27:49.53+00:00

Hello David Backhouse,

Thank you for your reply. We're sorry you're having this issue.

After my search and research, I think you can feedback this issue via "Feedback Hub" on the machine.

And you can try an alternative solution if you find a proper workaround.
Reference.

https://www.makeuseof.com/fix-element-not-found-error-windows/

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/file-history-element-not-found-when-clean-up-old/761eea3d-0ee1-4a4e-a9fd-9bd14546a175?page=1

Best Regards,
Daisy Zhou
David Backhouse 60 Reputation points

2023-07-28T08:57:27.8566667+00:00

Unfortunately the issue has been posted a number of times via Feedback Hub but with no response from Microsoft. So that route isn't working.

As I noted before there are many websites reporting the issue - none with a solution other than the code needs to be fixed by Microsoft.

The first link you provided is pretty useless since it does not address the specific File History issue. The second link is also useless since it does not provide a solution, merely a list of other frustrated users.
Andrew 10 Reputation points

2024-02-25T22:36:59.79+00:00

can confirm. have searched extensively for a solution and found from community feedback, its MICROSOFT

what i noticed is that it does the first delete of old files fine, then a directory is made in C:\Users*USER*\AppData\Local\Microsoft\Windows\FileHistory and then it no longer can find whatever element it is looking for. hope someone sees this and fixes it! would love for the system apps from microsoft to actually work and not depend on third party software. especially since apple has their house in order by comparison
Guy Smith 0 Reputation points

2025-01-11T15:23:29.8733333+00:00

This problem has been going on for years and Microsoft refuses to address it.

Fed-up, I bought EaseUS backup this week. It works, has clear notifications.

3 answers

MZ 0 Reputation points

2024-06-10T10:10:17.7+00:00
Using ProcMon i've got this informations:

FileHistory cleanup looks for the file user32.dll.mun in the directory C:\Windows\SystemResources, but there isn't it! -> error message "element not found" and stop cleanup

FileHistory backup doesn't need this file.

i found a file user32.dll.mui in C:\Windows\System32\de-DE

a simple copy from there to directory C:\Windows\SystemResources is not possible, because the target directory is heavy protected from TrustedInstaller (admin is not enough)

Question: from where can i get the correct user32.dll.mun and how to install it in the target directory?
Please sign in to rate this answer.
Tom B 0 Reputation points

2024-09-05T10:26:43.0066667+00:00

Using PowerRun I was able to copy the user32.dll.mui file that is stored in the WinSxS directory to the protected C:\Windows\SystemResources directory.

Trying to trick the system i rename the user32.dll.mui to user32.dll.mun

Sadly this did not resolve this issue. Does anyone has a user32.dll.mun file that I can test?

Tom B 0 Reputation points

2024-09-05T10:27:41.2566667+00:00

Also tried to use the user32.dll and rename it to user32.dll.mun

Still no luck

Jerry Ewing 0 Reputation points

2025-01-09T20:59:53.1933333+00:00

I have that file, but I still have the problem. C'mon, Microsoft, cloud backup is NOT a solution when I have 4TB of files!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more
JaySleezy3 0 Reputation points

2024-12-13T17:50:45.8433333+00:00

I was also getting this error message when saving to a network drive after I had cloned a client's computer to a new one. Somehow the system changed the default application (in my case) to open PNG files with "windows.system.launcher". Make sure your computer is opening files with the correct application and not something odd.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

file history - element not found

3 answers

Your answer