Free tools Windows power users keep installed
One-click scans. No signup required.
fhcleanup.dll is a genuine Microsoft Windows system component called File History Disk Cleanup Handler. If Windows says it is missing, corrupt, or cannot be loaded, repair Windows component files instead of downloading a replacement DLL.
The file normally belongs to File History and Disk Cleanup integration, not to a game, Visual C++ Redistributable, DirectX, .NET, or another third-party runtime.
What this file actually does
File History automatically maintains versions of selected personal files on another drive or network location. fhcleanup.dll provides the Windows handler used when older File History versions are cleaned up.
On a supported installation, the normal 64-bit Windows path is:
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
C:WindowsSystem32fhcleanup.dll
A 32-bit counterpart may also exist under:
C:WindowsSysWOW64fhcleanup.dll
Do not swap files between those folders. System32 contains the native system components for the installed Windows architecture, while SysWOW64 is used for 32-bit compatibility components on 64-bit Windows.
The file is a Windows component published by Microsoft. Its exact version and size depend on the Windows release, edition, architecture, and servicing level, so there is no safe universal DLL version to download.
Match the symptom to the likely cause
| What you see | More likely explanation | Best first action |
|---|---|---|
| “The program can’t start because fhcleanup.dll is missing” | A deleted, quarantined, or damaged Windows component | Run Windows Update, DISM, then SFC |
| “fhcleanup.dll cannot be located” during startup | Windows or a service is trying to load the File History handler | Check the file path, then repair Windows |
| “The module was not found” | The file or one of its dependent Windows components cannot load | Run DISM and SFC |
| “fhcleanup.dll is not designed to run on Windows” | Wrong, damaged, or mismatched binary | Remove the unofficial replacement and repair Windows |
| “Could not clean up File History data — Element not found” | File History configuration, destination, or metadata may be inconsistent | Check the File History drive and cleanup configuration |
| An unrelated game or app shows the error | The application may be surfacing a broader Windows problem | Repair Windows before reinstalling the app |
| Antivirus quarantined the file | Security software detected or isolated a system file | Verify the quarantine entry and scan Windows |
The “Element not found” message is not proof that fhcleanup.dll is missing. A disconnected File History destination or inconsistent backup metadata can produce a separate cleanup failure.
Fix 1: Install Windows updates and restart
An incomplete update can leave Windows components at different servicing levels.
- Press Windows + I to open Settings.
- Select Windows Update.
- Select Check for updates.
- Install all available updates.
- Restart the computer, even if Windows does not immediately require it.
- Retry the File History cleanup or the program that displayed the error.
On Windows 10, open Settings → Update & Security → Windows Update, then select Check for updates.
If the error remains, continue with component repair. Installing updates alone does not always reconstruct a damaged system file.
Fix 2: Repair Windows with DISM and SFC
DISM repairs the Windows component store. SFC then uses that repaired store to replace damaged or missing protected system files. Run them in this order.
- Open Start and type
Command Prompt. - Right-click Command Prompt.
- Select Run as administrator.
- Approve the User Account Control prompt.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for DISM to finish. It can appear paused for a while.
- Run:
sfc /scannow
- Wait until verification reaches 100 percent.
- Restart Windows.
- Retry the operation that produced the
fhcleanup.dllerror.
SFC may report that it found and repaired corrupt files. That is a successful result. It may also report that no integrity violations were found, which means the problem may involve File History configuration, a dependency, or security software rather than the file itself.
If DISM reports that source files cannot be found, do not copy fhcleanup.dll from another computer. Use a matching Windows installation source with DISM’s /Source option. The source must correspond appropriately to the installed Windows image and architecture, as Microsoft explains in its Windows image repair documentation.
Manually hunting through Windows folders and repeating DISM and SFC without knowing what changed can be tedious. Outbyte PC Repair can show detected Windows issues in its free scan, while repair actions require the full version; it is optional, and Windows’ built-in DISM and SFC remain the primary repair path.
Fix 3: Check whether the file is really present
Before attempting more invasive repairs, check the expected location.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
- Open File Explorer.
- Browse to
C:WindowsSystem32. - Search for
fhcleanup.dll. - If you use 64-bit Windows, also check
C:WindowsSysWOW64. - Right-click any matching file and select Properties.
- Open the Digital Signatures tab if it is available.
- Confirm that the signer is Microsoft and that Windows reports the signature as valid.
A file with the correct name is not automatically trustworthy. If it is unsigned, located in a user-download folder, or present in an unusual application directory, do not register or replace it. Run a full scan with Microsoft Defender and investigate the file’s origin.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If the file exists but Windows still cannot load it, the problem may be a damaged dependency or component store. Continue with DISM and SFC rather than copying over the existing file.
Fix 4: Check antivirus quarantine
Security software can remove or quarantine a Windows file after a false positive, or because another program altered it.
- Open Windows Security from Start.
- Select Virus & threat protection.
- Select Protection history.
- Look for an entry involving
fhcleanup.dll. - Check its path, detection reason, and timestamp.
- Do not restore it immediately if the path or signature is suspicious.
- Run a full scan of Windows.
- If the quarantined file was in the legitimate Windows directory, has a valid Microsoft signature, and the detection is confirmed as a false positive, use your security product’s Restore or Allow on device action.
- Run DISM and SFC afterward.
Do not restore an unsigned DLL downloaded from another source. If the file was quarantined because of malware or unauthorized modification, leave it isolated and repair or restore Windows instead.
Fix 5: Resolve a File History “Element not found” error
If the exact message is:
Could not clean up File History data — Element not found
treat it as a File History troubleshooting problem, not automatically as a missing-DLL problem.
First check the destination:
- Connect the external File History drive.
- If it is a network destination, confirm that the computer can reach it.
- Make sure the drive has its usual drive letter and is not offline.
- Open Control Panel.
- Select System and Security → File History.
- Select Advanced settings.
- Select Clean up versions.
- Choose the retention period and run cleanup.
Microsoft also provides the FhManagew.exe command-line utility. Open Command Prompt as administrator and use a command such as:
FhManagew.exe -cleanup 30
For a quiet cleanup:
FhManagew.exe -cleanup 365 -quiet
The number represents the age threshold in days. A value of 0 removes eligible versions except the newest version of each currently protected file. See Microsoft’s FhManagew.exe documentation before using a command that removes historical versions.
Back up important data before resetting File History or changing its destination. Do not delete the File History folder as a routine DLL fix, because that can destroy historical versions. If cleanup still fails while Windows passes DISM and SFC checks, the issue may be stale configuration or inconsistent File History metadata.
Microsoft also documents how to reconnect a File History drive.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsFix 6: Do not use Regsvr32 as the first repair
Some inspected versions of fhcleanup.dll expose COM registration functions such as DllRegisterServer. That makes regsvr32 technically relevant to the file’s registration model, but it does not make registration a general repair.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Avoid treating this as the solution:
regsvr32 fhcleanup.dll
Registration cannot recreate a missing binary, repair a damaged component store, restore servicing metadata, or fix an inconsistent File History database. It can also fail because of permissions, missing dependencies, or a 32-bit and 64-bit architecture mismatch.
Use regsvr32 only when Microsoft or a specific Windows repair procedure explicitly calls for it. For a missing or corrupt protected Windows component, DISM followed by SFC is the correct first-line repair.
Fix 7: Check architecture and avoid manual copying
A 32-bit DLL and a 64-bit DLL are not interchangeable, even when their filenames match.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Do not copy from
SysWOW64toSystem32. - Do not copy from another PC running a different Windows release.
- Do not use a DLL from an older installation to replace a current protected file.
- Do not download a file that merely has the same filename.
- Do not run a 32-bit registration command against a 64-bit component, or vice versa.
If an application reports the error but Windows itself appears healthy, identify whether that application is 32-bit or 64-bit. Even then, repair the Windows installation rather than sourcing a replacement DLL manually.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Fix 8: Repair or reinstall Windows
If Windows Update, DISM, and SFC do not restore the component, escalate without deleting personal files.
Windows 11 repair reinstall
Windows 11 may offer a repair reinstall through Windows Update:
- Open Settings.
- Select System.
- Select Recovery.
- Find Fix problems using Windows Update.
- Select Reinstall now.
- Follow the prompts and restart when asked.
This reinstalls the current Windows version while preserving apps, files, and settings when the feature is available for that installation.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →In-place installation
If the recovery option is unavailable, use matching Windows installation media. Start setup from within Windows and select Keep personal files and apps. Back up important files first and confirm that the installation media matches the installed Windows edition and architecture.
This replaces Windows system components without requiring a clean installation. A clean installation should be a later option, not the first response to one missing system DLL.
System Restore
If the problem began after a driver, update, security-product change, or system modification, System Restore may roll back system files and settings to an earlier restore point. It normally does not remove personal files, but applications and drivers installed after the restore point may be affected.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Open Start, search for Create a restore point, open it, select System Restore, and choose an appropriate restore point. If no suitable point exists, use the repair-installation path instead.
About drivers and Device Manager
fhcleanup.dll is not a device driver, so Device Manager is not normally the fix. Check drivers only when the error appeared alongside a failing storage device, disconnected backup drive, or recent hardware change.
- Right-click Start and select Device Manager.
- Expand Disk drives, Storage controllers, and any relevant network-device category.
- Look for a warning icon.
- Right-click the affected device and select Update driver.
- Choose Search automatically for drivers.
- Restart Windows if a driver is installed.
Windows Update and the hardware manufacturer remain the preferred sources for drivers. Outbyte Driver Updater can scan for outdated drivers, with installation handled by the full version; it is optional and does not replace repairing Windows or reinstalling the application that actually owns a separate error.
FAQ
Is fhcleanup.dll safe?
It is a legitimate Microsoft Windows component when it is in the Windows system directory and has a valid Microsoft signature. Its name alone is not proof of authenticity, so scan unusual copies.
Is it part of File History?
Yes. It is the File History Disk Cleanup Handler used by Windows’ File History and Disk Cleanup integration. It is not a general-purpose runtime package.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Should I download fhcleanup.dll separately?
No. There is no official standalone Microsoft redistributable for this file. Repair Windows through Windows Update, DISM, SFC, or a repair installation.
Why does a game or unrelated program mention it?
The program may be triggering a Windows component or displaying a generic loader error. That does not mean the game includes or should distribute fhcleanup.dll. Repair Windows first, then repair or reinstall the program if its own files are also damaged.
Will reinstalling a runtime fix it?
Not normally. fhcleanup.dll is a Windows File History component, not a Visual C++ Redistributable, DirectX, or .NET runtime file.
What if the error returns after SFC repairs it?
Install pending updates, restart, and check antivirus quarantine. If the file is repeatedly removed, investigate security detections or malware. If File History alone fails, check the destination drive and its configuration rather than repeatedly replacing the DLL.
Recommended Free Tools
When should I reinstall Windows?
Use an in-place repair installation when DISM and SFC cannot restore Windows or when multiple protected components fail. Back up important data first and select Keep personal files and apps when that option is available.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
