Reports of users are growing about getting the error 0X80071a91 while running windows update. This can get very critical if there are critical updates pending leaving your computer outdated. Error 0x80071a91 directly translates to Transaction support within the specified file system resource manager is not started or was shutdown due to an error. This error is mainly attributed to the choking of the service named File System Resource Manager (FSRM), but there can be other causes to this error, which will be addressed in the following guide.
Solution 1: Reset FSRM
In this method, we will simply reset File System Resource Manager (FSRM), through command prompt.
To do that, press Windows key and type cmd. In the search results, right click on cmd, and choose Run as administrator. In the black command prompt window, type the following command and press Enter:
fsutil resource setautoreset true C:\
Where C: is the drive where your Windows is installed.
After the command runs successfully restart your system and run Windows updates now.
If you get the error again, then move on to the next method.
Solution 2: Deleting Common Log File System (CLFS) transaction logs
Common Log File System (CLFS) transaction logs when are in a corrupt state, they can cause Windows updates to cause this error. We will simply delete them and a fresh copy will be created by Windows again.
To do that, press Windows key and type cmd.
In the search results, right click on cmd, and press Run as administrator.
In the black command prompt window, type the following commands and press Enter after each command:
cd /d %SystemRoot%\System32\SMI\Store\Machine attrib -s -h * del *.blf del *.regtrans-ms
If you get an error that these files are in use, then restart your system and then try. If you still get that these files are in use then download Unlocker from this link . Run the downloaded file and install Unlocker.
Press and hold Windows key and press R. In the run dialog, type %SystemRoot%\System32\SMI\Store\ and press Enter. Right click on the Machine folder and click Unlocker. If it is in use, then click Unlock All.
Now try the commands above to delete the files.
Restart your system at the end and check if the issue’s gone. If not, move to next solution.
Solution 3: Run Windows Update Troubleshooter
Go to this link http://go.microsoft.com/?linkid=9830262.
The troubleshooter will download and if you can Run/Open it then directly click Run/Open otherwise download and then run it.
Click Windows update in the troubleshooter window and click next.
It will automatically detect and fix errors it finds.
Restart your system and check if the error’s gone.
If not, move on to the next solution.
Solution 4: Restart Windows Update Services
BITS service, the Windows Update service, and the Cryptographic service are the services MSI Installer involved in Windows update. Anyone of them can be individually malfunctioning and can cause this error. But we will restart them all to remove any doubt. Click here to download the windowsupdateservices.bat file, right click on it and choose run as administrator.
If the update script opens as a text file, save it as .bat; then right click and choose run as administrator, or copy paste the commands and paste them in command prompt (admin)
Solution 5: Reregister Windows update files
In this step we will reregister the BITS files and the Windows Update files. Click here to download the windows reg update, right click on it and choose Run As Administrator.
Solution 6: Rename Corrupt Update Stores
Sometimes, previously failed updates can also trigger this error. It would be best to rename the old stores, so windows can re-attempt updates in a fresh/clean folder.
To do this, Press the Windows key to open Start (Search) and type cmd.
In the search results, right click on cmd, and choose Run As Administrator
In the black command prompt window, type the following commands and press Enter after each command:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
Where C: is the drive where you have installed Windows.
Now restart and check if the issue is resolved.
