Windows Update failure 0x80071a91

patrickwilson2024 · Mar 21, 2024

Hello,

Windows Updates keep failing for my Server 2019 installation with the above error code. When I run sfc /scannow I get the following:
Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

I have tried a DISM repair from and ISO image. That did not work.

Ran another DISM /Online repair

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.5122

[===========================90.8%==================== ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Please see attached files. Thanks.

Gary R · Mar 21, 2024

Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
The file will likely be too large to upload here, if so please upload to a file sharing service.
Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file

patrickwilson2024 · Mar 21, 2024

Here it is. Thanks!

Gary R · Mar 21, 2024

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

Download SFCFix.exe and save it to your desktop.
Download the attachment SFCFix.zip and also save it on your desktop.
Save any work you have open, and close all programs.
Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

SFCFix will launch, let it complete.
Once done, a file will appear on your desktop, called SFCFix.txt
Open the file, then copy and paste its content in your next reply.

Next ...

Click Search button and type Command Prompt
From the results, right click on the Command Prompt icon, and select Run as administrator
A Command Window will open.
Copy paste the command below into it, then press Enter
Dism /Online /Cleanup-Image /RestoreHealth
Once DISM has finished running ...
- Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
If the file is too large, upload it to a file sharing service, and post me the link.
Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Gary R · Mar 27, 2024

It's been 6 days since I last posted, and no reply from you.

Do you still need my help ?

If I don't hear back from you within 24 hours, I will presume not, and will close this topic.

patrickwilson2024 · Mar 27, 2024

Yes, I still need help. I have not had a chance to try the next step yet. Can you please keep this open until the end of next week? I am leaving on vacation and won't be able to proceed with this until then. Thanks.

Gary R · Mar 27, 2024

Yes, no problem. Thanks for letting me know.

The problem we have here is that there are a lot of people needing help, and very few trained helpers to help them, so if we're helping one person then we can't be helping another. So if someone doesn't reply promptly then we're in a quandary. We can't pick up a new topic (because there's only so many people you can help in the time you have available) in case the person who hasn't replied suddenly decides to reply.

Now as long as I know you're not going to reply for another week, then that's not a problem, but if I don't know, then it is.

Hope that makes sense.

patrickwilson2024 · Apr 5, 2024

Hello,

Please keep this ticket open for another week so that I can get approval from my team to proceed with the next step of this procedure. Thank you.

Gary R · Apr 5, 2024

OK, no problem.

After that I think we're going to have to consider closing the topic since it won't be progressing in any realistic sort of timeframe.

patrickwilson2024 · Apr 8, 2024

SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-04-08 19:55:59.839
Microsoft Windows Server 10 Build 17763 - amd64
Using .zip script file at C:\Users\administrator\Desktop\SFCFix.zip [0]

PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft.windows.s..ermanager.rdsplugin_31bf3856ad364e35_10.0.17763.1_none_b28097a6427ccb94\RemoteDesktop.Events.xml

Successfully copied file C:\Users\rea.tech13\AppData\Local\niemiro\Archive\amd64_microsoft.windows.s..ermanager.rdsplugin_31bf3856ad364e35_10.0.17763.1_none_b28097a6427ccb94\RemoteDesktop.Events.xml to C:\Windows\WinSxS\amd64_microsoft.windows.s..ermanager.rdsplugin_31bf3856ad364e35_10.0.17763.1_none_b28097a6427ccb94\RemoteDesktop.Events.xml.

Successfully restored ownership for C:\Windows\WinSxS\amd64_microsoft.windows.s..ermanager.rdsplugin_31bf3856ad364e35_10.0.17763.1_none_b28097a6427ccb94\RemoteDesktop.Events.xml
Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft.windows.s..ermanager.rdsplugin_31bf3856ad364e35_10.0.17763.1_none_b28097a6427ccb94\RemoteDesktop.Events.xml
PowerCopy:: directive completed successfully.

Successfully processed all directives.

Failed to generate a complete zip file. Upload aborted.

SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2024-04-08 20:00:23.017
Script hash: GGw7Yi7xE0ejogf42Jhcv98pi0CV0wJTaWp7oeriVZs=
----------------------EOF-----------------------

I ran the DISM online repair and this was the result.

I tried running fsutil resource setautoreset true c:\ and restarted the server. Ran the dism repair again and got the same result. I'm uploading the cbs.log. But I'm guessing that won't do any good since the DISM did not complete. Any further suggestions would be appreciated.

Gary R · Apr 9, 2024

Please open an elevated Command prompt and enter the following command ....

fsutil resource setautoreset true %SystemDrive%\

.... then try once more to run ....

Dism /Online /Cleanup-Image /RestoreHealth

.... if successful please post me the CBS.log created after DISM has completed.

If unsuccessful, please try the above instructions again. Sometimes it takes more than one run to resolve things.

If still unsuccessful please let me know.

patrickwilson2024 · Apr 9, 2024

I tried the fsutil command you provided and the dism /online twice. Still receiving the same error as before.

Gary R · Apr 10, 2024

OK, can you please post me your latest CBS.log so I can see if anything at all has changed since last time, after what we've done.

Can you also see if you have a logfile(s) in the following location ....

C:\Windows\System32\Config\TxR\*. Windows Update

... and if so, please post it/them.

patrickwilson2024 · Apr 10, 2024

I have attached the latest cbs.log file. There is no logfile in the other location you asked about.

Gary R · Apr 10, 2024

OK, thanks. Looking over your latest log now.

Just so you know ..... the fault you have .... STATUS_RM_NOT_ACTIVE .... ERROR_RM_NOT_ACTIVE ... is a difficult one to resolve, and we have had problems with some iterations of this fault, so there's probably about a 50/50 chance of having a successful result.

So. that being said, can you please do the following ....

In a Search window type Run and click on the icon in the search results to open a Run window.
in the Open: box type Services.msc and then click OK to open a Services window.
Scroll down the listed services to Windows Modules Installer and double click on it to open its properties window.
Set Startup type to Auto and click OK

Now Restart your computer. (This is important)

Next ...

In an elevated Command window please enter the following commands one at a time, and hit enter after each ....

fsutil resource setautoreset true %SystemDrive%\

attrib -r -s -h %SystemRoot%\System32\Config\TxR\*
del %SystemRoot%\System32\Config\TxR\*

attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\*
del %SystemRoot%\System32\SMI\Store\Machine\*.tm*
del %SystemRoot%\System32\SMI\Store\Machine\*.blf
del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms

Next ...

Now Restart your computer. (This is important)

Next ...

Try updating your computer.

If successful please let me know.

If not, please post the CBS.log created after your update attempt.

patrickwilson2024 · Apr 11, 2024

Thank you for the reply. I will try this on Monday evening and update you with my results then.

patrickwilson2024 · Apr 15, 2024

Gary,

Please see below. Thanks.

Gary R · Apr 16, 2024

Going to have to consult on this with my colleagues, may take a while. I'll get back to you ASAP, but don't at this point know when that might be.

Gary R · Apr 16, 2024

OK, can you please do the following .....

Download FRST64 to your Desktop.

Download the attached fixlist.txt and save it to the same location as FRST (must be in same folder or it won't process).
NOTICE: This script was written specifically for this user. Running it on another machine may cause damage to your operating system
Start and run FRST
Now press the Fix button once and wait.
FRST will process fixlist.txt
When finished, it will produce a log fixlog.txt in the same folder/directory as FRST64.exe
Please post me the log

patrickwilson2024 · Apr 16, 2024

Gary R said:
OK, can you please do the following .....

Download FRST64 to your Desktop.

Download the attached fixlist.txt and save it to the same location as FRST (must be in same folder or it won't process).

NOTICE: This script was written specifically for this user. Running it on another machine may cause damage to your operating system

Start and run FRST

Now press the Fix button once and wait.

FRST will process fixlist.txt

When finished, it will produce a log fixlog.txt in the same folder/directory as FRST64.exe

Please post me the log

Thanks. I will try this Weds evening and post the results.

Windows Update failure 0x80071a91

Member

Attachments

Forum Moderator, Security Analyst, Windows Update Analyst

Member

Attachments

Forum Moderator, Security Analyst, Windows Update Analyst

Attachments

Forum Moderator, Security Analyst, Windows Update Analyst

Member

Forum Moderator, Security Analyst, Windows Update Analyst

Member

Forum Moderator, Security Analyst, Windows Update Analyst

Member

Attachments

Forum Moderator, Security Analyst, Windows Update Analyst

Member

Forum Moderator, Security Analyst, Windows Update Analyst

Member

Attachments

Forum Moderator, Security Analyst, Windows Update Analyst

Member

Member

Forum Moderator, Security Analyst, Windows Update Analyst

Forum Moderator, Security Analyst, Windows Update Analyst

Attachments

Member