could not clean up file history data element not found

Install the latest Windows 11 cumulative update, restart, and then retry cleanup with Microsoft’s supported FhManagew.exe command instead of repeating the failed Control Panel operation.

1. Update Windows first

1. Open Settings → Windows Update.
2. Select Check for updates and install all available cumulative updates.
3. Restart Windows.

This is especially important if File History also stopped backing up, shows Reconnect your drive, fails to update Last backup, or reports No previous version available. Microsoft documented those symptoms after September 2026 updates and resolved them in updates released on or after September 22, 2026, including KB5124010 for Windows 11 24H2/25H2.^1^

To identify your version and build, press Windows key+R, enter winver, and select OK. The documented update problem does not specifically mention the cleanup message “Element not found,” so do not attribute that message to the update unless the other documented symptoms also apply.

2. Retry cleanup from Terminal

Right-click Start, select Terminal (Admin), and run the command matching the versions you want to retain:

FhManagew.exe -cleanup 30

This removes eligible versions older than 30 days. Other examples are:

FhManagew.exe -cleanup 90
FhManagew.exe -cleanup 365
FhManagew.exe -cleanup 0

Using 0 removes all eligible versions except the newest version of each file currently within File History’s protection scope. Review that risk before running it. Microsoft documents FhManagew.exe as the supported command for deleting versions older than a specified age.^2^

If this command also returns Element not found, the problem is not limited to the Control Panel interface. The exact error has been reported with File History cleanup, but there is no documented Microsoft repair that maps that message to one confirmed cause.^3^

3. Refresh the selected destination

Before replacing the backup set:

1. Open Control Panel → System and Security → File History.
2. Select Select drive.
3. Select the existing backup drive again and choose OK.
4. Select Run now and wait for it to finish.
5. Retry FhManagew.exe.

Microsoft explicitly documents reselecting a network destination when reconnecting File History.^4^ Reselecting the same local drive is a reported temporary workaround for File History state and tracking problems, but it is not an officially documented fix for this cleanup error.^5^

4. If cleanup still fails

The existing history catalog or repository may be inconsistent, but the error alone does not confirm that diagnosis.

If the old versions are important, leave the existing FileHistory folder intact and use a different drive for a fresh history:

1. Turn off File History.
2. Disconnect the existing backup drive and preserve it as an archive.
3. Connect another drive.
4. Open Control Panel → System and Security → File History → Select drive.
5. Select the new drive, then select Turn on.^6^

If the old versions are no longer needed, turn off File History and rename the top-level FileHistory folder on the backup drive before configuring a fresh set. Administrator permission may be required. Do not delete individual catalog or data subfolders, and retain the renamed folder until the new backup completes and its files can be restored successfully.

If the failure remains reproducible on a fully updated system, submit it through Feedback Hub with the winver version/build, recently installed KBs, exact cleanup command, full error text, and whether normal backups and Previous Versions still work.

References

1. September 8, 2026—KB5124008 (OS Builds 26200.9445 and 26100.9445)
2. FhManagew.exe
3. file history - element not found - Microsoft Q&A
4. Reconnect Your File History Drive in Windows | Microsoft Support
5. Windows 11/10 updates KB 5101684 and KB5120249 file history issue; other users have encountered problems with file history logging. - Microsoft Q&A
6. Backup and restore with File History | Microsoft Support