Windows update error 0x80071a91 on Server 2019

[x BlueRobot]

Is the SentinelAgent service related to SentinelOne? It may be worthwhile booting into Safe Mode with Networking and then attempting DISM from there, just to see if it runs to completion.

 

[gheil92]

Yes, SentinelAgent is the main service for SentinelOne. I'll try safe mode now.

 

[x BlueRobot]

Okay, please let me know how it goes.

 

[gheil92]

It appears to have failed with the same error. I've uploaded the CBS log that was generated after the run in Safe Mode.

 

[x BlueRobot]

Thanks, could you please open command prompt and enter the following two commands:

ktmutil tm list
ktmutil tx list

 

[gheil92]

C:\Users\Administrator>ktmutil tm list
TmGuid                                 TmLogPath
-------------------------------------- -----------------------------------------
{86720021-329d-11ed-b336-806e6f6e6963} \Device\HarddiskVolume4\$Extend\$RmMetadata\$TxfLog\$TxfLog::KtmLog
{38167328-7583-11ec-b316-000c2998a837} \Device\HarddiskVolume4\Users\xCloudRecovery\AppData\Local\Microsoft\Windows\UsrClass.dat{38167325-7583-11ec-b316-000c2998a837}.TM
{4f9c883d-ee8d-11ec-b323-863be6123dd4} \Device\HarddiskVolume4\Windows\ServiceProfiles\LocalService\NTUSER.DAT{4f9c882f-ee8d-11ec-b323-863be6123dd4}.TM
{3fc8cd3f-34bf-11e9-9bd1-cbaf5644d000} \Device\HarddiskVolume2\$Extend\$RmMetadata\$TxfLog\$TxfLog::KtmLog
{4f9c866b-ee8d-11ec-b323-806e6f6e6963} \SystemRoot\System32\Config\TxR\{4f9c8668-ee8d-11ec-b323-806e6f6e6963}.TM
{f90be773-ee6c-11ec-b324-000c29470a38} \Device\HarddiskVolume4\Users\Administrator\NTUSER.DAT{f90be761-ee6c-11ec-b324-000c29470a38}.TM
{1e187f7e-f937-11eb-b30a-000c2998a837} \Device\HarddiskVolume8\$Extend\$RmMetadata\$TxfLog\$TxfLog::KtmLog
{f90be7a3-ee6c-11ec-b324-000c29470a38} \Device\HarddiskVolume4\Users\Administrator\AppData\Local\Microsoft\Windows\UsrClass.dat{f90be79f-ee6c-11ec-b324-000c29470a38}.TM
{64dab4c4-3365-11ed-b33a-806e6f6e6963}
{d3dc66d8-ee74-11ec-b325-000c29470a42} \Device\HarddiskVolume6\$Extend\$RmMetadata\$TxfLog\$TxfLog::KtmLog
{381671e4-7583-11ec-b316-000c2998a837} \Device\HarddiskVolume4\Users\xCloudRecovery\NTUSER.DAT{1c3790b4-b8ad-11e8-aa21-e41d2d101530}.TM
{4f9c87e4-ee8d-11ec-b323-806e6f6e6963} \Device\HarddiskVolume4\Windows\ServiceProfiles\NetworkService\NTUSER.DAT{4f9c87e0-ee8d-11ec-b323-806e6f6e6963}.TM


C:\Users\Administrator>ktmutil tx list
TxGuid                                 Description
-------------------------------------- -----------------------------------------

Here's the output of those two commands - the second one did output nothing.

 

[x BlueRobot]

Have you tried without Sentinel installed at all?

 

[gheil92]

Looks like it gives me the same 6801 error. The DISM log is attached from that run, if you need it.

 

[x BlueRobot]

Let's make sure there is no transactions pending for NTFS too, please open command prompt and enter the following command:

fsutil transaction list

 

[gheil92]

The output for that is blank, so I assume that means there are no pending transactions?

 

[x BlueRobot]

Yes, it will mean there is none. The only other thing I can suggest is that you attempt a repair install using the Windows 2019 .ISO which is available from the Microsoft Evaluation Centre.

 

[gheil92]

Okay, I will give that a try. Thanks!

 

[x BlueRobot]

Okay, please let me know how it goes. Typically, with this kind error code, clearing the transaction files and then resetting the transaction manager works. I'm not sure why it isn't able to start.