File History's inability to work is usually caused by connection problems, insufficient permissions or disk space, third-party software interference, and system file corruption. First, check whether the backup target is connected and recognized, try to replace the interface or remap the network drive, and confirm whether the backup drive is correct in the settings; second, check the write permissions and remaining space of the target disk, it is recommended to retain at least 20% of the free space and recommend the use of NTFS format; then temporarily disable third-party security software, and at the command prompt, stop the fhsvc service, delete the cache in the RSA folder and restart the service; finally, if it still cannot be resolved, you can run the sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth commands at the administrator command prompt to repair the system files. Follow the above steps to check and most problems can be solved.

Windows File History is a practical tool that automatically backs up your personal files to prevent data loss. But sometimes you will find that it is not working - it may prompt "no backup disk access", "no drive available", or simply "not running". This situation is quite annoying, but most problems can actually be solved.

Below are some common reasons and corresponding troubleshooting methods to help you solve the problem that Windows File History does not work properly.

Check if the backup target is connected and recognized

File History requires an external hard drive or network location to save the backup. If you are using an external hard drive:

• Make sure the hard drive is properly connected and visible in "This PC".
• Try changing the USB port to troubleshoot the interface.
• If you are using a network path (such as NAS), make sure you are logged in and mapped to the network drive.

Sometimes even if the device is connected, the system may not recognize it. At this time, you can try restarting the computer and then check if there are any changes.

In addition, check whether the backup target is still in the list in the settings:

1. Open Settings > System > About > Advanced Settings > File History Settings.
2. Check whether the Backup Drive displays the correct device. If not, click "Add Drive" to reselect.

Insufficient system permissions or disk space

File History requires write permission to backup normally. If the target disk has read-only permissions, encryption locks, or disk space is almost full, backup failure will occur.

You can check this way:

• Right-click the backup disk > Properties > Security tab to ensure that the current user has "write" permission.
• Check if the remaining space in the disk is sufficient. It is recommended to keep at least 20% of the free space, otherwise the system will clean up old backups.

Additionally, some users report that a mobile hard drive with the format exFAT can cause File History errors in some cases. It is recommended to format the backup disk to NTFS format, with better compatibility.

Disable third-party security software or reset File History

Some antivirus software or firewalls may prevent File History from running properly. If you have third-party security software installed, you can try to temporarily close them and test whether the backup can start.

Another method is to clear the cache and configuration information of File History:

1. Open a command prompt (administrator).
2. Enter the following command and press Enter:

    net stop fhsvc

3. Enter C:\ProgramData\Microsoft\Crypto\RSA folder (need to display hidden files).
4. Delete folders starting with S-1-5 (these are the key caches for File History).
5. Run the command again to start the service:

    net start fhsvc

Then reopen the File History settings and let it reinitialize.

Check if the system files are corrupt

If none of the above methods work, it may be that the system file corruption affects the File History function. You can use the system's own tools to repair:

• Open a command prompt (administrator), enter:

   sfc /scannow

  This process may take several minutes and restart the computer after it is finished.

If the problem does not resolve it yet, you can also try running the DISM tool for deep repair:

 DISM /Online /Cleanup-Image /RestoreHealth

These two commands can help repair system components and may restore the functionality of File History.

Basically, these common investigation directions are all about this. Most of the time it is caused by disk connection, permissions or space problems, and in a few cases it requires handling system settings or file corruption. Check step by step in order, and the reason can usually be found.

The above is the detailed content of Troubleshooting Windows File History not working. For more information, please follow other related articles on the PHP Chinese website!