Other causes include problems with the FSRM service, interference from antivirus programs, or shutting down the computer incorrectly.

1. Reset FSRM

If the transaction log is damaged, Windows can’t manage update files properly. Resetting FSRM (File System Resource Manager) restarts the process that manages these logs, so updates can work again.

2. Delete Common Log File System (CLFS) Transaction Logs

If the CLFS transaction logs are damaged, updates can’t make changes to the system. Deleting these logs makes Windows create fresh ones, fixing any problems and letting updates work normally again.

3. Run the Windows Update Troubleshooter

Some update problems happen because services are set up wrong or there are small errors. The Windows Update Troubleshooter checks for these issues, fixes them, and puts update settings back to normal.

4. Restart Windows Update Services

Windows Update relies on several services, including the BITS service, Windows Update service, and Cryptographic service. If any of them isn’t working properly, update errors like this can appear. It’s best to restart all of them for a clean start.

5. Re-register Windows Update Files

Here, we will re-register both the BITS (Background Intelligent Transfer Service) and Windows Update files. Click here to download the Windows Reg Update file, right-click on it, and choose ‘Run as Administrator’.

6. Rename Corrupt Update Stores

Sometimes, failed updates can trigger this error. Renaming the existing update stores allows Windows to build new ones from scratch, which can fix the problem.

FIX  Windows Update Error 0x80071a91 - 56FIX  Windows Update Error 0x80071a91 - 53FIX  Windows Update Error 0x80071a91 - 70FIX  Windows Update Error 0x80071a91 - 26