Share via

File History Cleanup Fails & Backup Skips Long Paths – Windows 10 & 11 Bug?

Anonymous
2025-05-15T17:37:35+00:00

Hi everyone,

I’m encountering two major issues with File History in Windows 11 and Windows 10, affecting both cleanup functionality and backup reliability. The cleanup feature worked about a year ago, but after recent Windows updates, it appears to be completely broken. Microsoft Support has confirmed that there is no fix.

Issue 1: File History Cleanup Fails with "Element Not Found"

  • Running fhmanagew.exe -cleanup X results in "Element Not Found", even though backup files exist.
  • Cleanup fails regardless of file path length, metadata presence ($OF folder), or backup completeness.
  • The feature worked about a year ago, meaning a Windows update likely broke cleanup functionality.
  • SFC/DISM scans show no system corruption; Event Viewer does not log useful errors related to cleanup.
  • CHKDSK / r Confirms no file problems
  • File History Reset performed

Issue 2: File History Silently Skips Long Paths Without Warning

  • Files with paths longer than 144 characters in C:\Users are never backed up, yet Windows provides no warning.
  • The longest path in C:\Users\Documents is 250 characters, (Windows limit is apparently 256) but in File History, the longest backed-up path is 206 characters – This includes the already added prefix X:\FileHistory\USERNAME\PC-NAME\Data\C\Users\USERNAME and the added suffix (YYYY_MM_DD HH_MM_SS UTC)
  • Over 18,000 files were silently skipped from my backup, meaning File History is not reliable.
  • Event Viewer logs show no backup errors, relevant to the above - leaving users unaware that critical files are missing.

Microsoft Support Response

I contacted Microsoft Support, and they confirmed that there is no fix for either problem in Windows 10 or 11. Their only suggested workaround was to manually copy all 50,000+ files and folders to another drive every day, which defeats the entire purpose of an automated backup system.

Request for Community Input

  1. Has anyone else experienced these issues?
  2. Does anyone have a workaround that does not require manual file copying?

(I know I could buy a 3rd party backup solution – or manage with the old ‘Windows 7 Backup in control panel – or use the new MS cloud backup - but File History is just ‘Set & forget’ – if it worked) and after all – I’ve bought a license and wouldn’t even mind paying more for something that’s built in and is reliable - but not subscription based

  1. Has Microsoft ever acknowledged that a Windows update broke cleanup?

The more users that confirm these failures, the greater the chance Microsoft will address them in future updates.

Thanks!

Windows for home | Windows 11 | Recovery and backup

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-05-22T15:09:57+00:00

    Hello jhajin

    Thank you for taking the time to acknowledge my post

    I'm sorry to learn that you, like many others suffer the problem with 'Element not found'

    I too have set up quite a few Windows 10 & 11 PC's and with File History on - the cleanup problem still persists

    Interestingly - In April 2024 I formatted the disk and did a clean install (using the DVD iso I downloaded and created for the original install in January 2024) in an attempt to fix 'Element not found' - In desperation - In May 2024 - I chatted with MS support - after all the usual checks - they decided to do an on-line repair - they used 'quick assist' - downloaded the latest Windows 11 iso at that time and ran setup from within the running version of windows

    During the install and re-boots - quick assist was disconnected - I finished the install - all the time thinking 'what a waste of time' - over the next few days - I tested File History cleanup and to my astonishment - instead of 'Element not found' - I got either something like 'Done' or 'We can't find anything that old' - So it was working in Windows 11 - Unfortunately - after a few weeks (and probably Windows Updates) 'Element not found' returned

    I have read other posts where people say File History cleanup (Not backup) Needs 'User32dll.mun' and it searches for it in the C:\Windows\SystemResources folder - I have searched this folder on my system but it's not there - I have also searched many iso's by expanding the install.wim or install.esd folder but have never found it

    I sometimes wonder if this file IS the 'Element that is not found' - and also wonder - if for whatever reason - the .iso that the MS support technician downloaded in May 2024 DID contain 'User32dll.mun' - is that why it worked? - did a later update remove it? - who knows!

    All I do know is that it appears to be 'a walk in the park' for Microsoft to fix it

    Anyway - good luck to you also (and anyone else) who is trying to find a fix for this

    Was this answer helpful?

    0 comments